Hi,

I tried all 7 MKV files in MEP 2014 and only Suzimya was successful. Here are the detailed results:

https://dl.dropboxusercontent.com/u/4019461/MEP2014-MKV-Tests.jpg

I would suggest that you raise a ticketed support request. I don't currently use MKV files but I may do at some future time, so I too would like to know why MEP doesn't support them properly.

--
Terry, East Grinstead, UK

Hi

. . . . MEP doesn't support them properly . . .

The problem with mkv files is that they are a container format file whcih can hold multiple seperate videos within the container.  The seperate internal videos can be of any video format that is available and it is this that causes the probem.

If you do not have the intenal video file codecs installed then the files cannot be read. For a detailed list of files formats the mkv supports see here

DIVX is not MKV - the MKV is one of the many file formats supported by the DIVX player,and DIVX converter 

HTH

John

If you do not have the intenal video file codecs installed then the files cannot be read.

Morning John,

What I don't understand is why other players have no problem with any of those 7 widely varying MKV files? They are either using my system's installed codecs or the player's own built in versions, but in either case why is MEP not capable of doing the same?

Terry, East Grinstead, UK

Hi Terry

AFAIK - WMP and VLC do not share their codecs with any other applications. 

If you have other players they also may not share their codecs with other applications.

AFAICS - MEP can only use its own codecs, those which are installed with Windows or installed by other applications and are allowed to be shared.

HTH

John

Hi,

My point of view is to transform the MKV file in another file, more universal system, MKV try to attract users and keep them in a close system. The system is very good but limited to work inside this system. In the past DIVX try to implant his system in video player with limited success.

Video must be universal not limited to only one system. Are you ready to pay much more when you purchase a player to obtain DIVX certified reader? Do you need this certification?

Regards,

YR

Hi John,

My point is that if the developers of those other players (some virtually one-man bands, like VideoLan and the authors of MPC, MPC-HC and others) can do it, then why can't MAGIX?

Terry, East Grinstead, UKh

Hi terry

. . . . My point is that if the developers of those other players (some virtually one-man bands, like VideoLan and the authors of MPC, MPC-HC and others) can do it, then why can't MAGIX? . . .

That is one view however . . . .

The 'Windows standard' is for common dlls, codecs etc, to be installed once and be shared with all programs where needed. 

Gone are the 'bad old days' when each program had its own set of files eg Visual C runtimes, which were duplicated each time a different program was installed.

It is the likes of VLC etc  who are being non standard.

This in one sense a good thing because eg VLC can play almost anything because it has all the necessary codecs in its package - but it is bad in another sense in that it is unwilling to share    - which in itself may be a good thing if the codec packs it uses are non standard.

As you an see it is all swings and roundabouts and convoluted logic. 

HTH

John

Hi johnebaker.

I've not understood if you are a member of the Magix developer team or simply a moderator. I'm a developer.
What I know is that if a customer buys a software with a declared feature, the only thing that could happens is a bug about that feature. And the developer (Magix) has only one thing to do: admit that there is a problem and try to solve it. No other excuses. I've tried an other, much less famous software, to do what I have to do (Xilisoft DVD Creator). It works perfectly and I'm thinking to buy it and forget to spent money to buy MEP. Ok, it's less powerful, a lot feature less, but the market is wide.
If there is the willing to solve the problem, think I can wait ( a month ).
Often the thing that makes the difference is the customer support.

Regards

Hi,

John's a moderator, and this is a user forum, with no significant participation by Magix.

Did you raise a formal ticketed support request as I suggested? Refer them to this thread for more detail.

--
Terry, East Grinstead, UK

Hi

I have tested four of the files and agree with Terry - only suzumiya.mkv loads into MEP.

Of the four files I downloaded, two of them have headers stripped for the internal video file and the third has a very none standard resolution and no audio.

The 4th file suzumiya.mkv is standard 720p NTSC however it does use the Vorbis audio codec which MEP can handle.

Header stripping may IMHO, as I understand it, be the cause of the problem with 2 of the files - MEP cannot determine the frame start points which have been stripped and stored in the header file.

The third file should not in theory cause a problem, however MEP is baulking at it.

John

Hi Terry, just done. 

Thanks for the support.

Luca

Hi,

some news about the only file that MEP is able to read ("Suzumiya").

I've used the Matroska tool downloadable from its website: mkvalidator.

Here the details:

mkvalidator.exe --details h264_720p_hp_5.1_3mbps_vorbis_styled_and_unstyled_subs_suzumiya.mkv

WRN201: Unknown 'FlagEnabled' for read profile 'matroska v1' in TrackEntry at 4360
WRN201: Unknown 'CodecDecodeAll' for read profile 'matroska v1' in TrackEntry at 4360
WRN201: Unknown 'FlagInterlaced' for read profile 'matroska v1' in Video at 4532
WRN201: Unknown 'FlagEnabled' for read profile 'matroska v1' in TrackEntry at 4555
WRN201: Unknown 'CodecDecodeAll' for read profile 'matroska v1' in TrackEntry at 4555
WRN201: Unknown 'FlagEnabled' for read profile 'matroska v1' in TrackEntry at 9060
WRN201: Unknown 'CodecDecodeAll' for read profile 'matroska v1' in TrackEntry at 9060
WRN201: Unknown 'FlagEnabled' for read profile 'matroska v1' in TrackEntry at 15825
WRN201: Unknown 'CodecDecodeAll' for read profile 'matroska v1' in TrackEntry at 15825
WRN201: Unknown 'FlagEnabled' for read profile 'matroska v1' in TrackEntry at 21714
WRN201: Unknown 'CodecDecodeAll' for read profile 'matroska v1' in TrackEntry at 21714
WRN103: Unnecessary secondary SeekHead was found at 32211120
WRN0C0: First Block for video track #1 in Cluster at 912353 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 4568128 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 6829488 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 7833356 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 9459660 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 12754784 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 15631207 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 19137679 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 21733168 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 24556084 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 28113279 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 29195338 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 31940807 is not a keyframe
WRN0D0: There are 5042 bytes of void data

mkvalidator 0.4.2: the file appears to be valid
Track #1    V_MPEG4/ISO/AVC 3408331 bits/s
Track #2           A_VORBIS 139791 bits/s
Track #3         S_TEXT/ASS 640 bits/s
Track #4         S_TEXT/ASS 218 bits/s
Track #5        S_TEXT/UTF8 100 bits/s
        file created with libebml v0.7.7 + libmatroska v0.8.0 / mkvmerge v2.0.0
('After The Rain Has Fallen') built on Jan 13 2007 19:58:56

Ok, it seems to be valid, but how many warnings!!! And MES is able to read it?!?!
"Planet" has only a "bytes of void data" warning and using the other tool mkclean.exe I corrent it, but MEP does not read it anyway. So, I'm almost sure the problem is some kind of pre-check (wrong or too much strict) in the reading algorithm.

Unfortunately Magix advertises it opens mkv but does not really tell you which kind and it makes magix look foolish. Most mkv's I have to work with were at the .h264 codec magix will not open it. Magix has never upgraded that part of their program and really they should just do away with stating the program takes mkv's when in fact it really don't or they need to upgrade that.