OK - I ran into a space issue while doing my DB conversion, but it took me a while to figure out that this is what the problem was.. (Might want to make the warnings a little more obvious...)

Installed 2.0b3, started empeg,

loopcount=0
while loopcount<6 do

tried to play a song, invalid mp3 file.. ok..

ran emplode, tried to sync, got prompted to convert the DB, (keep in mind that I'm at work and doing most of this while I'm doing 20 other things..), clicked yes, (6000+ songs, this takes a while..) waited 20 minutes, got some warnings (didn't look like anything major, invalid mp3 warnings for some files..), clicked ok

tried to play song, invalid mp3
tried to re-sync, got error w/ unable to connect to db

loopcount=loopcount+1
done

expanded the field that the warnings were on, the actual error said that I was too low on disk space to do the current task

deleted playlist, resync'd, ran conversion again, same errors.

realized that just deleting the playlist doesn't delete the cd, found the album and deleted the reference to it in emplode's album list, resync'd, worked fine this time...


...SO emplode was acting correctly, but it would have been nice for the out of space error to have been more pronounced - as it is glancing at it didn't show it - I had to expand a field to read the entire message.

-mark

ps - I had about 9mb's free during all this.

This space used in memory of the victims from 09/11/01

How do you know if your database was converted successfully? The first time I had the request to do this, I cancelled (I was leaving the office, and did not want to get tied down for a while). I do not remember seeing the request again. I have synced successfully a few times since.

Paul G.
SN# 090000587 (96GB Smoke)
SN# 030103046 (10GB Blue - Emergency Spare)

I think my Mk1 is doing the same thing..Havent tried the Mk2 yet.

Does the cookie get reset on player start or on reboot? Because I've noticed the player restarts a couple times during the mass metadata change (supposedly due to invalid mp3's). Might it be this restarting that doesn't let me synch all these metadata changes?

_~= Dearing =~_
"WAY too happy about having #99."

Apparantly, that's what it was. I reinstalled 1.3, removed the offending tracks, and tried 2.00b3 again. After fixing the metadata, the sync went fine this time, presumably because the player didn't restart during the metadata process as it had before.
So, I can hear my music again! Yay!

_~= Dearing =~_
"WAY too happy about having #99."

The player's not supposed to restart during the metadata checking. If it does, get a serial trace and send it to carbugs@riohome.com.

-- roger

...some songs that aren't converted will not play properly..
-mark

This space used in memory of the victims from 09/11/01