I, like many other posters, have been expericing issues with the Promise DLNA plugin.
As detailed, a few posts above, my main issue was that, while the 'Pictures' and 'Music' shares on the NAS device pretty much seem to behave as expected, the 'Video' share would only partially show it's contents on my PS3.
I have been working with the New Zealand distributor for the Promise SmartStor devices and Promise Support in Asia, on this issue... well, as far as I can tell, I've done all the work and just reported to them both, often twice a day.
The tests that we have performed over the past week, have focused on Promise's belief that there must be a corrupt/damaged file, somewhere in my first sub-folder in the 'Video' share - this was based on:
1) Only this first sub-folder under 'Video' ever appeared. The other three never showed up.
2) Often not all of the files and folders, inside this first sub-folder, would be present.
Here is what I have discovered... if the Promise DLNA plugin, while indexing, comes across a file that it doesn't "like", it either halts the indexing process or causes it to display inaccurate information.
This was "proven" (and I use this term loosely), with two specific tests:a) Relocate first 'Video' sub-folder into 'Pictures':
The result of this test, was that only the 'Picture' share displayed on my PS3... neither 'Music' or 'Video' showed up at all!?b) Relocate first 'Video' sub-folder - which was in 'Picture' - to another share on that NAS, not scanned by DLNA plugin:
The resullt of this test was that all of my media (expect obviously for this first folder) was visable... including my other sub-folders under 'Video' which NEVER appeared in the past!
Note: Between the tests, the only way to completely remove the DLNA indexing data from the SmartStor, is to disbale the plugin, remove it, restart the NAS, reinstall it and then enable the plugin - then wait for approx. 5 hrs.
Now, I don't believe that I have a "corrupt/damaged file" - in the traditional sense of the word - on my NAS device. So, the next stage is to find the "offending file" and more importantly, why the DLNA plugin doesn't like it.
I will keep you posted...