Support and General Use > Audio Playback, Database and Playlists
Audio pauses and WPS lag?
Lear:
--- Quote from: epithetless on May 11, 2009, 11:05:03 AM ---The thing is, album art is already displayed on the WPS before the audio pauses and playing time lags occur...so I would assume at that point that any JPEG decompression and resizing routines would be done. Is that not the case?
--- End quote ---
No, it loads new album art for each track. (Though it ought to be possible to check if it has already been decoded and if so, just copy it.)
--- Quote ---On a different note, would a smaller-sized JPEG take less time/processing power to decompress?
--- End quote ---
Certainly. But even a bigger file shouldn't cause dropouts like that, I think. Seems like a few more yields() in the code would be in order.
epithetless:
--- Quote from: Lear on May 11, 2009, 04:06:08 PM ---
--- Quote from: epithetless on May 11, 2009, 11:05:03 AM ---The thing is, album art is already displayed on the WPS before the audio pauses and playing time lags occur...so I would assume at that point that any JPEG decompression and resizing routines would be done. Is that not the case?
--- End quote ---
No, it loads new album art for each track. (Though it ought to be possible to check if it has already been decoded and if so, just copy it.)
--- End quote ---
Yes, but when I'm seeing this problem occur, the album art has already loaded for the particular track I've just selected from the file browser (i.e. it's not the previous track's album art). Things go like this:
- I click on an MP3 from the file browser.
- The screen goes to the WPS, thinks for a brief moment, shows the album art and tag information, and the song starts playing.
- The current track time display stops at 0:01 (the remaining track time also stops) while the song continues to play for a couple of seconds.
- The audio cuts out, and the current and remaining track time displays disappear for a fraction of a second.
- The current track time display reappears at 0:03 or 0:04 (the correct track time), and the audio resumes. The remaining track time display also reappears with the correct time.
It doesn't happen with all (or even most) of my music, but it does consistently happen with certain tracks (meaning I can reproduce it with those tracks every time). For every other track, however, I've noticed that the current and remaining track time displays do blink off for a brief moment within the first few seconds of the song. The problem detailed above, when it occurs with offending songs, appears to be a protraction of whatever causes this blink. Perhaps that might help someone pinpoint a cause...
I did, by the way, manage to completely eliminate the issue (including the relatively minor track time blink) with BlacknBlue_Glass by removing all the album art coding from the theme, so it does seem to somehow be related to the calling/displaying of album art.
yapper:
Can you post one of your problem tracks somewhere? I haven't seen any of the issues you described.
Lear:
--- Quote from: epithetless on May 11, 2009, 09:16:59 PM ---Yes, but when I'm seeing this problem occur, the album art has already loaded for the particular track I've just selected from the file browser (i.e. it's not the previous track's album art).
--- End quote ---
Rockbox continues to buffer tracks after starting playback, so it will load album art for the buffered tracks (if the WPS uses album art).
--- Quote ---It doesn't happen with all (or even most) of my music, but it does consistently happen with certain tracks (meaning I can reproduce it with those tracks every time). For every other track, however, I've noticed that the current and remaining track time displays do blink off for a brief moment within the first few seconds of the song. The problem detailed above, when it occurs with offending songs, appears to be a protraction of whatever causes this blink. Perhaps that might help someone pinpoint a cause...
--- End quote ---
Maybe the tracks where it happens have larger album art files?
pondlife:
Does this mean that the same folder.jpg is actually bufffered/stored for eavh track in a folder?
Ideally, this should be handled internally by buffering.c (i.e. don't reload a file section that's already in memory).
pondlife
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version