Samsung UN46C8000XF: Mezzmo vs. Samsung DLNA server

[glc650]

Hi,

Using Mezzmo with a Samsung UN46C8000XF LED TV. So far I've come across a particular file + recordings (the only two I've tried so far) from my AVCHD camcorder that don't work with Mezzmo but play back just fine with the Samsung DLNA software.

1) VC-1 video in .ts container: A "file not supported" msg is displayed with Mezzmo; with the Samsung DLNA software it plays back just fine.

2) JVC AVCHD video in .mts container: Playback pauses and a "preparing file..." msg (like it is trying to buffer?) is displayed. Then the file plays for a few seconds; then pauses again with the same msg. With the Samsung DLNA software these files play through without pausing.

Thanks,

-g>.

[Paul]

Hi,

Can you please post FFmpeg information on those files (in Mezzmo right-click on the file and use the "Get FFmpeg Information" command) and also send a message to support (at) conceiva (dot) com and we'll send you an updated device profile to try.

You're using the "Samsung C" device profile, right?

[glc650]

VC-1:

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
[NULL @ 0330d6c0] start time is not set in av_estimate_timings_from_pts
Input #0, mpegts, from 'C:\Users\Garrett\Desktop\excluded from backup\BDrip\The.Dark.Knight.2008.1080p.BD-Remux.TrueHD.VC-1.ts':
Duration: 02:32:13.29, start: 600.000000, bitrate: 28587 kb/s
Program 1
Stream #0.0[0x1011]: Video: vc1, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 23.98 tbc
Stream #0.1[0x1100](eng): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.2[0x1101](eng): Audio: truehd, 48000 Hz, 6 channels, s32
Stream #0.3[0x1101]: Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.4[0x1102](eng): Audio: ac3, 48000 Hz, stereo, s16, 192 kb/s
Stream #0.5[0x1200](eng): Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: -99


AVCHD:

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

Seems stream 0 codec frame rate differs from container frame rate: 59.94 (60000/1001) -> 59.94 (60000/1001)
Input #0, mpegts, from 'C:\Users\Garrett\Desktop\excluded from backup\BDrip\test\00126.mts':
Duration: 00:00:10.75, start: 1.000022, bitrate: 22776 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 59.96 fps, 59.94 tbr, 90k tbn, 59.94 tbc
Stream #0.1[0x1100]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s
Stream #0.2[0x1200]: Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: 40

And yes I'm using the Samsung C profile as that was the one that was automatically selected.

I will email support right now.

Thanks,

-g>.

[Paul]

Thanks, I'll get back to you via e-mail shortly.

[glc650]

Ok so the VC-1 file now plays (although it paused at the very begining and show the "preparing to play... msg).

The AVCHD files are still "buffering" (pausing and showing the "preparing to play...." msg) on and off throughout each recording.

NOTE:

I only have one of the profile locations listed in the faq:

Windows Vista: C:\ProgramData\Conceiva\Mezzmo\DeviceProfiles

I don't have the other location:

C:\Users\All Users\Conceiva\Mezzmo\DeviceProfiles

When I do a search on SamsungLA.prf, the only other location that comes up is:

C:\ProgramData\Conceiva\Mezzmo\DeviceProfiles\back up

I've replaced the two files in both those locations.

[NavySEAL]

I don't have the other location:




That's normal. I only have it in the same one location as you for Windows 7

[glc650]

Ok I tried 3 or 4 more of my AVCHD recordings and they all pause and display the same msg throughout playback.

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

Seems stream 0 codec frame rate differs from container frame rate: 59.94 (60000/1001) -> 59.94 (60000/1001)
Input #0, mpegts, from 'C:\Users\Garrett\Videos\Canyon\dyno pulls\dyno pull #8 11-22-09.mts':
Duration: 00:05:41.02, start: 1.000022, bitrate: 24031 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 59.96 fps, 59.94 tbr, 90k tbn, 59.94 tbc
Stream #0.1[0x1100]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s
Stream #0.2[0x1200]: Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: 40



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

Seems stream 0 codec frame rate differs from container frame rate: 59.94 (60000/1001) -> 59.94 (60000/1001)
Input #0, mpegts, from 'C:\Users\Garrett\Videos\Everio MediaBrowser HD\HDDCAM\20100816\4757208581386797056\00001.mts':
Duration: 00:03:06.40, start: 1.000022, bitrate: 23998 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 59.96 fps, 59.94 tbr, 90k tbn, 59.94 tbc
Stream #0.1[0x1100]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s
Stream #0.2[0x1200]: Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: 40

Thanks,

-g>.

[Paul]

Can you please send us one of those files so that we could test it here? If they're larger than 10 MBs can you please upload to a service like www.megaupload.com or if they're smaller just e-mail to support (at) conceiva (dot) com - that would help us see what the problem could be.

[glc650]

I've uploaded one to megaupload:

http://www.megaupload.com/?d=LAQEZTQ4

Thanks,

-g>.

[Paul]

Thanks for the file. Interestingly, our version of PCSM doesn't even recognize this file as native (it doesn't appear in the Share Manager) - what version of PCSM do you have?

[glc650]

4.2 and I had to rename it first to .m2ts or .ts I don't remember now which extention worked but it played back without pausing.

[Paul]

Ah, ok, it's .ts and then PCSM picks it up. However, it also pauses on the TV while playing and buffers up - same as Mezzmo. It's possible that the bitrate is too high - if the file is transcoded to a bitrate below 20 Mbits then it plays fine. What's strange is that it plays ok on your system though.

[glc650]

Yea it plays just fine with the Samsung software. I only get buffering when I use Mezzmo to play it.

Are you saying Mezzmo has a 20mbit limit on h264/AVCHD files?

[Paul]

No, Mezzmo doesn't have any limits and can stream as fast as your network permits. The TV may have limits on what it can actually play, but if you can play it using PCSM then that's not it. I'll do some more testing here and see if I can find out why it's happening.

[glc650]

Yea it may just be the TV as I've also got a Samsung BD-C5900 3D blu-ray player and I tried it on there and it worked fine with Mezzmo (and PCSM after renaming the extension), although I had to switch from the default profile (Samsung BDP 3D) to Samsung C to get any files to play at all on the 5900. Is there an updated profile for Samsung Blu-ray 3D as well? I've got Samsung's flagship model (7900) coming next week. I'll try it on there as well.

Thanks,

-g>.

[Paul]

Yes, we've got updates for pretty much all Samsung profiles :)

[glc650]

So should I send another email to support (at) conceiva (dot) com and request the updated profiles for 5900 and 7900 3D BDPs or should I just continue to use and test with the Samsung C profile?

[Paul]

We're working on updating the 5900 profile right now, so it should be available within the next couple of days. So, the current "stock" "BDP 3D" profile doesn't play everything on the 5900, but the updated "Samsung C" does?

[glc650]

Yea the stock BDP 3D profile actually wouldn't play anything for me. I kept getting not supported format until I stopped Mezzmo, switched to Samsung C and restarted Mezzmo.

[Paul]

Ok, yes, please send us a message to support asking for the BDP 3D profile and as soon as we have an updated we'll send it to you.

[glc650]

Ok I installed the latest Samsung BDP 3D profile and tried it with the BD-C7900 (just arrived yesterday) but I'm having trouble with the same files I had trouble with on the TV before I got the updated profile (Samsung C) for that from you.

So on the BD-C7900 with the updated (BDP 3D) profile I get constant buffering on my AVCHD files (as well as on a .mov Transformers 2 trailer) and the VC-1 file either refuses to play (not supported format) or plays for up to a minute or so and then stops and says it's not supported.

Haven't tried the updated Samsung C profile with the BD-C7900. Will try that after work today.

Thanks,

-g>.

[Paul]

Yes, see how the "C" profile goes and if it works better we'll adjust the "3D" profile accordingly.

[glc650]

Ok I did a comparison between the BDP and TV with the same profile (Samsung C):

BDP:

VC-1 movie: plays but buffers constantly and lots of audio dropouts
AVCHD camcorder recordings: tried 2...both played fine
.mov Transformers 2 trailer: quite a bit of buffering during 2nd half of 2 minute trailer

TV:

VC-1 movie: played for 5 mins with no buffering and no audio dropouts
AVCHD camcorder recordings: (same as BDP)
.mov Transformers 2 trailer: (same as BDP)

NOTE: I checked the transcoding directory after testing each device and it appears neither device attempted to transcode to play these files back

[glc650]

Here's the info on the:

.mov Transformers 2 trailer:

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

Seems stream 1 codec frame rate differs from container frame rate: 5994.00 (5994/1) -> 23.98 (2997/125)
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\\drobo-nas\video\test\trailers\80297347.mov':
Metadata:
major_brand : qt
minor_version : 537199360
compatible_brands: qt
title : "Transformers: Revenge Of The Fallen" Trailer #1
title-eng : "Transformers: Revenge Of The Fallen" Trailer #1
artist : Yahoo! Movies
artist-eng : Yahoo! Movies
copyright : © 2009, Paramount Pictures.
copyright-eng : © 2009, Paramount Pictures.
Duration: 00:02:16.40, start: 0.000000, bitrate: 9585 kb/s
Stream #0.0(eng): Audio: aac, 48000 Hz, stereo, s16, 184 kb/s
Stream #0.1(eng): Video: h264, yuv420p, 1920x800, 9397 kb/s, 23.98 fps, 23.98 tbr, 2997 tbn, 5994 tbc
At least one output file must be specified


---> DB Level Info: 40

VC-1 movie:

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
[NULL @ 02d5c710] start time is not set in av_estimate_timings_from_pts
Input #0, mpegts, from '\\drobo-nas\video\test\The Dark Knight\The.Dark.Knight.2008.1080p.BD-Remux.TrueHD.VC-1 (1920x1080p, 16to9, 23.976).ts':
Duration: 02:32:13.29, start: 600.000000, bitrate: 28587 kb/s
Program 1
Stream #0.0[0x1011]: Video: vc1, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 23.98 tbc
Stream #0.1[0x1100](eng): Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.2[0x1101](eng): Audio: truehd, 48000 Hz, 6 channels, s32
Stream #0.3[0x1101]: Audio: ac3, 48000 Hz, 5.1, s16, 640 kb/s
Stream #0.4[0x1102](eng): Audio: ac3, 48000 Hz, stereo, s16, 192 kb/s
Stream #0.5[0x1200](eng): Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: -99

[Paul]

Thanks for the info. Have you tried playing those files using PCSM? If you have, what are the results?

I can't find any mpegts/vc1 files here - do you have one that you could send us for testing here?

[glc650]

PCSM + BDP:

VC-1: lots of buffering
.mov: can't even select it (it doesn't show up in the folder view)

PCSM + TV:

VC-1: plays fine
.mov: same as above

The VC-1 file I'm testing with is the only one I have and it is a full blu-ray rip.

Thanks,

-g>.

[Paul]

Thanks for the results. So, to sum it up - the BDP-3D does not support VC1 very well, so we need to remove that from the device profile for the BDP, right? Or it just doesn't support high-bitrate ones, which means we need to find the highest bitrate it will play (for example 20Mbits) and transcode everything above that.

[glc650]

Yea I guess that is what we are seeing here but what I don't understand is that a Blu-ray player has trouble playing a high bit rate VC-1 rip while the TV (which obviously doesn't even play Blu-ray discs) plays it just fine. You would think the BDP would be able to handle these files (this particular player plays high bit rate discs just fine).

Is there a way to trouble shoot this furher? Do you hav any short high bit rate VC-1 BD rips that I could try on both devices?

[Paul]

I agree with your logic, but over time I see things that are just like - illogical. Of course the engine handling actual BD playback and the media player for DLNA files are two different things, so that could be the reason for this discrepancy.

We don't have any such rips here, but we could make some for testing. Are you using some free software for ripping that we could also use here for testing?

[glc650]

No I didn't do the ripping on this one. My BD-ROM died a while back and I've been waiting for prices to drop on BD recorders/media before getting once of those to replace it. Eventually I'll want to start burning my AVCHD recorings and will get one.

[Paul]

Ok, we'll try to do some rips here and test with the hardware we have.

[waffull]

I agree with your logic, but over time I see things that are just like - illogical. Of course the engine handling actual BD playback and the media player for DLNA files are two different things, so that could be the reason for this discrepancy.

We don't have any such rips here, but we could make some for testing. Are you using some free software for ripping that we could also use here for testing?

While not free, Anydvd HD from http://www.slysoft.com, works really well. I was able to rip my blu-rays so they are identical to the disk and since I own the blu-rays, I strip the protection so I can stream from the computer.

Problem has been getting the m2ts to stream well with Mezzmo. It would also be nice if Mezzmo could read the playlists from the blu-ray and stream based on those, rather than having to select a specific m2ts to stream. But so far Mezzmo has been unable to stream large m2ts files.

I first started ripping my blu-rays into iso files since they can easily be mounted on the PC. It would also be extra nice if Mezzmo could read an iso;)

Thanks.

[Paul]

Can you please tell me what is the issue with streaming large m2ts files? We've tested some very large files here (around 30-40GBs) and they stream fine (wired of course). Are you on a wired or a wireless network? Can you please post FFmpeg information on one of those files? Do they start to play and then stop or don't start at all?

I guess I just found your second post about this, so ignore the above and I'll reply to you there :)

[waffull]

I posted problem in a new thread which you replied to, so to keep it neat, I'll stick to that new thread.
Thanks.

[absynthetic]

Well, I am having troubles playing this one file:

FFmpeg version SVN-r25512, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 18 2010 04:06:45 with gcc 4.4.2
configuration: --enable-gpl --enable-version3 --enable-libgsm --enable-pthreads --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libmp3lame --enable-libopenjpeg --enable-libschroedinger --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-libvpx --arch=x86 --enable-runtime-cpudetect --enable-libxvid --enable-libx264 --extra-libs='-lx264 -lpthread' --enable-librtmp --extra-libs='-lrtmp -lpolarssl -lws2_32 -lwinmm' --target-os=mingw32 --enable-avisynth --cross-prefix=i686-mingw32- --cc='ccache i686-mingw32-gcc' --enable-memalign-hack
libavutil 50.32. 3 / 50.32. 3
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.83. 0 / 52.83. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.52. 0 / 1.52. 0
libswscale 0.12. 0 / 0.12. 0

Seems stream 1 codec frame rate differs from container frame rate: 5994.00 (5994/1) -> 29.97 (2997/100)
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\Vickey\Downloads\file.mov':
Metadata:
major_brand : qt
minor_version : 537199360
compatible_brands: qt
Duration: 00:04:28.81, start: 0.000000, bitrate: 3938 kb/s
Stream #0.0(eng): Audio: aac, 44100 Hz, stereo, s16, 124 kb/s
Stream #0.1(eng): Video: h264, yuv420p, 1280x720, 3811 kb/s, PAR 1:1 DAR 16:9, 29.97 fps, 29.97 tbr, 2997 tbn, 5994 tbc
At least one output file must be specified


---> DB Level Info: 31

on my Samsung UN46C6500 with the Profile Samsung C would notify me "Unsupported file format" and will go on with the next movie on the q
What`s wrong with my picture?
Thanks in advance

[glc650]

Dennis,

I was trying to play my AVCHD (.mts) camcorder recordings today and was getting a lot of bufferring. Last time I played any (2-3 just for testing) they played back fine. That was before the last Mezzmo update. Not sure if that has anything to do with it (after the update I reloaded the Samsung C profile just to be sure). Anyway, I tried playing ~10 and they all buffered in the beggining (seemed to play fine after a few minutes assuming they are long enough clips).

Here's the FFMPEG info from a couple of them:

FFmpeg version SVN-r26071, Copyright (c) 2000-2010 the FFmpeg developers
built on Dec 22 2010 10:30:32 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.35. 0 / 50.35. 0
libavcore 0.16. 0 / 0.16. 0
libavcodec 52.100. 0 / 52.100. 0
libavformat 52.88. 0 / 52.88. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.69. 0 / 1.69. 0
libswscale 0.12. 0 / 0.12. 0

Seems stream 0 codec frame rate differs from container frame rate: 59.94 (60000/1001) -> 59.94 (60000/1001)
Input #0, mpegts, from 'C:\Users\Garrett\Videos\Canyon\alternator test 8-22-09\alternator test 8-22-09.mts':
Duration: 00:03:05.92, start: 1.000022, bitrate: 24009 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 59.96 fps, 59.94 tbr, 90k tbn, 59.94 tbc
Stream #0.1[0x1100]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s
Stream #0.2[0x1200]: Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: 40

and:

FFmpeg version SVN-r26071, Copyright (c) 2000-2010 the FFmpeg developers
built on Dec 22 2010 10:30:32 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.35. 0 / 50.35. 0
libavcore 0.16. 0 / 0.16. 0
libavcodec 52.100. 0 / 52.100. 0
libavformat 52.88. 0 / 52.88. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.69. 0 / 1.69. 0
libswscale 0.12. 0 / 0.12. 0

Seems stream 0 codec frame rate differs from container frame rate: 59.94 (60000/1001) -> 59.94 (60000/1001)
Input #0, mpegts, from 'C:\Users\Garrett\Videos\Everio MediaBrowser HD\HDDCAM\20100816\15300983036251780901\00130.mts' :
Duration: 00:00:43.45, start: 1.000022, bitrate: 23768 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 59.96 fps, 59.94 tbr, 90k tbn, 59.94 tbc
Stream #0.1[0x1100]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s
Stream #0.2[0x1200]: Subtitle: pgssub
At least one output file must be specified


---> DB Level Info: 40


I have a shortened mkv version of the first one. It also had to buffer:

FFmpeg version SVN-r26071, Copyright (c) 2000-2010 the FFmpeg developers
built on Dec 22 2010 10:30:32 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.35. 0 / 50.35. 0
libavcore 0.16. 0 / 0.16. 0
libavcodec 52.100. 0 / 52.100. 0
libavformat 52.88. 0 / 52.88. 0
libavdevice 52. 2. 2 / 52. 2. 2
libavfilter 1.69. 0 / 1.69. 0
libswscale 0.12. 0 / 0.12. 0
[matroska,webm @ 0175cf90] Unknown entry 0x80
[matroska,webm @ 0175cf90] Estimating duration from bitrate, this may be inaccurate
Input #0, matroska,webm, from 'C:\Users\Garrett\Videos\Canyon\YouTube\alternator test 8-22-09 (trim 2).mkv':
Duration: 00:01:25.71, start: 0.000000, bitrate: N/A
Stream #0.0(eng): Video: h264, yuv420p, 1920x1080, PAR 1:1 DAR 16:9, 29.97 fps, 29.97 tbr, 1k tbn, 59.94 tbc
Stream #0.1: Audio: aac, 44100 Hz, stereo, s16
At least one output file must be specified


---> DB Level Info: 40


BTW, my camcarder is a JVC GZ-HM200 HiDef SD/SDHC cam.

Thanks,

Garrett

[Paul]

Well, I am having troubles playing this one file:

on my Samsung UN46C6500 with the Profile Samsung C would notify me "Unsupported file format" and will go on with the next movie on the q
What`s wrong with my picture?
Thanks in advance
We've found that some encoders produce files that are not playable on certain devices. One way to test this is to try to play the same file using PCSM - if that doesn't play either, then we'll need to force transcoding of that file in Mezzmo. Do you have many files like that or only one?

[Paul]

Dennis,

I was trying to play my AVCHD (.mts) camcorder recordings today and was getting a lot of bufferring. Last time I played any (2-3 just for testing) they played back fine. That was before the last Mezzmo update. Not sure if that has anything to do with it (after the update I reloaded the Samsung C profile just to be sure). Anyway, I tried playing ~10 and they all buffered in the beggining (seemed to play fine after a few minutes assuming they are long enough clips).

BTW, my camcarder is a JVC GZ-HM200 HiDef SD/SDHC cam.

Thanks,

Garrett
I think that the bitrate is too high on those and the TV cannot play them smoothly (I've seen this happen on similar files before on a B-series TV). Please send in a message to support (at) conceiva (dot) com and I'll send you an updated device profile to try.

[glc650]

This is actually happening on the Samsung BD-C7900 Blu-ray player. I went to play back some of my cam footage over the holidays and noticed this problem. The Samsung TV is just a bedroom TV and problably wont be used for streaming (except for testing and maybe the occasional video when convienent). So do you have an updated profile for the BDPs too (or should I just try the TV profile with it)? I'll send an email anyway for the TV profile for testing later but wish to get the BDP working first since it is connected my main TV (which is an older TV without built in streaming).

Thanks,

Garrett

[Paul]

I suspect it'll be the same across all Samsung devices. Please do mention that you wish to get a BDP profile (or a BDP-3D) in your e-mail.

[glc650]

I took 3 of the AVCHD camcorder recordings that I last had trouble with (when I was trying to playback a bunch of my video for friends during the holidays) and remuxed them into 3 different containers (mkv, m2ts, ts) and all 9 files (3 recordings * 3 different container files) played back just fine. So that brings me to the following conclusion:

the high bit rate (22+ mbps according to ffmpeg on the native .mts files) of my recordings isn't the issue, the issue is either:

1) .mts plus high bit rate video streams is an issue for Samsung 3D (or maybe just .mts files in general? not sure as my recordings are the only native .mts files i have)
2) Samsung handles hight bit rate .mts files just fine, just not the ones from my comcorder for some reason (again, I have no other native .mts files to test this theory with)

NOTE: This test was performed with the latest Mezzmo but not the latest Samsung C (TV) profile. I didn't bother testing the 3D BDP profile as I've had better luck with the Samsung C profile since I started using Mezzmo and regardless of the device (46" C8000 3D TV or C7900 3D BDP). According to Mezzmo email support (last week), the latest Mezzmo update includes the latest Samsung TV/BDP profiles but I didn't think of that so after I updated I copied over the previous profiles (from support email) rather than using the built in ones.

[Paul]

We've found .mts files from several camcorders with higher bitrates that will stutter on the TV. It appears to be limited only to mts files with bitrates over 16 Mbits.

Do those remuxed files play fine using PCSM as well? Mezzmo may have been transcoding those (unless you know that you've turned transcoding off).

[glc650]

I'll try them with PCSM asap. Transcoding is enabled but there are no files in the transcoded files folder so I'm assuming Mezzmo was not transcoding in my case.

Is there another work around (besides remuxing)?

[Paul]

If the TV won't play them as-is, then we have to remux - there's no work-around, unfortunately. Let's see how your tests go as well and we'll proceed from there.

[hartlenb]

At the risk of confusing the problem you are working on here, I'm going to add my two cents, because I think we may be working the same problem. If they are different problems then just ignore the post.

I'm in the middle of a similar issue with Mezzmo support. My TV is a Samsung LN46C600 using the Samsung C profile. The AVHCD files from my camcorder are saved with a MTS format.

The TV doesn't recognize the MTS file type. But, if I change the extension to MPG, making no other changes, just changing it from .MTS to .MPG, the file plays fine on the TV. This is true when playing the file using PCSM, using the DLINK DNS-321 DLNA player and Mezzmo (with transcoding off).

So the TV is capable of playing the file at the bitrate. But if I try to play the file with the MTS extension; Mezzmo won't do it unless transcoding is enabled. This obviously doesn't make sense as the TV can play the file directly.

You may want to try renaming your MTS files as MPG to see if your TV can handle them this way also.

My next step with Mezzmo support is to run a program called Wireshark. I assume it is some kind of profiling tool. Not sure where it will lead but I'm thinking that a tweak to the device profile to treat MTS files the same way it does MPG would solve it.

[Paul]

There's also a possibility that the internal player on your TV is closer to the one in Samsung BDPs, which do play MTS files fine - as a test, try changing the device profile to "Samsung BDP" (or BDP 3D) and see if that plays the MTS files directly without transcoding and without stuttering. Please let me know how that goes.

[hartlenb]

There's also a possibility that the internal player on your TV is closer to the one in Samsung BDPs, which do play MTS files fine - as a test, try changing the device profile to "Samsung BDP" (or BDP 3D) and see if that plays the MTS files directly without transcoding and without stuttering. Please let me know how that goes.

That appears to work like a charm for me! Thanks.

[Paul]

Great! :) I'd recommend using that profile then.

[glc650]

Mezzmo (Samsung C and BDP 3D profiles):
renaming files to .mpg = buffering
renaming files to .ts = buffering
remuxed .mkv = slow motion and audio out of sync by a bunch
remuxed .m2ts = buffering
remuxed .ts files play fine

Samsung PC Share software:
same as above except .m2ts files aren't detected and files renamed to .ts play fine

So looks like the easiest work around is to use PC Share and rename my .mts recordings to .ts

[darkhorse]

I have purchased a Samsung UA55D6600 and I am testing Mezzmo.
I have a Panasonic HD recorder.
I am trying to watch HD 1920X1080 video and the files are M2ts.
The playback starts but then constantly stalls and buffers/loads. As others have experienced.
I have tried the profiles suggested Samsung BDP and BDP 3D same result.
Also tried transcoding off and on. No joy.

Any suggestions/ideas.
Thanks
Craig.

[Paul]

Most likely the bitrate of that MTS file is too high for the TV to handle.

Please send a message to support (at) conceiva (dot) com and we'll send you an updated device profile to try.

[Hokiebus]

I also have the same problem (Samsung 46c7000). Using MPEG4 format, profile C. Avatar streams great - Adjustment bureau keep getting "prepairing to play" msg. I've included the ffmpeg for both. Please help.

ffmpeg version N-31754-g64160ef, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 4 2011 17:48:25 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-ffplay --prefix=/media/windows/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --pkg-config=pkg-config
libavutil 51. 11. 1 / 51. 11. 1
libavcodec 53. 9. 1 / 53. 9. 1
libavformat 53. 6. 0 / 53. 6. 0
libavdevice 53. 2. 0 / 53. 2. 0
libavfilter 2. 27. 5 / 2. 27. 5
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'I:\Streaming\mp4\ADJUSTMENT_BUREAU\ADJUSTMENT_BUR EAU.Title4.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: mp42isom
creation_time : 2011-07-22 23:42:50
Duration: 01:45:51.97, start: 0.000000, bitrate: 1457 kb/s
Stream #0.0(und): Video: h264 (Main), yuv420p, 720x388, 1006 kb/s, 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc
Metadata:
creation_time : 2011-07-22 23:42:50
Stream #0.1(und): Audio: aac, 48000 Hz, 5.1(back), s16, 447 kb/s
Metadata:
creation_time : 2011-07-22 23:42:50
At least one output file must be specified


---> DB Level Info: 30, 0
---> Frame rate:
---> Aspect ratio

ffmpeg version N-31754-g64160ef, Copyright (c) 2000-2011 the FFmpeg developers
built on Aug 4 2011 17:48:25 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-ffplay --prefix=/media/windows/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --pkg-config=pkg-config
libavutil 51. 11. 1 / 51. 11. 1
libavcodec 53. 9. 1 / 53. 9. 1
libavformat 53. 6. 0 / 53. 6. 0
libavdevice 53. 2. 0 / 53. 2. 0
libavfilter 2. 27. 5 / 2. 27. 5
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'I:\Streaming\mp4\AVATAR\AVATAR.Title1.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
title : AVATAR.Title1.DVDRip
album : AVATAR
encoder : Lavf52.78.4
Duration: 02:41:42.06, start: 0.000000, bitrate: 1495 kb/s
Stream #0.0(und): Video: h264 (Main), yuv420p, 720x404, 1043 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc
Stream #0.1(und): Audio: aac, 48000 Hz, 5.1(back), s16, 447 kb/s
At least one output file must be specified


---> DB Level Info: 30, 0
---> Frame rate:
---> Aspect ratio:

[Paul]

This is a different issue, actually, as the bitrate issue usually only applies to MPEG-TS files, not MP4 files (and you files' bitrates are low in any case).

The two files were encoded using different encoders, so perhaps there's something in the file's specific encoding that causes this.

Would it be possible for you to upload this file to a site like www.megaupload.com so that we could test it here? Alternatively, if you can PM me a download link, that would work too.

[Hokiebus]

ur right 2 different coders. avatar used dvdfab (8.0.9.2), adjustment bureau used new version (8.1.1.2). not familiar with megaupload.

[Paul]

If you go to www.megaupload.com, you can upload files there (up to 2GBs for free, I think). Or, if you downloaded them from somewhere in the first place, I could use the same link (PM me if that's the case, don't post links on the forum, please) to grab them.