Vegas Pro 16 stupidly slow?

[Aaron Star]

When you open your CMD prompt, you need to right click on the CMD icon and choose “Run as Administrator.” Otherwise the WinSAT command will just open a window and close before you can read the results.

You can output the results to a txt file with by adding >results.txt to the end of the command. You should change director to your desktop before outputting the results file, this will make it easier to find the text file.

[Martin Stanesby]

Hi Aaron,

Thanks for the tip. I’ve copied the info return below.

> CPU LZW Compression 704.36 MB/s
> CPU AES256 Encryption 3272.97 MB/s
> CPU Vista Compression 1847.76 MB/s
> CPU SHA1 Hash 1798.31 MB/s
> Uniproc CPU LZW Compression 115.28 MB/s
> Uniproc CPU AES256 Encryption 422.04 MB/s
> Uniproc CPU Vista Compression 344.59 MB/s
> Uniproc CPU SHA1 Hash 464.76 MB/s
> Memory Performance 17268.80 MB/s
> Direct3D Batch Performance 42.00 F/s
> Direct3D Alpha Blend Performance 42.00 F/s
> Direct3D ALU Performance 42.00 F/s
> Direct3D Texture Load Performance 42.00 F/s
> Direct3D Batch Performance 42.00 F/s
> Direct3D Alpha Blend Performance 42.00 F/s
> Direct3D ALU Performance 42.00 F/s
> Direct3D Texture Load Performance 42.00 F/s
> Direct3D Geometry Performance 42.00 F/s
> Direct3D Geometry Performance 42.00 F/s
> Direct3D Constant Buffer Performance 42.00 F/s
> Video Memory Throughput 7437.08 MB/s
> Dshow Video Encode Time 0.00000 s
> Dshow Video Decode Time 0.00000 s
> Media Foundation Decode Time 0.00000 s
> Disk Sequential 64.0 Read 362.97 MB/s 7.9
> Disk Random 16.0 Read 293.39 MB/s 8.1

Thanks for your help.

Martin

[Aaron Star]

“I’m running Windows 10 64 bit, 16GB ram, GeForce GTX 860M (but have tried disabling this), i7-4710HQ 2.50ghz.” – but your winsat results do not show the MX860M in the results, the results show Intel. There might be something strange with the way your hardware drivers are loading on that laptop.

Also you have 17GB/s of memory bandwidth but only 7GB/s of video memory bandwidth, this seems really low. Since your test seemed to be using the Intel display chip that uses your RAM and not dedicated video memory, I would have thought this would be more on par.

Is your source media on the internal drive or external?

Is your Vegas project an old file from another version, or was it created in Vegas 16?

Are you running any 3rd party plugins or FX in your project?

What is the source media type in the project?

Have you contacted Magix support about this?

[Martin Stanesby]

Hi Aaron,
Yes my laptop has dual graphics, and you cannot disable Intel from controlling the display as dedicated graphics. However, my NVIDIA graphics are set in properties for certain applications and so it is presumed it kicks in when Vegas launches.

I’m wondering if those results returned also show the Intel video memory which is a lot lower than the nvidia one? Unfortunately I cannot gain access to advanced options in bios to tweak video memory.

To answer your other questions…..

I’m not using external drives. Source media is on internal drive.

The Vegas projects are both ones created within Vegas 16 and ones upgraded from Vegas 15. The slow issue was also evident in Vegas 15 anyhow.

Yes i am running a few third party plugins. I don’t think any were added just before the issue arose. But I will check.

The source media is .mp4.

I have contacted Magic support and waiting on a response.

Thanks
Martin