Posted by: mschrag
jEmplode 56 - 03/07/2004 20:46
jEmplode 56
http://www.jempeg.orgHopefully fixes the problems people have had with hanging at Updating UI. Hopefully won't break everyone else
Posted by: zexpe
Re: jEmplode 56 - 03/07/2004 22:05
Hey, that did the trick! Good work Mike - what would us Linux users do without your help?
BTW, while I'm here - how do soup playlist tags get assigned? With my Genre soup there's a playlist for every genre with that genre as the title, but the artist, album etc. fields are also filled out using an apparently randomly chosen track from that genre. Any particular reason for this behaviour? Doesn't really bother me, I just find it odd.
thanks very much,
Ross
Posted by: mschrag
Re: jEmplode 56 - 04/07/2004 01:01
Those fields are grabbed from the first track into the soup playlist. It makes more sense for something like an Album soup where Artist, Year, and Genre fill in. Maybe I should only do that for Album. Or make it a little smarter so that if one doesn't match, it converts to "Various" or something. That comparison is just another thing to slow that soup process down ...
Posted by: tfabris
Re: jEmplode 56 - 04/07/2004 14:15
Quick note about something I discovered with Jemplode, just noticed this morning...
I actually had this happen in either 54 or 55, but unless you did something about it in 56, I'm sure it's still there.
If you have your own V1+V2 tracks nicely tagged and filenamed, and sitting on your PC's hard disk, and you create a new playlist on the Rio Central, and drag and drop those tracks onto that playlist using Jemplode...
Tracks 8 and 9 will get the wrong track number on the Central. Because it's interpreting them as octal for some strange reason.
If I recall correctly, this is actually a bug in the Central itself. It's only on the Central, not on the Car player or the Karma as far as I know. I noticed it and reported it a while ago because it was happening in Emplode too. Since the code for the Central wasn't slated to be changed, someone from Cambridge (I don't recall who, sorry) stuck a work-around into emplode.
So, what I'm reporting here is... Whatever work-around they did in Emplode should probably get put into Jemplode as well.
Posted by: mschrag
Re: jEmplode 56 - 04/07/2004 18:29
I believe my EmpegSynchronizeClient code handles everything as UTF8 internally, but once it hits the wire for the Empeg it turns into ISO-8859-1. PearlSynchronizeClient obviously keeps it properly in UTF8. Is 2.0 ISO-8559-1 only and 3.0 is UTF8 by any chance? That might explain why this code is like this in my Empeg version. I think I just need to change the encoding name in my synchronizeTags method to switch to UTF8, so if it stops raining I'll bring the Empeg in and try it out.
Posted by: mschrag
Re: jEmplode 56 - 04/07/2004 18:32
Is this change perhaps that I just need to write out octal values in track number or all numeric tags when I'm talking to a Jupiter?
Posted by: mschrag
Re: jEmplode 56 - 04/07/2004 18:33
Oh -- By the way, if you'd like to switch the Empeg to use Protocol2 ... You know .. That would be just fine with me.
Posted by: adavidw
Re: jEmplode 56 - 04/07/2004 21:22
With future Rio players all using USB MSC, does Protocol 2 even have a future on any other Rio products?