I just made a proxy of a 2720x1530x32, 59.40fps clip 27;18f long. The proxy came out as:1280x720x12, and 01:09;01 long. it plays back at about half speed. Don't know how I screwed this up, it was just a simple menu selection. How can I fix it?
Which way do you use the proxy file — right by switching the preview setting?
Marco means, you have different ways to use proxies.
By not selecting it in your settings and than rightclicking at the projectmediafile
or by choosing the option for all concerned files at Options/Preferences/Video
What I mean is:
Some people ignore the right way of using the internal proxy workflow and think they can directly use the SFVP0 files. But this breaks some things. Manually using the SFVP0 files is strictly to be avoided as this may introduce errors like Widetrack described above. Instead, only use the internal proxy workflow the way it is meant to be used: Always leave the SFVP0 files untouched and switch from source file to proxy file by switching the preview setting.
I just today learned that these were the two ways to make a proxy. So when I made this proxy, I did it by right-clicking on the project media file. But then I learned about the Preferences option and opened that window, only to find that the option was already selelcted. If VP16 (or any other version) has ever actually made a proxy for me I never saw it. (But then, I also just today learned about the odd and misleading icon and filetype name the proxies have.) But I did identify and load one into a project manually today. And it's long and slow.Sorry for the confusion.
Kind of OT: I'm also just noticing how different the Vegas updating process is. It seems to insist that Vegas is open in order for me to download and install the latest VP16. Gives me the nasty feeling that my current version will be erased, so if the new build is "problematic" it's more trouble to down-date later. Progress.
"But I did identify and load one into a project manually today."
This is what you should not do within the Vegas internal proxy workflow and it's most likely the reason for your clip length and speed issue.
Gives me the nasty feeling that my current version will be erased, so if the new build is "problematic" it's more trouble to down-date later.
If you do not find the file/folder containing the previous build of your version, the links are in one of Nick's FAQs, point 5.
"But I did identify and load one into a project manually today."
This is what you should not do within the Vegas internal proxy workflow and it's most likely the reason for your clip length and speed issue.
Thanks, Marco. And I just saw that the workflow appears in the help window of this build. Good juju.
Gives me the nasty feeling that my current version will be erased, so if the new build is "problematic" it's more trouble to down-date later.
If you do not find the file/folder containing the previous build of your version, the links are in one of Nick's FAQs, point 5.
Thanks, VK. You are ever helpful.