"there isn't a fid 2 on this device"

Posted by: julf

"there isn't a fid 2 on this device" - 01/03/2007 18:29

I am using mp3tofid and rsync to keep my empeg and my main mp3 server in sync, together with jemplode. But every time I sync, I get the error message "there isn't a fid 2 on this device" from jemplode. Does fid 2 have any magical special significance?

Posted by: pim

Re: "there isn't a fid 2 on this device" - 01/03/2007 20:53

Quote:
I am using mp3tofid and rsync to keep my empeg and my main mp3 server in sync, together with jemplode.

You can't really mix mp3tofid and (j)emplode.

If you use (j)emplode and switch to mp3tofid+rsync, all your music will be reloaded.

If you use mp3tofid+rsync and the switch back to (j)emplode, you should be able to change things manually again. But if you then use mp3tofid+rsync again, it will undo all those manual changes made by (j)emplode.

Pim

Posted by: pim

Re: "there isn't a fid 2 on this device" - 01/03/2007 23:36

Quote:
I get the error message "there isn't a fid 2 on this device" from jemplode. Does fid 2 have any magical special significance?

mp3tofid writes a fake fid #0 of type "illegal", creates the root playlist at fid #100 and then starts allocating starting at fid #120. I based this on inspection of the database, the free empeg sources and on developer information.

I never came across fids 1-99. But then I never have used jemplode.

Pim

Posted by: julf

Re: "there isn't a fid 2 on this device" - 02/03/2007 04:56

Quote:
You can't really mix mp3tofid and (j)emplode.

Well, you can, if you are really, really careful

I don't actually use jemplode to upload any music - only to check on things.

Posted by: Roger

Re: "there isn't a fid 2 on this device" - 02/03/2007 06:02

Quote:
I never came across fids 1-99.

Fids < 0x100 are reserved, as is 0x110. See the emptool source code for details.

Posted by: dr_dos

Re: "there isn't a fid 2 on this device" - 03/03/2007 23:01

Quote:
Does fid 2 have any magical special significance?

It may have - but IIRC, after I upgraded to a 80GB HDD I saw the same error message until I re-built the DB several times. It then just disappeared...

Peter