Jump to content

Rockbox

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Adavidb (talk | contribs) at 18:02, 1 November 2016 (Disambiguate Doom (video game) to Doom (series) using popups; formatting: heading-style, whitespace (using Advisor.js)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

For the Run–D.M.C. song, see Rock Box.
Rockbox
Rockbox Logo
Main menu using default theme
DeveloperThe Rockbox Project
Written inC, assembly language
Source modelOpen source
Initial releaseJune 2, 2002; 22 years ago (2002-06-02)
Latest release3.13 / March 5, 2013; 11 years ago (2013-03-05)
Latest previewDaily
Repository
Marketing targetFirmware replacement for digital audio players
PlatformsDigital audio players, various
Default
user interface		GUI
LicenseGNU GPLv2 or later
Official websitewww.rockbox.org

Rockbox is a free and open-source software replacement for the OEM firmware in various forms of digital audio players (DAPs) with an original kernel.[1][2] It offers an alternative to the player's operating system, in many cases without removing the original firmware, which provides a plug-in architecture for adding various enhancements and functions. Enhancements include personal digital assistant (PDA) functions, applications, utilities, and games. Rockbox can also retrofit video playback functions on players first released in mid-2000. Rockbox includes a voice-driven user-interface suitable for operation by visually impaired users.[3][4]

Rockbox runs on a wide variety of devices with very different hardware abilities: from early Archos players with 1-bit character cell-based displays, to modern players with high resolution color displays, digital optical audio hardware and advanced recording abilities.

History

The Rockbox project began in late 2001 and was first implemented on the early Archos series of hard-disk based MP3 players/recorders (including the flash-only model Ondio), because of owner frustration with severe limitations in the manufacturer-supplied user interface and device operations. These devices have relatively weak main central processing units (CPU), and instead offload music playback to dedicated hardware MP3 decoding chips (MAS).[5] Rockbox was unable to significantly alter playback abilities. Instead, it offered a greatly improved user interface and added plug-in functions absent in the factory firmware. Rockbox can be permanently flashed into flash memory on the Archos devices, making it a firmware replacement.

Versions of Rockbox have since been produced for more sophisticated devices. These perform audio decoding in software,[6] allowing Rockbox to potentially support many more music formats than the original firmware, and adding the extensibility and increased functions already present in the Archos ports. Rockbox is run from the hard drive or flash memory after being started with a custom boot loader, so to upgrade Rockbox, users need only copy the files onto the player's drive and restart the device. Reflashing is only needed when changing the boot loader, and on some platforms is not needed at all.

The first of these ports, beginning in late 2004, was for the ColdFire-powered devices manufactured by iriver, focusing on the H1xx series of hard drive players (H110/H120/H140). About one year later, a port for the H3xx series became functional, offering similar functions.[5] In late 2005, work began on a port of Rockbox to Apple's iPod portable players based on CPUs from ARM Ltd. incorporated into systems on a chip sold by PortalPlayer. Throughout 2006, Rockbox ports were made available for a variety of iPod models. Beginning in 2007, ports became available for a large number of additional ARM based targets, including players from Sandisk, Toshiba, Olympus and Philips in addition to newer Apple and iRiver players based on a variety of ARM7, ARM9 and ARM11 series processors. During this time, extensive work was conducted optimizing open source audio decoders for each of the ARM series processors. In 2008, porting began to processors based on the MIPS architecture. In 2010, work began on supporting "hosted" architectures where Rockbox runs as an application inside of more complex operating system.

To date, all Rockbox ports have been accomplished by reverse engineering with little or no manufacturer assistance. As free software, many Rockbox developers and supporters hope to eventually see official manufacturer support for new ports, or at least unofficial assistance in porting Rockbox to new devices. Only a few companies have expressed interest in Rockbox, and none have officially contributed code to the project or included it with their hardware. The Sansa e200v1 port is the first to be started at the request of the hardware manufacturer, who gave the Rockbox team samples of their devices.

Rockbox is continuously developed, with new Git builds being released after every source change, and stable releases every 4 months for targets deemed sufficiently mature.[7] Additionally builds are often available to developers of unsupported targets, which, while somewhat functional, are typically not ready for general users due to incomplete features or poor stability.[8]

Future

Rockbox is targeted primarily at digital audio players, rather than the much more powerful general-purpose devices (such as smartphones and tablet computers), which have been increasing in popularity since 2010. Some authorities expect the former class of devices to become obsolete in the next few years.[9]

Daniel Stenberg, a founder of the Rockbox project, envisions the project evolving away from a standalone Rockbox operating system to Rockbox as a media player application that runs under mobile operating systems, such as Android, iOS, Sailfish OS or Tizen:

In a chat after my Rockbox talk at Fosdem 2010, two other core Rockbox developers (Zagor and gevaerts) seemed to agree to the general view that a Rockbox future involves it running as an application. Out of the existing systems mentioned above, I'd prefer to start this work focused on Android. It has the widest company backing combined with open source, and it's also the most used open phone OS. I don't think there's anything that will prevent us from working on all those platforms, as the back-bone should be able to remain the same and portable code we already have and use. Heck, it could then also become more of a regular app for common desktops, too.[10]

A project to port Rockbox to run as an application under a full-fledged operating system was accepted for Google's 2010 Summer of Code[11] and completed.[12] Currently, Rockbox runs on Android based players, but integration into Android and conversion to work with touch based devices is ongoing.[13] Subsequently, an anonymous Chinese developer unofficially ported Rockbox to Palm's WebOS.[14]

Customization

A custom Rockbox theme: Brushed Metal

Subject to the limitations of each particular platform, the appearance of Rockbox can be customised in various ways. Fonts and foreground and background colours can be added and selected, while a simple markup language can be used to create themes for the menu and playback screens.[15] These themes can include backgrounds and other images (such as icons), plus various formats for file names, ID3 tags, album art, file progress, and time and system information.

Rockbox has essentially been a file-tree based player, to which folders could be dragged and dropped and then navigated by folder structure. However, more recent versions have included a complementary database feature which allows the player to compile information from the files' ID3 tags.[16] The user can then navigate the files regardless of file structure.

Features

Target status

Rockbox has many features additional to those supported by the original operating firmware, but in many cases there are limitations. On platforms classified as "stable" and supported, the device can be used as a digital music player, but even on some such platforms Rockbox does not support charging or USB; the player must be dual-booted into the original firmware to be charged or to transfer files. Some platforms are classified as "unstable", but supported; those deemed "unusable" are not supported, and their use is not recommended. Some porting projects are in a pre-development hunting and gathering stage, with no code written.[17]

Codecs

Rockbox on software decoding platforms (non-Archos) supports playback of twelve lossy codecs (depending on how one counts), five lossless, two uncompressed and twelve miscellaneous formats.[18] This makes a conservative total of 30 supported audio formats, although a few of them do not operate in realtime on all platforms. Extensive work has gone into optimizing each codec, with FLAC, Ogg Vorbis, WMA, APE, TTA, MPC, Wavpack, ATRAC3, Cook and WMA Pro among the fastest known integer implementations for those formats.[19]

Lossy formats

Lossless formats

Uncompressed formats

Together they include over a dozen different PCM and ADPCM formats.

Miscellaneous formats

In addition, there are playback of game audio types ADX, SID, NSF, SAP, SPC, AY, GBS, HES, KSS, SGC, VGM, and VGZ. The MOD tracker format, and the Yamaha SMAF are also now supported.[20]

Some profiles in Monkey's Audio are not real time on all targets due to very high CPU needs. Also, Rockbox will not play files with a digital rights management (DRM) scheme.

Rockbox features

Beside the ability of playing and recording audio files, Rockbox offers many playback enhancements that other firmware packages may not have implemented yet. Listed below are a handful of these features.

Plug-ins

Rockbox developers can create plug-ins, which provide the user with other enhancements that may not be available on various firmware modules.

Available plug-ins include:

Architecture

Rockbox uses a simple kernel,[35] with a flat memory model and single process, letting it run on platforms without a memory management unit. Thin threads run cooperatively, returning control to a scheduler that prioritizes the audio thread; the only form of preemption is through interrupts. The operating system and plug-ins are written in C, with assembly used for code that is device- and platform-specific, and performance sensitive. The simple and lightweight architecture allows Rockbox to run on a variety of targets, with memory ranging from 1 to 64 MB, and CPU speeds ranging 12 to 532 MHz. Rockbox also provides support for multicore and asymmetric multiprocessor systems based on ARM, ColdFire, MIPS and SH. Several codecs can be parallelized across 2 CPU cores for increased power efficiency, and the HWCODEC interface allows for dedicated audio decoder DSPs.

Rockbox Utility

An iPod Nano showing a grayscale "Do Not Disconnect" screen from the iPod Mini series with a new screen on the iPod Classic, although it is bundled with the Rockbox package.

The Rockbox Utility is a free computer application, available for Linux, Mac OS X, and Microsoft Windows, built using Digia Qt platform, that is used to install and manage Rockbox on DAPs. Rockbox Utility provides automatic installation of Rockbox, as well as themes and voice files, directly onto a DAP with minimal user interaction. Rockbox Utility is updated frequently as support for new devices is added.

Supported devices

iPod Mini with Rockbox firmware
iPod classic 6th generation with Rockbox firmware

The following should be considered to be a list of devices that at least substantially work (listed as "Supported" or "Usable" on the Rockbox wiki Device Chart). Details are given on the Rockbox Target Status Web page.[17]

Apple

  • iPod 1st generation
  • iPod 2nd generation
  • iPod 3rd generation
  • iPod 4th generation
  • iPod 5th and 5.5 generation, video
  • iPod 6th generation (needs another bootloader, emCORE)
  • iPod Mini 1st generation
  • iPod Mini 2nd generation
  • iPod Nano 1st generation
  • iPod Nano 2nd generation

Archos

Cowon

  • X5 and X5L
  • X5V
  • M5, M5L
  • M3, M3L
  • D2

iriver

MPIO

Olympus

Packard Bell

  • Vibe 500

Philips

Rockchip

  • Rockchip RK27XX (generic). The Rockbox Web site as of January 2014 classified this as an unusable port: "Work has begun on porting Rockbox to these players, but much remains before they are usable".

Samsung

SanDisk

Main article: SanDisk Sansa

High capacity microSD, microSDHC, and microSDXC memory cards are supported on devices with SD (although SDXC cards need to be FAT32 formatted).

Toshiba

See also

References

  1. ^ http://www.rockbox.org/wiki/RockboxKernel
  2. ^ http://www.linuxjournal.com/article/10835
  3. ^ "BlindFAQ < Main < Wiki". www.rockbox.org. Retrieved 2016-05-14.
  4. ^ Miesenberger, Klaus; Klaus, Joachim; Zagler, Wolfgang; Karshmer, Arthur (2008-07-04). Computers Helping People with Special Needs: 11th International Conference, ICCHP 2008, Linz, Austria, July 9-11, 2008, Proceedings. Springer Science & Business Media. ISBN 9783540705390.
  5. ^ a b "rockbox history".
  6. ^ "rockbox software decode".
  7. ^ "buildsys".
  8. ^ "unstable".
  9. ^ Joe Brockmeier (June 16, 2010). "Rockbox 3.6 and Beyond". LWN.net.
  10. ^ Daniel Stenberg (February 15, 2010). "The Rockbox future is an app". Daniel Stenberg's blog.
  11. ^ "RockboxAsAnApplication2010 < Main < Wiki". Rockbox.org. Retrieved March 12, 2011.
  12. ^ Rockbox Contributors. "mail archive". Rockbox. Retrieved March 12, 2011. {{cite web}}: |author= has generic name (help)
  13. ^ "TouchscreenInterface < Main < Wiki". Rockbox.org. Retrieved March 12, 2011.
  14. ^ "万能播放器ROCKBOX for palm pre，新软支持下，绝对不会失望~~ – Palm Pre/+, Pixi/+, webOS – Pre,Pixi,webOS,Treo – Powered by Discuz!". Treo8.com. Retrieved March 12, 2011.
  15. ^ "Customising the User Interface". Rockbox Manual. Retrieved May 22, 2011.
  16. ^ "Database". Rockbox Manual. Retrieved May 22, 2011.
  17. ^ a b Rockbox Target Status
  18. ^ "Rockbox Supported audio formats". Rockbox Manual.
  19. ^ "Codec performance comparison – Hydrogenaudio Forums". Hydrogenaudio. Retrieved March 12, 2011.
  20. ^ "Other Codecs". Rockbox Manual. Retrieved May 22, 2011.
  21. ^ "Codec Featureset". Rockbox Manual. Retrieved May 22, 2011.
  22. ^ "Crossfade". Rockbox Manual. Retrieved May 22, 2011.
  23. ^ a b c Software decoding targets only
  24. ^ "Pitch". Rockbox Manual. Retrieved May 22, 2011.
  25. ^ "Rockbox themes". Retrieved 19 April 2012.
  26. ^ MP3.
  27. ^ "Recording". Rockbox Manual. Retrieved May 22, 2011.
  28. ^ "Some limitations. Details at Rockbox Wiki". Rockbox.org. Retrieved March 12, 2011.
  29. ^ 129 shade greyscale is achieved on 1 bit and 2 bit (4 shade) greyscale targets due to exploitation of the slow passive LCD refresh rate.
  30. ^ Rockboy supports original Game Boy and Game Boy Color ROMs.
  31. ^ ZXBox emulates ZX Spectrum 48. The original site of Spectemu
  32. ^ http://forums.rockbox.org/index.php/topic,48586.0.html
  33. ^ The mpegplayer plug-in supports MPEG-1 and MPEG-2 video streams with MPEG audio (layer II/III) multiplexed into .mpg files with no hard limits on frame rate or bit rate. Files must be encoded at native screen resolution. Seeking is now implemented. [1]
  34. ^ FS#8806 - MikMod MOD, S3M, IT, XM player
  35. ^ "About the Rockbox kernel". Rockbox.org. Retrieved March 12, 2011.
Wikimedia Commons has media related to Rockbox.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Rockbox&oldid=747315949"