Hi, all.

 

I'm using Vegas Pro 21 (legit). I've been making a new video and it's going to be in 4K. Of course, editing using 4K files is near impossible so I re-rendered all of my video footage into 720p proxies so it was easier to edit with. I've now done my editing and it's all ready to render in 720p.

 

However, I want to change these files to use the 4K files, not the 720p proxies.

 

For easier 4k editing use (next) time the Vegas proxy option, which creates automatically proxies of your 4k media and also automatically uses the original 4k footage to render your project. So no need to create own proxies or replacing files for rendering. Creating Vegas proxies isn't that slow, it's faster than the time you spend to write this post...Also a faster computer suitable for editing 4k footage is an option to save time.

If the names in the 2 folders are made to match exactly, pointing to the 4k folder in Vegas with Swap instead of Replace will replace them all in one swoop. Looks like the easiest recovery now is to add "_proxy" to the names of all your 4k clips.

I would do this, but then all my 4K files would have to be renamed "proxies" which then makes matters confusing.

For easier 4k editing use (next) time the Vegas proxy option, which creates automatically proxies of your 4k media and also automatically uses the original 4k footage to render your project. So no need to create own proxies or replacing files for rendering. Creating Vegas proxies isn't that slow, it's faster than the time you spend to write this post...Also a faster computer suitable for editing 4k footage is an option to save time.

So, I just tried this option again. Huh, they must have sped the proxy thing up since I last upgraded. I remember Vegas 18 taking over 20 minutes to do a minute's worth so I always used handbrake to re-render them which took less than a minute to create. This time, it was about the same speed of the proxy. So I will try this next time.

However there's an issue. While I cannot tell if it's actually worked or not (whereas mine I could because it would say "_proxy"), every time I click off VEGAS, and then click back on it, it then re-builds the same proxy. If I used the VEGAS way to make two proxies, it builds both of them again whenever I click off and back on. Meaning I've got to re-create the proxy every single time I re-click on the window. Why is it doing this?

Also, I would have thought a 16-core CPU with a 3080TI GPU and 64GB RAM would be pretty good for editing lol

EDIT: I closed VEGAS down and re-opened it and now it's not rebuilding anymore. But going real slow. I then wondered if it was even using the proxy file so I renamed the proxy file it built and vegas didn't complain. I renamed the 4K file and then it did; meaning it wasn't even using the proxy. Unless I'm doing something wrong, it seems unreliable?

EDIT2: I found a solution to my problem. I discovered if I open the VEG file in a HEX editor, I could search for the "_proxy" filename. So I found all instasnces of "5F 00 70 00 72 00 6F 00 78 00 79 00 2E 00 4D 00 50 00 34" and replaced them all with "2E 00 4D 00 50 00 34 00 00 00 00 00 00 00 00 00 00 00 00" (changes all "_proxy.mp4" to ".mp4 ".

I then re-opened the project file, and it complained it couldn't find the 4K file (because it's in the previous folder). I told it where to find one, then it found the rest automatically. All my proxies are now using my 4K files.

Thanks for the help. I much rather use the VEGAS way but I can't tell if it's really using the proxy or not so I may stick to the way I do it for now. Thanks for the advice, all.

 

However there's an issue. While I cannot tell if it's actually worked or not (whereas mine I could because it would say "_proxy"), every time I click off VEGAS, and then click back on it, it then re-builds the same proxy. If I used the VEGAS way to make two proxies, it builds both of them again whenever I click off and back on. Meaning I've got to re-create the proxy every single time I re-click on the window. Why is it doing this?

I cannot replicate the issue you described.

@redhotsonic The built in proxy facility has the advantage that it automatically bypasses for all renders. It also automatically bypasses if preview is set to Good or Best. Or if you rename or delete the the proxy file. Default proxies don't seem to work as well for me with some material, like 60p, and don't play as efficiently as manually made proxies.