meskibob wrote:Have you gone through and completely cleaned out the database since upgrading to one of the newer versions?
See the following for how to reset your media library: viewtopic.php?f=6&t=1410&p=6444#p6429
Try reseting the media library, disable it, close out PMS, reopen it, and then enable the library. That should hopefully reset the db, and then all you need to do is browse in the XMB to start creating the cache.
As written, the instructions are a little inaccurate. You'll have to save the settings before closing PS3MS. Otherwise, when you reopen PS3MS the Media Library settings will already be enabled by default. It's no big deal, but with this in mind I did the following:
1. Disabled the Media Library under Navigation/Parsing Settings.
2. Saved settings.
3. Closed PS3MS.
4. Restarted PS3MS.
5. Enabled the Media Library.
6. Saved settings.
7. Click the "Restart HTTP server" button.
8. Checked the contents of the \database directory.
Unfortunately, these steps don't appear to have completely reset the Media Library since the \database directory still contained all the old files and their original content. Instead, I went ahead and deleted the \database directory to insure no cross contamination.
meskibob wrote:With that post, the scanning feature (the magnifying glass just above the share settings) was rather slow, but with the latest versions it is much faster and is probably recommended for your case. Note that when it is doing the scan you probably shouldn't be browsing through PMS on the XMB, as it tends to screw things up (atleast in my experience).
After deleting the contents of the \database directory, I then clicked the magnifying glass and PS3MS went through the two shared folders of 2,757 files. I discovered that there are actually two different completion times.
The first occurred when the magnifying glass button returned to a "Start" state which was immediately preceded by the cleaning up of the cache. That took 39 minutes. It took an additional 8 minutes before JavaW.exe was finished with the database and the CPU returned back to zero along with the hard drive activity ceasing. Total time was 47 minutes and change. This is where a accurate progression gauge (or at least a status bar that refreshes properly) would have come in handy, because doing anything during those last 8 minutes would have resulted in errors.
Also, I was not browsing through PS3MS on the PS3 while this was all taking place. In fact I was listening to some MP3 files from an attached thumb drive off the PS3 to pass the time, letting the computer work unobstructed.
Once that was finally finished, I quit the MP3 playback on the PS3 and went over to the PS3MS directory. Then selected the first (larger of the two) shared PS3MS directories. Once again I received twice the "Media Server Error: A DLNA protocol error (2006) has occurred", followed by the "There are no titles". However, back on the computer JavaW.exe CPU usage was again going through the roof. This carried on for 11 minutes with no change to the database files or any other files that I found. So, who knows what the heck it was doing for 11 minutes.
Should, for whatever reason, the PS3 disconnect during this time (DLNA 7531 errors aplenty), you won't be able to properly reconnect until JavaW.exe finishes. PS3MS doesn't know the PS3 disconnected. PS3MS will put the PS3MS icon back in the XMB, but upon entering you will see nothing but a DLNA 7531 error. You can trick PS3MS to make the Restart button clickable again, but you'll have to wait for JavaW.exe to finish or you'll have to kill off the process as PS3MS is off in it's own world and will appear locked up. Once revived, PS3MS will then spend an additional 11 minutes in that far away mystical place as before.
Once JavaW.exe calms down, I then went back to the PS3MS directory and now the entries started to appear one by one at a blazing 77 Kbps, with about four second gaps between each burst of 10 entries, making for an average of 18 Kbps! Since playing a video can stop the directory from getting completely listed, it took an additional 15 minutes to list the directory.
If the PS3MS program is restarted (or only it's server) or do certain things with the PS3, the cache on the PS3 is gone and PS3MS Media Library is of no obvious immediate value. Re-entering the PS3MS directory will again result in two "Media Server Error: A DLNA protocol error (2006) has occurred", followed by the "There are no titles". JavaW.exe is back to doing it's mysterious high CPU usage for the next 11 minutes. Once JavaW.exe calms down again, re-entering the PS3MS directory the contents will again begin to slowly appear and after 15 minutes (now a total of 26 minutes later) the directory is browsable again.
In review; it takes 47 minutes to build a cache that appears to be ineffective. Then 11 minutes for mysterious things to take place. Followed by an additional 15 minutes to display the entire contents of a shared directory. From start to a completely usable directory took 73 minutes, provided that something doesn't get restarted, then it could go as high as 110 minutes for the dust to finally settle.
Keep in mind up to this point all of this time was used to get just one directory to fully list it's contents. I'm guessing that the time for other directories to display are reduced by work that was first accomplished getting the first directory to appear.
Hopefully I've demonstrated that there is a relationship between directory size and the PS3 timing out. The DLNA 2006 error would never appear if it wasn't for JavaW.exe being totally consumed with it's Area 51 stuff and would instead send data to the PS3 in a reasonable amount of time. I would argue that a reasonable amount of time is defined by the first 30 seconds if you do not wish to see a DLNA 2006 error and/or before an additional 30 seconds if you don't want the process to completely fail the first time entering the PS3MS directory.
Anyway, I don't expect my results to match identically to others. There are factors which will change the timing. Including earlier versions, which the last time I checked, don't have this problem. So, YMMV.
Last but not least, I do appreciate your input on this matter with your suggestion to rebuild the Media Library. Whether it sounds like it or not, I also appreciate PS3MS and the author(s). I'm only trying to determine if there is a problem and then bring that problem to the attention of those that can do something about fixing it, that others and myself, are experiencing.
P.S. I haven't even gotten around to tracking down the audio and video freezing and unfreezing of PS3 compatible MPEG-1 videos during playback problem. And, how it ironically happens more often with a wired connection than with a wireless one. :/
Oh, and before I forget, if you turn off the PS3 with the controller, PS3MS still says, "PS3 has been found!". After waiting 10 minutes reached around back and flipped the main power switch. PS3MS still showed the PS3 as found. I then unplugged the router with no change. Looks like PS3MS is seeing PS3 ghosts.