When using the Empeg inside or in the car the buttons & remote stop responding after about 30 minutes. I'm using 2.0b7

It might be HiJack as well (just upgraded to v82 so I'll check it out)

Anyone else have this problem?

This "player stops responding to button input" thing has been there since 2.0b3 as a very rare and intermittent bug.

If you can reproduce it reliably (I can't), bring it up in the Bug Reports forum and see if the Empeg folks can help us diagnose it.

I had the same thing happening right after upgrading to beta 7 (no Hijack) and doing my first sync. I got an error at the "retreiving database" after the upload and tried to power off my player. It didn't respond. It did respond to 1 last remote button press (menu) but after that...end. The empeg seemed _incredibly_ slow just before all this happened. I tried to reproduce it but ofcourse the 2nd sync session went ok. My best guess would be something like a serious memory leak or something like that (I own an Empeg Mk2). Are these problems reported by RIO owners (16Mb) as well ?

Hmm.... Ok if I can make it happen again I'll report it :) wvloon I have a Mk2a (Rio Car).

I forgot to mention that it is random. And now that tfabris mentions it, I think it did happen with 2.0b3 as well!

Is there anything I can do with Hyper terminal like a memory dump of some sort next time it happens?

I wouldn't say very rare, in my case it happens about once a week. Unfortunately there is no sign of a pattern as to when it will happen.

Well today I got up and my remote doesn't work anymore! So I decided to change the battery! Everything works!

I feel like such a dumbass :) But now the front buttons have stopped reponding! hmm...

I had an odd "battery failure" problem when I was demoing my Mk2a the other week. I had two remotes, the Kenwood and the Rio. I was using the Rio for the demo (the Kenwood was in my shirt pocket) when the unit stopped responding to the remote (front panel was still working).

I whipped the Kenwood out of my pocket and tried that, it worked fine. I tried the Rio again, no joy. So, dead battery in the Rio I thought. I wanted to use the Rio for the demo (I have forgotten most of the cryptic buttons on the Kenwood), so I swapped the batteries between the Rio and Kenwood.

The result was, as you have probably guessed by now, that both remotes worked and have so ever since. Odd.

I am so glad I am a software developer rather than a software/hardware tester, as these sorts of issues would drive me potty...

P.S. I just got an "Don't blame me, it's a hardware problem" t-shirt for Christmas, the perfect gift for an software engineer.

Just a quick update.

I believe the lockup of the front panel buttons & remote are the cause of the serial cable!!! I was restarting my comp and what not. And the empeg (Rio Car) does random things if the cable is connected and I reboot!

Now the dead battery in the remote is a different story :) Weird that the battery went dead at the same time as this other issue!!!

I believe the lockup of the front panel buttons & remote are the cause of the serial cable!!! I was restarting my comp and what not. And the empeg (Rio Car) does random things if the cable is connected and I reboot!

I've seen this bug many times in the car, with no serial cable connected.

Tom

I have also had lockups of the UI and such without a serial cable connected. Haven't seen one in 2.0b7 yet but several in 2.0b3.

Well I'm not sure then :) I had about 4 or 5 lockups! Since I've disconnected the serial cable and listened for about 3 hours I haven't had a lockup!

Oh well..... I'll keep trying to figure out the hanging problem.

Haven't seen one in 2.0b7 yet but several in 2.0b3.

It happened to me yesterday with 2.0b7 and it wasn't listed as fixed in the release notes so I'm pretty sure empeg still knows about it.

An interesting thing about the bug that happened in 2.0b7 this time which I never noticed 2.0b3 (probably just a fluke): When the unit stops responding in transient mode, sometimes the line of text gets stuck while moving in/out and just 1 row of pixels shows throughout the song. I let the player continue playing and looked at it later, and it was still locked up, but the line of text was now 4 pixels and had updated to the next song. I never noticed this change before, but who knows if it has anything to do with the new beta.

Tom

Well I've got it down to while it's not docked and I'm in AUX mode it will lock, so far it’s every time as soon as I go into AUX mode. I have an MK2a running Hijack 2.0b11 running off the 12v adapter and just RCA out to a computer or speakers. I can get the volume knob to respond by pressing it for 2secs then the Hijack menu comes up but the remote won't still won't respond. I can reboot the system (randomly that will lock too) and if I get the timing right I can get the source to change back to the player, then all is fine... Anyone have this problem too and or a fix?

Thanks for listening
JrFaust