Playing
- with Preview setting?
- on which screen?

Preview setting PREVIEW FULL

Which screen?

Which screen?

Main screen, Second screen?

Which screen?

Main screen, Second screen?

 

It is not important

Project UHD, please.

My results on your asked options on laptop from signature.
I / O off

I / O Quicks UHD 630 

I / O Nvidia

I get my best results on Vegas installation default I/O with Preview Best>Auto

Thank you.

So you only get the best results with the CPU i7-10875H processor?

I think so because these are the default settings on the laptop for File I/O,

By default, you have an internal gpu from the intel. But you would get the best results with I / O off with the best auto. Not with the default settings as you wrote in the previous post. No?

On my last picture you see what for me and my goals the best option is and that are default Vegas settings with on my preview screen the setting Preview Best>Auto.
That's the reason I asked you wich preview settings you prefered for this test.

Can you please still tell me which card you have set in the video tab? Does this setting change the playback speed with I / O off?

Thank you.

Like I told before all settings for Video and FileI/O are the default ones after the VPro installation, Video is this

Since version 18 I use for those settings only the default ones because for me and my editting they are the best.

I'd use the Intel iGPU for decoding for stability and performance and keep file i/o on all defaults.
In general Vegas likes fast CPUs more than many cores. Never heard of any problems with too much system ram- Vegas just won't make use of it past a certain point.

AVC and HEVC aren't the same and within these formats there are other variables. Performance isn't illogical but the logic requires understanding of exactly what media is being used (only new Intel iGPUs can use hardware decoding on HEVC 10-bit 4:2:2 so you'll see them beat high-end NVIDIA and AMC cards, for example).

Vegas benchmark here has timeline preview times- but note that this isn't about decoding basic AVC so much as it is moving text, graphics and other difficult objects. Link

Techgage has a variety of benchmarks: https://techgage.com/article/magix-vegas-pro-18-processor-graphics-card-performance/2/

I'd use the Intel iGPU for decoding for stability and performance and keep file i/o on all defaults.

@RogerS Stability and reliability I understand, but what do you mean by performance?

Is that something you've tested or can quickly test sometime soon, timeline playback speed is too hit and miss with all the variables such as buffering, but could you do a intel QSV encode using Intel decoder and then Nvidia decoder and see if you see the performance increases with the Intel decoder?

Interested in first hand reports, if you tested both for the benchmark test you oversee that would be good data

Hmm, good question, Todd and I think I spoke too broadly. For just testing decoding as the OP wants, we need to specify which media precisely.

@pierre-k I would be willing to do a test or two. Can you describe the type of AVC you are most interested in? (and HEVC if you want that too). Or better yet make a test file of reasonable length available (30 sec?). Happy to put it in my Dropbox if you like.
If there is a particular hardware combination you are considering perhaps we can find someone who has it to do the same test.

I don't think the render benchmark project is the best for this as just the decoding side isn't much of a test for any GPU- what makes it hard are all the other layers of graphics. Column R has average framerates but the difference isn't the decoder (see notes- a few even report slightly better times with the legacy decoder). In the top slots (>18fps) we see 11th gen Intel i7 and i9s and the Ryzen 9-5950x. Don't think you can go wrong with any of those CPUs and a NVIDIA 3060+ or AMD 6800+.

Guys, you're complicating things for me again.

Benchmark The project is ideal for testing. I want to find someone who can play this project with the most fps.

I will edit the requirements ....

your PC .............................................?

Preview Screen....................Best Full

Properties/Video/Gpu off

I / O off ................................. ? FPS
I / O QuickSync (Type)...........? Fps
I / O Nvidia or AMD ...............? Fps

Properties/Video/ Gpu On (Type?)

I / O off .................................. ? FPS
I / O QuickSync (Type)....... ....? Fps
I / O Nvidia or AMD ................? Fps

Could a new Benchmark list have been created accordingly, which will focus only on playback?

The benchmark is not ideal for testing as any modern GPU and CPU will give you the same result- 25fps for just decoding the media itself. This tests other things where the GPU does matter- see column R for the most FPS. You can go to data/sort if you like.

If you want to test just decoding, try a more challenging file, and we need to make a new project to test. I suggest a 30 second one so it won't all be cached by dynamic ram preview.

J-V thank you very much for the data. I continue.

Intel Xeon E3-1231V3 4 core 3,40Ghz, Dram 16GB, GTX970, Vegas 19 b550.
The Xeon processor does not have QuickSync.
Play the whole project from start to finish, twice in a row.

Preview Screen....................Best Full

Properties/Video/Gpu off

I / O off ................................. 0 FPS
I / O QuickSync (none)...........x Fps
I / O Nvidia GTX970 ...............0 Fps

Properties/Video/ Gpu On (GTX 970)

I / O off .................................. 1 FPS
I / O QuickSync (none)....... ....x Fps
I / O Nvidia GTX970 ................1 Fps

Remember to close and reopen Vegas each time you make a change.

As the whole timeline varies wildly I just did the highlighted section as per the original test.
No point in turning GPU off for preview as it wouldn't generate any data.

For file i/o:
Intel 1.2
NVIDIA 1.3
off 1.2

Decoding isn't the limiting factor here- not a good test of decoding.

As the whole timeline varies wildly I just did the highlighted section as per the original test.
No point in turning GPU off for preview as it wouldn't generate any data.

For file i/o:
Intel 1.2
NVIDIA 1.3
off 1.2

Decoding isn't the limiting factor here- not a good test of decoding.

Thanks

The project contains a lot of effects, graphics and video files. It's good to know what PC will play this project in max fps. So far, Intel 8-core seems to be a higher priority than GPU and QuickSync for Vegas and I / O.

It needs more users and tests.

Max FPS PC hasn't been released yet. You can see the improvement year by year though as new hardware comes out.

Feel free to recruit users to submit benchmark results - I have done what I can to encourage it

Nobody else?

Ich melde mich @pierre-k, please read it thoroughly.

1, hardware combination encloses VEGAS limitation. 
1-1, forget that system requirement which means you can run VEGAS, doesn't mean you can run it well. 
1-2, big RAM helps editing quick and solid without shoveling temporary data; big %dynamic longer RAMpreview. 
1-3, CPU is the 1st basic invest for NLE; the more power the better e.g. modern 16cores/32threads. 
1-4, GPU the 2nd basic invest for NLE; VRAM less than 8 GB no good; disable GPU acceleration stupid. 
1-5, no more HDD as storage medium into operation.  


2, VEGAS project properties set basic rules to HW. 
2-1, make 100% sure what you will produce, and what parameters you do choose. 
2-2, be not cheated, your display has 60Hz and that's the ideal fps for a smooth production. 
2-3, FrameBlend uplifts low fps source smoother in high fps project with proper HW consumption. 
2-4, DisableResample is good and HW friendly for low fps project; FrameBlend is nonsense by downgrading. 
2-5, OpticalFlow should only be used occasionally at event-level; it's pure CPU performance, amazing but inefficient! 
2-6, don't modify your project including its rendering else you have a ground to declare. 

3, don't fancy your HW is Hercules; estimate the optimal timeline preview. 
3-1, take the 8bit fullRange format as reference, preview quality/resolution ->Good/Half, project HD/4K you like. 
3-2, add credit "Scrolling on Transparent" onto timeline and loop play 2-3x for full fps speed. 
3-3, Good/Half is cool, Good/Full top! No Auto-Adjust, no Preview/Draft (no proxy).  
3-4, add Titles&Text "Coming at You" above, loop play or RAMpreview, if no full fps, down to Good/Half/Quarter. 
3-5, be not surprised if playback speed drops when scopes live monitoring and/or extern display connected. 

4, HEVC source still a walnut, 10bit422HEVC absolut killer. 
4-1, to crack them, VEGAS has developed an all-purpose SO4.dll, not very successful. 
4-2, not few people still guard their antique as treasure and try VEGAS on it; all the problems go to fileIO-Tab. 
4-3, you must test what is to check/uncheck and which combination best performed by your machine. 
4-4, my machine has this as best, can decode every thing well except 10bit422HEVC. 

Thank you.