Mezzmo 2.7.1: Samsung C, D and Philips TV 7000 prematurely skip to next title

[mark11]

We do think we know why it has cropped up. Mezzmo is delivering data much faster now to DLNA devices since v2.6 and this seems to have exposed problems in some users' home network setups. A few users also reported disconnects like BeFi when upgrading from v2.5 to v2.6 (or to v2.7) and after working through it with them, they found issues in their home network & rectified it. The are streaming fine now with v2.7.x.

Having said that, if there are issues in Mezzmo, then we're happy to find & fix them to get any user up and running.

Hi Paul,

I do not mean to throw fuel on to the fire but... I am one of the ones that you worked through the Samsung BDP disconnect issues I was having. To hear that Mezzmo delivering data faster caused an issue with my Samsung device where no issue existed prior is a little disconcerting. Does Mezzmo have the ability to adjust its delivery rate?

[BeFi]

Hi Paul,

I do not mean to throw fuel on to the fire but... I am one of the ones that you worked through the Samsung BDP disconnect issues I was having. To hear that Mezzmo delivering data faster caused an issue with my Samsung device where no issue existed prior is a little disconcerting. Does Mezzmo have the ability to adjust its delivery rate?

Thanks Mark for supporting me here.

Its a pity that this perfect product got ruined by an attempt to improve something that seemed to not need any improvement. Mezzmo was rock stable until 2.5 and speed of navigation wasn't an issue. Since 2.6 its supposed to be faster whatever that means but since this acceleration was introduced it has side-effects like disconnects on my Samsung D, stuttering on my Samsung C and D, devices not recognized, skipping. These effects have affected just one of my device type or several. I was told that the Samsung TV's are particularly sensitive (to faster streaming ;-). The latest issue (random skipping) however affects my two Samsungs and my Philips 7000 equally.

I still haven't given up hope that we can jointly convince the Conceiva team to remove that strange acceleration-logic from Mezzmo. Otherwise I will use the rock-stable Mezzmo 2.5 until I run into compatibility issues in the future. If that happens I will have to depart for another DLNA-product.

[Paul]

I still haven't given up hope...

We have not given up hope either, BeFi We'll continue to try to isolate & fix the problem you are having with later versions of Mezzmo.

Can you please email us the FFmpeg Information on one of the files that skipped to the next file when you tried Mezzmo v2.7.1.0? You can use Mezzmo v2.5 to get this FFmpeg information (no need to re-install Mezzmo v2.7.1.0). Right-click on the file in Mezzmo and click 'Get Ffmpeg Information'.

Once we get this, we'll try to replicate your problem here with our Samsung C and D-series TVs.

[Gus]

Sorry to say, i too have this issue. I watched quite a few TV shows and Films over the weekend, and most were skipping to the next file after about 20mins.

My setup is all cabled, and while the TV isnt gigabit, all other devices are Gigabit. Not only that, the only devices powered up were my server (HP ProLiant N40L) and my TV (LE40C650). The server has no other function apart from Mezzmo.

The files were all MKVs and were mostly 1.3gb 720p TV shows.

Happy to grab logs etc but they might be a little on the big side since it can take 20-30mins to happen, and it may not happen.

Happy to test any patch if you would like.
cheers

Gus

[Paul]

Hi Gus,

Please do capture a set of logs so we can see this happen. Don't worry if it takes several movies for it to occur. Once it does occur, stop your Mezzmo server and exit Mezzmo. Zip up all the logs and send them to us at support [at] conceiva [dot] com. If the logs are over 10MB zipped, then upload them to a filesharing site like dropbox or rapidshare & send us the download link.

[BeFi]

Hi Paul,

FFmpeg information of a file that skipped after app. 2/3rd of its lenght. I watched the same file with Mezzmo 2.5 twice since with no skipping.

ffmpeg version N-36036-ga40f43d, Copyright (c) 2000-2011 the FFmpeg developers
built on Dec 22 2011 13:44:49 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=/media/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --extra-cflags=-I/home/dennis/cc/include --extra-ldflags=-L/home/dennis/cc/lib --pkg-config=pkg-config --disable-w32threads
libavutil 51. 32. 0 / 51. 32. 0
libavcodec 53. 46. 1 / 53. 46. 1
libavformat 53. 27. 0 / 53. 27. 0
libavdevice 53. 4. 0 / 53. 4. 0
libavfilter 2. 53. 0 / 2. 53. 0
libswscale 2. 1. 0 / 2. 1. 0
[mpeg @ 003d89e0] max_analyze_duration 5000000 reached at 5000000
Input #0, mpeg, from 'F:\Filme\Natur und Reise\Rucksack - Auf dem Keschtnweg in Südtirol _11-10_15-27-00.mpg':
Duration: 00:28:30.79, start: 0.296300, bitrate: 7872 kb/s
Stream #0:0[0x1e0]: Video: mpeg2video (Main), yuv420p, 720x576 [SAR 64:45 DAR 16:9], 9585 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
Stream #0:1[0x1c0]: Audio: mp2, 48000 Hz, stereo, s16, 192 kb/s
At least one output file must be specified


---> DB Level Info: 8, 4
---> Frame rate: 25,00
---> Aspect ratio: 16:9

FFmpeg of a second file during which skipping occured, again probably 30-35 mins into the file.

ffmpeg version N-36036-ga40f43d, Copyright (c) 2000-2011 the FFmpeg developers
built on Dec 22 2011 13:44:49 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=/media/ffmpeg --enable-libmp3lame --enable-libx264 --enable-gpl --extra-libs='-lx264 -lpthread' --enable-runtime-cpudetect --extra-cflags=-I/home/dennis/cc/include --extra-ldflags=-L/home/dennis/cc/lib --pkg-config=pkg-config --disable-w32threads
libavutil 51. 32. 0 / 51. 32. 0
libavcodec 53. 46. 1 / 53. 46. 1
libavformat 53. 27. 0 / 53. 27. 0
libavdevice 53. 4. 0 / 53. 4. 0
libavfilter 2. 53. 0 / 2. 53. 0
libswscale 2. 1. 0 / 2. 1. 0
[mpeg @ 016889e0] max_analyze_duration 5000000 reached at 5000000
Input #0, mpeg, from 'F:\Filme\Natur und Reise\Die Alpen von oben - Vom Dauphiné in die Hochalpen_09-20_19-27-01.mpg':
Duration: 00:43:09.80, start: 0.360000, bitrate: 5835 kb/s
Stream #0:0[0x1e0]: Video: mpeg2video (Main), yuv420p, 720x576 [SAR 64:45 DAR 16:9], 9553 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
Stream #0:1[0x1c0]: Audio: mp2, 48000 Hz, stereo, s16, 224 kb/s
At least one output file must be specified


---> DB Level Info: 8, 4
---> Frame rate: 25,00
---> Aspect ratio: 16:9

Needless to add that I had watched the same file with 2.5 at least three times without skipping.

I haven't seen a file skipping in its first 10-15mins on any of my three TVs. It always seems to happen in the later half of the file. It doesn't happen in every file viewed which makes the phenomenon hard to catch.

[KillerCheeze]

I came here to post the exact same issue, Samsung C series TV here.

MKV files are skipping to the next file anywhere from 10-30 minutes into the file. For me it's happening more often than not, although not everytime. I've just had to give up on a file by the time it skipped a 4th time.

Also in addition I am now finding all MP4 files have audio sync issues until I convert them to MKV.

Seems from the other posts that this may be a real issue and not just isolated to the OP.

[Paul]

Thanks for informing us, KillCheeze. We're looking into it right now. We'll post back our findings.

In the meantime, given that you can replicate the issue every time, can you capture a set of logs when this happens? It will really help us determine what the problem might be. Please turn on logging (see http://forum.conceiva.com/showthread...nostic-logging) and restart your Mezzmo server. Stream the file that always skips and let it play. After it skips to the next file, then stop your Mezzmo server and exit Mezzmo. Zip up all logs and send them to us at support [at] conceiva [dot] com.

[Paul]

Update: We've been streaming videos to our Samsung C and D series TVs all day today and have not seen any skipping as yet. So, we would really appreciate a set of logs from users that are experiencing this problem. Many thanks!