John Rofrano
3
COW Coins
Forum Replies Created
-
After the swipe completes, you press the S key to split the video and drag it to a track above the mask track.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I don’t have alpha swipes but if you are referring to the fact that a track has been put in mask mode so it needs a solid white mask to see the video below it, that’s easy to solve. Split the video and drag it to a higher track that is not in mask mode.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
If you want to try and resolve the codec issue, then get a copy of GSpot and open the files with it and see what codecs they use. GSpot will also tell you if the codec is installed on your system. Then just go get the codecs that you don’t have and install them. If Vegas still doesn’t open them then you are stuck since you refuse to recode them into a format that Vegas can edit. Good luck.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
> It seems that the Super C site puts you into a loop and you can’t actually download the program. I’ve spent almost an hour there trying to figure out how and where to DL that program. Unless it’s my connection!
Allen, You’ve got to really want it bad enough. 😉
I have no proof of this but it may be intentional to drive pages hits on the site. Notice they have a lot of advertising on the site and I’m guessing they get paid by the page hit so driving customers around in circles probably makes them more money.
It takes three pages to get to it. On the first page, the link to the second page is at the bottom. On the second page this link to the third page is on the top. On the third page, the link to the actual download is again at the bottom.
I will not post a direct link because I assume if they wanted it to be easy they would have posed a big download button on their site, but I will tell you that the link is on the bottom of this page.
Hint: Search for “Download SUPER © setup file”
~jr
http://www.johnrofrano.com
http://www.vasst.com -
When you say 2-3 TB of clips, are you talking about the size of the clips themselves? The Media Manager does not store the clips; it just stores the name of the clip with some meta-data about it. Much like a phone book stores phone numbers and not the actual people. So the capacity limit would not be the size of the clips as much as the number of clips. More clips would create more names and those names would have to be stored in the Media Manager database.
I have no idea what that capacity is but since the database is just a file, I would image it would be limited to the NTFS file size limit of 2TB. You would have to ask Sony if they did any capacity testing for how many filenames they can store in it.
Having said that, the Media Manager allows you to create multiple libraries and so there is nothing stopping you from creating more libraries and having an endless amount of storage capacity. I have one library for my ACID loops and another for my stock video footage. This keeps the search fast because I’m limiting the amount of data I need to search through by category. When I’m working in ACID I don’t need to see video footage and when I’m working in Vegas I’m mostly using video but if I need ACID loops I just switch libraries. It works out quite well.
BTW, I have a training DVD on the Media Manager if you really want to learn a lot more about how to get the most out of it. It’s called the VASST Absolute Training for Vegas+DVD, Vol. 7: Media Manager Demystified. Here is a sample clip that explains what I just explained above: ZIP
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Nothing will edit FLV files so forget it. It is an output only format. It looks like you are taking a bunch of other output files that you found on the web and are trying to re-edit them. Vegas is not going to do a good job with these files. they are in highly compressed formats that make them very difficult to edit.
My recommendation would be to re-encode these files into something Vegas can edit easily. Use a free convertion utility like Super (c) and output them to AVI using the Huffyuv or similar lossless codec. This will make them compatible with Vegas and save you a lot of headaches.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
There are two things to check: One is that you are rendering to a hard drive that is NTFS and not FAT32. Many external hard drives are formatted for FAT32 which has a 4GB file size limit. Once the file reaches this limit Vegas has to start another file. The other thing to check is that the rendering template you are using has Create an OpenDML (AVI version 2.0) compatible file checked. If this is unchecked, your AVI files will be limited to 2GB in size.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
The default Text Generator has a transparent background. You’d have to be doing something special to get it not to be transparent. Anyway, go to the Properties tab on the Generated Text and pull the alpha slider all the way down on the Background color or just set the Alpha (A) to zero in the data entry fields.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
You’re very welcome and I hope it renders correctly this time.
More importantly, you need to find a workflow for future projects. Rendering uncompressed is OK for small files but for larger projects, a format like DV, MJPEG, or HUFFYUV might be a better choice. But we’ll worry about that after you get this project to work. 😉
~jr
http://www.johnrofrano.com
http://www.vasst.com -
> Now when I am finished doing that to all of my clips I move the uncompressed avi files into the folder that I took them out of so that Sony Vegas can properly read the files in the project timeline, correct?
Correct! So if you are using a separate folder, just keep the same filename. Then move the uncompressed files back to where Vegas expected them and it will use them instead of the DivX files. this should make it all work.
~jr
http://www.johnrofrano.com
http://www.vasst.com