Stephen Mann
Forum Replies Created
-
No. It just means that when you double-click on a veg file, Windows starts Vegas Pro 10 and open the veg project.
If you need to open a Version 9 project, just double click on the Pro 9 icon – not the veg file, then drag the veg file to the blank project.
You should probably back up your V9 veg files because when you save a project from V10, you can’t open it again in V9.
FWIW – I installed V10 in mid project, I have that much confidence in my PC and in Sony Vegas, and I am quite pleased with the performance and feature improvements.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I’ve been using Vegas since Version 3, and I’ve never used nor needed the trimmer. I learned to edit on the timeline and using the trimmer would certainly slow me down. I think it’s there for people familiar with the old editing paradigm of Premiere and FCP.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
DVD Burners are cheap. If it isn’t your problem then you have a spare. Is this your only PC?
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
No idea, but I use hdvsplit instead of the capture program in Vegas. It’s a small program that only captures HDV from tape.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Put the event on the timeline, right click on it, open properties, general.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
You are describing two actions – the ‘markers too close’ error comes when you are preparing the DVD, and you say that it stops burning at 65%.
If it ALWAYS stops at 65% then it could be that you have a flaw in the media – go back to Vegas and encode the MPEG and AC3 files again. Also, make sure your temp and destination folders are not getting full.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
It’s been years since I had to use Premiere, but I believe that I am correct that Vegas is unique as a non-destructive editor.
This is not fact, but my observation as a programmer from a prior life. I would really appreciate if someone from SCS would confirm or squash my hypothesis.
In a destructive editor, you are making changes to the media as you edit. Therefore, you have edited media to offload to the GPU for preview. In a non-destructive editor, like Vegas, your instructions on the timeline are simply instructions of how to generate your output when you go to “render as”. During preview, Vegas has to construct each frame from the instructions in the veg file. It makes a bitmapped image of each frame for display. There’s nothing that a GPU can do for preview. In fact, using the GPU could well slow the process.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Vista is the second-worst OS that Microsoft made. Windows 7 makes up for that mistake.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
OK, short test this morning.
I have a quad-core HP desktop that has just barely enough horsepower to edit HDV and get real-time preview.
I have an HDV project that has a lot of effects and compositing that brings this system to its knees in Version 9. I had to do RAM preview because changes on the timeline took seconds to show up in preview.
Version 10 – world of difference. I can use the scroll wheel on this project and I get full-speed previews even on events with six NewBlue FX and two Sony FX.
This is turning out to be the best upgrade of Sony Vegas yet.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I don’t see your problem. What’s wrong with nested veg files? I can’t see where what you are describing is any different.
Steve Mann
MannMade Digital Video
http://www.mmdv.com