PDA

View Full Version : samsung d series smart tv codec not supported



troyb1
06-29-2012, 05:29 PM
im getting a video codec not supported using the samsung d profile. the codec is the same as all the other videos that run fine. thanks for your help!

ffmpeg version N-40693-gc457a29 Copyright (c) 2000-2012 the FFmpeg developers
built on May 15 2012 12:57:14 with gcc 4.6.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --enable-static --disable-shared --enable-zlib --disable-postproc --prefix=/home/peter/ffmpeg/build/gpl --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --extra-cflags=-I/home/peter/cc/include --extra-ldflags=-L/home/peter/cc/lib --pkg-config=pkg-config --disable-w32threads
libavutil 51. 51.100 / 51. 51.100
libavcodec 54. 21.101 / 54. 21.101
libavformat 54. 5.100 / 54. 5.100
libavdevice 53. 4.100 / 53. 4.100
libavfilter 2. 73.100 / 2. 73.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 11.100 / 0. 11.100
Input #0, matroska,webm, from 'H:\Meet.The.Robinsons.2007.1080p.BluRay.DTS.x264-hV\Meet.The.Robinsons.2007.1080p.BluRay.DTS.x264-hV.mkv':
Metadata:
creation_time : 2007-11-26 22:25:33
Duration: 01:33:40.86, start: 0.000000, bitrate: 10028 kb/s
Stream #0:0(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), s16, 1536 kb/s (default)
Stream #0:1(eng): Video: h264 (High), yuv420p, 1920x1080, SAR 1:1 DAR 16:9, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
At least one output file must be specified


---> DB Level Info: 51, 100
---> Frame rate: 23.98
---> Aspect ratio: 16:9

JohnM
06-30-2012, 01:26 AM
It would help if you could post one from a working file for comparison. The only thing that grabbed my eye was the webm.

troyb1
06-30-2012, 05:31 AM
It would help if you could post one from a working file for comparison. The only thing that grabbed my eye was the webm.

heres a working one, same video and audio codec thanks John!

ffmpeg version N-40693-gc457a29 Copyright (c) 2000-2012 the FFmpeg developers
built on May 15 2012 12:57:14 with gcc 4.6.2
configuration: --enable-memalign-hack --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --enable-static --disable-shared --enable-zlib --disable-postproc --prefix=/home/peter/ffmpeg/build/gpl --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --extra-cflags=-I/home/peter/cc/include --extra-ldflags=-L/home/peter/cc/lib --pkg-config=pkg-config --disable-w32threads
libavutil 51. 51.100 / 51. 51.100
libavcodec 54. 21.101 / 54. 21.101
libavformat 54. 5.100 / 54. 5.100
libavdevice 53. 4.100 / 53. 4.100
libavfilter 2. 73.100 / 2. 73.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 11.100 / 0. 11.100
Input #0, matroska,webm, from 'H:\American.Reunion.UNRATED.1080p.BluRay.X264-BLOW\American.Reunion.UNRATED.1080p.BluRay.X264-BLOW.mkv':
Metadata:
creation_time : 2012-06-28 05:21:26
Duration: 01:53:51.49, start: 0.000000, bitrate: 9617 kb/s
Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x1040, SAR 1:1 DAR 24:13, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
Stream #0:1: Audio: dts (DTS), 48000 Hz, 5.1(side), s16, 1536 kb/s (default)
At least one output file must be specified


---> DB Level Info: 41, 100
---> Frame rate: 23.98
---> Aspect ratio: 24:13

JohnM
06-30-2012, 08:49 AM
The two obvious differences (other than stream ids) is that the working file is at a different video resolution 1920x1040 versus the 1920x1080 for the one that fails. I doubt that is the problem if your tv can show 1080p resolution. The most likely is that the bit rate is higher for the failing file (10028kbps vs 9617kbps) and may exceed the capabilities of your system.

troyb1
06-30-2012, 09:54 AM
The two obvious differences (other than stream ids) is that the working file is at a different video resolution 1920x1040 versus the 1920x1080 for the one that fails. I doubt that is the problem if your tv can show 1080p resolution. The most likely is that the bit rate is higher for the failing file (10028kbps vs 9617kbps) and may exceed the capabilities of your system.

thanks for checking

Paul
07-01-2012, 05:41 PM
If you send us an email to support [at] conceiva [dot] com, we can send you a modified Samsung D device profile for you to try. This will transcode the (failing) file so that is does play.