Slow/No folder content delivery to DLNA

[jayheyl]

I'm running Mezzmo 4.1.2 on Win7-64 and am having a problem with folder contents sometimes being extremely slow to appear on the DLNA target (Sony BDP-S5100). Sometimes they don't show up at all. Other times they show up very quickly. The database has just under 15,000 items in it. Due to the slow performance I moved the database to a SSD drive. This helped a bit but still I'm seeing an annoying number of folders on the TV (via the Blu-Ray player) show up apparently empty when I know they're not. I'm not seeing the same type of slowness when accessing the database via the Mezzmo console. When a folder refuses to come up it seems to stay that way. Traveling up the directory tree and back down does not result in contents showing up if they were not displayed the first time. The problem occurs with no particular folder that I can tell. One time a folder will work fine, then it won't, then it's fine again (on multiple restarts of the Blu-Ray player).

The computer has a quad core i7 CPU and 32GB RAM so it should be well equipped to provide blazing speed. I've not seen many transcoding issues. The computer is hard wired to the network though the Blu-Ray player is using wi-fi.

I was away for a while and didn't keep up with Mezzmo updates, only recently updating from 3.x to 4.1.0 (and ultimately to 4.1.2). I did not see this problem with 3.x.

[Paul]

Understand. A set of logs will tell us what's going wrong. Turn on logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and restart your Mezzmo server. Reproduce the slow browsing and no content delivery problems you mention. Then stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

[mrgenie]

Understand. A set of logs will tell us what's going wrong. Turn on logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and restart your Mezzmo server. Reproduce the slow browsing and no content delivery problems you mention. Then stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

Any luck on this one? I experience the same issue from time to time..

And I have no idea why, because sometimes it works just flawless.. sometimes I get the described issue.
Not that it's a biggy, I simply exit the Media Player on the Samsung TV and restart it. Usually restarting the Samsung DLNA Player a 2nd time solves the issue.. sometimes I need to give it a third attempt..
and sometimes it works just right out of the box the first time :)

It's not a big issue, pressing 2 or 3 buttons additionally.. But would be nice if you can track what is causing it..

I thought it was a Samsung issue, but since non-Samsung users also report this, or at least 1 non Samsung, i guess it might be something else then just blaming it on Samsung.

I did notice: restarting all network devices.. wait 5 Minutes, and this issue never happens!
After a few hours network routers/switches/servers back on.. and it gets back..

[Paul]

Have you upgraded to Mezzmo v4.1.3.0? We did make several improvements in this area for this version. Let us know how that goes. If no better, then a set of logs will tell us what's going wrong. Turn on logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and restart your Mezzmo server. Reproduce the slow browsing and no content delivery problems you mention. Then stop your Mezzmo server and exit Mezzmo. Zip up all the logs and email them to us at support [at] conceiva [dot] com.

[AndyCr15]

Well I've just e-mailed logs to you.

1st attempt 'No media found'
2nd attempt I browsed to the folder no problem.

Usually it hangs on going into the folder, then only shows a few of the files.

[Paul]

We have not received your logs as yet :(. Please upload the zipped logs to a filesharing site like Google Drive, Dropbox, OneDrive, mega.co.nz, etc. and then email us the download link to support [at] conceiva [dot] com.

[AndyCr15]

Done. Thanks.

[cdawe]

Hi guys,

I'm having this issue now with the new Version 5 of Mezzmo ... Samsung Smart TV - Model UN40ES6100.

Folders are painfully slow to list - over a minute sometimes. Now, I admit full well that I have a lot of folders ... but my home network is Full Gigabit from stem to stern and everything else is working nicely. Mezzmo does play flawlessly but the folder listing is ... ugh! lol

Still, I love the program and I want to add my vote for a Mezzmo on Linux. I'm using TVMobili on Mint right now, and since the Latest release of mint, it just doesn't seem to run as nicely as before.

Curt

UPDATE: Logs folders just sent for your perusal.

Thanks guys.

[BeFi]

I have the same effect ever since Mezzmo 3.x and with several Samsung TV's (C, E, J) and in my case the explanation is really simple:

My Mezzmo server PC is configured to have its hard disks (containing the media Mezzmo points to) wind down after a predefined time (set in Windows Power settings). The server PC does not sleep though.
If I start browsing with Mezzmo after the hard disks have been wound down it takes app. 20 secs for the server PC to restore its full function. During that time my Samsung's behavior is random:
+ Sometimes I can immmediately see the top level folders in Mezzmo but have to wait 20 secs until I can browse them.
+ Sometimes Samsung's DLNA client terminates with a error message. The second attempt (after a couple of seconds) works smooth. At that time the hard disks 'have woken up'
+ Sometimes I can start even a video (e.g. in Recently Added) but the video rather hangs itself up. Most often then Samsungs DLNA client terminates with a error message

If I wait 20 secs after selecting the DLNA server on my Samsung's I never have issues with browsing.

This may not describe the root cause of YOUR issue but its worth eliminating this possibility.

[Peter]

From the logs it looks like the timeout of 250ms is causing Mezzmo to deliver one item at a time to the device and this is causing it to be very slow, we have sent you an updated device profile which has a higher timeout setting of 5250ms to see if this helps resolve the issue.