Just a remark @Sandhill_Films , why is your projectsetting 2160p24 and not 1080p24 when footage is just 1080?

@andyrpsmith you have a good GPU but your CPU not so great, but that also means your system is more valuable as a benchmark for the playback at native frame rate. It would be most likely CPU efficiency is less in VP21 at this moment.

Yes Todd you are absolutely right, my CPU is old but is running at 4GHz and runs all the AI features OK, in general time to render is not an issue for me as it's just a hobby. My screen is 1920 x 1080 so my GPU is well matched to it and runs games really well. As it does everything I need at the moment I will stick with it. Also it is quite handy to see how new Vegas versions run with it and so far it's OK, I have all versions from V13. Many thanks.

I downloaded the test file, tried VP20 and VP21 and ran into some strange behavior. Playback is identical for both versions. The video is smooth.

The problem arises if you use a simple Transition.

It plays 20 times jerkily, then several times smoothly and then again several times jerkily. During playback, the CPU cores are turned off and on differently. I didn't understand their logic. I think if Vegas needs immediate performance for Transition, it should activate all cores, or at least the big ones.. It doesn't happen in my demo. CPU cores turn on illogically.

This would explain why Vegas sometimes plays smoothly and sometimes strangely.

What do you think?

I wrote a scathing comment earlier about your practice of recording at very high frames rates on the possibility that you might do slow motion in delivery, but my libertarian nature got the better of me and I deleted the comment before posting. I'm perfectly willing to allow you to think and do as you please.

My Considered Opinion

You're wasting a lot of camera bits that will never make it to the viewer with the practice. Let me assure you, "ALL people shoot at different settings from their timeline. ALL PEOPLE." could be true, but that don't make it a good idea.

I did some research into the notion of "always" shooting 120fps on some wedding video forums, and indeed, the goal seems to be oldschool slomo. Optical Flow slomo in Vegas now makes that unnecessary, and is good enough that shooting at delivery frame rate probably makes the most sense for editing efficiency, and possibly perceptually for audiences, because it is uniformly smooth at all playhead rates. No bumps.

I downloaded the test file, tried VP20 and VP21 and ran into some strange behavior. Playback is identical for both versions. The video is smooth.

The problem arises if you use a simple Transition.

It plays 20 times jerkily, then several times smoothly and then again several times jerkily.

@pierre-k It's a decoder bug/limitation. Try without GPU decode using Legacy AVC, I bet will play almost perfectly across the dissolve. In Vegas it uses approx 30% GPU decoder for playback of 120fps, but during the transition where you might expect 60% decode it's zigzaging up to near 100% and jerking and dropping frames as you say. but turn decoder off, it works fine.

I did a comparison with Resolve, and it works the way I believe Vegas should work, playing at 120fps, GPU decode is at 15%, during the transition GPU decode is at 30%, it all makes sense, but not so for Vegas GPU decode

Like I said. It works great in 20 and 17 so it's a bug in 21. Needs to be fixed. I'm going back in to 20. Anyway to get my money back? I don't have time to haggle with yet another bug in Vegas.

Anyway to get my money back?

https://www.magix.com/int/terms-and-conditions/

I . General Terms and Conditions § 3 Consumer Cancellation Policy

@Sandhill_Films

@Sandhill_Films

When I installed Vegas 21, playback was laggy compared to Vegas 20. Then I found out that a setting in preferences wasn't the same. In Preferences > File I/O options > Hardware Decoder to Use, Intel was selected in Vegas 21, but in Vegas 20 it is set it to Nvidia. Nvidia is much better than Intel (on my machine).

So what good is it to have an nVidia Card and why doesnt Vegas Pro 21 or 20 or 17 for that matter, take advantage of the card. I turned it all off in the File IO and now it plays fine at 24 frames Project. Davinci takes full advantage of the nVidia card and the files play flawlessly. I'm just not a fan of learning how to edit in Davinci.

@Sandhill_Films

When I installed Vegas 21, playback was laggy compared to Vegas 20. Then I found out that a setting in preferences wasn't the same. In Preferences > File I/O options > Hardware Decoder to Use, Intel was selected in Vegas 21, but in Vegas 20 it is set it to Nvidia. Nvidia is much better than Intel (on my machine).

 

No unfortunately mine is better with nVidia turned OFF in the File IO which doesnt make sense. The nVidia card should be WAY better at those task but I guess not on my computer

I downloaded the test file, tried VP20 and VP21 and ran into some strange behavior. Playback is identical for both versions. The video is smooth.

The problem arises if you use a simple Transition.

It plays 20 times jerkily, then several times smoothly and then again several times jerkily.

@pierre-k It's a decoder bug/limitation. Try without GPU decode using Legacy AVC, I bet will play almost perfectly across the dissolve. In Vegas it uses approx 30% GPU decoder for playback of 120fps, but during the transition where you might expect 60% decode it's zigzaging up to near 100% and jerking and dropping frames as you say. but turn decoder off, it works fine.

I did a comparison with Resolve, and it works the way I believe Vegas should work, playing at 120fps, GPU decode is at 15%, during the transition GPU decode is at 30%, it all makes sense, but not so for Vegas GPU decode

Yeah its works great now with everything turned OFF in File IO. See my image in my comment above.

Just a remark @Sandhill_Films , why is your projectsetting 2160p24 and not 1080p24 when footage is just 1080?

Even though I shoot at 1080p most of the day, I do shoot 4K from time to time and always on the drone(aerial) shots. I always render to 4K because if you don't, YouTube, Facebook and Instagram will crush it with compression but if the file you upload is 4K, they process it WAY better

No unfortunately mine is better with nVidia turned OFF in the File IO which doesnt make sense. The nVidia card should be WAY better at those task but I guess not on my computer

 

@Sandhill_Films NVIDIA NVDEC should work better in VEGAS but doesn't. NVIDIA GPUs do a fine job at accelerating Fx and the timeline in VEGAS (preferences/ video), but if the media isn't decoding well overall performance will be poor.

That said you should *never* have to use NVDEC as you have an Intel K processor which comes with QSV decoding. QSV works much better in VEGAS and doesn't have this problem. As a bonus it should significantly improve preview performance (esp. with HEVC media if legacy is unchecked). All you have to do is enable it in bios and install drivers for it.

2 GPUs are better than one!

@Sandhill_Films

Davinci takes full advantage of the nVidia card and the files play flawlessly. I'm just not a fan of learning how to edit in Davinci.

Resolve isn't that tough to figure out. The first day. It was pretty daunting, but then I caught on real fast. Each software has its advantages and disadvantages. I sent you a private message.

RogerS: can i use QSC decoding with i7-2600 cpu too? I have 1660Ti for decoding and QSV isn't in the list in preferences. No monitor is needed to the video output on mainboard, right? Just i dont have the driver?

This is my proper stats on the build.

Intel® Core™ i9-13900KF 3.00GHz

MSI PRO Z690-P DDR4 - ATX

(2) * 16GB DDR4-3200 Corsair Vengance LPX

NVIDIA® GeForce® RTX 3060 12GB GDDR6

500GB SAMSUNG 980 NVMe M.2 SSD - OS

4TB SAMSUNG 980 NVMe M.2 SSD - SOFTWARE

CLX Quench 360 Closed Liquid Cooler

SET SAKARA Mid Tower Black

(4) * RAZER 120mm Case Fans

750 Watt EVGA BQ 80Plus Bronze

2x Asus ProArt PA278QV 27" WQHD Monitors

M-Audio AV32 Speaker Monitors

M-Audio BX8a Speaker Monitors

Because you have such a good CPU, and I think you got the specs correct this time, because 13900KF being associated with a 360mm water cooler makes perfect sense, turn on Legacy AVC decoding. For this particular camera file you don't need a GPU decoder and infact it's the reason for the lagging. You do not have an Intel IGPU

But always remember you have Legacy AVC turned on, because other camera formats may greatly benefit from GPU decode, and result in lagging due to it not being on or won't even display.

Vegas decoding is such a broken mess. nobody should have to do this, and it's so confusing for people.

I wrote a scathing comment earlier about your practice of recording at very high frames rates on the possibility that you might do slow motion in delivery, but my libertarian nature got the better of me and I deleted the comment before posting. I'm perfectly willing to allow you to think and do as you please.

My Considered Opinion

You're wasting a lot of camera bits that will never make it to the viewer with the practice. Let me assure you, "ALL people shoot at different settings from their timeline. ALL PEOPLE." could be true, but that don't make it a good idea.

I did some research into the notion of "always" shooting 120fps on some wedding video forums, and indeed, the goal seems to be oldschool slomo. Optical Flow slomo in Vegas now makes that unnecessary, and is good enough that shooting at delivery frame rate probably makes the most sense for editing efficiency, and possibly perceptually for audiences, because it is uniformly smooth at all playhead rates. No bumps.

You can still tell when using Optical Flow. I use Topaz Video AI sometimes when we forget to set back to 120p and its on 24p. Topaz looks good but actual 120p is much cleaner.

Because you have such a good CPU, and I think you got the specs correct this time, because 13900KF being associated with a 360mm water cooler makes perfect sense, turn on Legacy AVC decoding. For this particular camera file you don't need a GPU decoder and infact it's the reason for the lagging.

But always remember you have Legacy AVC turned on, because other camera formats may greatly benefit from GPU decode, and result in lagging due to it not being on.

Vegas decoding is such a broken mess. nobody should have to do this, and it's so confusing for people.

Yeah I am going to uncheck Legacy AVC now and try for a while. Yeah specs are definitely right now. lol. I got them off the order in my old email from last November.

Thanks for clarifying it's KF- that changes everything. Sometimes the modern decoder + NVDEC will benefit you, sometimes not so testing is a good idea. Good luck.

@relaxvideo You don't have a HD 530 or newer iGPU given the age of the CPU. GPU decoding may work with say VP 15 (I believe; I retired my 2nd gen Intel when that came out) but not VP 18 or newer.

yes, cpu is Intel® HD Graphics 2000 with Quick Sync Video supported. So you say VP15 (which i dont have, only 11/12) maybe support it, but 19 (and 21) not?! Why?