Support and General Use > Audio Playback, Database and Playlists

Ridiculous Lagging on H10

(1/1)

maretard:
Hey, I've been using Rockbox for the longest time on my iRiver H10 20G, and it's worked absolutely wonderfully most of the time (EQ creates intense lag because of CPU issues, but whatever, don't use it anyway). But yesterday night, I loaded a Current Build on my iRiver, since I haven't updated Rockbox in like three months (ugh) expecting some new features or improved performance or at least that peace of mind you get when you have up-to-date software. Alas, it was not so. :(

I started up my iRiver, everything loaded as normal. I noticed new FM Radio support, and tried it - Static, even on the most obvious (98.5,95.5,94.1) frequencies. Clicking sounds every time I moved the cursor or changed volume; possibly electrical interference from the iRiver's parts? Either way, this is trivial, since it's new and there are bound to be some kinks. My main issue is with audio playback.

I started up "Choose the One Who Loves You Most" by Copeland, and immediately the hard disk started spinning (I could feel the repeated vibrations) like usual. Or so I thought, until the music started freezing every 2 seconds for about one whole second, and the hard disk's vibrations wouldn't stop. Ever.

So I just let it run, thinking the hard disk would spin down after awhile. No such luck - 20 minutes later, I was into my 2nd song (should've been like 5/6 songs) and the lagging was still present, as well as the vibrations.

I already "minimized" Rockbox's CPU usage, in case that was doing anything. No EQ (as normal), no crossfades, everything default. The lag is still horrendous.

I took to shaking the player in frustration in an attempt to dislodge the hard drive. Didn't work. :D

What on earth is going on?

I mean, I know Rockbox isn't the most CPU-friendly firmware ever, but I'm fairly certain it shouldn't lag this much on default settings, right? o_O?

Chronon:
You say that it didn't do this previously.  Why don't you try to isolate when this behavior started to occur?  Then file a bug report on the tracker.  This is not the proper place for a bug report.  

Navigation

[0] Message Index