ca68cae76f
The plugin manager was attempting to buffer the IOs. However, the ffmpeg plugin already handles this (it reads in 64K chunks, the same size as the buffer here, so this buffering was effectively useless), and the media extractor already runs the decoding in a separate thread thanks to the chunk cache. So, we do not need an extra level of buffering here. We should leave any extra buffering to the upper layers (BMediaTrack or Media Extractor), if it's needed, as they would have much more control on the creation of the data io object. Change-Id: I65b67919da107c8b910dd08f8cdb8e3745af92c7 Reviewed-on: https://review.haiku-os.org/c/1588 Reviewed-by: Stephan Aßmus <superstippi@gmx.de>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.