Revue and Accessories

[deviousrich]

hi,

i have two NAS with DLNA servers. both were working fine with the 2.0 media player, on the new player the first nas indexed and plays files fine, but the second nas (with a lot more files, 4TB of MP# and MKV) now wont work.

the media player complains it cant index this nas and even if i go to folder view i can see the files but it cant play them.

any ideas why? (nothing else besides the update has changed). i know the formats are compatable as they played perviously and still play through gtvbox player which i installed

very frustraiting to go backwards!

[jrichardson]

Can you tell me what DLNA NAS you are using?

Typicaly have the "Inxex Failed" message indicates that the LMP Scanner has run into a malformed file.  It's a bit frustrating, but there may be a bad MKV file that is causing the scanner to fail.  Especialy if it also happens when doing a "Folder" browse.

Find the bad file, and that should solve your issue. 

[ahsanur]

post your question in this topic you might get more help.

http://forums.logitech.com/t5/Revue/Post-Honeycomb-Logitech-Media-Player-Server-and-Bookmarks/td-p/7...

[deviousrich]

?i have two buffallo linksation pros

what gets me is even if i go to folder view none of the mkvs play on the second nas. i tried copying one to the first nas and that works fine which is why i think its got to be a voume of files thing. not even mp3s play off the second nas, either through folder view or standard view.

on that nas (the failing one) there mp3s, mkvs and pictures and the only thing that seems to work is pictures

 any way for me to tell what file the LMP scanner doesnt like? there are about 2000 mkvs and about 80000 mp3s so i am not going to manually check them...

is there any debug logs i can check? 

[deviousrich]

tried resetting everything and that didnt help either so i agree this must be something to do with the indexing.

anyone know the rules its using to index?

[Eferzz]

---

deviousrich wrote:

tried resetting everything and that didnt help either so i agree this must be something to do with the indexing.

anyone know the rules its using to index?

---

Are your multimedia files at the root of your share folder?  I would recommend placing your files into directories.  That way you can use a process of division to find out which files are causing a problem in indexing.  Scripting individual directory creation and file moving would be the easiest way.  Otherwise you can use a process of creating "n" folders and put an "n-th" amount of files into each one.  Eg., ten folders = tenth of your files in each folder.

Here's an example of a linux one liner to create individual directories for each file and move them into it.  It has to be ran while in the same directory of your files.  Provided that all of your multimedia files sit in a singular directory.

---

for i in `ls`; do mkdir ${i}.dir; mv ${i} ${i}.dir; done

---

[deviousrich]

hi,

yes everything is already in indervidual folders. one folder per movie (with JPGs in each) and one folder per album for the mp3s. no one folder is massive.

what gets me is this NAS works with every other application i tried and xbox, PS3, o2 Joggler and the old media player. its only this new media player thats failing....

[DefendeBob]

Mine isnt working either though, so you're not alone.

Id love to say that the updated media player is better, but its not seeing any of my content.

[CatLogitech]

Where is the DLNA that you are trying to access?

Have you checked your router firewall and tried disabling that as a test?

Did you disable your computer's firewalls and security software?

[deviousrich]

hi,

the DLNA is on a NAS. i have 2 NAS on the same network, one works with LMP and one doesnt the only difference is the size / volume of data on the NAS.

they all work with various other clients on the network so i have ruled anything but the revue out of the equation.

they both worked litteraly 30 seconds before the update for the revue came through (as was watching a film) and nothing else has been changed or rebooted since then.

the only thought i have is that the index process is failing at some point due to the quantity of files or one of the files it falls over.