This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Feature requests · Rockbox frontpage
FS#8634 - Gapless Playback on H140 does not work with new builds
Attached to Project:
Rockbox
Opened by Avi (TrappyWappy) - Saturday, 23 February 2008, 19:14 GMT+2
Last edited by Steve Bavin (pondlife) - Thursday, 17 April 2008, 19:28 GMT+2
Opened by Avi (TrappyWappy) - Saturday, 23 February 2008, 19:14 GMT+2
Last edited by Steve Bavin (pondlife) - Thursday, 17 April 2008, 19:28 GMT+2
|
DetailsI have been having trouble with new builds (since January 2008, I cannot remember exactly what date, but the problem persists with all new builds) when it comes to gapless playback on my H140. I have Ogg Vorbis and LAME MP3s on my iRiver, but mostly Vorbis (about 8000 files or so). I use the database, and I have the load to RAM option set to "Yes." Whether or not I change this does not affect whether or not tracks play gaplessly or not.
Music plays gaplessly on the current build I am using (December 24) with or without a built database. Whether I update the build by overwriting or just deleting the old .rockbox folder, gapless playback stops working. I have tried formatting my iRiver, I have used both version 5 and 6 of the bootloader (currently using 6, problem originated with 5), but I have not been able to successfully use gapless playback with any new build of Rockbox. Problem persists with both MP3s and Oggs. |
This task depends upon
I've also used various builds from January. The problem does not occur until I load the database, however.
The last build I have that I know works is the December 24 build.
2) You can go back and test older builds. This is what I was asking you to do. If you can track down exactly which SVN revision broke gapless, it will make it much easier for someone to fix it.
I have no idea how to do that and the files I want to add as examples are too large to attach.
If you need help with it, feel free to ask in the forums.
If you could, please e-mail me two sample tracks (i.e. before and after the gap) to 11r6iom02@sneakemail.com.
I can't repro a problem (using the file browser), so to proceed with this I need 2 bits of info:
- which revision it stopped working in (do an SVN binary chop)
- sample files
Unless Gather Runtime Data is involved, perhaps, or something like that. Just an idea.
FS#8667. It would explain why it only happens when playing from the database. Playing from a playlist could also trigger it, I think.FS#8667as it was a duplicate ofFS#8601.Avi, does the disk spin up on track change and does turning on Directory cache make the problem go away?
Gapless playback will work via the file browser early on. I say this because I was listening to music today and noticed that, at some point, it was no longer playing back gapless, despite the fact that it had started out gapless. Unfortunately, I was listening at work, so I was coming and going and I don't know when it started to NOT work properly again. I have a sneaking suspicion it is somehow related to playlist size. I started out the day with one album in the playlist, but then added a few more albums at some point so that I wouldn't have to keep messing around with the H140 while I was working. Testing out gapless playback with only one album in the playlist works correctly (via the file browser, but not the database). EDIT: I just noticed that gapless isn't working any more (again, after rebooting and starting a new playlist which started out gapless) and the playlist size is only 17 songs. Also, just so you know what to look for, when gapless playback is NOT working, the HDD indicator light on the H140 lights up when there are 2 seconds remaining in the song. Additionally, the time remaining for the current song freezes at the 2 second mark, the song finishes, then there is a pause and the next song begins playing. Anyway, if the problem is not related to playlist size, maybe it's related to how long the player has been turned on, playing music?
FS#8601, then the size of the playlist is largely irrelevant as you say. The question is, are the filenames in memory or not? If you just play a directory, they will be. If the dircache is enabled, they should be too (if I understand the code correctly). Otherwise, once you start inserting or removing tracks, they will no longer be (possibly delayed a bit; the playlist code may cache things for a while and I don't know the code well enough to tell for sure). Playlist and database playback will also not keep the filenames in memory (unless the dircache is enabled).I'd say you probably don't need to do much more investigation at this point. Better wait for
FS#8601to be fixed, and then see if this bug is fixed too.No gaps, no disk spin-up before playing, works well.