running on my internal laptop HD(lol) with a mild amount of slices and fades. Looking at process explorer, this Vegas project uses only ~ 600 MB, so taking into consideration that Vegas is a bigger app to start with and probably has some buffering enabled by default (didn't check) I definately suspect there's something going on with Reaper's high RAM use. Of course I don't get all the Reaper specific stuff there (lanes, crossfades) but all Audio items are imported and the project plays as it should. I converted the Reaper project with AA translator into a Vegas project and opened it in Vegas. Is the RAM use normal and expected or is there something strange going on ? In case anyone wonders, I started this project with the 3 GB switch enabled which worked, but I've read in this forum that this can cause other problems (ie with some plugins), so I did this test with the standard Windows boot (no 3 GB switch). Here's what Reaper looks like (using default theme, click to enlarge): Even with buffering disabled and FX loaded offline I get massive GUI glitches and and after a short time the project crashes. I wonder why Reaper takes so much RAM, being on WIN XP (having 4 gigs installed and recognized by Windows) I cannot run this project properly. If this helps, the tracks in this project contain usually two or three lanes and lots of small Audio snippets, usually crossfaded. Reaper allocates 1,6 GB RAM loading the barebones project, ie just the Audio items. Note that for this test I disabled buffering completely (set Media buffer size to 0 ms in preferences) prior to loading and checked the "Open with FX offline (recovery mode)" tickbox in the loading dialog. I was curious so I left process explorer ( ) running while opening the project. (50 tracks in total, ~ 35 audio tracks, rest is busses and Aux, no VSTi's, just FX). I'm currently having trouble running a bigger Reaper project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |