Emplode 2.0b3: Error during "Checking Media"

Posted by: trevorp

Emplode 2.0b3: Error during "Checking Media" - 19/10/2001 07:35

I just added a playlist to emplode, and synchronised it. It gave me an error on the "Checking media" stage. I then tried to re-sync, and got an invalid cookie message, even though I did not power off the empeg.

-Trevor

-----
Mk 2, Green 12GB, Tuner, 2.0b3, 080000349
Posted by: tfabris

Re: Emplode 2.0b3: Error during "Checking Media" - 19/10/2001 07:45

The invalid cookie is for any time there is a mis-match between the connected emplode session and the player's current session.

This can be induced by either a restart of the player, OR, a synch error in emplode.

I have been in the habit of exiting emplode completely after every synch error, but I can see how this is confusing for some. Empeg guys: perhaps there's a way to handle this more gracefully in emplode? Such as close the current connected session window after you get a synch error?

___________
Tony Fabris
Posted by: Derek

Re: Emplode 2.0b3: Error during "Checking Media" - 20/10/2001 02:17

The only thing that is still very annoying about this Tony is that none of your changes have been uploaded to the empeg yet, and if you have to close emplode or the session you are going to lose all your changes! A failure checking media doesn't necessarily mean you have an invalid session does it (actually I think the thing is here that the "checking media" error shouldn't have occurred in the first place, but I'm sure it can be better handled anyway)

(list 6284, Mk1 S/N 00299 4GB blue [for sale]. Mk2 S/N 080000094 26GB blue)
Posted by: Roger

Re: Emplode 2.0b3: Error during "Checking Media" - 20/10/2001 03:20

It's a mess. We're thinking of using the database sequence number as the cookie -- this should save this hassle.

In future, it'll be properly transactioned, of course .



-- roger
Posted by: bonzi

Re: Emplode 2.0b3: Error during "Checking Media" - 20/10/2001 03:31

It's a mess. We're thinking of using the database sequence number as the cookie -- this should save this hassle.

Wasn't that sync number in config.ini intended to serve that purpose? The problem, of course, is to increment it when and only when database gets successfully changed.

Hence:

In future, it'll be properly transactioned, of course

But of course!

Dragi "Bonzi" Raos
Zagreb, Croatia
Q#5196, MkII#80000376, 18GB green