BD-D6500 - Slow to recognize Mezzmo, disconnects browsing folders and while playing

[mark11]

Hey Guys,

I am still getting around to watching contenty on alm my devices after the 301 upgrades. My newest issue is my Samsung BD-D6500. It has a few problems..
1. Mezzmo will not show up in the BD Player unless I start and stop the media server on the PC. It is wireless but only 15 feet away from the router with an XBOX 360 that picks up Mezzmo with no issues.
2. I disconnects as I dive into folders for content. But I read you guys are working on folder browsing speed related to Samsung devices having some timing issues.
3. I get disconnects watching almost all content from Mezzmo in the BD player. I see no pattern - different formats, trans-coded, not trans-coded.

Please help.

[Paul]

Hi Mark,

Thanks for reporting this. I think we have addressed all these issues in the upcoming Mezzmo release. It should be available in the next 1-2 days. If you still have problems after trying it, let us know and we'll look into it.

[mark11]

Hi Mark,

Thanks for reporting this. I think we have addressed all these issues in the upcoming Mezzmo release. It should be available in the next 1-2 days. If you still have problems after trying it, let us know and we'll look into it.

Awesome. Sounds good.

[mark11]

Awesome. Sounds good.


3.0.2 updates - still not good on the BD-D6500.

1. Mezzmo will not be recognized by the player unless I restart the Mezzmo media server. Then it only recognizes with 5-10 minutes 50% of the time.

2. Once connected, I still get random disconnects going into the folders.

3. Once connected and playing content, I still get random disconnects.

I spent a considerable amount of time trying on this one. This one is wireless but only about 25t feet from router and almost line of sight. As a test, an XBox ands Sony SMP pick Mezzmo in the same location instantaneously. The Sony SMP reports signal strength +90% every time I check. I also have tried another few media center software packages (Windows, built in media server on my NAS, tvmobili and playon) and they all seem to show up on the BD-D6500 pretty fast.

What is the deal with the Mezzmo and the Samsung devices when hooked up wireless?

[Paul]

Hi Mark,

We'll test our Samsung BD model on a wireless network and see if we can replicate your experiences.

[Paul]

Hi Mark,

We just did a quick test here using our Samsung devices on a wireless network. Mezzmo server appeared on them instantly and we can browse playlist/folders without a problem. We played a few videos without a problem. We do know that Samsung devices are very time sensitive and anything that could possibly delay Mezzmo responding to a Samsung request may cause a disconnect.

A few things to look at:

1. Turn off logging if it is on. Logging does slow down Mezzmo server responding to devices. Restart your Mezzmo server and try again.

2. Start Windows Task Manager. Go to the Processes tab and show processes from all users. Check if Mezzmo.exe or MezzmoMediaServer.exe are busy.

3. If no better, then send through a set of logs to us and we'll see if we can see anything that may be causing the problem.

[mark11]

Hi Mark,

We just did a quick test here using our Samsung devices on a wireless network. Mezzmo server appeared on them instantly and we can browse playlist/folders without a problem. We played a few videos without a problem. We do know that Samsung devices are very time sensitive and anything that could possibly delay Mezzmo responding to a Samsung request may cause a disconnect.

A few things to look at:

1. Turn off logging if it is on. Logging does slow down Mezzmo server responding to devices. Restart your Mezzmo server and try again.

2. Start Windows Task Manager. Go to the Processes tab and show processes from all users. Check if Mezzmo.exe or MezzmoMediaServer.exe are busy.

3. If no better, then send through a set of logs to us and we'll see if we can see anything that may be causing the problem.

Loggin was off. Both Mezzmo tasks were running but no busy. Do I need to port forward behind my own network?

[Paul]

Hi Mark,

Please send through a set of logs and we'll see if we can see anything blocking/slowing down communication between your Samsung BDP and Mezzmo. Turn off your Samsung BDP, and then turn on logging in Mezzmo and start your Mezzmo server. Turn on your Samsung BDP and wait until Mezzmo appears on your Samsung BDP. When it finally appears, stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us.

[mark11]

Hi Mark,

Please send through a set of logs and we'll see if we can see anything blocking/slowing down communication between your Samsung BDP and Mezzmo. Turn off your Samsung BDP, and then turn on logging in Mezzmo and start your Mezzmo server. Turn on your Samsung BDP and wait until Mezzmo appears on your Samsung BDP. When it finally appears, stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us.

Logs have been sent. For what it is worth Mezzmo connected fairly fast - 5-10 minutes. Thanks for the help.

[Paul]

Thanks, Mark. We'll check out your logs and report back.

[mark11]

Thanks, Mark. We'll check out your logs and report back.

In the mean time, I did some more investigating. I have an old box that had Mezzmo 2.4.5 that has not been started up in quite some time. When I start 2.4.5 up, the BD-D6500 recognized Mezzmo in seconds. I did so everytime, repeatedly. After restarts of the BDP, Media Server restarts restarts of the pc and restarts of the network, it recognized Mezzmo in seconds. Then I upgraded Mezzmo to 3.0.2. The BDP only recognized Mezzmo once after multiple tries of the scenarios above. And when it recognized Mezzmo, it tool 5 plus minutes.

So... A few months back, I fixed this same issue on my other Samsung BDP (after your instance that I had network issues) by hard wiring to that location. I do not have that ability in this area. And given that prior versions of Mezzmo seem to work great with the BD-D6500 and the newer versions do not, what is the deal? When and why did you turn Mezzmo from an AK-47 into an M-16? (Google Ak47 vs M16 tolerances). Mezzmo used to just work. I find that I am having to spend more and more time making Mezzmo work. I am having trouble understanding what is happening here.

[Paul]

Hi Mark,

We're analyzing your logs now and we can see a problem. We will email you shortly.

[mark11]

Hi Mark,

We're analyzing your logs now and we can see a problem. We will email you shortly.

I am curious to hear what you think.

[Paul]

Hi Mark,

Email just sent. Let us know how your testing goes.

[mark11]

Hi Mark,

Email just sent. Let us know how your testing goes.

SOLVED!

Attention all Samsung BDP users using wireless. If you have set a static IP in the Samsung device, please change it back to dynamic. Manual back to Auto. For some reason, it looks like the code in the device for the static IP setup is not functioning correctly. It limits the player ability to reach out to a media server and it also seems to cause the player not be able to hear a media server that is announcing itself. This has also attributed to some drops in playback and file navigation drops once connected.

I have confirmed this on two models - BD-D6500 and BD-C6500. Once I switched back to Auto (dynamic), Mezzmo appears at device start up every time now.

This does not impact wired connections.

Thanks to Paul for providing a detailed explanation of the parts of the DNLA protocol.

[Snyper]

So, this is a Samsung issue? I have filtering setup to only show certain content to this device. If I switch the player to DHCP I can't set a specific rule for it as the IP may be different every time it's turned on. Does the patch that was emailed fix the problem, or is there some other way I can still send filtered content to a device without a static ip?

I've just been doing a bit of Googling for this after reading the above post and came across this post (and other similar ones)...

http://www.eightforums.com/network-sharing/13306-dhcp-works-static-ip-doesnt.html

To sum up, even though this should never be the solution in my case, all my devices have static ip's, it appears that setting static ip numbers outside the range provided by the DHCP server might fix this fault. Reading through the post sounds promising and I will try it out this afternoon. I'd like to hear if this works for anyone else also.

...

I tried this last night on most of the devices around my home, wireless, ethernet and powerline. I changed all of the static IP's to numbers outside the range allocated by DHCP and ... instant detection! I tried multiple times on multiple devices and it worked every time. I still had timeouts and things associated with Samsung equipment, but the Mezzmo server was found every time.

There is a chance this may just be a coincidence, and it will break the next time I use it, but it looks promising at the moment.

[Snyper]

Just letting everyone know that since I made the changes mentioned above, I haven't had this issue reoccur. It looks like this may be the solution to many of the 'slow detection', 'mezzmo drops out', etc. issues.

[Paul]

Many thanks for the confirmation, Snyper. We'll read up about this and see if it is culprit that causes some users to have connection issues.

[mark11]

So, this is a Samsung issue? I have filtering setup to only show certain content to this device. If I switch the player to DHCP I can't set a specific rule for it as the IP may be different every time it's turned on. Does the patch that was emailed fix the problem, or is there some other way I can still send filtered content to a device without a static ip?

I've just been doing a bit of Googling for this after reading the above post and came across this post (and other similar ones)...

http://www.eightforums.com/network-sharing/13306-dhcp-works-static-ip-doesnt.html

To sum up, even though this should never be the solution in my case, all my devices have static ip's, it appears that setting static ip numbers outside the range provided by the DHCP server might fix this fault. Reading through the post sounds promising and I will try it out this afternoon. I'd like to hear if this works for anyone else also.

...

I tried this last night on most of the devices around my home, wireless, ethernet and powerline. I changed all of the static IP's to numbers outside the range allocated by DHCP and ... instant detection! I tried multiple times on multiple devices and it worked every time. I still had timeouts and things associated with Samsung equipment, but the Mezzmo server was found every time.

There is a chance this may just be a coincidence, and it will break the next time I use it, but it looks promising at the moment.

Nice follow-up. I may try the static IP outside of my DHCP range. Using DHCP, while getting me Mezzmo back, is a minor inconvenience. Thanks.

BTW - Not sure if this is a Samsung problem or not. I do have other devices - Sony, M$, Apple, Android - that do not have an issue with using a static IP inside of my DHCP range. I am still using them this way today with no issues. Perhaps my Samsungs are a bit sensitive