Webplayer Jukebox app.bin

[Martin_L]

@pennhaven:

I'm not seeing any button in the upper right of the "catalog page".

The first page shown is the playlist. With the "square with lines" button you go to the catalog page (to select songs) the first page you see is the catalog that relies in a database (requires local drives attached, and a .wdtv folder in the root). At the upper-right corner there is a "files" button, to change to the catalog that relies on folder-browsing. To go back to the database-catalog, you can click the button at that corner that now reads "database".
I do not see a reason for these buttons not showing (even if the database-catalog functionality won't work for you because your files are not local).
If you provide more detail, we could try to figure something else with respect to that problem.
(Depending on your browser you may not see a button, but only the words "files" or "databases". Clicking them also works.)

(Please, test the application with a local drive to see functionallity, and from that, you will be able to compare)

Possibly the issue is that I'm using shares mounted from my NAS and not directly attached USB drives. I'm using 1.05.04 SVN rev 640 with a .wdlxtv.db file on the root of my music share, but I don't know if the SQLite DB will function that way.

I do not have experience with mounted shares. Certainly the current app will not work for remote files in that setup.
Your comment makes me think that I might need to include a configuration box to define the root for browsing files. I will consider this for future versions. In the meantime, you may need to tweak the file itself ("webplayer.pl") within the app.bin. (Unless your shares get mounted in /tmp/media/usb/...)
About the database... well, I would need a sample file to see how the contents are organized and how the app could be adapted to work also with shares. I can not prepare a specific setup to test this, but we will see.

Regards,

Martin

[Martin_L]

I'm having issues too, because of the dreaded 'media library requires more space' problem. dmaosd does not seem to realize that the drive has plenty of space, thus it does not create the .wd_tv/*.cas database. I have to browse using the folder structure, because I can't figure out what's wrong.

@naltimari:
Sorry to hear that. The application requires a .wd_tv/*.cas database to use part of its functions. Certainly, browsing folders will work.
You need to solve the database creation problem (this is not an issue of the application). I guess that it is because of partitions... maybe wdtv does not expect partitioned drives.
I assume that when you access your files on the TV, the same problem is present: no genre/album/author browsing, only folder browsing.
Have you tried a non-partitioned USB memory for testing?
Does deleting ".wd_tv" dir, to force wdtv rebuilding the database, help?
I did not face that problem so I can not offer further help. I suggest you to post the error in another thread of the forum to seek more expert help.

Good luck!

Martin

[pennhaven]

@pennhaven:

I'm not seeing any button in the upper right of the "catalog page".

Possibly the issue is that I'm using shares mounted from my NAS and not directly attached USB drives. I'm using 1.05.04 SVN rev 640 with a .wdlxtv.db file on the root of my music share, but I don't know if the SQLite DB will function that way.

I do not have experience with mounted shares. Certainly the current app will not work for remote files in that setup.
Your comment makes me think that I might need to include a configuration box to define the root for browsing files. I will consider this for future versions. In the meantime, you may need to tweak the file itself ("webplayer.pl") within the app.bin. (Unless your shares get mounted in /tmp/media/usb/...)
About the database... well, I would need a sample file to see how the contents are organized and how the app could be adapted to work also with shares. I can not prepare a specific setup to test this, but we will see.

I've resolved the first issue. That was due to me not properly disabling the s99user-script code which loaded the original mozzilla/Wondercow webplayer.perl code. So now I am actually running your app.bin, not the older version, and now I see all the proper buttons.

Still not able to utilize the database however. Xmount mounts the shares at two points. So the relevant share in my case is mounted:
/tmp/media/usb/Audio
/tmp/media/usb/USB2/Audio

Your configuration / database origin dialog shows only:
/tmp/media/usb/USB2/Audio/nann-nnnn

So, if my understanding is not incorrect, with a .wdlxtv.db file on the Audio share, if I unpack your app.bin and edit webplayer.pl to use /tmp/media/usb/USB2/Audio should I be in business? Or am I completely confused or noncomprehending what the latest sqlite functionality is about and how it relates (or does not) to your app.

Since you mentioned sqlite earlier I didn't expect a need for the .wd_tv/*.cas database mentioned the naltimari posts. I thought that .db was for the original WD media library and that your app was using the new pdo_sqlite added to the 1.05.04 svn. I didn't expect the original media libary db was still playing a role. Does your app actually utilize the pdo_sqlite or not? Do I need to have Media Library enabled in the OSD menu and forget about the .wdlxtv.db files?

Sorry for my lack of comprehension.

[naltimari]

The application requires a .wd_tv/*.cas database to use part of its functions.

I opened the Perl file and noticed that... It's been ages since I don't code anything in Perl, but that was easy to spot.

You need to solve the database creation problem (this is not an issue of the application). I guess that it is because of partitions... maybe wdtv does not expect partitioned drives.

I'm assuming that, too, because I have another bi-partitioned HD that suffers the same problem (even though it's a WD too!). I tried a single-partition 8Gb pendrive and the error does not happen.

Does deleting ".wd_tv" dir, to force wdtv rebuilding the database, help?

No, I turned the 'Media Library' feature off, erased the .wd_tv folder, and then turned the feature on again, no luck.

I suggest you to post the error in another thread of the forum to seek more expert help.

Thanks, but I couldn't find any solutions here, and WD's support site also does not offer any help, besides turning the Media Library feature off.

Unfortunely, I can't afford NOT to have two partitions; one of the USB ports is 'taken' by the wireless adapter, which leaves me with only one free USB port. I need an ext3 partition to hold the '.rootFS' filesystem, because I'm 'tinkering' with the firmware. So, I have to have a 2nd partition for all my media files, and it needs to be a NTFS because eventually I re-connect the portable USB HD to non-Linux devices (my notebook, my Wii, whatever).

Now, moving along: since it's dmaosd that creates this internal .cas database, and dmaosd is closed source, wouldn't it be wiser to NOT rely on this format? Anyway, you could make an 'abstraction-layer' that works with the .cas and some other schema (like minidlna's, for instance)

[Martin_L]

Note on the application:
The database functions (for this version), rely on the database (wdtv.cas) created by WDTV software on each drive (and stored in the .wd_tv folder) connected to the USB ports. Thus, it works only for local drives, and requires the original WD 'Media Library' in the OSD menu feature on, to create the index (you can turn the feature off once created if you do not change your files, and you do not need updating). It also needs the sqLite executable (which is included in custom firmware versions 0.5.x.x) to access the database.

Development notes:
A potential hack for the current version to index files in remote shares (or inaccesible partitions) would be to expose at least once that drive locally to the wdtv USB, to create the index, and, when later the shared drive is mounted remotely, it would have a ".wd_tv/wdtv.cas" in its root dir, with the relative paths of the files correctly stored, thus being accessible (this is in theory, I did not test it).
Any ".wd_tv/wdtv.cas" hanging from "/tmp/media/usb" can be potentially located and used by the application.

I could not find enough info on the .wdlxtv.db files, wdlxtv-db-tool, or the '/tmp/wdlxtv.db' and '/usr/share/wdlxtv-db/wdlxtv_db.sql' files. I would really appreciate if recliq (or anyone else) could enlighten me here about the potential use and behavior of these files. By browsing the wdlxtv-db-tool code, I got the impression that this is only for video files, but I could be wrong.
If I could find info about all this I could modify my app to use both systems. (my searchs have been not very productive).
(@pennhaven: what do you mean with "pdo_sqlite"? have a php api for accessing multimedia meta-info been implemented? where do I find that info? This app currently uses the sqLite executable to access the original WD media library.)

My initial (still future) aim when developing this app was to have a programable UPnP control point (or DLNA Media Controller) located at the WDTV, with multiple potential interfaces (web, http commands, and even a UMSP plugin), that could interact with any UPnP/DLNA renderer (the WDTV itself or any other in the network) and with any uPNP/DLNA Media Server (at the WDTV, i.e. minidlna or other in the network). In fact, WDLXTV is already a renderer and can be a media server.
The app currently controls WDTV media renderer (thanks to "upnp-cmd"!) but lacks the functionallity of interaction with media servers. This is a huge challenge and help in this direction would be greatly appreciated (naltimari, do you feel like going in this direction?).

Thanks for your suggestions!

Martin

[Martin_L]

@naltimari

Unfortunely, I can't afford NOT to have two partitions; one of the USB ports is 'taken' by the wireless adapter, which leaves me with only one free USB port. I need an ext3 partition to hold the '.rootFS' filesystem, because I'm 'tinkering' with the firmware. So, I have to have a 2nd partition for all my media files, and it needs to be a NTFS because eventually I re-connect the portable USB HD to non-Linux devices (my notebook, my Wii, whatever).

Just a bit off-topic, but you may not have thought of the possibility of using a USB hub. It actually works (I succesfully tested a Flash memory firmware + media files on HD connected to the same USB). I did not test whether the .cas db is correctly created. This alternative could work for your setup. I got my hub for $4. Please make me know if you have positive results.

Hope it helps!

M.

[Martin_L]

@pennhaven

check this:
http://lime-technology.com/forum/index.php?topic=11126.msg107237#msg107237

http://forum.wdlxtv.com/viewtopic.php?f=&t=1585
http://forum.wdlxtv.com/viewtopic.php?f=&t=570

you may need an .addMounts file on the root of a locally attached USB drive. I do not now if this procedure still applies with recent firmwares.

Possibly an easier way:
http://forum.wdlxtv.com/viewtopic.php?f=3&t=6020&p=49877&hilit=addmounts#p49898

Martin

[pennhaven]

@Martin L

@pennhaven
you may need an .addMounts file on the root of a locally attached USB drive.

Thanks for the followup and clarification regarding the database. I was aware of the need for .addMounts to facilitate the Media Library with shares - just didn't realize you were using the Media Library database, which unfortunately has not worked reliably with my NAS. When I have tested it works initially, but over time the database loses track of the share contents and media files start to disappear from the index. I suspect this may be due to my utilizing S3 sleep on my NAS when not in use. I was hoping that you had a new approach which might result in a more robust database.

I could not find enough info on the .wdlxtv.db files, wdlxtv-db-tool, or the '/tmp/wdlxtv.db' and '/usr/share/wdlxtv-db/wdlxtv_db.sql' files. I would really appreciate if recliq (or anyone else) could enlighten me here about the potential use and behavior of these files. By browsing the wdlxtv-db-tool code, I got the impression that this is only for video files, but I could be wrong.
If I could find info about all this I could modify my app to use both systems. (my searchs have been not very productive).
(@pennhaven: what do you mean with "pdo_sqlite"? have a php api for accessing multimedia meta-info been implemented? where do I find that info? This app currently uses the sqLite executable to access the original WD media library.)

Regarding pdo_sqlite for php 5. It was added to the svn in rev 639.

I think we should include pdo_sqlite for php5 as soon as possible into the firmware.
To handle images in sqlite with blobs you need either a perl or php module since the sqlite3 shell binary seems not able to handle them... at least I didn't manage to.

pdo_sqlite.tgz

@ b-rad / recliq

I suggest that Martin L please be provided with access to the beta forum, developer status, etc.

[Sniper_Swe]

player looks great on smartphone nokia n9 meego harmattan:)
strangly it looks better then both firefox and ie8:P

picture: http://yfrog.com/ob7jip

[KAD]

finally got around to trying this out, and it sounds like I've got the same issue as pennhaven
all my media is on a mounted NFS share, so I was not able to access any media using this webplayer

KAD