Vegas Pro 16 builds later than 307 – CPU power for previewing is lost

[Francois Pénzes]

Hi George

After reading your last post, I was trying to wrap my head around this since it worked for me and after going thru all of my settings, I noticed that I had accidentally changed the Dynamic RAM Preview max to 128MB. I can now preview in Best(Full) with no stuttering even with some FX applied. Go figure. Wish I could rationalize this…and had found about this a long time ago. I guess that’s why everything was working fine for me.

If some tech wizard is reading this, an explanation would be most welcome.

Cheers !

PC Win 10 Pro 64-bit 16gb Intel® Core™i7-2600k Quad Core 3.40GHz
Cameras: Canon XF305 + Canon XH-A1
Blackmagic HyperDeck Studio Mini
Vegas Pro 16, User since Vegas 3.0

\’\’When the cutting stops, the editing begins…\’\’

[George Dean]

Francois, are you working in 32 bit floating point full range and getting best/full?

Best Regards……George

[Francois Pénzes]

Hi George

Yes I was at 32 bit Floating Point Full Range…. but…..

I was at colleagues place when I did the testing and he told me 2 days after that he had changed his system to something a bit beefed up after I tried it on my system and couldn’t reproduce my previous results. He’s running an i9 (4.4Ghz) with NVMe SSDs , plus a hole bunch of crazy over the top stuff.

Seriously thinking of getting one of those !!

Cheers !

PC Win 10 Pro 64-bit 16gb Intel® Core™i7-2600k Quad Core 3.40GHz
Cameras: Canon XF305 + Canon XH-A1
Blackmagic HyperDeck Studio Mini
Vegas Pro 16, User since Vegas 3.0

\’\’When the cutting stops, the editing begins…\’\’

[George Dean]

Francois,

That sounds like a beast of a machine. If I were not retired and did not have so many other budget busting activities, I would probably have that or some type of workstation, but for now my little box is doing what I need it to do. Good luck in the future, it would make sense for the workflow you are in to upgrade to something you know will work.

Best Regards……George