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

**BeFi** · 10-03-2012, 11:53 PM

After more extensive use I have to report that 2.7.1. causes my three TV's (Samsung C, D and Philips TV 7000) to occasionally skip to the next library title.

The effect is not reproducible and happens 20-40 mins into the MPEG2 streams. The effect does not appear on each stream. There is no 'Preparing to Play' message that would indicate the network connection to be too slow or interrupted. Th devices simply and instantly skip to the next title.

I am back to Mezzmo 2.5.0 which still seems to be the last stable version for my environment.

**Paul** · 10-04-2012, 07:18 AM

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** · 10-04-2012, 09:21 AM

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** · 10-04-2012, 09:40 AM

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** · 10-04-2012, 01:10 PM

Originally Posted by 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.

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** · 10-04-2012, 02:35 PM

Originally Posted by 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.

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** · 10-04-2012, 02:57 PM

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.

**BeFi** · 10-04-2012, 03:08 PM

Peter,

I am back to 2.5 and don't plan to upgrade to newer versions any more - I am sorry. 2.5 is streaming to all my three TVs in a rock-stable fashion. The newer versions of Mezzo have zero functional advantage for my setup but bring instabilities.

My recommendation to you guys is to remove the acceleration algorithms you added since 2.6. i have not seen any visible speed advantage but it has wreaked havoc of all sorts.

**BeFi** · 10-08-2012, 12:52 AM

Originally Posted by mark11

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** · 10-08-2012, 11:21 AM

Originally Posted by BeFi

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.