#225741 - 03/07/2004 20:46
jEmplode 56
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
jEmplode 56 http://www.jempeg.orgHopefully fixes the problems people have had with hanging at Updating UI. Hopefully won't break everyone else
|
Top
|
|
|
|
#225742 - 03/07/2004 22:05
Re: jEmplode 56
[Re: mschrag]
|
journeyman
Registered: 21/08/2002
Posts: 63
Loc: Edinburgh, UK
|
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
|
Top
|
|
|
|
#225743 - 04/07/2004 01:01
Re: jEmplode 56
[Re: zexpe]
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
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 ...
|
Top
|
|
|
|
#225744 - 04/07/2004 14:15
Re: jEmplode 56
[Re: mschrag]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
|
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.
|
Top
|
|
|
|
#225745 - 04/07/2004 14:29
Re: jEmplode 56
[Re: mschrag]
|
carpal tunnel
Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
|
Quote: jEmplode 56
I don't have a PC with Java to hand right now, so perhaps someone could answer: how good is it at beyond-Latin-1 characters with v3 alphas? If someone runs it on NT/2000/XP, can they enter arbitrary Unicode tags, to be represented as UTF-8 on the player? What about 95/98/Me/Unix in a non-Latin-1 codepage, say Latin-5 or Latin-7? Does the Greek or Cyrillic make it into UTF-8 tags on the player properly? I guess it all just works, as it'd have to just work for RMML and Karma.
Just askin', y'know.
Peter
|
Top
|
|
|
|
#225746 - 04/07/2004 18:29
Re: jEmplode 56
[Re: peter]
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
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.
|
Top
|
|
|
|
#225747 - 04/07/2004 18:30
Re: jEmplode 56
[Re: tfabris]
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
Quote: So, what I'm reporting here is... Whatever work-around they did in Emplode should probably get put into Jemplode as well.
If Peter or other happens to know what might be causing this, I'll fix it up.
|
Top
|
|
|
|
#225748 - 04/07/2004 18:32
Re: jEmplode 56
[Re: mschrag]
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
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?
|
Top
|
|
|
|
#225749 - 04/07/2004 18:33
Re: jEmplode 56
[Re: peter]
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
Oh -- By the way, if you'd like to switch the Empeg to use Protocol2 ... You know .. That would be just fine with me.
|
Top
|
|
|
|
#225750 - 04/07/2004 18:36
Re: jEmplode 56
[Re: mschrag]
|
carpal tunnel
Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
|
Quote: Is 2.0 ISO-8859-1 only and 3.0 is UTF-8 by any chance?
Exactly, yes. That's why 3.x keeps a separate database file.
Peter
|
Top
|
|
|
|
#225751 - 04/07/2004 18:40
Re: jEmplode 56
[Re: mschrag]
|
carpal tunnel
Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
|
Quote: If Peter or other happens to know what might be causing this, I'll fix it up.
The underlying issue is that we misused strtol(3), not realising that -- as well as defaulting to decimal and allowing "0x" to specify hex -- a leading zero specifies octal, so "08" and "09" are illegal input and come out as zero. What I can't immediately remember is where these numbers with leading zeroes came from -- perhaps if people have track number strings with leading zeroes they got put straight into the *1 files and interpreted as octal. If so the fix is to always convert track numbers to numeric rather than string type, and write them out in decimal, thus ensuring no leading zero.
Peter
|
Top
|
|
|
|
#225752 - 04/07/2004 18:45
Re: jEmplode 56
[Re: mschrag]
|
carpal tunnel
Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
|
Quote: Oh -- By the way, if you'd like to switch the Empeg to use Protocol2 ... You know .. That would be just fine with me.
Yeah, it kinda staggered into life once a few months ago but would need plenty of extra work to make it even amersfoortably stable. Some fairly major things, like search windows and dynamic data support, are going to need rewriting.
Peter
|
Top
|
|
|
|
#225753 - 04/07/2004 20:13
Re: jEmplode 56
[Re: peter]
|
carpal tunnel
Registered: 20/12/1999
Posts: 31594
Loc: Seattle, WA
|
Quote: What I can't immediately remember is where these numbers with leading zeroes came from
A perfectly good ID3v2 tag with the tracks correctly numbered as 01 02 03 04 etc.
ID3V1 uses a binary byte for its track number so you can't specify leading zeroes. But ID3V2 uses a string as its track number, so it's perfectly valid to have an ID3V2 tag with leading zeroes.
Note that I didn't put these straight into the *1 files or anything. I just had a properly-tagged MP3 that I dropped onto Jemplode.
Edited by tfabris (04/07/2004 20:15)
|
Top
|
|
|
|
#225754 - 04/07/2004 21:22
Re: jEmplode 56
[Re: peter]
|
addict
Registered: 10/11/2000
Posts: 497
Loc: Utah, USA
|
With future Rio players all using USB MSC, does Protocol 2 even have a future on any other Rio products?
_________________________
-Aaron
|
Top
|
|
|
|
#225755 - 05/07/2004 05:15
Re: jEmplode 56
[Re: adavidw]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
Quote: With future Rio players all using USB MSC, does Protocol 2 even have a future on any other Rio products?
Well, yeah. USB Mass Storage doesn't work over Ethernet .
_________________________
-- roger
|
Top
|
|
|
|
#225756 - 05/07/2004 05:16
Re: jEmplode 56
[Re: Roger]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
Quote: Well, yeah...
Of course, this assumes that future Rio products have Ethernet...
Right now, the products don't use protocol2 over USB, anyway.
_________________________
-- roger
|
Top
|
|
|
|
#225757 - 05/07/2004 18:18
Re: jEmplode 56
[Re: peter]
|
carpal tunnel
Registered: 13/07/2000
Posts: 4180
Loc: Cambridge, England
|
Quote: how good is it at beyond-Latin-1 characters with v3 alphas?
In fact, I've just checked Emplode 2.10, and it works, although it might in fact just be copying the UTF-8 output of our tagging library straight into the *1 files not realising that neither is Latin-1. Three cheers for not knowing what you're talking about! (Emplode 2.10 doesn't display such tags correctly in its own UI, but the right thing gets onto the player.)
Peter
|
Top
|
|
|
|
#225758 - 05/07/2004 19:37
Re: jEmplode 56
[Re: peter]
|
pooh-bah
Registered: 09/09/2000
Posts: 2303
Loc: Richmond, VA
|
Quote: Three cheers for not knowing what you're talking about!
This has been my mantra for jEmplode for a couple years now!
Edited by wfaulk (05/07/2004 23:35)
|
Top
|
|
|
|
#225759 - 06/07/2004 05:44
Re: jEmplode 56
[Re: peter]
|
carpal tunnel
Registered: 18/01/2000
Posts: 5683
Loc: London, UK
|
Quote: it might in fact just be copying the UTF-8 output of our tagging library straight into the *1 files not realising that neither is Latin-1.
It is.
However, the reason that we never released 2.10 is that, for some reason, it was more unstable than v2.0-final, despite not having changed anything much.
_________________________
-- roger
|
Top
|
|
|
|
|
|