Kind of need a help in this. Is there any way to add one veg file to another?.
Every time I put in timeline one veg file and try to add another the first on is gone.Trying to organize my veg files amd mess I have.
You have to remember that .veg files aren't media, they're program files, which is why you can't "put them in the timeline."
Think of it like a word processor. You can't insert another file on a page -- you can only insert the file's contents. In the same respect, you'd have to open another instance of Vegas, copy all of the contents in the .veg file you want to "insert" and copy into the other project. You could also render the one and then only have one "file" to insert.
Ouside of some kind of script doing this for you, I'm not sure there is a fix that will do exactly what you want.
It is just of question of storage and change to project latter if needed. I have a bunch of veg for one project and would like to make one final veg.
I will try to open 2 vegas and see if I can copy and paste.
Thanks
Copying stuff from one veg to another will not alter the amount of storage taken up. The vegs are only very tiny files (in comparison to the source video they refer to)... so copying the events from one veg to another will have no impact at all on storage.
Hi Liam. I think it would be nice to have an "Import Project" function in Vegas. Premiere can do it so it should be possible.
By the way, my system is normally pretty stable, but the one time I tried to copy everything from one project to another, both instances of Vegas crashed and I had to reboot the system before Vegas would start again. Had a deadline to meet, so didn't try it again or nvestigate further.
I agree... this is not ideal... and your suggestion is one that has been requested by a LOT of users (me included).
One specific problem with the current approach is that you cannot easily copy a track (and it's associated FX's and keyframes) from one veg to another. You can get around it.. but it is a little cumbersome.
However... the upside is that you can open multiple instances of Vegas.. and VERY few other NLE's have such a capability (or at least that is what I hear... I only use Vegas)
I know this aint exactly what ya want, but I'll render each veg ( or scene ) and combine all the final rendered " scenes " into a new project. Not what you were looking for but it is a whole lot less taxing on the system.
Yes, the capability of running Vegas multiple times can be very useful. I also use Premiere (V6) and Canopus Edius, and they don't allow this. (It's understandable with Edius because it's tied to my Storm card and I only have one of those!).
What you're looking for are nested projects which VV doesn't have.
Others have asked for it and while I can see its uses personally I prefer the render out one part and then the next etc and have a master veg that brings it all together.
I find this approach far less prone to errors, I can individually QA each bit and then it's locked down. I'd suggest being able to lock down tracks and part of the overall project would be more important than nesting.
I have been rendering and adding the avi files to other projects. Have wondered if I am retaining the highest quality by doing this. Anybody know if there is any loss? Do the files rerender when you render the project you added it to? I seems to because the time it takes to render that part of the file is about the same as the original render.
If you make no changes then there is no rerender
If you captured some video from a DV camera and did only cuts then what gets PTT is exactly the same as what the camera recorded. If you add a fade or any FX then only the section affected is decompressed, calcs done on it and recompressed. The remainder of the frames stay just as the camera recorded them.
Also I'd add that the VV codec is excellent, test done show you can rerender 99 times with no noticable loss of quality. In other words it isn't an issue you need to pay too much attention to.
Hi farss. No, I'm not really looking for nested projects, just the ability to bring all the content of one project into another (with event and track settings retained), and then move it around as part of one bigger project. Rendering takes away the ability to go back and make changes, or at least, it makes it a much bigger hassle.