C5500 works well with Mezzmo

Hi there, thought I can share my experience with the Samsung player and DLNA streaming.

So far I've tried the following media servers on my Win7 PC:
-Samsung PC Share Manager 4.03
-Serviio 0.4.2
-TVersity 1.9.2
-Mezzmo 2.1.11.0

I gave up with Samsung soft very quickly as I wasn't able to share external folders. I tried Serviio then, and even play/pause worked fine I couldn't get external subtitles to work. The same was with TVersity software. Finally I tried Mezzmo and so far everything works fine. It has dedicated profile for Samsung BDP players and external subtitles works fine as well as pause/FF/REW functionality however I still need to do that with left/right buttons on the remote.

Canon T3i vs T2i

I have a Samsung TV LN32C550 and it works fine too! (subtitles and all).

The only bug I've found is that it doesn't transcode MOV (Quicktime) movies. At least my Samsung model can't handle MOV files. These are the supported file types from the LCD manual:

http://img839.imageshack.us/img839/206/supported.png

The profile I'm using is "Samsung C". Probably the profile doesn't match my TV specs.

Anyway, I really don't care much because MOV files are quite rare.

Thank you!

Regaring those MOV files - can you please post FFmpeg information on one of those (in Mezzmo right-click on the file and use the "Get FFmpeg Information" command) and we'll test it here?

This is the information you requested:

Code:

---

ffmpeg version git-N-30186-gd9d5603, Copyright (c) 2000-2011 the FFmpeg developers
  built on May 25 2011 12:16:07 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/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --pkg-config=pkg-config
  libavutil    51.  2. 1 / 51.  2. 1
  libavcodec  53.  6. 0 / 53.  6. 0
  libavformat  53.  2. 0 / 53.  2. 0
  libavdevice  53.  0. 0 / 53.  0. 0
  libavfilter  2. 10. 0 /  2. 10. 0
  libswscale    0. 14. 0 /  0. 14. 0
  libpostproc  51.  2. 0 / 51.  2. 0

Seems stream 0 codec frame rate differs from container frame rate: 47.95 (48000/1001) -> 23.98 (2997/125)
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\Gonza\Videos\Movie 1.mov':
  Metadata:
    major_brand    : mp42
    minor_version  : 0
    compatible_brands: mp42mp41
    creation_time  : 2011-02-23 00:52:48
  Duration: 00:12:05.01, start: 0.000000, bitrate: 6522 kb/s
    Stream #0.0(eng): Video: h264 (Main), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 6358 kb/s, 23.98 fps, 23.98 tbr, 23976 tbn, 47.95 tbc
    Metadata:
      creation_time  : 2011-02-23 00:52:48
    Stream #0.1(eng): Audio: aac, 48000 Hz, stereo, s16, 157 kb/s
    Metadata:
      creation_time  : 2011-02-23 00:52:48
At least one output file must be specified


---> DB Level Info: 42

---

Thanks for the info - we'll do some testing here to see if these file types need to be removed from the device profile.

It may be possible that there's something in the encoding of that specific file that prevents its playback, since MP4 files are generally supported (albeit they are a little bit different to MOV files on the container level).

Ok thank you. Talking about this brought me an idea.

By now you'd probably know that it's not a simple task to cover all TV models using profiles. Sometimes there are certain files that according to the profile should be played fine, but don't (like my case). So, I was thinking that it would be nice to add an option in the library to force certain files to be transcoded. Something like:

Right Click on the desired file -> "force transcode".

There are also other situations that could benefit from this. Like when the video type is compatible with the TV but it doesn't fullfill other requeriments to be played. For example, in my TV H264 is playable but only upto profile 4.1 or certain amount of stored frames depending on the resolution of the video.

Yes, that'll be part of pre-transcoding available in the release after the next one :)

The profile levels are already part of the device profile, but sometimes it's not enough - sometimes it's something else inside the file encoding itself, which we cannot easily deduce.