Thanks LongIslander but been down this road a few many times. Know all about the proxies and preview settings and cpu is i7 3930k. Amazing enough it doesn't matter which setting. It will still do this. Thank you for the shout out. I appreciate it.

VEGAS 18 System Requirements:

Processor: 6th Generation Intel Core i5 (or AMD equivalent) or better. 2.5 Ghz and 4 Core minimum. For 4K, 7th Generation Intel Core i7 (i7 7xxx... or AMD equivalent) or better. 3.0 Ghz and 8 Core minimum.

fwiw I long ago accepted that transitions (even simple fades) will drop frames no matter how I tune my systems. It's frustrating but if the transition is critical to me, I just render out that part to make sure it's going to look the way I want. Frustrating but I too have yet to find a sure-fire solution

VEGAS 18 System Requirements:

Processor: 6th Generation Intel Core i5 (or AMD equivalent) or better. 2.5 Ghz and 4 Core minimum. For 4K, 7th Generation Intel Core i7 (i7 7xxx... or AMD equivalent) or better. 3.0 Ghz and 8 Core minimum.

Hello Frosty. Yes I saw those as well but it was no different with earlier versions of vegas pro on this end. I can put anything on the timeline that is not 4k and still get this to happen. It has been this way for us since we dropped into vegas 15. Cpu does great and the gpu side is equal as far as seeing it being utilized. Major improvement there.

This is pretty much where I left off with Vegas 15. Everyone tried to help but to no avail. Crazy I know. Thank you for your time Dr Frosty. ; ) Well appreciated sir.

fwiw I long ago accepted that transitions (even simple fades) will drop frames no matter how I tune my systems. It's frustrating but if the transition is critical to me, I just render out that part to make sure it's going to look the way I want. Frustrating but I too have yet to find a sure-fire solution

I am sure you went through all the system requirements as well, etc. Tried lesser formats for standard HD rather than 4 k? Wish I could help us both LOL. ; ) Thank you for your response.

fwiw I long ago accepted that transitions (even simple fades) will drop frames no matter how I tune my systems. It's frustrating but if the transition is critical to me, I just render out that part to make sure it's going to look the way I want. Frustrating but I too have yet to find a sure-fire solution

I am sure you went through all the system requirements as well, etc. Tried lesser formats for standard HD rather than 4 k? Wish I could help us both LOL. ; ) Thank you for your response.

Yeah, I don't work with 4k all that often and have found that there just seems to be something very inefficient in the VP pipeline when it comes to blending images. In one respect it's because they don't make very good use of the GPU. If I watch task manager when playing back, I can see that CPU use goes up by 20-30% during the transition but GPU use doesn't budge. Also they don't do much, if any, scaling on the GPU so setting your project size to the same size as your source media will get you some speedup.

Yes, David, you have added Generated Effects exactly at the two places where the preview rate drops to 20, which ain't bad at all, especially for a third generation i7. That is because you are asking your system to render in real time, and only the most robust will keep up. Be fully aware that those two sections do not exist as files, but only as sets of instructions to your CPU.

The solution, of which I truly thought you were aware, Is to Prerender the "effected" events, either with RAM or file prerender. So you can see that it is not Vegas misbehaving, nor is it a criticism of your system. Prerender works every time as intended, so your high expectations are not altogether unreasonable.

Yes, David, you have added Generated Effects exactly at the two places where the preview rate drops to 20, which ain't bad at all, especially for a third generation i7! That is because you are asking your system to render in real time, and only the most robust will keep up. Be fully aware that those two sections do not exist as files, but only as sets of instructions to your CPU.

The solution, of which I truly thought you were aware, Is to Prerender the "effected" events, either with RAM or file prerender. So you can see that it is not Vegas misbehaving, nor is it a criticism of your system. Prerender works every time as intended, so your high expectations are not altogether unreasonable.

Well put Musicvid as always. This is starting to make more and more sense to me now. I should probably look into upgrading my cpu if I wish to keep up with 4 k natively at this junction.Thank you also again Frosty for making me more aware of the specs. : )

I knew about pre rendering files in Vegas indeed, but so used to using proxies in premiere pro. Can't understand why the 4k proxies don't make for a better smooth playback in Vegas. I sent all my specs to Magix support and they asked me to not use proxies and just run the 4k files. Both again played fine but any time a cut came up from one to another a pause of the motion before the next clip plays. This again only happens every few clips. That is still what baffles me. I should at least get smooth playback. Proxies in premiere is the only thing saving my BUT on adobe. They play flawless with effects. There is noway of making a 4k file run on my rig in adobe without proxies. So I wonder what is different with Vegas proxies. Maybe I should be asking that? Thank you for shedding more light on this kind sir. Truly appreciate it.

Files are 3840X2160 23.976 xavc-s then I choose to make proxies in Vegas. Maybe I should try another codec for proxies in vegas? If possible?

 

Files are 3840X2160 23.976 xavc-s then I choose to make proxies in Vegas. Maybe I should try another codec for proxies in vegas? If possible?

Vegas creates a 1080p AVC proxy using NVENC. That could be the problem especially if you are working with 50p or 60p. Ideally there would be an option to choose 720p as well for people with slower computers.

Premiere renders your effects and transitions in the background. It's just a matter of where they allocate your resources. So I assume the best preview is with proxies for the media, and prerenders for the generated media.

 

Files are 3840X2160 23.976 xavc-s then I choose to make proxies in Vegas. Maybe I should try another codec for proxies in vegas? If possible?

Vegas creates a 1080p AVC proxy using NVENC. That could be the problem especially if you are working with 50p or 60p. Ideally there would be an option to choose 720p as well for people with slower computers.

My files are 23.976. Premiere pro uses QuickTime as a proxy I believe.

Premiere renders your effects and transitions in the background. It's just a matter of where they allocate your resources. So I assume the best preview is with proxies for the media, and prerenders for the generated media.

Is there a way to change what codec, settings, etc in vegas?

 

Vegas creates a 1080p AVC proxy using NVENC. That could be the problem especially if you are working with 50p or 60p. Ideally there would be an option to choose 720p as well for people with slower computers.

My files are 23.976. Premiere pro uses QuickTime as a proxy I believe.

Our cpu's are basically the same. I don't see any fps drop using fade in/out transition with proxy created that is 1080P50, and you're only using 1/2 the frame rate. It may just depend on the transition you're using, and if it's not peaking out your cpu during the transition it might not help with getting a faster CPU, although a medium speed 4core in 2020 is dated for video editing. Vegas still has to real time render the effect, if Vegas is not efficient enough it can't do it. People with 3700x 8 cores and 3900x 12 core have complained about similar although they weren't using proxies and might have been using 4K

Also when looking at cpu in something like task manager it may not update fast enough to record the 100% cpu spike if there was one.

 

Vegas creates a 1080p AVC proxy using NVENC. That could be the problem especially if you are working with 50p or 60p. Ideally there would be an option to choose 720p as well for people with slower computers.

My files are 23.976. Premiere pro uses QuickTime as a proxy I believe.

Our cpu's are basically the same. I don't see any fps drop using fade in/out transition with proxy created that is 1080P50, and you're only using 1/2 the frame rate. It may just depend on the transition you're using, and if it's not peaking out your cpu during the transition it might not help with getting a faster CPU, although a medium speed 4core in 2020 is dated for video editing. Vegas still has to real time render the effect, if Vegas is not efficient enough it can't do it. People with 3700x 8 cores and 3900x 12 core have complained about similar although they weren't using proxies and might have been using 4K

Also when looking at cpu in something like task manager it may not update fast enough to record the 100% cpu spike if there was one.

I should clarify that I am not using transitions. This is just clips with cuts between the files. Sorry if was not clear.

It is working as a transition though (from what I recall) , it's a bug that was in vp17 and still in VP18?. even though it should only be reading your top clip, it's reading both top and bottom clip, as if you're mixing the 2 clips in a transition. Someone can correct me if this is wrong

VEGAS' stock proxies are 720p 720p XDCAM EX 35Mbps. You can make NVENC 1080p proxies using happy otter scripts (tools4vegas.com), though its proxy system doesn't work as well as VEGAS', at least it was more difficult to use the last time I tried.

I've also noticed that a few generations ago: frame drops between clip cuts. Generally The playback rate will improve after cut to full fps, within a second or so. I'd say this is a read-ahead issue that stops where a clip stops, and doesn't 'look ahead' as you would expect it to. Still happens in VP18. And of course you're not seeing this if you're all low and safe, but if you must push the system to a considered edge (and it works during a 'long' clip) then I would expect this should also work in a fast cut sequence.. unfortunately not.

It is working as a transition though (from what I recall) , it's a bug that was in vp17 and still in VP18?. even though it should only be reading your top clip, it's reading both top and bottom clip, as if you're mixing the 2 clips in a transition. Someone can correct me if this is wrong

wwaag has tinkered something there once - in my opinion it is only a workaround - but until there is a solution by the developers - maybe applicable temporarily? https://tools4vegas.com/removehiddenevents/

I've also noticed that a few generations ago: frame drops between clip cuts. Generally The playback rate will improve after cut to full fps, within a second or so. I'd say this is a read-ahead issue that stops where a clip stops, and doesn't 'look ahead' as you would expect it to. Still happens in VP18. And of course you're not seeing this if you're all low and safe, but if you must push the system to a considered edge (and it works during a 'long' clip) then I would expect this should also work in a fast cut sequence.. unfortunately not.

 

Yes this seems right. Its the looking ahead that misses and then drops frames then speeds up to catch the next clip already in progress. You would figure even a proxy would not have this issue.

It is working as a transition though (from what I recall) , it's a bug that was in vp17 and still in VP18?. even though it should only be reading your top clip, it's reading both top and bottom clip, as if you're mixing the 2 clips in a transition. Someone can correct me if this is wrong

wwaag has tinkered something there once - in my opinion it is only a workaround - but until there is a solution by the developers - maybe applicable temporarily? https://tools4vegas.com/removehiddenevents/

The only thing is this happens with edits on the same timeline. Doesn't have to be above each other. I will give it a shot though. Thank you.

Update. I did try it and did nothing to help. Still odd though is I can play the same 3 edits in a loop and the first one will pause then play the next clip every time. 1/2 a second pause maybe?

I don't want to read everything again - the project settings and media properties fit together?

I don't want to read everything again - the project settings and media properties fit together?

Yes sir.