New Problem since Beta 11

Hi All-

Installed b11 and Hijack 193 (along with the new Emplode) on Saturday and all seemed great. Now I'm seeing a weirdness when I upload songs with Emplode.

The upload process goes along fine..all the songs seem to get there but when it gets to 'restarting player' it just seems to hang. The blue led pulses slowly on the player and the restart never happens. After a timeout I get this error from Emplode: Synchronize failed while restarting player. An operation was attempted on something that is not a socket. (error 0x80072736.) I then pull power to the player and restore it and do a resync....this causes the database to get rebuilt for a minute or so and then all is fine.

Any ideas what's up with me and/or the player?

TIA,

Bill

There is a known bug in beta11 with restarting the player after a synch. I think it was Roger who explained that the player is in a "wibbly wobbly world" or something like that.

If it's the known bug, don't worry about it. Your synch still worked, and all is still well. Reboot your player, exit emplode and re-open it, and everything should be OK.

ya i get the same thing.. ive always gotten that in b7 and b11, its not really anything major.. just have to manuuly pull the plug.

They *still* haven't fixed this damned bug??

I just downloaded beta 11, hoping that this problem, at least, had been solved.

They *still* haven't fixed this damned bug??

Actually, it's a whole new bug that behaves similarly to the old one.

I like this thread - the "wibbly wobbly world" of the player and the "whole new bug that behaves similarly to the old one" have just cheered up a particularly dreich morning

Glad to see technology bringing a little fun into the world!

They *still* haven't fixed this damned bug??

I guess we must have been busy with the 100 (count them) other bugs fixes.

Rob

I have been very impressed, no more UI lock-ups on mime. Thanks guys!

BETABETABETABETABETABETABETABETA

It is just a minor issue however... I mean, restarting emplode and pulling the power cable out for 2 seconds hasn't managed to ruin my day yet. I do appreciate priority being given to slightly more significant bugs such as the "copy and paste" bug and straightening of the VU meter needles:).

I have been very impressed, no more UI lock-ups on mime.

My UI locked up once under 2.0 beta 11 while home connected. No lock-up problems while car connected, yet.

I've had quite a few lock-ups both in the car and at work/home with 2.0b11. I haven't bothered to report it before because I knew the Empeg guys are aware of it.

Mine locked up in the car on my way to work today. After pressing skip-right. Even the hijack-menu doesn't come up.

MArius (Escort Cab + MArkII)

Ok, Mine locked up once now too. No problem.

Maybe if windows my box booted in <5 seconds too, I woulnt mind when it crashes either.

I have found that if the player is in stand-by mode the sync doesn't lock up. If the player is "on", that's were the problem occurs.

Have had 4 hangs with beta 11 in the car (without hijack at the moment) - buttons do not respond, and the transient info stops during it's scroll off. Everything works fine musically so I just leave it until I have to adjust something, and then its a pull out of cradle and reinsert.

Ah well, the hazards of beta

I'm just glad you guys are continuing to develop firmware for a player that has been discontinued. I just wanted to say thanks for coming out with new firmware, and thanks for releasing Beta versions so we have something new to play with in the mean time.

I'm a new Rio user, started off with the new beta code, really liked it, and then I got the lock-up/socket error as described above during the restarting of player.

Then after a number of sync's (I added another 15GB of music and changed LOTS of tags), I got an error about the sequence number mismatch and that "someone was here before us". I checked the .ini file in /empeg/whatever and sure enough, it listed 35 and emplode was expecting to write 36. This bothered me because I had made about 45 mins of changes just in tags alone and I couldn't figure out how to fix this.

So I exited emplode, lost my changes, rebooted the Rio and could connect again.

However, this time I connected via USB instead of ethernet. Now when I upload with emplode and make changes, it sits for a long long long time during the writing player configuration section, but doesn't lock up with the socket error. Some pieces also seem faster, but who knows.

Anyway, love the player. I already have some things on my wish list but I'll wait and see how things play out as I learn. I'm a PJB owner as well (portable mp3 player - see http://www.pjbox.com/ for more info) so I have certain wants/needs.

it sits for a long long long time during the writing player configuration section

Check to see if it's this bug and get back to us...

Yes, a fellow rio owner who sits next to me saw my post and said "hey, wait, there's another bug" and sure enough my visual favorites was very lengthy in the DSP section. I went into emplode to remove all of them (I don't care for favorites right now) and I'm re-sync'ing.

Of course, NOW that I'm re-syncing, it took about 2 minutes for it to "check disk integrity" and it's still sitting on "remounting disks." for the 2nd minute in a row. I wonder if something else got messed up.

ok, it just finished. I notice again that the socket error doesn't occur in USB transfer mode, so I'll probably stick with it.

I have experienced the same error a time or two, but it is intermittent. No compaints!