-
Vegas 10e crashes constantly moments after opening project avi.dll error
Vegas keeps crashing moments after I open it with a project that has about 8 hours of footage on, and I just copied and pasted some clips and put them on the timeline twice so I could cut up clips for a trailer video of an event I did and leave the other one untouched for when I eventually make a multicam track, I shot it on three cameras. With four hours cut and pasted the project is closer to 13 hours on the timeline.
The footage is AVI converted by Cineform. A screen cap of the error information is attached to this.
I just got Vegas 10e and it crashes much more regularly than Vegas 9 did. I keep all my media on an internal drive that’s connected by an eSata cable to an external enclosure. It’s a 1TB drive and has 26 GB free on it. NTFS format. I have Vegas installed on my 2 TB E drive, run Windows 7 on my smaller C drive (250 GB), and have most of the temporary files such as prerendered video set to go to my E drive since my C drive is losing space, it has about 10 GB left free, though most of that’s got to be taken up from some kind of temporary files from my antivirus or something. But it’s been that way for a while, so I don’t know if I can blame that.
Here are my system specs.
Intel i7 3.07 Ghz
12 GB DDR3 RAM
AMD Radeon HD 6800I’m thinking I’ll try just shortening the length of the project. I’m kind of lazy and hate going through project media more than once to put it on the timeline, so what I always do is lay out everything on my timeline on the left, and either cut footage from there and put it on the right side of the timeline for video or will copy and paste footage to the right side of the timeline and cut it, that way I feel I can always refer back to the original, uncut footage easily. But in this case I may have to free up some of the timeline, though I have to think Vegas and my computer can handle 13 hours of footage.
Edit: After some searching, I realize the avi.dll error has been a long time problem for people. But I’m not sure why it’s coming up for me now.
It also turns out that some of my project properties weren’t matched up to my footage. I had the resolution set to 1440×1080 when I shot it at 1920×1080. And I noticed that I didn’t original direct the prerendered files folder to the E drive folder I usually select for projects instead of the C drive, where it was sending them by default. But I’ve been editing this footage for hours over the course of a few days and haven’t had this problem yet. I’ve now been able to work on the project once without it crashing, but the crashes have started again.
-
3 Replies
-
What version of Cineform are you running?
Sony totally hosed Cineform in Vegas 10… in unbelievable and epic ways.
So, going back to Vegas 9, Cineform was just a plain old everyday video CODEC. You could use in Video for Windows, DirectShow, even Quicktime, and those subsystems were how Vegas talked to Cineform. Worked great, every time.
In Vegas 10, Sony added some additional magic. Not sure what the goals where, but the Cineform people put in a private API, which Vegas is using. This lets Vegas… do… something… it couldn’t do before, presumably.
The problem is, you can’t switch that off, and Vegas and/or Cineform weren’t following best software engineering practices, in several ways. For one, if you’re running a pre 5.something version of Cineform, Vegas 10 will probably just crash. What it SHOULD do is check the version of Cineform, and not try to use the magic new APIs if it sees an older, Video for Windows only version. Alas, that’s not what it does… it just crashes. So after upgrading to Vegas 10 least year, I was pretty much forced to drop another stack of bills on the Cineform upgrade.
That got me to the point where Vegas would load Cineform files. But alas, it still wouldn’t write them. Up until Vegas 10c or 10d, it crashed every single time I tried to write out Cineform. Again, best software practices would offer me a check box somewhere that says “Use VfW for Cineform”, allowing me, the user, to bypass that buggy new stuff and still get my work done… after all, the new Cineform works just dandy, still, in Vegas 9. So I got used to using DNxHD or MXF/MPEG-2 for intermediate files, given that Cineform was essentially rendered useless for most of the last year. I was still having mixed results, even with Vegas 10e… getting crashes or even completely weird rendering results with Cineform, and generally not trusting the two to not screw me over in the future.
But anyway… the answer is probably that you need to upgrade Cineform to get Vegas 10 happy. If you have NeoScene 5.x, download the latest. If not, you may have to buy the upgrade. Had I known all the trouble, I might have just fired up Vegas 9 and converted all my Cineform to DNxHD right there and then (copy those over, remove the Cineform AVIs, and Vegas will ask about replacing them… other than the huge HDD space and rending time, it’s painless).
-Dave
-
Interesting. I’m glad I waited to get Vegas 10 until now, because I have three cameras that shoot to AVCHD, which I convert to AVI using Cineform. I just updated Cineform to version 5.5.4. For now the crashes have stopped, but I’ll be using the updated version in the future. And I’ll be upgrading to 11 when that comes out, so I hope that doesn’t get screwed up.
Edit: Still crashing. I’ll restart my computer. On other projects this doesn’t happen nearly as often.
-
There is a simple reason for these crashes. I just went through the same thing and found that one of the files (a clip) that is part of the main project was not at the same frame rate as all the others. Hence, even though Sony claims to be able to handle that, you will run into issues at a certain project size. Also make sure your project properties are set to match the frame rate as well.
I discovered this the hard way. It seemed something had changed and all of a sudden I started getting those nasty aviplug.dll errors. I took the entire project off to another system that did not have Cineform on it. Same results. Hence, it purely had to do with frame rates. The change that happened and that looked as if some weird things came upon Vegas was simply that a file with a different frame rate was introduced to the project. Of course, if one does not pay attention to detail, then it may look like – “geez, all of a sudden the thing blew up for no reason.” – but as we all know, there is always a reason. 🙂
Reply to this Discussion! Login or Sign Up