MEP 2014 corrupts some VOBs when imported

terrypin wrote on 2/12/2014, 9:37 AM

This strange problem is consistently repeatable here. And does not arise in MEP 16, 17, MX, or 2013.

A small minority of the dozen or so VOB files I've dragged onto the timeline of a fresh MEP 2014 project have somewhow become corrupted, like this:

But merely changing the extension to MPG fixes it:

Also, bizarrely, if I copy the VOB first and then import that copy, the problem doesn't arise!

Even more mysterious: if I export the start containing some corruption and then import that MP4, a fragment of audio from later in the video gets added!

Or for better quality:

https://dl.dropboxusercontent.com/u/4019461/MEP2014-VOB-Import-3.jpg

Note that proxy editing is not in use.

Anyone able to reproduce please? FWIW, the few examples have been the first 'main' VOB of the set, 1 GB in size.

Or any ideas on the cause?

--
Terry, East Grinstead, UK

Comments

terrypin wrote on 2/14/2014, 3:44 AM

If anyone is curious about this strange issue, I've been able to extract a 2 MB fragment of one of those strangely behaving VOB files and have uploaded it here:

https://dl.dropboxusercontent.com/u/4019461/VTS_01_1.zip

Maybe that will give some clue as to the cause.

There's one odd difference between the playback of this fragment in MEP compared to that of the full VOB: a copied version still displays the audio corruption (but not the video corruption!) whereas the original was 'cured' in both respects.

Note that I've dropped the reference about changing the extension to MPG. Further tests (on the original full VOBs, in their HD folders) show that all that's necessary to fix them (stop all corruption) is to copy them within the folder. So, for example, VTS_01_1.VOB gives corrupted playback, but Copy of VTS_01_1.VOB does not.

As they say, go figure!

--
Terry, East Grinstead, UK

johnebaker wrote on 2/14/2014, 12:17 PM

Hi Terry

That file clip is seriously corrupted no matter what I do to it ie mpg convert etc !!!

Plus it crashed MEP while creating a proxy file - luckily MEP recovered without a restart

John

terrypin wrote on 2/14/2014, 2:15 PM

Hi John,

Yet presumably, like the full VOB, it plays fine on all previous MEP versions.

Terry, East Grinstead, UK

johnebaker wrote on 2/15/2014, 5:19 AM

Hi Terry

I should have made it clear - the clip does not play properly on anything ie :-

WMP

VLC

MEP any version

Nero player, Nero Recode

AVS Video converter, Video Editor or Video Remaker

John

terrypin wrote on 2/15/2014, 9:50 AM

Hi John,

You're right. I'd assumed my fragment would behave like the full VOB, rashly as I now see from further tests!

I assume you get something like this in all cases?
https://www.dropbox.com/s/bub291dliy3ul8o/VOB-Puzzle-PlaybackCorrupt.avi

The full VOB behaves perfectly in all of them - except MEP 2014! Here's the same section from MEP 17 for example:

https://www.dropbox.com/s/cxw49fb8uxv7ye2/VOBfromMEP17.mp4

Here are some other notes:

1. For neatness and to ensure they have no influence I removed the rest of the set (IFO, BUP,etc) to a Temp folder.
2. The original, VTS_01_1.VOB, does not play back properly.
3. The copy plays back OK.
4. The renamed VOB shown here plays back OK.
5. If the copy is renamed back to the original, that does not play back properly!

To paraphrase the Bard, "What's in a name?".

--
Terry, East Grinstead, UK

johnebaker wrote on 2/15/2014, 1:48 PM

Hi Terry

. . . . I assume you get something like this in all cases? . . .

Yes. like some one was strangling the duck in the middle .

The behaviour in naming is peculiar

. . . . To paraphrase the Bard, "What's in a name?". . . .

Better ask a rose expert

John

terrypin wrote on 2/19/2014, 10:29 AM

Magix confirm this is a known bug.

Although it doesn't seem to have affected anyone here except me, I'll include Ralf's reply in full below for anyone interested:

Worry no more about the resolution of this unsolved puzzle. This has been identified as a bug of the procedure that is supposed to handle the concatenation of VOB files, as they are subject to a strict binary split once they hit the 1 GB limit and thus frames can just get broken. Thus regular import of the individual files isn't good enough and VOB import requires special handling. This seems to be broken now. The file name is relevant in that handling mechanism, which explains why it's relevant to the problem but doesn't appear to have anything to do with the existence of associated meta files. This is more or less a known problem and already with development. It's currently a bit in limbo there and awaiting some decisions to be made. I'll bring some attention to it again and hope that will do to get things rolling.

One fewer puzzle nagging away at me.

--
Terry, East Grinstead, UK