[George Dean]

Renato, as far as I’m aware there is no way to turn it off. If someone else knows I’m all ears!

Increasing the height of the track may help provide more area for the mouse pointer to grab and avoid hitting the opacity line, but that comes with other problems like taking up too much real estate on multi track projects.

On the other hand, my feeble memory thinks I once read a user came up with a work around, but I didn’t follow up on it and cannot find the link. Could it be my memory is playing tricks (very possible), or perhaps someone will have a solution!

Best Regards……George

[George Dean]

Hi Sam,

“I don’t mind going through menu’s to find something, but if you know where it is, why keep it from us…?”

Well, I’m not David, but following this thread, it appears you are being a bit rude! The OP question wasn’t about keyboard or menu commands, he was just mentioning it, so why would he unnecessarily include it? If you don’t mind looking in the manual, what is the big beef? But to prevent a war, Ctrl+F if you are on Windows.

And, he answer the OP in his reply!

Best Regards……George

[George Dean]

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

Best Regards……George

[George Dean]

Hi Francois,

Actually I did reproduce his complaint, which was why the latest builds of VP16 when using no GPU acceleration, had a slower playback than previous version when running in 32 bit floating point full range. My system will not run this at full speed in any preview quality, and the difference for me is about 2-3 frames per second slower playback than when using VP15.

The side difference, being the reason Wilfried increases his Dynamic RAM to 32 gb and runs without GPU acceleration is the stoppage issues he has encounter, and this is what I cannot duplicate on my box and VP16 build 361. However, like I stated previously, his projects are mostly much more demanding on resources and much larger than I have.

Best Regards……George

[George Dean]

I think I have reached the outer limits of my shallow knowledge on this subject! Perhaps the Master Display refers to a calibrated color display as it has custom settings, but that is an off the wall guess!! I pecked around a bit and could not find anything about it. There is nothing about it in the Vegas Help, but then Vegas Pro 16 Help has many references which have not been updated since VP15 and certainly anything in a recent build is not going to be there.

My primary NLE is DaVinci Resolve (now on version 16b1) which runs as a default in floating point and 10 bit, much smoother than Vegas, but in Vegas Pro I’m not experiencing the issues you have with Dynamic RAM settings and the program stopping, which could be the difference between your M5000 and my little R9 390, as well as, your project is most likely much larger and more complex than my projects.

The few times I have worked in 32 bit Floating point full range I have set Vegas to 8 bit for the cutting and editing, certain FX’s, then switched it over to floating point for the color management/corrections, but again those were more or less experimenting and not a real lengthy projects.

Best Regards……George

[George Dean]

Hi Wilfried,

Ah, you are working in 32 bit floating point full range, that is a different beast, I was testing in 8 bit.

So my first question, just out of curiosity is….why are you working in 32 bit float point full?

Also, why are you using CPU only?

Secondly, when in 32 bit floating point full range, I get similar results as you, slower preview speeds in MVP16/361 than MVP15. Not by much just a couple fps. However my little system will not run anything in 32 bit floating point full range at full preview speed!

Best Regards……George

[George Dean]

Hi Wilfried,

If I understand you, I can not get the same results. Actually I get somewhat opposite results. My comparison were on the same box, using MVP15 build 416, and MVP16 build 361 (with a short test using SVP13 build 453).

I used a .m2t (HDV) clip from a Canon XL2 captured with SVP13, a DNxHD 220x (UHD) .mov and a ProRes HQ (UHD) .mov, all 29.970 fps for comparison.

I monitored CPU percentage usage with Windows 10 Task Manager.

MVP15 m2t 5.5% CPU 29.970i fps preview quality Best/Full
MVP16 m2t 13.3% CPU 29.970i fps preview quality Best/Full

MVP15 DNxHD UHD 28% CPU 14 fps preview quality Best/Full
MVP16 DNxHD UHD 42% CPU 14 fps preview quality Best/Full

MVP15 DNxHD UHD proxy 28% CPU 29.970 fps preview quality Preview/Full
MVP16 DNxHD UHD proxy 51% CPU 29.970 fps preview quality Preview/Full

MVP15 ProRes UHD proxy 29% CPU 29.970 fps preview quality Preview/Full
MVP16 ProRes UHD proxy 52% CPU 29.970 fps preview quality Preview/Full

There is zero difference between the MVP15 and MVP16 in playback preview fps, and more percentage of the CPU being used by MVP16 build 361 than MVP15 build 416 and SVP13 build 453.

All my project setting were identical for this comparison. The only difference between the three is the plugin used to decode the ProRes HQ UHD, as SVP13 used qt7plug and MVP15/16 use mxhevcplug, however preview playback and CPU percentage used followed the same pattern, no difference in playback, but MVP16/361 using a shown higher percentage of CPU.

Best Regards……George

[George Dean]

Josh, how about this…..

https://www.softpedia.com/get/Multimedia/Video/Other-VIDEO-Tools/svdts.shtml

Best Regards……George

[George Dean]

Josh, what version of Vegas Pro are you using?

Best Regards……George

[George Dean]

An alternative to a full reset of Vegas, which does reset all the settings back to their original installation defaults is….

Try this….. https://www.sonyvegas.co.uk/clear-plug-cache/

Best Regards……George