WD can see my servers but a ‘No Media in Folder’ message for both. Tried rebooting every switch, router and PC on my network and the WDTV numerous times. Also can’t get to any SMB shares (which I haven’t seen reporteed). Rolled back to 1.05.04 and everything seems back to normal. Thanks for trying guys, some of the new stuff looked good but all my important media is on Tversity so that’s a deal-breaker for me. I appreeciate that there’s an easy rollback process. For anuyone who doesn’t have the link:
same here
wd tv live gives “there is no media in the current folder”
and tversity gives an error "could not execute SQL statement, reason: unrecognized token: "" "
Yes it has been noted over in the Tversity forums for the latest Live+ firmware- http://forums.tversity.com/viewtopic.php?f=7&t=65812
Appears to be something specific to Tversity as I don’t have any similar problem with Twonkymedia. And I don’t recall seeing any similar reports for other DLNA servers.
You might want to contact Tversity support to see if they know what the problem is.
WDTV latest firmware and Tversity Pro 1.9.3 - everything works perfectly
A reported resolution has been posted over in the Tversity forum- http://forums.tversity.com/viewtopic.php?f=7&t=65812&start=15
It seems the profile description for the WD TV Live in TVersity to 1.9.7 is wrong.
Actually, I think the TVersity profile was CORRECT … until WD added a function.
The SQL Query that’s bombing out is the “CONTAINER” section.
The WD didn’t pass a Container in the previous versions, presumably meaning one may see PHOTOS and VIDEOS even if MUSIC is selected.
The WD’s now pass the top-level Container, so TVersity didn’t know that (until now) and that profile modification now sorts the CONTAINER into the correct section.
I think that will make both TVersity and the WD work better in that combination.
Someone let me know if I’m insane, because I’m looking at this purely as an outsider. I don’t use TVersity.
No not insane, but there seems to be some history to this problem that was just coincidental with the WD TV Live update.
The original user developed profile for the WD is in this thread- http://forums.tversity.com/viewtopic.php?f=7&t=51636
Note the line which is what the recent fix advises.
Other reports indicate that if you roll back to Tversity 1.9.6 or earlier, or just stayed on an earlier release then you don’t have the problem.
Tversity just had two recent back-to-back updates which is very unusual for them-
Version 1.9.6 (July 15, 2011) - added official WD TV Live support amongst many other things
Version 1.9.7 (July 29, 2011) - regression bug fixes
Previous release was in November 24, 2010.
Just idle speculation, but if it worked in Tversity 1.9.6 and earlier ( http://forums.tversity.com/viewtopic.php?f=7&t=65812#p143164) but not with Tversity 1.9.7, well I leave people to draw their own conclusions.
UPDATE- I stand corrected. The problem also occurs in a standard Tversity 1.9.6 install. However applying the change posted over in the Tversity forum (i.e. make it the same as the original user developed profile) makes it work correctly.
