Using the RIO remote i have noticed that either it works or doesnt work. When it doesnt work, I get frustrated and push the buttons zillions of times, then the HU will catch up to all of my playing around and cycle right past what I was hoping to accomplish. Or it won'r respond at all and i put the remote back in its cave.

Other times it is very respondent to what I want to do.

I have a convertable, and this happens with the top up or down, the point being that maybe the more direct sunlight on the HU, the less reponsive it will be to the IR sigal from the remote.

...this also happens with a brand new battery!

any suggestions???

Thanks,

Ed

Are you running the 2.0 final software?

I haven't heard anyone complain about this one in quite a while.

Just loaded it!

for the most part it works fine..but when it doesnt..it REALLY doesnt!


would u happen to know where th receiver for the signal is on the face plate? maybe during a hardware upgrade I had partially covered it up.

The fact that your commands eventually do get to the software would indicate that it's not being blocked physically.

I don't remember if there were causes for this beyond a software bug. Is it possible that he has a hardware issue that is causing this, folks?

Time to fire up the Hijack Button Codes Display

...and what is that??!!?!?!?!?

I get frustrated and push the buttons zillions of times, then the HU will catch up to all of my playing around and cycle right past what I was hoping to accomplish.

I can think of a few things that might cause this:

- Running an old version of the player software where this is a known bug (but you say it's 2.0 final so that's not it).

- Running third-party programs which are grabbing CPU time. Are you running any? If so, can you disable them?

- Hard disk trouble, and the pause is the hard disk trying to spin up and locate a file but it's having to do re-tries. Have you been noticing symptoms of hard disk trouble lately?

It's on the Hijack menu.

If Hijack works when the remote is otherwise non-responsive, then we know the remote is actually okay. If not, maybe the long knob press will still work to bring up the Hijack menu, and the "Button Codes Display" will then show us whether the remote is functioning.

Cheers

This happens to me, however it only happens when I'm playing WMA's. Fortunately I have very few WMA's in my player. I'm not sure what this means exactly, other than I avoid WMA's

This happens to me, however it only happens when I'm playing WMA's

Can you reproduce this consistently? Can you describe the type of WMA files such as their bit rate and how they were created? Can anyone else reproduce this?

I regularly listen to WMA files on my player (I convert each week's CarTalk into WMA format and put it onto the player for listening later), and I have never noticed this. Anyone else?

It happens to me every time. I'm running the latest Hijack kernal if that matters, however I am still running 2.0b13 (I think) so that could be the issue?. The WMA's are encoded VBR w/ the bitrate ranging from 135 to 215Kbps

Its frustrating because I'll go to turn up the volume for example, and it doesn't do anything so I turn it up more and still nothing, then about 5 seconds later my ears are bleeding

Hi all

I suffer this problem too...
Last month I tried to upload some WMA stuff, coded with Nero at vbr medium-high quality.
The empeg seems to use all processor time to decode it, and all buttons take a lot of time to work. If I turn up volume, 5 seconds after, it goes to the top suddenly. I have to pull it out and reboot it, and load any other song to relax the cpu...

Cheers:

Miguel.

Mpelaz, is this with 2.0 final, or is it with Beta 13?