V8b crashes on HDV import: "mcmpegin.dll"

john-beale wrote on 4/17/2008, 2:19 PM
I've been using Vegas 8b for several projects with no problems. Now, under strong time pressure to get this job finished, the program crashes when displaying a HDV file (no edits at all- just scrubbing the timeline with single HDV file on it). Why does this happen!?

An error occurred during the current operation.
An Exception has occurred.

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x2321735C
In Module 'mcmpegin.dll' at Address 0x23200000 + 0x1735C
Thread: VideoCache ID=0x1028 Stack=0x3AFF000-0x3B00000

------------
Note- my other programs, like Womble and Nero Showtime, play this file 100% ok.

Comments

john-beale wrote on 4/17/2008, 8:57 PM
A bit more background: I had actually converted the 1080i HDV to Cineform AVI. An overnight render hung on one of the clips in the AVI (which seemed fine during edit). "cancel render" did not work. After closing Vegas through the task manager and opening the project again, the entire clip shows as red frames in the timeline and black in the preview window. It did NOT do that during the edit session. I tried moving the clip to a different drive; had the same problem. I tried opening just that clip in a separate Vegas session with no edits; same problem.

Then I tried importing the original .m2t and there was a black frame at the moment the problem occurred, but it seemed "contagious": once playback reached that frame, then over a period of a few seconds (real time) the entire clip on the timeline went black, where initially it had shown valid images across the full clip.

After that I recaptured the problem section from the HDV tape, deleted the problem clip in the original project and put in the new HDV clip. Now the render is working ok. But really, what is going on here? Seems like two issues: 1) some tape glitch during reading causes a bad frame, but even worse, 2) strange or non-existent error-handling within Vegas, not only on the HDV .m2t but also Cineform Intermediate AVI file.
blink3times wrote on 4/17/2008, 9:11 PM
I get red frames every so often and I find that it's related more to the cam or the tape. The red frames are an indication that Vegas hasn't a friggin' clue what's on the timeline usually because of a bad capture (ie: dirty tape head, dropped frames, tape used too many times, tape too new and not used enough.....etc)

The last capture I did had a lot of dropped frames on the first clip (about a 15 second clip) and sure enough when I put it on the time line I had some red frames. Some times you can clip the red frames out and successfully render, and yet other times the whole clip is trash.
Videojohn wrote on 4/19/2008, 4:23 PM
Hi jbeale,
I'm having EXACTLY THE SAME PROBLEM!
I also captured my HDV footage 720p (from the JVC GY-HD111E) with connect HD 2.1, and I've had a LOT of problem with importing the .m2t files in Vegas (Pro 8.0b) Media Pool. I soon as I scrubbed, Vegas crashed and show the same error message that you indicate.

So I send this message to Sony support, and they answer that maybe the installation of Vegas was corrupted and that I should reinstall Vegas (with editing the registry). I did so, but in the mean time I reimported my footage by converting (with cineform) to .avi intermediate.

So I'm now editing .avi intermediate files. ANd I have exactly the sme pb than you have. It is not red frame appearing at the begining of the clip or at the end, BUT the whole clips and after the all the oictures in the timeline turning RED, and then the preview window is black (no pictyure appear.

Until now my "method" is to close Vegas and reopen it. And it works... until the next Red-crash!!!!

What a headache! until now I did not find any solution so I continue to edit with those very bad conditions because I have very hight pressure to finish the project.

Did youu finally find any solutionj from your side?

Could it be a VEGAS BUG? (since it semmes that we are various to havve the same problem) HOW CAN WE FIX THIS?
JJKizak wrote on 4/19/2008, 4:32 PM
I believe you have to use the latest Cineform Neo to work with 8.0b but don't take that to the bank. There are several old threads on this.
JJK
Videojohn wrote on 4/20/2008, 1:13 AM
Why? it worked with previous versions of Vegas? And Vegas 8 Pro haven't been advertised to be a "professional HD editing software"?
BrianAK wrote on 4/20/2008, 5:34 AM
Videojohn,

Although both your comments should be true, there have been many threads discussing issues with 8b that you might want to review. It has been confusing as people have had issues in a variety of situations, and others none at all.

What I have found is I believe there is some type of memory allocation issue, or change, that is affects how some of us work. In my case I am working with much smaller projects, basically splitting jobs into smaller parts, with less media on the timeline.
Videojohn wrote on 4/20/2008, 12:00 PM
Ok, thanks for the note. But whatever the pb is it's always difficult to think that this problem is aleeatory or has no solution.
bruceo wrote on 4/20/2008, 1:23 PM
I have had this issue quite often with m2t's and most frequently with footage from Sony DR60 and CF recorders. It seems that Vegas is tolerant enough to import these clips to the media pool and allows you to play them in the media pool preview and these clips play fine in any media player such as WMP, but drop them on the timeline and it is all FUBAR with red frames or black frames and if any of those frames are displayed by the clip thumbnail you will get a video buffer stack dump and if you are lucky enough the scrub the timeline, when the playhead hits one of these you get a MC encoder .dll stack dump and if you try to render you will get a lockup render without being able to exit. BIG problem. I have some SDE's scheduled next month and am freaking about this issue and I may have to use FCP or Premiere to do this since 8.0c is not scheduled for release until June. SCS please release it asap with this fix!!