Rockbox Development > Feature Ideas

Buffer level in WPS

<< < (2/3) > >>

Yotto:
In the debug buffer, there's a "track count" that I have always thought was the number of files buffered. It counts down with each track and then counts up while buffering. It is possible that NiHaoMike is discussing a different thing to read, but this is what I was talking about. Sorry for the confusion.

I don't see any time indicator on that screen. I can't see a reason to know that number, but that doesn't of course mean that there is no such reason.

And when talking about next track names vs id3 tags, I'm specifically talking about the playlist viewport. You can, while displaying that viewport, display the id3 tags if they're loaded and the file name if they're not loaded. I've been using that functionality to determine if the next track is loaded (presuming it wouldn't load unless the current track is fully loaded, and therefore safe to delete).

I'm thinking of an idea on how to use the playlist viewport to more concisely show that the current track is fully loaded. It won't be as pretty, code-wise, as a simple tag but I think that it will work. Especially if you can display multiple playlist viewports at the same time.

JdGordon:
like I said above. You cannot use the availability of the next tracks ID3 for anything other than showing that info. It is an incorrect assumption that the current track is finished buffering if that is available.

The numbers in the debug screen are not very useful to anyone not interested in debugging playback, I don't even know what some of those values mean.

Yotto:
Hrm. I was hoping you meant "for the %Fx tags."

The http://www.rockbox.org/wiki/CustomWPS page is a bit misleading on this. In the "Next Track Info" section, it reads:

--- Quote ---Take note that the next song information WILL NOT be available at all times, but will most likely be available by the end of a song. We suggest you use the conditional display tags when displaying information about the next song, just in case.
--- End quote ---
This at least implies that it's not loaded until the song is buffered.

And in the playlist viewer it is even more explicit:

--- Quote ---#  "show if id3" - Skin code to display if the track has been buffered (supported skins explained below)
# "show otherwise" - Skin code to display if the track hasnt been buffered, really only the filename is know at this point.
--- End quote ---

pixelma:
A small clarification about the note on CustomWPS about the next track info as I know it:


--- Quote from: Yotto on March 21, 2010, 09:51:35 AM ---The http://www.rockbox.org/wiki/CustomWPS page is a bit misleading on this. In the "Next Track Info" section, it reads:

--- Quote ---Take note that the next song information WILL NOT be available at all times, but will most likely be available by the end of a song. We suggest you use the conditional display tags when displaying information about the next song, just in case.
--- End quote ---
This at least implies that it's not loaded until the song is buffered.

--- End quote ---


--- Quote from: JdGordon on March 21, 2010, 12:30:22 AM ---the next tracks id3 should *always* be visible (it is loaded seperatly for the track after the last one in the buffer).

--- End quote ---

Both is true in two cases: The first applies to all targets... sometimes there simply is no next track.

The second is a bit more complicated... there are differences in playback and buffering between software codec targets which do all the decoding on the CPU and the hardware codec targets which have a decoder chip for this (only the Archoses belong to the latter). On software codec targets, the metadata of the next track is always there provided there is one. On hardware codec targets, the next track's metadata is only available if the next track is partially buffered which means only within 1-1.5 minutes before the track change with common MP3 files.

My guess is that this comment is there for a long time already, maybe it could be clarified a bit on CustomWPS, not sure how though. About the new playlist tags - I don't know how they work because I haven't tried yet. But I would assume it uses the next track info the same as the pure next track info does, it would be weird if it implements its own mechanism.

soap:
You also don't get next track information at the end of a playlist.  This may seem obvious, but if you have folder advance turned on the fact you're technically at the end of a playlist is pretty well abstracted under most circumstances.

Navigation

[0] Message Index

[#] Next page

[*] Previous page