Nothing's changed with vp22 proxies that I can tell. The only Vegas-native alternative is using the Swap Video Files function in Project Media. I do that sometimes if all my media is in one folder and I point it to a different folder with replacement media with matching names. Downside is that the function needs to be manually re-run to render with media in the original folder. Works best for me (for marker frame-alignment) with manually-made proxies having the same or at least an even-division of the original frame rates. Fwiw, I only have issues with Vegas-default proxies in projects whose media are at double rate or higher... because of the way the Vegas proxy scheme time-stretches those clips to keep markers aligned with the fixed frame rate they use.

You are dealing with something completely different than me. I just don't understand why the proxy in Vegas is worse than the original proxy file. I am pointing out an obvious bug. And why is everything ok with Vegasaur and HOS?

Nothing's changed with vp22 proxies that I can tell. The only Vegas-native alternative is using the Swap Video Files function in Project Media. I do that sometimes if all my media is in one folder and I point it to a different folder with replacement media with matching names. Downside is that the function needs to be manually re-run to render with media in the original folder. Works best for me (for marker frame-alignment) with manually-made proxies having the same or at least an even-division of the original frame rates.

With Vegas proxies have the same amount of frames as the original, so no fear for mis-frame alignments.

I just don't understand why the proxy in Vegas is worse than the original proxy file.

?

You are dealing with something completely different than me. I just don't understand why the proxy in Vegas is worse than the original proxy file. I am pointing out an obvious bug. And why is everything ok with Vegasaur and HOS?

I think it's a combination of lower preview quality settings x a lower resolution XDCAM file. Not sure it is a bug and more inherent to how VEGAS was designed. It might be time for an update as we're not in a 720p world anymore.

Try to take the VEGAS proxy file and give it a normal MXF extension. Bring it into VEGAS and look at it at best/full. Then look at the proxy at preview/full. What do you see? (Lower settings than preview/full will look awful.)

@3POINT what the current proxy does to to text is unacceptable, the compression is too high, at 30fps Prores 422 Proxy is 23MB/s in last encode, the XDCAM is 24fps. Prores is a variable bit rate codec. I'd like the new proxy to look a little better than the 720P prores proxy but what can you do, if you turn the resolution and bitrate too high there will be constant complaints about Vegas filling up people's drives.

@Former user What are you talking about text, my 4k camera doesn't film text. Are you talking about 4k screengrabs? Capture your screengrabs with the right codec and there's no need for proxy creation.

FYI XDCAM proxies are always 24fps, no matter the framerate of your footage/project, but no problem each frame of your footage is covered in the 24 fps proxy (so no missing frames). This 24fps proxy will just be played at projectframerate (speedup to 25,30 or even 50,60 fps) and everything is fine.

@3POINT The problem seen with my screen capture looks to be unrelated to xdcam, but Vegas over sharpening a 720P video. With fine text that's already sharpened it destroys it, and with the buildings here it amplifies moire effect

Original/PR proxy/Xdcam

So if they plug the PR 422 Proxy into where Xdcam is and operates the same, it'll look very similar but be faster and that's probably what's behind the possible switch. For a 4K 30 second file XDCAM takes 23seconds, PR Proxy takes 6.5 seconds, an increase in proxy creation speed of 3.5 times, considerable time saving. Because ProRes is able to use 100% of your CPU, unlike Xdcam, proxy creation speed will be different depending on the CPU. I have a modest CPU running at default everything.

 

So if they plug the PR 422 Proxy into where Xdcam is and operates the same, it'll look very similar but be faster and that's probably what's behind the possible switch.

Guess what this thread was about: "Change proxy format to speed up Proxy Building in Vegas 22", till you and @pierre-k complained about quality degradation due to downsampling to 720p.

On my PC (see my signature), where I don't have a need for proxies, building a XDCAM proxy isn't much slower than creating a Prores Proxy. @RedRob-CandlelightProdctns was hoping to speed up Proxy Building by using codecs that makes use of GPU. For that you must have a recent GPU. Better invest in a recent GPU and recent CPU and you don't have a need creating proxies, just like me.

 

So if they plug the PR 422 Proxy into where Xdcam is and operates the same, it'll look very similar but be faster and that's probably what's behind the possible switch.

Guess what this thread was about: "Change proxy format to speed up Proxy Building in Vegas 22", till you and @pierre-k complained about quality degradation due to downsampling to 720p.

@3POINT That does make a lot more sense!, and it looks to be the Point resizing filter, described in the ffvdub configuration menu as "Fastest, Ugliest" . So this is legacy scaling from 20 years ago, they needed fastest CPU resizer due to no GPU integration in Vegas yet, and many people were using 2 and 4 core CPU's. That had no option.

(Point resizing filter)

Can this be changed in preferences anywhere?

... Works best for me (for marker frame-alignment) with manually-made proxies having the same or at least an even-division of the original frame rates.

With Vegas proxies have the same amount of frames as the original, so no fear for mis-frame alignments.

Yes. But the overhead of time-warping to force-fit the frames on creation and then getting them to play back properly in edit can make them ineffective as a performance enhancer. May have been cleverly immaterial for 25p or 30p clips before double rates got so popular. The easy decoding xdcam mp4 format helps a little. But when I tried a 4k 60p multicam project, the Vegas-native proxies didn't help at all. Even though they were 1/4 the frame size. Whereas creating my own xdcam 30p HD proxies in a proxy folder worked like a charm and looked way better. And since my home-brew proxies were exactly 1/2 the original rate, makers placed in edit on a frame boundary stayed put. There was a time that older versions of Vegas allowed manually created proxies to be recognized simply by changing the file-type to sfvp0. But that feature got revoked.