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

[Paul]

Hi BeFi,

That is dissapointing. As mentioned in your other posts, did you check your home network for possible causes (e.g. cabling, router, network cards, etc.)? Perhaps even try turning off all devices connected to your home network except your PC and one of your TVs to see if that works (i.e. less congestion). If it does, then try another TV. It may help isolate a problem device or a weak point in your home network.

We are happy to continue to help you isolate the problem. Probably the best next step is to get Wireshark logs so we can see all data transmission on your home network while you are streaming. If you are keen, let us know & we'll help out.

We have not had any other reports like this as yet for Mezzmo v2.7.1.0. If any other user is experiencing this type of problem, please let us know.

[ftanner]

Having quite a bit of experience with networking, you'd think that if it were a network issue it wouldn't have "suddenly" cropped up after upgrading from version 2.5.0; that it would have been an issue all along if that were the case.

Of course, this is being said based solely on the information that he is giving.

[Paul]

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.

[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

[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.

[BeFi]

Hi BeFi,

That is dissapointing. As mentioned in your other posts, did you check your home network for possible causes (e.g. cabling, router, network cards, etc.)? Perhaps even try turning off all devices connected to your home network except your PC and one of your TVs to see if that works (i.e. less congestion). If it does, then try another TV. It may help isolate a problem device or a weak point in your home network.

Paul

The effect I am reporting here is new. It is not a disconnect issue like in my earler post related to 2.6.x. Its Mezzmo skipping to the next title.The skipping happens fast in one second or so.

Edit: and the skipping now affects all three of my TVs - Not just the Samsung D as with most of the 2.6.x issues.

The disconnects I reported with 2.6.x looked very different: stream stopped and the TV entirely exited its DLNA client falling back to TV. THAT were disconnects! What we are now facing is a random behavior of Mezzmo itself.

To the 'user have rectified the weak points in their home networks and are streaming fine now with 2.7 ....': I did not see a single thread in the forum confirming that the 2.6 patches or 2.7 has fixed a user's streaming problem. I have however seen multiple posts on skipping to next title. If i read these posts my setup seem to be on the stable side as the skipping occurs rather seldom.

Bernhard

[Peter]

Hi Bernhard,
can you please enable diagnostic logging and send us logs showing this behavior of Mezzmo where the skipping occurs. If the skipping is occurring on files that are transcoded then this could be caused by transcoding being too slow, if the skipping is occurring on native files then this is something else and we would like to see the logs to determine what is causing it.