WDLXTV-0.4.5.3 - Doesn't show MovieSheets [Resolved]

[gregrocket]

WDLXTV-0.4.5.3 - Doesn't show MovieSheets after update from 0.4.3.2. I've checked setting and they look correct but the movie sheets that used to display no longer work. Icons do show images.

[recliq]

http://wiki.wdlxtv.com/How_to_use_Movie_sheets
try setting

Code: Select all

config_tool -c WDTVEXT=OFF

[gregrocket]

I have the WD Live Plus. Isn't that command for the WD Live?

I had movie sheet working perfectly before the update. Now I only see the icons images but not the movie sheets.

[NoSubstitute]

If you read it again, you will see that he told you to disable wdtvext.
What he didn't tell you is what to do to enable moviesheets.

Check the new movesheet wiki article. I think it will be all you need to make them show up.

[gregrocket]

Movie sheet where working perfectly when I was using v0.4.3.2 but stopped working after updating firmware to 0.4.5.3

Here is what I've just tried:
I opened Putty and issued the command: config_tool -c WDTVEXT=OFF

Opened web frontend and made sure under Tab "WDTVEXT Features"
MSHEETMODE set to SHEET
GENMSHEET - Checked
LISTMSHEET - Checked
VIDMSHEET - Checked
MOVIESHEET - Checked
LINKSHEETS - Checked

On the WD unit I went to setup and verified videos are set to "thumbnail mode" and under system settings "Display file size" is set to "Off"

I pulled the power plug, waited a bit, plugged it back in. I turned the WD on and waited for the flashing lights to complete. (This took a bit) Went into videos and still no movie sheets. The icons for each movie show the image of the DVD cover in each icon, as before, but the moviesheets that used to display before the update still do not show up.

[b-rad.cc]

http://forum.wdlxtv.com/viewtopic.php?f=57&t=2079&p=23999#p23999

[gregrocket]

WD HD TV Live Plus
WD Elements 2TB USB Drive
WDLXTV-0.4.5.3
Move Sheets worked when using XDLXTV-0.4.3.2 and stopped working after update to 0.4.5.3

Using putty I issued command: ls /msheets
WD Responds back:

Code: Select all

# ls /msheets
#

Then grep /tmp/media/usb /proc/mounts
ls -la /msheets

Code: Select all

# grep /tmp/media/usb /proc/mounts
/dev/sda1 /tmp/media/usb/USB2/96AC709DAC707A17 ufsd rw 0 0
\134\134192.168.1.50\134photos /tmp/media/usb/FreeNAS\040Photos cifs ro,mand,unc=\\192.168.1.50\photos,username=guest,posixpaths,rsize=64512,wsize=130048 0 0
\134\134192.168.1.50\134music /tmp/media/usb/FreeNAS\040Music cifs ro,mand,unc=\\192.168.1.50\music,username=guest,posixpaths,rsize=64512,wsize=130048 0 0
\134\134192.168.1.50\134music /tmp/media/usb/USB2/FreeNAS\040Music cifs ro,mand,unc=\\192.168.1.50\music,username=guest,posixpaths,rsize=64512,wsize=130048 0 0
\134\134192.168.1.50\134photos /tmp/media/usb/USB2/FreeNAS\040Photos cifs ro,mand,unc=\\192.168.1.50\photos,username=guest,posixpaths,rsize=64512,wsize=130048 0 0
# ls -la /msheets
#

[b-rad.cc]

what does this say:

Code: Select all

egrep 'LINKSHEET|WDTVEXT' /conf/config

[gregrocket]

Code: Select all

# egrep 'LINKSHEET|WDTVEXT' /conf/config
LINKSHEETS='ON'
WDTVEXT='OFF'
#


Also movie sheets are less then 500kb about 200kb ea.

[gregrocket]

Well after trying numerous things this is what I discovered as the problem.

I have a WD Elements usb hard drive that is hooked up to the WD Plus.
I wanted a single directory to hold all the movie sheets.
I named this directory on the WD Elements HD "msheets"
Put all my movie sheets in this directory.
I put the diretory name on the WDLXTV Web Frontend > Tab WDTVeXT Features > MSHEETDIR > /msheets/
This was the only way it would work for me in version 0.4.3.2 and it worked perfectly.

I did the update to 0.4.5.3 and movie sheets stopped working. It did not matter if the sheets where in the directory I made for the movie sheets or if I put them in the directory where the movies actually existed. I tried various things, as noted in my previous posts, but nothing worked.

Finally I just removed the /msheets/ reference in the Web Frontend under MSHEETDIR leaving it blank, rebooted, and movies sheets started working. I'm not exactly sure why this would change, if it's a bug or not, but that was the problem.