Freshly reinstalled Sony Vegas won't open the video edits I produced with it before
August 29, 2011 12:06 PM   Subscribe

I recently had to reinstall Windows (XP) on my PC to kill some malware. Subsequently, I reinstalled Sony Vegas Movie Studio 9, which I've been using for the last couple of years on this machine. Today I went to open one of my video edits for the first time... but Vegas chokes on it. Can you help me figure out why? Error log after the jump.

When I open my edit, the whole thing appears to load... but right at end, I get a dialog that says this:


An error occurred during the current operation.

An Exception has occurred.



When I click "Details", I get this:


Vegas Movie Studio Platinum 9.0
Version 9.0b (Build 92)
Exception 0xC0000005 (access violation) READ:0x30 IP:0x6E08EE
In Module 'VegasMovieStudioPE90.exe' at Address 0x400000 + 0x2E08EE
Thread: GUI ID=0x4C4 Stack=0x126000-0x130000
Registers:
EAX=00000000 CS=001b EIP=006e08ee EFLGS=00210246
EBX=09e19d00 SS=0023 ESP=00126280 EBP=001262e4
ECX=00000001 DS=0023 ESI=2887cf80 FS=003b
EDX=09d7d5e4 ES=0023 EDI=0000000c GS=0000
Bytes at CS:EIP:
006E08EE: 83 78 30 00 74 60 8B 48 .x0.t`.H
006E08F6: 30 DD 40 50 8B 51 04 DD 0.@P.Q..
Stack Dump:
00126280: 00000000
00126284: 09937848 09810000 + 127848
00126288: 00008061
0012628C: 000509AE 00030000 + 209AE
00126290: 00126288 00030000 + F6288
00126294: 001262B4 00030000 + F62B4
00126298: 77D4B7AB 77D40000 + B7AB (USER32.dll)
0012629C: 00AEC8B0 00400000 + 6EC8B0 (VegasMovieStudioPE90.exe)
001262A0: 01AEAA98 01A50000 + 9AA98
001262A4: 00000001
001262A8: 0000001C
001262AC: 00000007
001262B0: 056BC208 05320000 + 39C208
001262B4: 00050A1A 00030000 + 20A1A
001262B8: 005A5730 00400000 + 1A5730 (VegasMovieStudioPE90.exe)
001262BC: 000509AE 00030000 + 209AE
> 001262C0: 77D4B4A9 77D40000 + B4A9 (USER32.dll)
> 001262C4: 005B0C6D 00400000 + 1B0C6D (VegasMovieStudioPE90.exe)
001262C8: 00040A0C 00030000 + 10A0C
001262CC: 00000000
001262D0: 00000001
001262D4: 00000000
> 001262E0: 00418212 00400000 + 18212 (VegasMovieStudioPE90.exe)
001262E4: 00050A1A 00030000 + 20A1A
> 001262E8: 0041823E 00400000 + 1823E (VegasMovieStudioPE90.exe)
001262EC: 09937848 09810000 + 127848
> 001262F0: 7C8097AD 7C800000 + 97AD (kernel32.dll)
001262F4: 00008061
001262F8: 00000000
> 001262FC: 00401B59 00400000 + 1B59 (VegasMovieStudioPE90.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0085815B 00400000 + 45815B (VegasMovieStudioPE90.exe)
0012FFFC: 00000000


Can anyone shed light on this?

Unfortunately, most of the Vegas-related discussion threads I've found via Google offer generic advice like "try reinstalling Vegas". In my case, reinstalling Vegas was actually the source of the problem. I'm hoping someone can see something in that error spaghetti that might suggest another remedy. Thanks!
posted by Artifice_Eternity to Technology (11 answers total)
 
Further details: I've just determined that some of my edits will open, while others will crash Vegas. And I'm starting to suspect the issue has to do with edits that contain QuickTime files.

I know that Vegas has had problems with certain kinds of QT files. I've downloaded Sony's replacement qt7plug.dll file and put it in the proper driver folder (as I recall doing previously when I first started editing QuickTime files in Vegas).

But I just realized that I don't even have QuickTime itself installed on my computer at the moment! I'm remedying this now, and will report on whether it fixes Vegas.
posted by Artifice_Eternity at 12:32 PM on August 29, 2011


Also, you may want to update to 9.0e from the following website:

http://www.sonycreativesoftware.com/download/updates/vegasfamily

Maybe something between version b and version e fixes this. Especially if the old install was on version e and you haven't updated this one yet.
posted by deezil at 12:35 PM on August 29, 2011


Errrr crap, that was for Vega Pro, not Vegas Platinum... disregard.
posted by deezil at 12:35 PM on August 29, 2011


Alas, reinstalling QuickTime does not seem to have made Vegas able to read the edits in question, even after I rebooted my machine.

deezil, I'll poke around and see if I can find some kind of update for my version of Vegas that might be useful.
posted by Artifice_Eternity at 1:00 PM on August 29, 2011


Keep in mind that "Quicktime" is just a container and that there are hundreds of QT codecs.

My guess would be that you no longer have the codec needed to read those files. See if you can find out what codec they are (H264 is a usual suspect) and then reinstall that. You can probably find the codec name somewhere under "properties" of the .mov file.
posted by drjimmy11 at 1:22 PM on August 29, 2011


Thanks, drjimmy11. I've opened a couple of the files in QuickTime, and the Movie Inspector shows the codec is H.264.

Since my last post, I actually uninstalled and reinstalled Vegas, in the hopes that it would now be able to use the codecs installed with QuickTime. QT must have the H.264 codec, since it's reading these files, but apparently Vegas can't use it.

Not sure what to try next.
posted by Artifice_Eternity at 1:57 PM on August 29, 2011


If this is a codec problem, FFDShow might help.
posted by neckro23 at 2:49 PM on August 29, 2011


neckro23: Thanks... I actually installed FFDshow earlier this afternoon, to no avail. I also installed X264VFW, SUPER, and VLC. And following advice I saw elsewhere, I uninstalled QuickTime 7.7 and installed 7.6 instead.

So far, nothing has worked.
posted by Artifice_Eternity at 2:59 PM on August 29, 2011


Here's a new discovery: If I start a new project, I can import some of the questionable MOVs into it. But when I put them in the timeline, they show up as audio files only -- there's no video track.
posted by Artifice_Eternity at 3:01 PM on August 29, 2011


All right, after much frustration, I may have found a workable, if less-than-optimal, solution.

Just now I was able to open one of my edits that was previously crashing Vegas, by moving all of the MOVs out of the folder where they'd been living. Vegas opened the edit, and asked me where the missing MOVs where. I told it to leave them all offline. It proceeded to open the edit without further problems.

Next I will try converting the files to AVIs, and seeing if Vegas will read them. I've already done this with one of my edits that contained a single MOV; when I substituted an AVI version, Vegas swapped it right in, using what appears to be the correct section of it in the edit.

I don't understand what missing piece of the codec puzzle is causing this problem, but I'm at the point where I'd rather stop fighting it and just work around it.

It sucks because I generate a lot of video footage using a pair of Kodak Zi8s, which output MOVs (and which in fact were the source of the MOVs that Vegas is now choking on)... so going forward, I may have to convert all the files that come from those cameras before I can edit them. C'est la vie. I'm just glad not to have lost access to my edits.
posted by Artifice_Eternity at 4:57 PM on August 29, 2011


Final update: Last night I converted 31 H.264 QuickTime files to Xvid AVIs, keeping the data rate and other characteristics the same.

I was able to replace the media in the edit without a problem. All of the effects and filters I'd applied to the clips in Vegas are still intact.

Looks like I'll be doing this with my other clips and edits as well.
posted by Artifice_Eternity at 9:35 AM on August 30, 2011


« Older i thought tumblr was supposed to make blogging...   |   Where can I find great scratching hip-hop music? Newer »
This thread is closed to new comments.