Yay! It's heartwarming to know someone appreciates the work I put in. I had thought about your idea for the codes, and yes frankly the internal ID is prone to change on rescan. My general process has been that I tend to update in bulk, so I print a new book. It is clearly less than ideal, and I have thought about a server side mod to make the IDs static. If someone else is interested in using the scripts, it would possibly provide me some drive to dig into that deeper.
I would think an ISBN number would also be a good way to go. A tie in with Amazon's S3 service may be a good way to get that data en masse. I think if anything, I would likely support them both, as what I have works for me. We would need some way of ultimately translating the CD's barcode to a slimserver album id + artist id, or write a server plugin that allows to call via an ISBN number stored in the DB. With slim's db schema this would be harder than it sounds. I have printed my books with this: http://www.staplescopycenter.com (the company I work for has an interest in people using this; but really I honestly just think it is a great service as a customer.) It has worked out really well, I upload a PDF and pickup a 1500 page three hole drilled printout in a couple of hours. I don't think I could print it myself in any cheaper/easier way. RFID tags would be another (perhaps greener) way to go if I could find a cheap source for them. If you download the software, the README file has some recommendations and pointers on scanners. Bluetooth scanners do seem hideously expensive, and finding a cheap/working scanner on ebay seems to be nearly impossible. I am very happy with the one I have. One idea I had that I have not done is to make a barcode widget with a scanner + gumstix (http://gumstix.com/). The bit that translates from barcodes to slimserver CLI commands would run on the gumstix, and could send slimserver commands via wifi. I will say cuecats are utter crap, don't consider one for more than rudimentary proof of concept. If you are in the SF area I'd be glad to give you mine to be rid of them. If you get a scanner and get things setup, I would be glad to do some custom work. I mainly got it to a point where it worked well for me, and QA'd some with another forum user, I have not worked on it much more b/c it does what I need, was not going to write features for no-one to use :) -Chris On 5/15/07, smst <[EMAIL PROTECTED]> wrote:
I was thinking about a barcode-reading feature some time ago (mentioned it 'in this forum thread' (http://forums.slimdevices.com/showthread.php?t=20138)), and today I remembered it. And I see that an implementation exists! Excellent. I particularly like the use of a few special barcodes to control modes and other functions. Thanks for putting the work in; it looks very cool. I've still not printed a catalogue of my collection (the expense of the trading card storage and a new printer doesn't fit well with the relatively low priority of the printout!) but wanted to make a suggestion anyway, in case it's useful for others. It concerns the ID used to identify a given album: where does it come from? Is it a SlimServer db internal ID? Is it prone to change on a rescan? I propose this: have the basic play-this-album barcode be exactly the barcode printed on the original CD's packaging. For those albums which don't have that metadata stored, use a number based on the db ID (or whatever is used currently) but adjusted to be in a range illegal for the CD barcode. (I'm pretty sure there are rules and checksums for those barcodes... least elegantly, they're not longer than 14 digits so an adjusted ID above 1,000 million million would be sure not to clash!) Personally, I have a PRODUCTNUMBER tag on every file (where the CD had a barcode!) containing the relevant digits. I imagine that one could extend the SlimServer db to include a custom album ID based on a user-defined tag, or generated automatically in the absence of such a tag. (I don't know if that's easy to do or not; it's just an idea meant to trigger discussion.) The obvious upshot of this is that the barcode scanner will now work in the absence of a printed catalogue: I just scan the barcode on the disc, which is on the shelf next to me (as I still find a use for all those bits of plastic; haven't got SBs everywhere yet!). Everything else ("Play all by this artist", changing mode, random mix, etc) can be triggered by IDs outside of the album ID range. "Play all by this artist" could be implemented automatically, without recourse to another ID: if the scanned number is in some special range outside of the album range, chop off all but the last 14 digits to identify the album then dereference it to the artist. One could imagine other such special ranges (eg 3x10^15, or '3' plus a 14 digit album ID, could mean "take me to the album so I can pick a track"). Since I don't have a barcode scanner yet, and may be the only person who would benefit from this, I'm not asking for any of it to be implemented! I'm merely thinking aloud. And on that note: would I be right in thinking that cheap barcode scanners plug into a PC? I'd like to buy one, but I won't have a PC in the living room, or even a laptop or PDA (and if I had the latter, there are some good SlimServer skins to use instead). Does anyone know of anything wireless (IR, bluetooth, wifi)? Although presumably that won't be cheap. Thanks again for DirectPlaybookPDF -- even though I haven't bought any hardware to use it yet, I appreciate the fact that the software exists and you've taken the time to make it work. -- smst ------------------------------------------------------------------------ smst's Profile: http://forums.slimdevices.com/member.php?userid=752 View this thread: http://forums.slimdevices.com/showthread.php?t=29630 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
