FS#6152 - Transcoder Interface + benchmarks

Attached to Project: Rockbox
Opened by Paul Louden (darkkone) - Monday, 09 October 2006, 18:11 GMT
Task Type Feature Requests
Category Recording
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


This really falls in Playback as well, but I felt Recording was a little more close to home with it.

The idea is of course simple: Choose an input codec (any of our playback codec) and an output codec (any of our encoder codecs) and go. In theory this would also allow us to record to non-realtime codecs, since we could have a Vorbis encoder that a user could run after the fact on his files, say at his hotel while plugged in or whatnot, before returning for more encoding the next day (just in case a computer is not viable).

Anyway, the extension of this is to then allow its use for benchmarking (Encode from WAV, decode to WAV). In benchmarking mode it would have to not yield, keep the CPU boosted, load the entire file to RAM in advance, and time how long it takes to decode the file, preferably logging it somewhere our outputting it, with some format similar to "Filename, Time of track, Decode time, Speed %".
This task depends upon

Closed by  Bj√∂rn Stenberg (zagor)

Reason for closing:  Fixed
Additional comments about closing:  Closing all feature requests.
Comment by Davide (Davide-NYC) - Monday, 09 October 2006, 18:24 GMT
Just to repeat and accentuate: This plugin should also decode from (currently) non-realtime encoders.
I'm thinking about AAC (M4A) and WMA right now.
See this thread:
Comment by Davide (Davide-NYC) - Tuesday, 24 October 2006, 18:41 GMT
This could also just be two separate plugins. A Decoder and an Encoder, both with a benchmark mode.
The forum is flooded with "my audio is skipping/halting/stopping" posts. All of these people could be recruited to generate decoder benchmark data across all target platforms if the decoder plugin existed. Thereby turning complaints/questions into useful data! :-)
The current method for generating this data is too time consuming:
Comment by Davide (Davide-NYC) - Saturday, 14 July 2007, 02:30 GMT
we now have test_codec. Although it currently crashes when swapping codecs. (at least on an H120)