Mark Allen
Forum Replies Created
-
People will need a better description of the error message to know why it’s having a problem. What you’ve said so far sounds like what happens if I forget to turn on the hard drive where I store the video and Vegas is allowing me to tell it where the files are. When that happens to me I close Vegas without saving, make sure the files are where they belong, and restart Vegas. Then everything loads properly.
If your .VEG file (the project file) has somehow been damaged then you’ll need someone more experienced to help. But the first thing I’d try if you haven’t been making backups of your .VEG file is run through some old autosaves and see if any of them are better than what you’ve got. They’re in the “C:UsersAppDataLocalSonyVegas Pro10.0” directory.
-
I saw the same thing with a much larger project and ended up with the same solution. I just added the clips a dozen or so at a time until all were part of the project and that avoided the crashes. This was a while ago but I believe my workflow at the time was converting .MOVs from a 7D to AVI using NeoScene and then importing the AVIs. The thing is, I think that it happened to me with Vegas 9 pro rather than 10 pro. Since then I’ve just imported the .MOVs directly into 10 pro and I don’t think I’ve seen the problem since.
Anyhow, I found the workaround so that particular kind of crash never bothered me too much. Personally, I automatically save without thinking about it before I’m going to do a long series of undos. That’s crashed on me so many times that the save has become almost a reflex.
Regarding your CPU fan, that’s normal behavior. With a good heatsink, the temp in a modern CPU can go up or down extremely quickly and the CPU fan speed will follow along with it. You could install something like RealTemp to see if the CPU fan is doing its job but probably it is. This kind of crashing is more likely software than hardware but you can torture test with Prime95 in torture test mode to be sure. If your machine can run that for 24 hours without an error then your CPU is likely not the problem. But I’ve seen this problem on my machine which is rock solid and I just ended up doing what you did.
-
If you don’t mind a couple of extra steps to get your MPEG-2 output then a possible solution would be to output to a free lossless encoder format like Lagarith as an AVI file and then use an AVI to MPEG-2 converter to generate at your desired bitrate. I haven’t used it but TMPGenc can make the conversion. There are probably free MPEG-2 converters which can also do the job.
-
It’s been a long time since I’ve used the non-pro version of Vegas but I believe losing the MPEG-2 custom button was one of its limitations. At least, that’s what I recall. Limited number of tracks I remember clearly (picture Edvard Munch’s The Scream). Losing some of the rendering custom buttons I believe was also a limitation.
-
For #2:
I normally do it by clicking the first event on the video timeline I have to move, then ctrl-click the audio which goes with it. That selects the first event on both the video and audio tracks which needs to move. Then right-click on one of the selected events and do “select events to end”. That will select all the video and audio to the right. You can do that for as many tracks as you need. Now just drag them to the left to line them up. If you’re grouping events then you’ll want to “ignore event grouping” before doing this.
Now that I think about it, I think most people use “Post edit ripple” to do that. I’m just used to doing it manually. Take a look at the “post edit ripple” entry on the “Edit menu”. It’s pretty self-explanatory. Post edit ripple can also move your markers if you use them.
Sometimes I find myself moving big stretches of events around between tracks. In cases like those there’s no way for rippling to know where I want them so you just get used to moving them around as a group manually. But for a simple delete, ripple editing gets it done with little fuss.
-
I haven’t used Vegas to capture from my HV30 in quite a while. I just tried it and got the same error message. Huh? Then I tried it again and realized that I didn’t select “HDV” when the “Capture video” dialog box shows up. I got the error message when I just left it at the “DV” default. Set it to “HDV” and give it another try.
If that’s not your problem then I’d just use HDVSplit. Many people use it and I’ve had no problems with it.
-
I’m running a very similar 8GB 10d pro system without problems. Okay… with the occasional crash which isn’t out of the ordinary. I’d run Prime95 in torture test mode and make sure to override the memory settings so it accesses your whole 8GB. I’ve had RAM which would pass MemTest86+ but gets flaky when the CPU is heavily loaded. Vegas can do that even when not rendering. RAM should pass both MemTest86 and Prime95 before it’s considered reliable.