k, ive tested this multiple times on various days.
at the beginning of a few songs (these songs tend to start slow/soft) the player seems to do this until the sound ... changes? i cant describe when in the song it is. in one song theres some soft spoken word and the player doesnt respond until the music actually starts. which is coo because the previous song (info transient) will have had its title drop out the bottom, then it switches to the next song. the title doesnt pop up until the music starts. idno, i thought it was a coo part of the bug.

since ive managed to have it do this to me repeatedly i decided it is probably bug-post-worthy. i can point anyone who would like to test this to some of the exact files i have trouble with, if it would help.

The tracks in question: Have you analyzed them and made sure that they're OK? In other words, they don't have bad frames and they don't have bad VBR headers?

no vbr files exist on my player. as far as the other part, what should i use to confirm quality?

as far as the other part, what should i use to confirm quality?

FAQ entry is right here.

the only one that was small enough to be checked out by mp3trim freeware checked out a-ok. what now?

Give us more exact details as to what's going wrong. Please describe the problem as clearly as possible. I'm not clear on exactly what the problem is.

k, for instance the song Void by Skold starts off rather quiet. in the first 10 seconds there is not much sound at all. the at about 10.5 seconds the bass line starts. until that bass line hits there the player doesnt respond to any key presses. when the player does respond and if ive pressed many keys it will process them all quickly with a bunch of coo beep noises.

Are you sure it's ALL KEY PRESSES, or is it just that fast-forward doesn't work?

If the latter, it's a known bug in Beta 13.

i am very positive its all key presses. other than the hijack long knob press. for fun (because it makes coo noises) i like to hit down up down up down up down up down up as many times as possible, as when it catches up it does two disctinct beeps in succession over and over.
its not just this one song that does it, but in all the songs that it does it on it always catches up at the same moment in that song. different times per song.

That's odd. Dunno what that is.

Activate the drive activity indicator and see if it only happens when it's caching.

it only seems to do it in transient info. and not only while its caching.

Got me stumped, then. Anyone else?

What visual are you running? Have you tried a different one? You say only in transient mode. Just to be clear, how about none mode (or whatever it's called)?

visual is tripping prisoner. on the info in ... whatever its called with track title at top and that line that goes all the way across in the middle and the time in bottom right and the artist and album it doesnt do it

Does it do the same thing if you use a different visual?

Does it do the same thing if you change the info mode to ``Off''?

different visual, im not sure. if the visual is not displayed then it doesnt appear to do it. as stated.

What I'm asking is what happens when you display only the visual and no track info at all?

And also try a different visual to see if you get the same symptoms.

tripping prisoner and sugar cube appear to be the only ones it does it in. and the visual has to be shown.

i am not happy to report that since breaking my vfd i havent had this problem. the other hand is, i havent much used the empeg since.