It was a single selection only - didn't try multiple. But if Emplode also does it (Brad), then it's probably just a protocol thing on the Empeg side of the connection.

Cheers

There's definitely a bug with multiple selection and some of the play controls, but single selection is pretty straightforward, so I assume it's protocol also ...

Am I wrong to have hope that it could then be fixed?

Works fine already in the Hijack web interface..

I could change that impl to do a GET against the webserver if you have hijack installed ...

When doing "download" tunes from player to my computer, I've set it to name the files like this (from options):

{tracknr} - {title}{ext}

The problem with this, is that single-digit track numbers are not zero padded, so I have to go and rename the files afterwards, changing:

1 - Some Fun.mp3

into:

01 - Some Fun.mp3

Any chance of having JEmplode do the zero padding for us?

Cheers

http://jempeg.cs.caltech.edu/tagNames.html

if you do:

{tracknr:2} - {title}{ext}

it will do what you want ...

Yes, there is a padding feature already in Jemplode, I think the syntax is merely {tracknr:2} if I recall correctly.

Damn, now where'd that pebble go? It was right here a second ago...

Peachy!

Even better, "pos:2" which is what I wanted in the first place -- odd that the same spellings used BY JEMPLODE on the display don't actually work here.. "pos" instead of "Position", etc.

Cheers!

I think that Mike coded it so that if there's a no position, it'll use the track number. Or was that... If there's no track number, it'll use the position? I don't remember which...

There is actually a "tracknrorpos" tag (well, it's a virtual tag like "decade" is) I think that does this ... But there was a bug until a couple days ago that will be FITNR. I'll double check.

Each NodeTag object has a DisplayName and a TagName ... People wouldn't really want to see "pos" in the table header probably. Here are all the tags:

http://www.inzyme.com/rio/empeg/docs/api/constant-values.html#org.jempeg.nodestore.DatabaseTags.ARTIST_TAG

That's cool. The cribsheet you linked to earlier has all that I need on it, thanks!

Cheers

just noticed that the latest build of jemplode was created 1/10/04. should everyone using v50 that was downloaded when you announced it on the 8th "upgrade" to this bleeding edge one?

It's a really small fix for someone who was using jEmplode with their Karma (though it would apply to everyone). Track numbers weren't being written to MP3's properly when on download. I think that's the only real difference ...

You install Cantus and fix your tags.

My tagged albums are all nice. It's those weird bootlegs I have where the tags are a mess, and I doubt this will help.

In fact I'd be shocked if anything short of listening and recognizing the music with some sort of acoustic algorithm would help in any case (and certainly not in all cases)

recognizing the music with some sort of acoustic algorithm

you try MusicBrainz?