A fast, extensible gapless audio player and streamer for iOS and macOS with low CPU usage.
StreamingKit is an open-source audio playback and streaming library for iOS and macOS, designed to handle gapless playback across different audio formats with minimal CPU usage. It provides a flexible architecture that separates data sources from player logic, supporting features like HTTP streaming, encryption, and real-time audio processing. The library uses CoreAudio for efficient decoding and offers a simple API for developers to integrate advanced audio capabilities into their apps.
iOS and macOS developers building audio-intensive applications such as music players, podcast apps, or streaming services that require reliable, high-performance playback with custom features.
Developers choose StreamingKit for its unique combination of gapless playback support across mixed formats, extensible data source system, and low resource footprint, all wrapped in a clean, object-oriented API that simplifies complex audio handling.
A fast and extensible gapless AudioPlayer/AudioStreamer for OSX and iOS (iPhone, iPad)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uniquely supports seamless transitions between different audio formats like MP3 and AAC, a highlighted feature in the README that sets it apart from other libraries.
Optimized for minimal CPU and battery usage, with the README citing 0%–1% CPU when streaming, making it ideal for energy-efficient audio apps.
Decouples data sources from player logic, allowing easy custom implementations for HTTP streaming, encryption, and auto-recovery, as evidenced by the provided Local and HTTP DataSources.
Uses AudioUnit API for intercepting raw PCM data, enabling features like level metering and custom EQ filters, with examples showing frame filter integration.
Last significant update was in 2019, which may lead to compatibility issues with newer iOS/macOS versions, lack of modern API support, and limited community activity.
Written in Objective-C with examples in that language, making it less appealing for Swift-centric developers or projects using SwiftUI, requiring bridging headers and interoperability overhead.
Documentation is hosted on a wiki and might not be comprehensive or up-to-date, as the README points to it for more details, potentially increasing the learning curve.