-
Some MKV Files Play for 10 Seconds then stop
With my Samsung UNC55C6500 I have a 8GB version of the movie 300 in mkv format. However, my Samsung TV (using the Samsung C profile) plays about 15 seconds of this file and then skips to the next file. The codec information is below.
Video Codec: H264 - MPEG-4 AVC (part 10) (avc1) 1280x528
Audio Codec: A52 Audio (aka AC3) (a52).
Any advice is greatly appreciated.
-
Can you please post FFmpeg information on that file (in Mezzmo right-click on the file and use the "Get FFmpeg Information" command) - most probably it's transcoding and the transcoding speed is not fast enough for smooth playback.
-
Information.
FFmpeg version SVN-r25446, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 12 2010 10:38:21 with gcc 4.4.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-mingw32- --enable-static --disable-shared --enable-zlib --disable-ffprobe --disable-ffplay --prefix=/media/windows-share/ffmpeg --extra-cflags=-U__STRICT_ANSI__ --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.81. 0 / 52.81. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.50. 1 / 1.50. 1
libswscale 0.12. 0 / 0.12. 0
[matroska,webm @ 0036d0f0] Invalid stream 3 or size 3
[matroska,webm @ 0036d0f0] max_analyze_duration reached
[matroska,webm @ 0036d0f0] 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 'F:\Movies\720p\300.mkv':
Duration: 01:56:32.57, start: 0.000000, bitrate: 640 kb/s
Stream #0.0(eng): Video: h264, yuv420p, 1280x528, PAR 1:1 DAR 80:33, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc
Stream #0.1(eng): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x0000
At least one output file must be specified
---> DB Level Info: 51
I doubt that it is the speed of my computer or connection. I have gigabit internet running to the TV and my PC is a 3.4ghz Phenom X4 with 4gb of ram. Other files of similar size (and even 1080p work fine).
-
Thanks for the info. Yes, that needs to be transcoded (Samsung TVs don't support playing MKVs with profile level above 41 and it's 51 in this case). Can you please send a message to support (at) conceiva (dot) com and I'll send you an updated device profile to try to possibly make transcoding faster.
-
Any chance of posting these profiles to the forum so others can download them? The problem of Samsung devices only playing small bits of video is something many of us experience and it seems like it comes down to Samsung expecting/needing both the file size and the length of the video in order to play it. Files it only plays a few seconds of are always missing either the file size or length.
Thank you...
-
The reason why these updates are not posted publicly is because they're relevant only for the current version of Mezzmo and some of them also require a patched version of the server, so posting links that will remain after a new version is released will cause more troubles than it'll solve problems. We always look at each problem individually, as some issues are not really the same, even if the symptoms appear to be the same initially.
-
Thanks for the explanation, that makes sense. I guess I'll send an email requesting the profiles. I also noticed that the db level info for a bunch of flv/mpg/avi files are -99. Here's a sample... What does -99 mean?
FFmpeg version SVN-r25446, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 12 2010 10:38:21 with gcc 4.4.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-mingw32- --enable-static --disable-shared --enable-zlib --disable-ffprobe --disable-ffplay --prefix=/media/windows-share/ffmpeg --extra-cflags=-U__STRICT_ANSI__ --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.81. 0 / 52.81. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.50. 1 / 1.50. 1
libswscale 0.12. 0 / 0.12. 0
[mpeg @ 0126cff0] max_analyze_duration reached
Input #0, mpeg, from 'H:\Videos\TV\NCIS\NCIS Season 1\Pilot 1_000 - Meltdown.mpg':
Duration: 00:44:11.81, start: 0.232644, bitrate: 1392 kb/s
Stream #0.0[0x1e0]: Video: mpeg1video, yuv420p, 352x240 [PAR 200:219 DAR 880:657], 1150 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 29.97 tbc
Stream #0.1[0x1c0]: Audio: mp2, 44100 Hz, 2 channels, s16, 224 kb/s
At least one output file must be specified
---> DB Level Info: -99
-
Nothing really, level is not relevant for all formats and means different things for different formats. At the moment we only use it with MKVs.
-
T-valdeuc_3000.6
I had the same problem here. Stopped playing after a few sec with files with DB level info: 51. Though after I updated my TV with the new firmware (3000.6; I got a UE37C6700) one of the two files actully does play, though the sound volume fluctuates during play.:
=====
FFmpeg version SVN-r25446, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 12 2010 10:38:21 with gcc 4.4.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-mingw32- --enable-static --disable-shared --enable-zlib --disable-ffprobe --disable-ffplay --prefix=/media/windows-share/ffmpeg --extra-cflags=-U__STRICT_ANSI__ --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.81. 0 / 52.81. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.50. 1 / 1.50. 1
libswscale 0.12. 0 / 0.12. 0
[matroska,webm @ 013eccc0] max_analyze_duration reached
[matroska,webm @ 013eccc0] 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:\BluRay\The Matrix Trilogy\The Matrix Revolutions 2003.mkv':
Duration: 02:09:15.93, start: 0.000000, bitrate: 640 kb/s
Stream #0.0(eng): Video: h264, yuv420p, 1920x800, PAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc
Stream #0.1(eng): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x0000
Stream #0.3(swe): Subtitle: [0][0][0][0] / 0x0000
At least one output file must be specified
---> DB Level Info: 51
======
The other one still doesn'nt:
======
FFmpeg version SVN-r25446, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 12 2010 10:38:21 with gcc 4.4.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-mingw32- --enable-static --disable-shared --enable-zlib --disable-ffprobe --disable-ffplay --prefix=/media/windows-share/ffmpeg --extra-cflags=-U__STRICT_ANSI__ --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.81. 0 / 52.81. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.50. 1 / 1.50. 1
libswscale 0.12. 0 / 0.12. 0
[matroska,webm @ 0124ccc0] max_analyze_duration reached
[matroska,webm @ 0124ccc0] 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:\BluRay\The Matrix Trilogy\The Matrix Reloaded 2003.mkv':
Duration: 02:18:15.52, start: 0.000000, bitrate: 640 kb/s
Stream #0.0(eng): Video: h264, yuv420p, 1920x800, PAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc
Stream #0.1(eng): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x0000
Stream #0.3(swe): Subtitle: [0][0][0][0] / 0x0000
At least one output file must be specified
---> DB Level Info: 51
=======
Any chance this helps in making it work? I would love to have the DB-level-51-files work as well.
Last edited by eynickey; 11-06-2010 at 02:01 AM.
Reason: typo
-
To see if the TV supports this profile level (51) natively you can try using the "Samsung BDP" device profile - that will pass those files through without transcoding.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks