Auto DRAM rendering when editing

pierre-k wrote on 8/5/2021, 3:56 AM

What do you think about it?

If someone has 64GB of ram, they could assign three-quarters of the capacity to this feature. Sometimes, when editing, I get stuck on a section and gradually fine-tune it. Constantly using shift + b shortcuts and waiting to be rendered is annoying.

My idea is to mark a section to be automatically rendered in DRAM. And I can work in peace and I don't have to keep playing this section all the time until it plays smoothly after the fifth play. In preview half, DRAM Shift + b is incredibly fast. Why not make it automatic and in the background?

Are you experimental and optional for this feature?

Comments

RogerS wrote on 8/5/2021, 3:58 AM

A bigger playback buffer would be great and it would be good if it's done in the background without user input. Add to the feature request thread? https://www.vegascreativesoftware.info/us/forum/vegas-pro-19-feature-requests--123432/?page=12#ca814442

pierre-k wrote on 8/5/2021, 4:31 AM

I believe that most dissatisfied users will stop complaining why the video is not smooth.

VEGASDerek wrote on 8/5/2021, 8:02 AM

This is definitely something we a looking at for the future, but first thing we need to do is fix up our prerender and dynamic RAM architecture which is not working properly at the moment.

pierre-k wrote on 8/5/2021, 9:11 AM

dynamic RAM architecture which is not working properly at the moment.

I like your approach. You openly admit that something is not working in Vegas. This strategy is fair and users understand such a language.

wilvan wrote on 8/5/2021, 3:11 PM

This is definitely something we a looking at for the future, but first thing we need to do is fix up our prerender and dynamic RAM architecture which is not working properly at the moment.

Indeed , should have been fixed already as a priority , prior to screen capture and stock film additions and AI color black-and white old film 😉 . Am still using the sony's 12-13 versions here once and a while for quick simple editing work and works just great with 32 GB of DR ( out of 128 GB ) BUT with GPU=OFF .

Automatic DR rendering I did NOT like at all since it was taking HUGE background resources non-stop and in parts I was not at all previewing and editing and slowed down the part I needed to be fast . This gets even worse on a , for example , 2 hour long timeline .That was with fusion on my pretty powerfull HP Z840 ( see my profile ) and had to disable that automatic DR rendering . Am only interested in fast preview on that part I am editing actually .

Sony  PXW-FX9 and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2025
Adobe After Effects CC 2025 & Adobe Media Encoder CC 2025
Avid Media Composer 2024.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

pierre-k wrote on 8/5/2021, 3:20 PM

Ideally, the DRAM should automatically render only the area where the playhead is. If we are editing something in the middle of an hour-long film, then we do not necessarily need to have the first half hour in DRAM and wait until it counts to the place we need.

Yes I agree. Ai generally has such poor results, especially in coloring, that this innovation is the last thing that interests users.

pierre-k wrote on 8/5/2021, 3:34 PM

And to make it even more complicated, only places where gpu and cpu are not enough would be stored in DRAM. When the software detects that the playhead is approaching a point that the gpu will not tighten, it will start pre-saving.

If everything is saved automatically in DRAM, then we probably don't need gpu.

Don't know exactly how DRAM works in premiere and davinci?

wilvan wrote on 8/6/2021, 12:05 AM

When they would ever consider implementing automatic DR rendering in the future , there should certainly be a ON/OFF switch for that function meaning ON=automatically and OFF = manually ( user defined timeline region ) and stop limiting the DR settings to 32 GB when there is real workstations in the market for a pretty long time now which allow for 256 GB of RAM and more . ( when U call it "pro" , it should be " pro " 😉 )

Sony  PXW-FX9 and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2025
Adobe After Effects CC 2025 & Adobe Media Encoder CC 2025
Avid Media Composer 2024.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )