When rendering it crashes cause it uses 32GB up, but doesnt see my rest 32GB.... What to do?
@Kloverton - Are you expecting to see VP17 using more than 32Gb? How much more?
Preference - Video
It doesn't matter how much more, if i'm getting a message about system being low on memory, and task manager show only 46% of RAM usage, what is about 32GB of ram, those are the questions to VP, why its not using rest 32GB
Former user
wrote on 10/2/2019, 9:15 PM
Low on memory could also refer to a harddrive, such as your temp drive.
When rendering it crashes cause it uses 32GB up, but doesnt see my rest 32GB.... What to do?
@Kloverton - Are you expecting to see VP17 using more than 32Gb? How much more?
Preference - Video
It doesn't matter how much more, if i'm getting a message about system being low on memory, and task manager show only 46% of RAM usage, what is about 32GB of ram, those are the questions to VP, why its not using rest 32GB
Possible partial explanation: VP 17 (well reported bug) leaves residue as per still active in the Task Manager list after you close the program, or it crashes...so, if that has occurred, upon opening again, you are then double hitting the resources without knowing it, that is but one possible explanation.This is my Task Manager after closing Vegas, still showing as active, using 3 Gb RAM:
That "residue" program will also effect your using something like a MIDI linked hardware controller, the residue file is active and won't release the MIDI ports and so if you open Vegas again, no controller will be available, just a FYI for those reading about this.
If that has occurred, you need to "right clik" on vegas in TM list and "end process."
More likely:
You won't see Vegas showing any RAM allocations above 32 gigs, because, well, it's Vegas, an old program, even if that is available on your system, I, myself, went from 32 to 64 and saw no real improvement in Vegas
The ONLY place one can tell Vegas how much RAM to use, for anything, is in the Ram Allocation window under the Video tab in Preferences.
. It has a 32 G Max. You really don't get that much benefit, IMHO, of utilizing RAM preview (I'm thinking this is to what you are referring) for anything extending that long, and besides, if you allocate anything to RAM preview, then that RAM is no longer available to the program or operating system more generally. I don't know if that extends to when you render. I'm using about 8 G, there is a sweet spot, depending on how much RAM one has, but I'm not sure what that is, 8 seems to work for me pretty well.
Now, Vegas doesn't use that sort of RAM anyway, (I wish it did, unless in specific tasks, certain fx programmed for that, but I've not seen that. I maybe missing something, someone else chime in..) as I've said, and these "running low on memory" warnings are not hampering me, I can go ahead and keep running, so I think it's a glitch....especially with 64 G...it likely is a misread, or some side application, or a double instance of Vegas open, but, more likely, a glitch.
I hope that helps. Not entirely scientific, but this is just how Vegas works per my experience.
Not entirely scientific, but this is just how Vegas works per my experience.
@zdogg - Any RAM set in that TAB is purley for increasing the building of RAM Previews. Period! Now, taking this away from the PC RAM Resources will ultimately, has to impinge on the actual workings of the PC System. You want that to happen? I'm guessing that's a "No"? So, find your own sweetspot to work with and carry on. These discussions have been going on since "The Dawn of Time", and most likely before that.
Previewing: For slick Previewing, I now inevitably use WAAG's fabulous KwikPreview - marvellous. I have it sitting on my Toolbar.
Thanks again WAGGLE!
Rendering: I make sure I have that new I/O Tab in Prefs looking for my nVidia Card AND GPU Accel ON.
It doesn't matter how much more, if i'm getting a message about system being low on memory, and task manager show only 46% of RAM usage, what is about 32GB of ram, those are the questions to VP, why its not using rest 32GB
What about your Dynamic RAM setting? How much are allocated to him?
Like @Former user said
Low on memory could also refer to a harddrive, such as your temp drive.
What about your HDD/SSD free space? A screenshot that shows your error would be welcome.
Grazie, in case you're misreading my "gist" here, I know all about the RAM allocation, I say - explicitly - in trying to be helpful to others, that this is the ONLY place you get to "tell" Vegas anything about RAM allocation and it is for that task: i.e., preview, ONLY, and it will "reserve" that from being utilized more generally. Do we agree that we agree??
I don't think you read my succinct but complete response, in which I delineate that I have 64 G RAM and Most of that is not being used, per the program more generally, and so 8 G Preview is not "huge" RAM preview buffer,in my case, nor in hers, ALTHOUGH, (caveat alert!!) for HER, she's using bigger files, I'm not using 4-8k files at the moment, so that may change her "sweet spot" on the RAM preview set aside That's simply IMHO, per my experience with Vegas which is probably about as long as yours, VERY LONG (Sonic Foundry Vegas 3, Pre Sony, ring a bell?)
That said, thanks for the WAGG tip,
ARE WE OK? Do you approve??? ahahahah THANKS Paisano!!
I have seen something similar on my machine. under normal operation VP will never use more than 50% total RAM. However, render with nVidia and 'dynamic RAM'=value xxx, you see ram creeping up in the task manager. this can eventually crash the system 'out of resources'.
Turn 'dynamic ram'=0 fixed my problem. i guess this is a bug.
@K.G_Media That ram limit has to do with buffering output for preview. I think it's only of significance if you have a video board that cannot keep up. If you have a fast modern video board, however, it's probably way faster slapping up the preview than Vegas is in processing it. If your ram is on the slow side, a preview buffer can be a detriment. Some folks set it to 0 and get better preview performance.