PDA

View Full Version : still a problem with some mkv container files and samsung c-series



micha
09-02-2010, 12:45 AM
I'm using the latest version of Mezzmo (2.1.9.0) and my TV is a LE40C579, but there are still some files that won't play. Mezzmo is not trying to transcode them and my TV tells me: "video codec not supported". Maybe you could have a look into the ffmpeg output and give me a hint what the samsung TV doesn't support and change the c-profile to support the files.


here is the first video not playing:

FFmpeg version SVN-r24378, Copyright (c) 2000-2010 the FFmpeg developers
built on Jul 21 2010 12:51:48 with gcc 4.4.0
configuration: --enable-static --disable-shared --enable-memalign-hack --enable-libmp3lame --extra-cflags=-I/c/msys/local/include --extra-ldflags=-L/c/msys/local/lib --enable-zlib --enable-w32threads --extra-cflags=-fno-common --enable-gpl --enable-libx264 --disable-ffplay --disable-ffprobe --disable-ffserver --enable-postproc --enable-runtime-cpudetect --extra-cflags=-U__STRICT_ANSI__
libavutil 50.22. 0 / 50.22. 0
libavcodec 52.84. 0 / 52.84. 0
libavformat 52.76. 0 / 52.76. 0
libavdevice 52. 2. 0 / 52. 2. 0
libavfilter 1.25. 1 / 1.25. 1
libswscale 0.11. 0 / 0.11. 0
libpostproc 51. 2. 0 / 51. 2. 0
[matroska @ 016ddf70] max_analyze_duration reached
[matroska @ 016ddf70] Estimating duration from bitrate, this may be inaccurate

Seems stream 0 codec frame rate differs from container frame rate: 47.95 (20000000/417083) -> 23.98 (24000/1001)
Input #0, matroska, from 'X:\some.mkv':
Duration: 02:04:32.48, start: 0.000000, bitrate: 1280 kb/s
Stream #0.0: Video: h264, yuv420p, 1920x800, PAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc
Metadata:
title : Video
Stream #0.1(ger): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Metadata:
title : German AC3
Stream #0.2(eng): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Metadata:
title : English AC3
Stream #0.3(ger): Subtitle: [0][0][0][0] / 0x0000
Metadata:
title : German
At least one output file must be specified

and here is the second video not playing:
FFmpeg version SVN-r24378, Copyright (c) 2000-2010 the FFmpeg developers
built on Jul 21 2010 12:51:48 with gcc 4.4.0
configuration: --enable-static --disable-shared --enable-memalign-hack --enable-libmp3lame --extra-cflags=-I/c/msys/local/include --extra-ldflags=-L/c/msys/local/lib --enable-zlib --enable-w32threads --extra-cflags=-fno-common --enable-gpl --enable-libx264 --disable-ffplay --disable-ffprobe --disable-ffserver --enable-postproc --enable-runtime-cpudetect --extra-cflags=-U__STRICT_ANSI__
libavutil 50.22. 0 / 50.22. 0
libavcodec 52.84. 0 / 52.84. 0
libavformat 52.76. 0 / 52.76. 0
libavdevice 52. 2. 0 / 52. 2. 0
libavfilter 1.25. 1 / 1.25. 1
libswscale 0.11. 0 / 0.11. 0
libpostproc 51. 2. 0 / 51. 2. 0
[matroska @ 016ddf70] Estimating duration from bitrate, this may be inaccurate

Seems stream 0 codec frame rate differs from container frame rate: 47.95 (5000000/104271) -> 24.00 (24/1)
Input #0, matroska, from 'X:\some_other.mkv':
Duration: 02:11:06.21, start: 0.000000, bitrate: N/A
Stream #0.0: Video: h264, yuv420p, 1920x800, PAR 1:1 DAR 12:5, 23.98 fps, 24 tbr, 1k tbn, 47.95 tbc
Metadata:
title : Video
Stream #0.1(ger): Audio: dca, 48000 Hz, 6 channels, s16
Metadata:
title : Deutsch DTS 5.1
At least one output file must be specified


Thanks :)

Paul
09-02-2010, 10:58 AM
Contact us at support [at] concieva [dot] com, and we can supply a patch that may help.

micha
09-07-2010, 12:59 AM
Still waiting for a feedback, wrote like 4 days ago. ;)

Paul
09-07-2010, 11:02 AM
Sorry for the delay. We think we have identified the reason for the MKV problems and expect to release an update by the end of this week. Thanks for your patience.

If you cannot wait, you can download the previous version - Mezzmo v2.1.8.0 - from http://www.conceiva.com/downloads/mezzmo-setup-2180.exe

When uninstalling v2.1.9.0, make sure you select the checkbox to keep your Mezzmo library in the uninstaller.

micha
09-07-2010, 04:27 PM
It didn't work with version 2.1.8.0 either.. so i'm waiting for the update and hope the best.. :)

Paul
09-09-2010, 09:51 AM
It's possible that the frame rate of those files (23.98 fps) is not supported by the TV - I've seen a similar thing happen before. At the moment, Mezzmo doesn't support changing the framerate, but that's something which is high on our development to-do list and should be implemented soon.

To confirm, do you have another MKV file that plays? If you get FFmpeg info on that, what frame rate does it have?

micha
09-09-2010, 06:31 PM
I have some other mkv files that play.. like:



FFmpeg version SVN-r24894, Copyright (c) 2000-2010 the FFmpeg developers
built on Aug 24 2010 15:03:07 with gcc 4.4.0
configuration: --enable-static --disable-shared --enable-memalign-hack --enable-libmp3lame --extra-cflags=-I/c/msys/local/include --extra-ldflags=-L/c/msys/local/lib --enable-zlib --enable-w32threads --extra-cflags=-fno-common --enable-gpl --enable-libx264 --disable-ffplay --disable-ffprobe --disable-ffserver --enable-runtime-cpudetect --extra-cflags=-U__STRICT_ANSI__
libavutil 50.24. 0 / 50.24. 0
libavcore 0. 6. 0 / 0. 6. 0
libavcodec 52.86. 1 / 52.86. 1
libavformat 52.78. 3 / 52.78. 3
libavdevice 52. 2. 1 / 52. 2. 1
libavfilter 1.37. 0 / 1.37. 0
libswscale 0.11. 0 / 0.11. 0
[matroska,webm @ 016adfa0] Estimating duration from bitrate, this may be inaccurate

Seems stream 0 codec frame rate differs from container frame rate: 47.95 (5000000/104271) -> 23.98 (24000/1001)
Input #0, matroska,webm, from 'X:\the_other.mkv':
Duration: 01:52:25.73, start: 0.000000, bitrate: N/A
Stream #0.0(ger): Video: h264, yuv420p, 1280x688 [PAR 1:1 DAR 80:43], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc
Stream #0.1(ger): Audio: dca, 48000 Hz, 6 channels, s16
Stream #0.2(ger): Subtitle: [0][0][0][0] / 0x0000
At least one output file must be specified


or



FFmpeg version SVN-r24894, Copyright (c) 2000-2010 the FFmpeg developers
built on Aug 24 2010 15:03:07 with gcc 4.4.0
configuration: --enable-static --disable-shared --enable-memalign-hack --enable-libmp3lame --extra-cflags=-I/c/msys/local/include --extra-ldflags=-L/c/msys/local/lib --enable-zlib --enable-w32threads --extra-cflags=-fno-common --enable-gpl --enable-libx264 --disable-ffplay --disable-ffprobe --disable-ffserver --enable-runtime-cpudetect --extra-cflags=-U__STRICT_ANSI__
libavutil 50.24. 0 / 50.24. 0
libavcore 0. 6. 0 / 0. 6. 0
libavcodec 52.86. 1 / 52.86. 1
libavformat 52.78. 3 / 52.78. 3
libavdevice 52. 2. 1 / 52. 2. 1
libavfilter 1.37. 0 / 1.37. 0
libswscale 0.11. 0 / 0.11. 0
[matroska,webm @ 016adfa0] Estimating duration from bitrate, this may be inaccurate
Input #0, matroska,webm, from 'X:\yet_another.mkv':
Duration: 01:36:37.54, start: 0.000000, bitrate: N/A
Stream #0.0(eng): Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 20k tbn, 47.95 tbc
Stream #0.1(ger): Audio: dca, 48000 Hz, 6 channels, s16
Metadata:
title : German DTS 1509kbps
Stream #0.2(eng): Audio: dca, 48000 Hz, 6 channels, s16
Metadata:
title : English DTS 1509kbps
At least one output file must be specified


So i guess it is not the framerate..

Paul
09-10-2010, 08:44 AM
Intreresting... Thanks for posting working FFmpeg info as well! I agree, at first glance the frame rates seem not to matter in this particular case. I'll need to do some more research and get back to you on this.

Do those files play via Samsung's Share Manager soft?

micha
09-10-2010, 06:32 PM
No, they don't. Maybe the used codec or some of the encoding options are the problem...

RMerlin
09-11-2010, 12:39 AM
The H264 codec supports multiple profiles and levels which determine features used by the encoder. It's possible that your video uses either a profile or a level unsupported by your TV. Check which profile (Baseline, High, etc...) and level (3.1, 4.0, etc...) your file used, with Mediainfo: http://mediainfo.sourceforge.net/en

Then, check your TV specifications to determine which profile and level are supported.

Generally speaking, a direct Blue-Ray rip done in High Profile Level 5.1 will not play on a TV or a basic media streamer like the WDTV Live.

Excellent reference for more info about H264 profiles and levels: http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC

micha
09-11-2010, 01:42 AM
That's it.. Thanks for the information. The files are indeed High@L5.1. I guess i could convert them to 4.1 and give it a try again.

Paul
09-13-2010, 08:51 AM
I wonder if there's any way in FFmpeg to get the profile level information from the file... If it was possible, we could then add that to the device profile as well. I'll need to do some research on this, but if you know a way, please let me know :) Thanks!

RMerlin
09-13-2010, 08:59 AM
I see that Mediainfo has a DLL available for third party developers - this might be worth looking at, if FFMPeg can't retrieve that information.

http://mediainfo.sourceforge.net/en/Download/Windows

From what I can see, they use a GLPL license.

I'll do some digging to see if ffmpeg could provide more information on H264 files.

Paul
09-13-2010, 09:19 AM
Thanks - great info! I'll investigate using the DLL in addition to FFmpeg if we can't get the info from FFmpeg in the first place.

RMerlin
09-13-2010, 12:28 PM
I couldn't find any way to obtain the profile information through either ffmpeg or ffprobe. I guess using Mediainfo to complement FFMpeg would be the simplest way (provided the API gives you easy access to those specific info).

Paul
09-13-2010, 12:32 PM
Thanks for your investigation! I'll dig around a bit as well and evaluate using Mediainfo's DLL too.

Paul
09-13-2010, 02:37 PM
Actually I believe that I've found where that's stored in FFmpeg. If I'm right, it's part of the AVCodecContext structure, at least it seems to be consistent with what MediaInfo reports. With this knowledge we can probably do something useful now :)