error in module "MPEG2.dll" preventing me from creating an MPEg

brucehusker wrote on 9/3/2012, 4:22 PM

I tried doing a search for this error message, but it returned 0 results. A search on Google with the same topic produced problems with this in version 14. Has anyone experienced this with MEP Pro MX plus? I just spent the last week editing a wedding day and night and now I can't get the resulting file to export as an MPEG2. i tried all the cheap fixes, reboot etc to no avail. This is actually part two of this wedding, and the first part rendered fine. Any idea what the problem could be? Could it be that I'm mixing files from 2 different cameras? (This just occured to me as I was typing.) My camera produces m2ts files and the other camera produces mpg files? I have mixed them together freely. other than that, I have no thoughts. also, I'm running Win7Pro. I did notice in my Google search, that version 14 had this problem and the fix was changing the "DEP" settings in the Windows system settings. Thast applied at the time to XP & Vista. I did check these settings in my Win7 system and they were set to the default Windows only setting. Also I just checked my first disk edit file and it also contained both types of raw files, so that's not it apparently.

Now I loaded up my disk 2 edit and tried exporting a BluRay bitrate file, but it also crashed with the same error. So I loaded up my disk 1 edit and exported a file with the same BluRay bitrate settings and it appears to be fine. This tells me it's not my Win7 system, but rather something in my Magix structure perhaps, or some effect I've applied that's mucking up the export. I'm going to try to isolate it by running an export on individual sections. I'll be back.

Thanks...Bruce

Comments

johnebaker wrote on 9/4/2012, 1:33 AM

Your description of the problem tells me it is the second part of the wedding project that has the problem and MEP is fine.

I have had this problem with a previous version of MEP which was caused by mixed audio types ie wav and mp3 files of background music and sound effects, along with the camera audio.

If you have mixed audio files try converting the additional audio to mp3 (leave camera audio alone).

In the folder where the video is you should find some files with the extension .hdp and maybe .h0 - move them to another folder and load second the project into MEP again and try to burn using the image recorder or burn to re-writeable DVD - saves wasting DVD's

HTH

John

brucehusker wrote on 9/4/2012, 7:05 AM

Hi John,

Thanks for the reply. I did have some mixed wav & mp3 sound files, but I had already converted the wavs to mp3 and that didn't help. I did locate the other file types you mentioned and moved those out of my project music folder, but that also did no good. I have been able to export as an MPEG2 portions of my disk 2, so I think I have the location of the problem narrowed down to the first third of the edit, but I can't find anything there out of the ordinary. There must be something I'm just missing. I'm going to try exporting some different types of files today in an effort to make sure it's the MPEG module that at fault. Thanks again & I'll be back!

Bruce

brucehusker wrote on 9/4/2012, 5:07 PM

Me again...I just tried to create an avi file instead of an MPEG and got the same error. Maybe I'm misunderstanding what the MPEG2.dll does. I was thinking it was for the creation of an MPEG2 file, but if that's the case, why would it hinder the creation of an avi? I'm going to try authoring a disk with my edit and see if it will burn. I'll be back.

Bruce

johnebaker wrote on 9/4/2012, 6:19 PM

IIRC mpeg2.dll is the mpeg codec file. Codec comes from Encoder Decoder so it does both jobs ie decodes mpg files to a video stream and encodes a video stream to and mpeg format.

It is probable that one of the mpg files on the timeline is causing the problem, how is often not determined however you can try one of the following:

Select a some video clips and right click select Create (new) frametable, repeat this for all the video clips on the timeline. Save the project and try burning to disc

Tip - use a rewriteable DVD so you can erase it and re-use it if the encode crashes.

If this fails then continue the reduction of export range in the section you have identified where the problem is.

A quick way is to use the range bar and set ranges to export ie

1. select half the portion where you know the error is

2. export it as a mpg video.

This will identify which 'half' has the problem.

Repeat steps 1 and 2 until you find the 'bad section'

Remove all transitions and effects in the bad section and try exporting it again.

If it exports OK then the problem is with a transition or effect, if not then it is one of the clips itself, you then need to eliminate the clip and try re-importing to the timeline

Also in the program settings make sure Automatically create frametable option is checked on the Video/Audio tab

HTH

John

brucehusker wrote on 9/4/2012, 8:11 PM

Intresting little tidbit...I took my edit file, moved to the burn menu, aythored a DVD menu, burned to a disk, and all went without a hitch. I just watched the DVD I burned and it looks and plays as it should. I am relieved but also even more puzzled than before.

Bruce

Scenestealer wrote on 9/5/2012, 2:08 AM

Hi John and Bruce

I presume the .mts file is an avchd file so I would definitely not use the "Create frame table new" command on an already edited timeline as this can completely mess up your edit points, audio sync and add black frames. Magix support do not recommend using it at all on AVC files and this is why it is unchecked in the program settings by default. It can be useful however when importing MPEG2 files from older DVD disc camcorders in solving frametable issues.

Regards

Peter

brucehusker wrote on 9/5/2012, 7:02 AM

Peter...thanks for that tip. Since I got a file to burn from my problem disk 2 edit, I'm going to finish the wedding before i go back and solve this question. (Unless it reoccurs of course) In the meantime, any further thoughts are very appreciated.

Bruce

johnebaker wrote on 9/5/2012, 1:18 PM

Hi Peter

Also thanks for the tip - I have not used the frametable command on my projects for over a year as I am importing AVCHD files

At one point I was mixing HD (just after I bought the HD camera) and mpg files (from my old camera) as Bruce is doing and found it necessary to use the frametable command to actually correct an issue with black frames from the mpg files when mixed with AVCHD.

John

Scenestealer wrote on 9/5/2012, 6:33 PM

Hi John

I guess that pretty much fits with my experience although in any situation I would only use that command after the initial import of the MPEG2 and then bring in the AVCHD, to be safe. There have been instances where using it on unedited AVC files straight after import has created truncated clips - like, 1st clip okay - 2nd and 3rd clip messed up.

Peter