PDA

View Full Version : Playback MOV from Canon EOS 7D on Samsung



Luk
09-17-2010, 03:51 AM
Context : Canon EOS 7D, Samsung TV UE37C6820, Windows 7 (64bit), Mezzmo V2.1.9.0
Mezzmo works fine i.e. I can browse photos from/on the PC and display them on the TV, idem for video and audio.

Behaviour : The MOV files recorded with the Canon are copied on the PC's Harddisk. They can be perfectly watched with Quicktime on the PC.
When I playback a MOV file on the TV, it plays for 2-3 sec. and then switches to the next one, it plays again 2 sec. The 3rd MOV file (sometimes the 2nd) makes the TV reboot i.e. TV switches off and on again!
MOV files (not recorded with Canon) play well.
When I browse the PC's folder containing those MOV files, the thumbnails appear correctly.
Playback of a MOV file takes 2 minutes or more to start.
MOV file size = 200-500KB

Question : Does somebody have a similar experience?
Does anybody have a solution so that "I can see my kids play" on my TV screen in HD?

Paul
09-17-2010, 09:59 AM
Can you please FFmpeg information about one of those MOV files (in Mezzmo right-click on the file and use the "Get FFmpeg Information" command)?

Luk
09-18-2010, 07:29 AM
Here is the FFmpeg info you asked for.
One thing to mention also, the TV has a wired connection to the LAN via a D-Link router/switch.

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

Seems stream 0 codec frame rate differs from container frame rate: 50000.00 (50000/1) -> 25.00 (25/1)
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'K:\My Movies\My Canon Movies\20100911_Hoogstraten\MVI_2197.MOV':
Metadata:
major_brand : qt
minor_version : 537331968
compatible_brands: qt CAEP
Duration: 00:00:39.20, start: 0.000000, bitrate: 45984 kb/s
Stream #0.0(eng): Video: h264, yuvj420p, 1920x1088, 44445 kb/s, 25 fps, 25 tbr, 25k tbn, 50k tbc
Stream #0.1(eng): Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
At least one output file must be specified

Tx.

RMerlin
09-18-2010, 10:24 AM
Duration: 00:00:39.20, start: 0.000000, bitrate: 45984 kb/s
Stream #0.0(eng): Video: h264, yuvj420p, 1920x1088, 44445 kb/s, 25 fps, 25 tbr, 25k tbn, 50k tbc
Stream #0.1(eng): Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s



45 Mbits, 1920x1088 is probably using High Profile @ Level 5.1, which is rarely supported by TVs (as this is BlueRay quality). Usually, Level 3.1 or 4.1 is the highest that can be played through DLNA, at a few Mbits (check your TV specifications for details).

You can confirm the file profile by using Mediainfo: http://mediainfo.sourceforge.net/en

Luk
09-18-2010, 04:15 PM
Here is the MediaInfo of the file

General
Complete name : K:\My Movies\My Canon Movies\20100911_Hoogstraten\MVI_2197.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 215 MiB
Duration : 39s 200ms
Overall bit rate : 46.0 Mbps
Encoded date : UTC 2010-09-11 13:30:02
Tagged date : UTC 2010-09-11 13:30:02

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Baseline@L5.0
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 39s 200ms
Bit rate mode : Variable
Bit rate : 44.4 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Original height : 1 088 pixels
Display aspect ratio : 16:9
Original display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.857
Stream size : 208 MiB (97%)
Language : English
Encoded date : UTC 2010-09-11 13:30:02
Tagged date : UTC 2010-09-11 13:30:02
Color primaries : BT.709-5, BT.1361, IEC 61966-2-4, SMPTE RP177
Transfer characteristics : BT.709-5, BT.1361
Matrix coefficients : BT.601-6 525, BT.1358 525, BT.1700 NTSC, SMPTE 170M

Audio
ID : 2
Format : PCM
Format settings, Endianness : Little
Format settings, Sign : Signed
Codec ID : sowt
Duration : 39s 200ms
Bit rate mode : Constant
Bit rate : 1 536 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Stream size : 7.18 MiB (3%)
Language : English
Encoded date : UTC 2010-09-11 13:30:02
Tagged date : UTC 2010-09-11 13:30:02



I can see the Format profile is Baseline@L5.0.
This is info I found in TV's manual :
37

Does this mean I cannot play these MOV files on a Samsung UE37C6820 at all? :confused:

RMerlin
09-19-2010, 03:46 AM
The only way would be through transcoding. Unfortunately, Mezzmo is currently unable to determine the H264 profile and level used by a file, so it can't tell if a given H264 file needs transcoding or not. Conceiva is aware of the issue and are actively working on a solution.

One possible workaround would be to modify your device profile to force transcoding any H264 file that has a video size larger than 1,280720 (since Level 5.0 only supports 1920x1080 or higher, it means that you would be transcoding anything susceptible of being Level 5.0 or higher). This is something Conceiva can help you with after the weekend if you aren't comfortable with editing device profiles :) Send them an email about this at support (at) conceiva (dot) com mentioning this, and they should be able to send you back an updated profile for you to try.

For reference, the resolutions supported by various profiles can be seen on Wikipedia, under "Levels": http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC

Paul
09-20-2010, 10:06 AM
Mezzmo 2.1.10 will be profile-aware (already implemented and being tested right now), so hopefully that'll solve these issues :)