Samsung C can't get directory info after updates

Mezzmo is working well with Xbox and ps3. I like the product.

It was working okay with my Samsung PN58C8000. I updated the software with a new online update and then new 9/2/2010 firmware from Samsung via USB. Now the Sammy C can't even get directory information. It just locks up, while MezzmoMediaServer.exe goes to 100% just trying to serve up directory info (think it's in a loop). The Sammy works fine with other media servers (.e.g. my Cisco E300 router has one built in and it also works with WMP).

My info:
Samsung PN58C8000
Software: 2010/07/16_001026
Also updated by USB a 9/2/2010 Firmware update - 1026.0

Mezzmo:
2.1.9.0
No changes to profile

Problem: The Sammy can see the Mezzmo server and select it without a problem. However, when I try to look at the "Videos" folder, while trying to get the directory structure, it locks up on screen with a "loading" banner, but the spinning icon freezes (in fact, I can't even use the remote to turn off the TV). Meanwhile, MezzmoMediaServer goes to 100%. The media server's log also balloons in size quickly, to over 150 megs in just a few minutes. It appears to be having problems showing directory info. I'll spare you the hex dumps, but this is what it looks like repeatedly in the log (my comptuer is 192.168.1.104 and the Sammy is 192.168.1.158) (I can email to you a larger segment of the log if you'd like):

281103 - Sep 06 02:38:29.177 - > ---------------------------------------------------------------------

281104 - Sep 06 02:38:29.177 - > RequestAnswered on socket 52232, PersistentConnection = 0, Reserved6 = 1

281105 - Sep 06 02:38:29.177 - INFO > Send_Raw: RetVal = -2 (865)

281106 - Sep 06 02:38:29.177 - INFO > StreamBody: RetVal = -2 (1262)

281107 - Sep 06 02:38:29.177 - INFO > Response took 31 ms

281108 - Sep 06 02:38:29.177 - WARN > 644 ILibWebClient_FinishedResponse: wcdo->Server != 0, deferDestruction = 0 on socket 52232 (643)

281109 - Sep 06 02:38:29.179 - > Disconnect: socket 52232

281110 - Sep 06 02:38:29.181 - INFO > 644 fd_counts: readset = 4, writeset = 0, errorset = 3

281111 - Sep 06 02:38:29.185 - INFO > 644 fd_counts: readset = 3, writeset = 0, errorset = 2

281112 - Sep 06 02:38:29.186 - > 644 PostSelect: (accept) socket 52232 is available for listen socket 3076

281113 - Sep 06 02:38:29.186 - > 644 PostSelect: (accept) connected socket 52232 on listen socket 3076 to 192.168.1.158

281114 - Sep 06 02:38:29.189 - INFO > 644 fd_counts: readset = 4, writeset = 0, errorset = 3

281115 - Sep 06 02:38:29.189 - IN > recvfrom socket 52232, bytes received = 642

POST /ContentDirectory/control HTTP/1.0

HOST: 192.168.1.104:53168

CONTENT-LENGTH: 415

CONTENT-TYPE: text/xml;charset="utf-8"

USER-AGENT: DLNADOC/1.50

SOAPACTION: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"



<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1"><ObjectID>0</ObjectID><BrowseFlag>BrowseDirectChildren</BrowseFlag><Filter>*</Filter><StartingIndex>0</StartingIndex><RequestedCount>1</RequestedCount><SortCriteria></SortCriteria></u:Browse></s:Body></s:Envelope>



281116 - Sep 06 02:38:29.189 - > ---------------------------------------------------------------------

281117 - Sep 06 02:38:29.189 - INFO > OnData: we have the entire packet: DeferDestruction = 1 on socket 52232 (1434)

281118 - Sep 06 02:38:29.189 - IN > 644 [ Samsung C]: HTTP-PACKET for 192.168.1.104 from 192.168.1.104 /ContentDirectory/control

281119 - Sep 06 02:38:29.189 - > 644 [ Samsung C]: ProcessPOST: /ContentDirectory/control

281120 - Sep 06 02:38:29.189 - > DMS_ProcessQuery: RemoteIp = 192.168.1.158

281121 - Sep 06 02:38:29.189 - IN > DMS_ProcessQuery: cds_query->ObjectID = 0, filter = FFFFFFF (*), sort =

281122 - Sep 06 02:38:29.189 - IN > DMS_ProcessQuery: 0 - Starting = 0, Requested = 1

281123 - Sep 06 02:38:29.189 - > 644 [ Samsung C]: DMS_ProcessQuery: SENDING TO

281124 - Sep 06 02:38:29.220 - > 644 [ Samsung C]: DMS_ProcessQuery: Counted (496) 0 - total = 0 (0 ms)

281125 - Sep 06 02:38:29.221 - > 644 [ Samsung C]: AddElement: id = all*pn/0*pn/3, parent = 0

281126 - Sep 06 02:38:29.222 - > 644 [ Samsung C]: AddElement: Music children: 8

281127 - Sep 06 02:38:29.222 - OUT > 644 SendTo: (send) socket 52232, length = 194, bytes sent = 194

HTTP/1.1 200 OK

Date: Mon, 06 Sep 2010 02:38:29 GMT

EXT:

CONTENT-TYPE: text/xml; charset="utf-8"

Server: Windows, UPnP/1.0 DLNADOC/1.50, Mezzmo Media Server/2.1.9.0

Content-Length: 1331





281128 - Sep 06 02:38:29.222 -

---start hex dump---
[I DELETED THIS FROM THIS POST]
---end hex dump-----

281129 - Sep 06 02:38:29.222 - > ---------------------------------------------------------------------

281130 - Sep 06 02:38:29.223 - OUT > 644 SendTo: (send) socket 52232, length = 1331, bytes sent = 1331

<?xml version="1.0" encoding="utf-8"?>

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<s:Body>

<u:BrowseResponse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1"><Result>&lt;DIDL-Lite xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:upnp=&quot;urn:schemas-upnp-org:metadata-1-0/upnp/&quot; xmlns=&quot;urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/&quot; xmlns:av=&quot;urn:schemas-sony-com:av&quot; xmlns:dlna=&quot;urn:schemas-dlna-org:metadata-1-0/&quot; xmlns:sec=&quot;http://www.sec.co.kr/&quot;&gt;

&lt;container id=&quot;all*pn/0*pn/3&quot; parentID=&quot;0&quot; searchable=&quot;1&quot; restricted=&quot;1&quot; dlna:dlnaManaged=&quot;0&quot; childCount=&quot;8&quot;&gt;

&lt;searchClass includeDerived=&quot;1&quot;&gt;object.item&lt;/searchClass&gt;

&lt;searchClass includeDerived=&quot;1&quot;&gt;object.container&l t;/searchClass&gt;

&lt;searchClass includeDerived=&quot;0&quot;&gt;object.container.s torageFolder&lt;/searchClass&gt;

&lt;dc:title&gt;Music&lt;/dc:title&gt;

&lt;upnp:class&gt;object.container&lt;/upnp:class&gt;

&lt;/container&gt;



&lt;/DIDL-Lite&gt;</Result>

<NumberReturned>1</NumberReturned>

<TotalMatches>0</TotalMatches>

<UpdateID>0</UpdateID></u:BrowseResponse>

</s:Body>

</s:Envelope>

281131 - Sep 06 02:38:29.225 -

---start hex dump---

Can you try this for me?

1. Stop your Mezzmo server.
2. In Mezzmo, go to the "Video" -> "All Video Files" playlist.
3. Right-click on "All Video Files" in the tree and click "Maintain Playlist" menu item.
4. Click OK on the Maintain dialog, and let it update all your entries in your Mezzmo library. Wait until it finishes.
5. In Mezzmo, go to the Transcoding Settings dialog and click the "Delete Transcoded Files" button.
6. Start your Mezzmo server and try playing files on your TV again.

Let me know how it goes.

Okay. Like I said, it's only looping at the directory stage when my Samsung tries to access directories -- not when my Xbox or ps3 do it. But I'm doing it now.

Side question: Is there any way to get Mezzmo not to make thumbnails? I don't want them and they seem to take a long time to create.

At the moment, there's no way to stop making thumbnails. It has also been suggested by a few other users to have the ability to turn making thumbnails off. We'll consider adding this into a future version. Thanks for the feedback.

I eventually had to stop making it maintain playlists. I have several thousand files (a few TB worth). It eventually just slowed to crawl, doing 1 file per 5 minutes or so. I'm trying to restart it and have it just update info when files are missing.

But it still works fine on all files with my Xbox and Ps3. Just won't work with the Sammy C. Still can't figure out why the Media Server hangs when the updated Sammy C attempts to connect.

Can you please send a complete log file of trying to browse that folder which locks up to support (at) conceiva (dot) com and I'll take a look at what's happening.

Will do.

Also, I fixed the problem of maintaining the whole video playlist by hitting mainain playlist it separately for each drive on which I had video files. Got through it in about half a day.

As a sidenote, ffmpeg repeatedly crashes at times. Not sure why.