OK -- So note that while this doesn't appear all that different outwardly, there are some pretty substantial changes behind the scenes. Not to mention this thing was in a billion pieces on the floor not too long ago. I lead in with this to point out that there will probably be some weird problems (the entire synchronization system has been rewritten to accomodate the Karma).

Basically consider this alpha quality for right now, but it would be nice to get some feedback. I'm not putting it on the real jEmplode site yet, though I probably will for the next release.

http://www.inzyme.com/rio/install.htm

ms

I'm already livin' on the edge... might as well download it and try to shoot myself in the foot. I should have it installed in a few seconds

Ask and you shall receive. Apparently my sync attempt trashed my database. When it finishes rebuilding, I'll try again.

Not likely a jEmplode problem: see next message

Looks like I had the empeg plugged into a bad power cable which cut out at just the right time...

Meaning jEmplode = not at fault, or is it still suspect?

I doubt jEmplode had anything to do with it. It was just unfortunate timing; I plugged the empeg into one of those cell phone power bricks whose cord was apparently damaged earlier to try it, updated some playlists and tried to sync, lost, and then while it was rebuilding the database on player restart I happened to nudge the serial cable slightly (I have it consoled for some debug work) and it rebooted. Fiddling with the cable shows it's no good. Oh well, at least it was a sleazy adapter and not one of the nice, small ones.

Downloading now. Should I be seeing how it works on the Central, too?

Wow ... Speaking of feeling lucky .... You can try ... No idea what it will do.

nice dog.

That would be Sydney ...

first bug. on a virgin empeg, it can't create a 1st database. heck, not even emplode 2.1 can do it. had to use v2final.

here's the relevant log when i tried to sync.


e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
! fidfile_disk.cpp : 968:Why did write return zero for offset=0, size=0?

woof, woof.

It uploaded one album with no problems. I like how you made it so I can browse the playlists while syncing.

I'm not brave enough to try it on the central

I'm not brave enough to try it on the central

Seeing as how the prior version of Jemplode that I tried on the Central tried to delete everything, that's probably a good idea.

Been busy, haven't tried this version yet...

How would I get my empeg back into this state to test this out?

Disk builder ?

first impressions.

1) the ability to interact with the interface while syncing is dope, but takes a lot of getting used to. theres no indication on the main screen when i hit sync that anythings happening. can the transfer bar share the bottom half of the playlists tab? the details can stay where they are.
2) whenever i sync with emplode, when i go back to jemplode, it gives me a "Playlists referred to a missing tune or playlist with ID 272".
3) dupechecking is excellent and hashes are calculated really fast!
4) windows shortcuts (.lnk files) arent implemented yet =(.
5) tags changed on the hdd doesnt change the tags on the player if it recognizes as a dupe.
6) some of my files are not syncing thru. it gives a UTF16-LE error for the reason.
7) a while back, we had a discussion whether "remove completely" will apply to fids with more than one ref. right now it deletes it completely and changes all playlists that contains it. can we get a toggle where it wont do that? especially useful when i have a favorites playlist that contain singles and refernces to albums i want to clear.
8) so where's the autosync to hdd feature of the karma?

as you can see, a lot of this is is what i was hoping would be in jemplode. sorry. but the #1 thing that is most important is the quick hash generation. too bad i have to upload all my files again to generate the new ones. yay to 60gigs of uploading this weekend!

Interesting. It seems to behave better with the Central than the prior version did.

I get one error message when connecting which says "'All Music' referred to a missing playlist with ID number 272", but then it correctly displays all artists and albums, something the prior version didn't do.

Note that "All Music" is displayed in Jemplode in the same place that the root playlist of the Empeg Car would be displayed. Only I don't think you get to choose the name for it on the Central like you do on the Empeg Car.

I'm not going to try Synching with the Central yet, since "All Music" is coming up red, but I just wanted to say things are looking promising.

I had about the same error with the empeg but after I did the sync it went away and "All Music" wasn't red anymore.

turns out my player was stil v2b11, and that was what was causing it to fail (and give a weird FSCK error in jemplode). upgrading to v2final allowed jemplode to build the initial database on the virgin empeg.

272 = Unattached Items ... So what it calls "All Music", in jEmplode + RioCar it calls "Playlists", right?

All Music is most likely coming up red because it added Unattached Items to it ... You should be able to open the Transfer Details tab and see exactly what changes are pending (nice side effect of having access to that queue now).

I lied a little bit ... 272 is Unattached Items, but it's not that jEmplode has added it, it's that jEmplode has REMOVED it. I took out the Unattached Items check inside of jEmplode so it wouldn't break the Karma. I guess I probably need to add it back in as an optional setting. I believe what happens is that you don't actually have an Unattached Items playlist on your player, rather it's kind of faked. So Emplode creates a phantom 272 playlist to fulfill the reference that the root playlist has for it. I seem to recall old jEmplode did that also (made a non-syncing addition of Unattached Items in the UI).

more stuff.

1) jemplode allows you to exit while a sync is happening. really bad, since the bar is invisible to an unknowing user. did that accidentally.
2) you try to add some files (about 60 albums), not sync and revert changes, then readd the files, and the transfer queue goes crazy, with a lot of duplicates and nullpointerexception. my guess is that the revert changes function doesnt clear the queue correctly. didnt even want to see what happens if i hit sync.
3) starting jemplode right pane is on nothing. if you drag files to the pane, it goes to the all soup without getting into any playlist. suggest to default starting the right pane in the "Playlists" folder.
4) i was able to crash the v2final player by doing the following. i tried to upload the 60 albums again, then before syncing, deleted everything with "remove completely". it left me with a lot of "Updating Playlists" in the transfer details, so i synced, then without restarting jemplode, i readded the albums, synced again. can recreate the crash doing the same steps.
5) using the cancel button in the sync doesnt work. it keeps on going. you need to highlight all the items and rightclick, then cancel for it to actually happen.
6) WMA files arent supported.

272 is Unattached Items, but it's not that jEmplode has added it, it's that jEmplode has REMOVED it.

Hence JEmplode's desire to delete everything from the Central when you press synch? Everything on the Central is an unattached item, playlists aren't used by default unless you specifically create them.

why does jemplode shoot a UDP packet on startup?

Protocol UDP Connected to 44.243.178.24 Port 45592

Are they actually in Unattached Items or are they just unattached (slightly different) ... In current Empegs, it's legit to not be in any playlists (including unattached items), but the Unattached Items playlist is still secretly there (Emplode hides it with some magic). I just fixed this, though, so Unattached should reappear in jEmplode (next version).

ms

Broadcast discovery ... It broadcasts a '?' on the empeg's port and any Empegs on the network respond to the request. If you don't need discovery, you can turn it off in the Select Connection Dialog's options menu

I'm telling you this like you didn't write the faqin FAQ.

Are they actually in Unattached Items or are they just unattached (slightly different) ...

I have no idea. All I remember is...

- Back in the old days of the car player, if something wasn't in a playlist, it was an unattached item, and that was a bad thing.

- When they added soup views to the car player and to the central, it became OK for there to be a song that wasn't in a playlist. So they hid the Unattached items and aren't displaying any errors about it any more.

I could be remembering all of that wrong, hence the reason I'm not understanding what you mean by there being a slight difference between Unattached and unattached.

I'm telling you this like you didn't write the faqin FAQ.

Heh, you know orders of magnitude more about this stuff than I do. I've looked at the synchronization code enough to know that it would be dangerous for me to try to grasp it.

Mine was missing ID 2, when it recovered. I guess I should try another sync. While it was rebuilding I went out for food, and had an adventure I will post details aabout to OffTopic shortly