mirror of
https://github.com/Rockbox/rockbox.git
synced 2026-10-09 23:53:28 -04:00
2890d4a40d
The comment packet is not used by the codec, but skipping it grew the stream's packet buffer to the packet's full size. Heap use rose with the size of the tags: a file with 300 KB of embedded album art needed 617 KB of heap, and one with 940 KB of art could not be opened even with a 992 KB codec buffer. Skip the packet without storing it: forget the part already buffered and let ogg_stream_pagein() drop the rest, as it does for a packet whose start was lost. Seeking to the start of a file ran the headers through the stream again, which buffered the whole comment packet by the normal path. Start the seek search at the first audio page instead, as libvorbis does, and handle a target inside that page. With both, heap use no longer depends on the tags. Large tags cost at most about 90 KB over an untagged file, from the two Ogg buffers growing to hold one full page each. Checked with perfsim on the Sansa Clip+ model, not on a device, with the heap limited to what a 512 KB codec buffer leaves: files with up to 1.5 MB of art or 240 KB of text decode to the same PCM hashes as the untagged audio, and 15 seeks per file, including to 0, 30 and 150 ms, give the same positions and PCM as the unmodified codec on ten files. Chained streams were not tested. Change-Id: Id27ebf98b436d813cfa3179951eee5bd7b2c0cd2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| android | ||
| apps | ||
| backdrops | ||
| bootloader | ||
| docs | ||
| firmware | ||
| fonts | ||
| icons | ||
| lib | ||
| manual | ||
| packaging | ||
| tools | ||
| uisimulator | ||
| utils | ||
| wps | ||
| .gitattributes | ||
| .gitignore | ||
| .gitreview | ||
__________ __ ___.
Open \______ \ ____ ____ | | _\_ |__ _______ ___
Source | _// _ \_/ ___\| |/ /| __ \ / _ \ \/ /
Jukebox | | ( <_> ) \___| < | \_\ ( <_> > < <
Firmware |____|_ /\____/ \___ >__|_ \|___ /\____/__/\_ \
\/ \/ \/ \/ \/
Build Your Own Rockbox
1. Clone 'rockbox' from git (or extract a downloaded archive).
$ git clone git://git.rockbox.org/rockbox
or
$ tar xJf rockbox.tar.xz
2. Create a build directory, preferably in the same directory as the firmware/
and apps/ directories. This is where all generated files will be written.
$ cd rockbox
$ mkdir build
$ cd build
3. Make sure you have mips/m68k/arm-elf-gcc and siblings in the PATH. Make sure
that you have 'perl' in your PATH too. Your gcc cross compiler needs to be
a particular version depending on what player you are compiling for. These
can be generated using the rockboxdev.sh script in the /tools/ folder of the
source.
$ which arm-elf-eabi-gcc
$ which perl
4. In your build directory, run the 'tools/configure' script and enter what
target you want to build for and if you want a debug version or not (and a
few more questions). It'll prompt you. The debug version is for making a
gdb version out of it. It is only useful if you run gdb towards your target
Archos.
$ ../tools/configure
5. *ploink*. Now you have got a Makefile generated for you.
6. Run 'make' and soon the necessary pieces from the firmware and the apps
directories have been compiled, linked and scrambled for you.
$ make
$ make zip
7. unzip the rockbox.zip on your music player, reboot it and
*smile*.
If you want to build for more than one target, just create several build
directories and create a setup for each target:
$ mkdir build-fuzeplus
$ cd build-fuzeplus
$ ../tools/configure
$ mkdir build-xduoox3
$ cd build-xduoox3
$ ../tools/configure
Questions anyone? Ask on the mailing list or on IRC. We'll be happy to help you!