It's clearly not identical as NVENC renders finish now.
Regardless as you even stated this version was supposed to be an "overhaul" and improvement for "dynamic ram". But it seems to be identical. It shouldn't effect a render period no matter what amount its set at. And its Cleary somehow still linked up with poor coding.
@Longslander
You should open a thread of your own - exploring the problems your PC is clearly having - instead of bashing other threads.
I got distorted frames in rendered video when I increased the Dynamic RAM Preview in VP19.
So for me the behaviour is exactly as it used to be in previous versions.
I've recently noted dynamic ram renders are affected by the quality of the video preview that is set. I.e., and especially with 4K footage, setting video preview quality to "preview full" rather than "best full" results in a much faster ram render and still of sufficient quality to make edit decisions.
I've always used dynamic ram preview as I've never personally had a problem with rendering my projects, but now I'm confused. I have footage from my 2.7K Mavic mini that can be a little glitchy on my timeline with DRP set to 0 but if I enable DRP it plays smooth at full 25fps. But I found the complete opposite to be true with the SampleProject 4K. With DRP set to 0 it plays the loop region at around 4fps, but if I enable DRP and allocate any amount of RAM, large or small, it drops to 1.4fps.
the SampleProject 4K. With DRP set to 0 it plays the loop region at around 4fps, but if I enable DRP and allocate any amount of RAM, large or small, it drops to 1.4fps.
@Vincent-Brice Vegas will crash with ram preview set to 0, at 10% it works fine, which also shouldn't be the case, and I don't believe I've ever seen that behavior until I tested now. It's like there's an instability with Vegas, the slightest things change, be it windows updates or driver updates and it works differently.
(2nd half of video is where dynamic ram preview is set to 0)
@Former user This is interesting. You have already been helping me with my constant crashing, and the only thing I found to stop it has been to enable Legacy AVC decoding. I did try to "turn GPU decoding off, but keep using Magix decoder (sO4)" as you said but it still crashed. BUT, without enabling Legacy AVC decoder on the SampleProject 4K and and DRP set to 0%, it ran the loop region for ages without a crash. I think it would have gone on all day!! I did try to screen record it, as you did above, to show how the frame rate more than doubles when I set DRP to 0%, but screen capture doesn't work for me. It picks up my video camera (excuse the mugshot) but not my screens. I'll have to search the forum for that now too!
This is interesting. You have already been helping me with my constant crashing, and the only thing I found to stop it has been to enable Legacy AVC decoding. I did try to "turn GPU decoding off, but keep using Magix decoder (sO4)" as you said but it still crashed. BUT, without enabling Legacy AVC decoder on the SampleProject 4K and and DRP set to 0%, it ran the loop region for ages without a crash. I think it would have gone on all day!! I did try to screen record it, as you did above, to show how the frame rate more than doubles when I set DRP to 0%, but screen capture doesn't work for me. It picks up my video camera (excuse the mugshot) but not my screens. I'll have to search the forum for that now too!
Vincent, maybe I missed it if it was in another thread, but what is the GPU decoder in use? There could be an issue with certain GPUs and the Vegas decoding, as well as the timeline preview x DRP. I use Intel and haven't had many issues but NVDEC has well documented problems (which Todd has reported on himself). GPU drivers are another factor- in general, try to stay up to date with them.
If you wouldn't mind adding your system specs to your signature it would help understand what hardware you are using.
@RogerS Haha, it was your own words: "The difference between 13 and 19 is that 19 uses the GPU to decode media. Sometimes this doesn't work as well as you'd hope." So I enabled Legacy AVC decoding and this has been the only thing I have found to stop Vegas 19 crashing constantly. (Oh, and when I tried my old Radeon R9 380 GPU and with Legacy AVC decoder disabled, unchecked, it didn't crash then either). So I'm thinking it's just a problem with my RX 5500 XT, do you think? (Windows and drivers up to date, even tried pro drivers, but no difference). I've done as you suggest and put my spec in my signature. Many thanks, Vince
Sorry, I have trouble keeping track on who I have spoken to and in what context here.
But yes, depending on the GPU and media it doesn't always work stably. I'm on Intel now so have a positive experience with GPU decoding (stable and faster) but when I used the NVDIA decoding experienced my share of crashes (and couldn't figure out why for a while).
Not sure if it will help you but here a user found benefits from AMD driver 22.5.1 vs 22.5.2. The thread also had advice for totally clearing away old drivers for when you upgrade GPUs as Vegas can get confused.
Yeah, trying 22.5.2 was out of desperation, nothing else was working, ancient drivers, pro drivers, nothing. I did a wipe and clean install of windows and Vegas and it was crashing from the word go.
Anyone notice that increasing value for dynamic ram preview actually increases the amount of VRAM used by GPU, not only increases the amount of system ram allowed for Dynamic Ram Preview? I don't think this feature has been adequately explained. Also is it using extra VRAM or just reserving it.
In this video start with 20%(of 32gig ram), then 10%,5%,0%, Vram use changes with each percentage.
It uses both systemRAM and VRAM very efficiently.
I give 16GB (25%) to my dynamicRAM, my graphic card has 16GB VRAM.
The playback for preview uses VRAM ca. to 12GB, by editing it raises to 14GB and above as I observed.
Vegas has crashed on me for years - since v12, and now v19. Sometimes a lockup, and sometimes trapped so the dialog box pops up. I admit that it is putting me off using it, which is a shame.
But what I don't understand is why the code cannot be enhanced to handle unexpected situations. Every processing thread should be wrapped with a timeout or similar, so the system does not lockup under any situation.
As for DRP, I don't really understand it. I just want to get a project done without needing to fiddle with such settings. And scanning forums and YouTube for ways to stop crashes.
UPDATE: I had set DRP to 5% memory (on my 16Gb laptop). It has Intel iRIS GPU, with regularly updated drivers. But one particular project using .gif masks with Source Alpha compositing mode would always lock up. Set the DRP to 0 - and now it edits throughout without any hanging.
When it does 'hang' (rather than the detected fault that pops-up a dialog) - how can we report this back to Vegas so they can identify the root cause, and hopefully improve the software for everyone?
@merlin-beedell It's so funny the variations that ones experience. I have only just upgraded to 19 having been using Sony Vegas 13.0 since early 2016 and for me 13 was so stable. I can honestly say that the ONLY time in crashed was when applying two built in FX, so I never used them, and on rare occasions when applying stabilization. If that did happen, then I could not use stabilization on that particular sub-clip, it was that predictable. And that was true for my i7, that it was originally on, and then my current Ryzen 9. And it also survived the upgrade to Windows 11 no problem. I only upgraded to 19 recently because I thought I needed HEVC support for a GoPro hero 10, but for me 19 crashes constantly. I have tried every recommendation offered so far but none has worked so I have now contacted support. I notice that if anyone moans about Vegas they get criticised. I'm only a hobbyist taking family and travel videos but if anyone uses this for work, then I must admit, I can feel their frustration. I love Vegas and just hope I can find what is causing the crashing and that you can too ;)