My proxy files are getting deleted when I close the program. This is not something that I want to have happen. I've manually created proxy files for all the video clips that I want to use on a project, but they're gone when I open VSX2 back up to work on the project again.
I haven't found settings anywhere to change this functionality, or even how to set proxy folder size limits to try and workaround the problem.
Any Suggestions?
Proxy Files getting deleted...
Moderator: Ken Berry
I was having the same problem with VS Pro X2. It was frustrating to have to re-create the proxy files every time I started an editing session.
As a result, I have stopped using the proxy files created by VS and now create my own, based on the suggestion from another user (etech) shown in the quote in the second message (posted by Ken Berry) in the link below.
It took me a while to work out the correct work flow but once I did, I find I like this method better than using the VS proxy files. It not only solved the disappearing proxy file problem, it solved the problem mentioned in the first message in the link, which is that VS doesn't use its own proxy files when previewing individual clips. It only uses them when previewing the project.
http://phpbb.ulead.com.tw/EN/viewtopic. ... highlight=
As a result, I have stopped using the proxy files created by VS and now create my own, based on the suggestion from another user (etech) shown in the quote in the second message (posted by Ken Berry) in the link below.
It took me a while to work out the correct work flow but once I did, I find I like this method better than using the VS proxy files. It not only solved the disappearing proxy file problem, it solved the problem mentioned in the first message in the link, which is that VS doesn't use its own proxy files when previewing individual clips. It only uses them when previewing the project.
http://phpbb.ulead.com.tw/EN/viewtopic. ... highlight=
Double Encode?
This seems like a painful workaround, but one nonetheless, so thanks for the response.
I do have a question though, if you're encoding down to 720x480 for the dvd before editing, doesn't that re-encode the mpeg a second time when you reprocess the edits? I've had real bad performance encoding a second time, it looks much worse than it should.
Any insight on this problem? Thanks again.
I do have a question though, if you're encoding down to 720x480 for the dvd before editing, doesn't that re-encode the mpeg a second time when you reprocess the edits? I've had real bad performance encoding a second time, it looks much worse than it should.
Any insight on this problem? Thanks again.
A second encoding doesn't take place. First I make sure that my edits of the 720x480 clips are final. I do this by burning a DVD+RW disc with the edited 720x480 and playing it. If I see a problem or something I want to change, I edit again and re-burn the DVD+RW.
After all edits are final, I rename the folder that the 720x480 clips are in. That causes VS to say that it can't find the files ,and it offers to re-link. I then re-link to the folder that contains the actual unedited clips that came out of the camcorder. Then I create a file or disc (either AVCHD or standard DVD) and it only re-encodes once by applying the edits to the original clips.
The key to the re-linking is to make sure the files have the same name (i.e. the original files from the camcorder and the 720x480 files created by the VS batch conversion.) My camcorder's AVCHD files have an extension of .mts. When I batch convert them in VS to 720x480 it creates files with an extension of .mpg (there doesn't seem to be a way to force VS to create the files with an extension of .mts.) So after conversion, I use a freeware extension changing program to change the .mpg to .mts. Then I edit these files with VS.
I have found that it isn't too much of a pain, and being able to preview at the clip level is a big advantage for AVCHD. When previewing clips (rather than the project) VS doesn't use the proxy files it creates, so I would get choppy playback. With this method, clip playback is smooth because it is actually playing 720x480 clips, not 1920x1080 AVCHD clips.
It took a while to work out the steps involved with this technique. To help me remember them, I documented them. If you want, I can PM the document to you.
After all edits are final, I rename the folder that the 720x480 clips are in. That causes VS to say that it can't find the files ,and it offers to re-link. I then re-link to the folder that contains the actual unedited clips that came out of the camcorder. Then I create a file or disc (either AVCHD or standard DVD) and it only re-encodes once by applying the edits to the original clips.
The key to the re-linking is to make sure the files have the same name (i.e. the original files from the camcorder and the 720x480 files created by the VS batch conversion.) My camcorder's AVCHD files have an extension of .mts. When I batch convert them in VS to 720x480 it creates files with an extension of .mpg (there doesn't seem to be a way to force VS to create the files with an extension of .mts.) So after conversion, I use a freeware extension changing program to change the .mpg to .mts. Then I edit these files with VS.
I have found that it isn't too much of a pain, and being able to preview at the clip level is a big advantage for AVCHD. When previewing clips (rather than the project) VS doesn't use the proxy files it creates, so I would get choppy playback. With this method, clip playback is smooth because it is actually playing 720x480 clips, not 1920x1080 AVCHD clips.
It took a while to work out the steps involved with this technique. To help me remember them, I documented them. If you want, I can PM the document to you.
Thanks for the reply, I suspected that this is the way it worked, however the post was a little unclear, because they made it sound like you only relink for hd quality outputs, and that they were using the down-scaled 480 for the dvd projects.
Anyway, this answers my question, it's just what we have to deal with, until they refine SmartProxy to fully do the job, rather than halfway.
Ulead:
1.) Fix SmartProxy for use throughout the editing process, including clip and library level.
2.) Keep the proxy files between program uses until manually deleted, or at least given the option to configure it to this behavior.
3.) Allow sub-folder hierarchy when managing library and re-linking files, so all video could be included from sub-folders of the file tree.
It doesn't seem like there is any benefit to making the 480 other than as a proxy file, I don't think I would even make my dvd quality outputs from the 480 source, unless there was a way to get the edits in without actually re-encoding the video.'(plus I have them to make a standard dvd)'
'Plus I also have them all in DVD compliant format'
Anyway, this answers my question, it's just what we have to deal with, until they refine SmartProxy to fully do the job, rather than halfway.
Ulead:
1.) Fix SmartProxy for use throughout the editing process, including clip and library level.
2.) Keep the proxy files between program uses until manually deleted, or at least given the option to configure it to this behavior.
3.) Allow sub-folder hierarchy when managing library and re-linking files, so all video could be included from sub-folders of the file tree.