Archived. A new, from scratch plugin is being developed in a sub folder in my app https://github.com/yringler/inside-app, which, if all goes well, may end up being merged into audio_service, or split off to be its own repo.
This plugin works for what I need, and I'm using it in a production app with 600+ users, but it is very dated. All of the complicated code, most of the work, is working around limitations in the just_audio plugin, audio_service, and hive - limitations which either do not exist anymore or quickly won't be an issue. I do intend to update to the latest audio_service/just_audio, but right now I'm busy with other parts of the app, and the audio play back works fine.
As is enumerated below and in the project issues, this plugin doesn't support some basic things, and is not sufficiant for most use cases. I can only recommend it's use if at least one of the following is true:
- You are aware of and OK with the limitations, and are comfortable fixing any bugs which may bug you
- You are willing to make PRs for any features which it doesn't have yet.
- You want to fork this entirely and make you're own, better plugin
It is because of these limitations that I haven't published this to pub.dev yet.
In beta, and in production use (in an app of mine).
Intended to be a robust, well written, easy to use implementation of audio_service using just_audio.
Note that initial goal is only to support a limited set of requirements (i.e. mine), not to be properly configurable.
For example, it doesn't support
- playlists
- customizing the buttons on the android notification.
- playing audio from any source other than URL
- setting audio metadata - album, artist, etc
That being said, I hope that it is a good starting point for others to base their implementations off, and PRs (or feature requests, or forks) are most welcome.
This is not yet available on pub.dev, but can be used from git
just_audio_service:
git:
url: https://github.com/yringler/just_audio_service.gitSee documention for audio_service. This plugin is currently on version 0.10.0, but will be kept up to date with the latest audio_service plugin for the foreseeable future.
This package has two things, a regular implementation of BackgroundAudioTask, and a PositionedAudioTask which, together with a PositionManager on the UI side, helps keep track of current position and optionaly can save a position (with hivedb).
Note that
- If you don't want the persistance, you can just use AudioTask()
- (TODO: add a MemoryPositionManager, which keeps track of positions in memory, per app run)
- You can still use the
PositionManager, which provides a stream which doesn't lag with constant location updates, with the regularAudioTask
You can either use AudioTask in your top level audio_service _audioPlayerTaskEntrypoint or PositionedAudioTask
Here's a sample (from the example project) of everything which you have to do to start an audio task which will persist position in media
// NOTE: Your entrypoint MUST be a top-level function.
void _audioPlayerTaskEntrypoint() {
AudioServiceBackground.run(() => PositionedAudioTask.standard());
}PositionedAudioTask has another constructor which lets you customize the base audio task and the persistance mechanism.
To use PositionManager: you'd want to make sure to only have one instance per app, either using provider, some other DI mechanism, or saving it to a static property.
To take advantage of the position streams, seek via the seek method, not directly with AudioService method.
Note that if you opt to save position, (For example, by using the PositionedAudioTask.standard() constructor, you can call seek on a media which isn't active, and playback for that media will start from the seeked-to position.
There is now also a DownloadAudioTask, which is used with DownloadManager on the client to download audio files for
offline playback. It is somewhat progressive - if audio is streaming and then downloaded, when the download is finished the
playback will switch to the offline file.
My initial audio BackgroundAudioTask quickly descended into a labyrinth of spaghetti code, inhabited by hosts of minotaur quick to consume any who hoped to maintain it.
Therefore, I set out to try again. This time, I have perhaps gone to the other extreme, and am relying heavily on the state pattern. Each just_audio state has it's own class, which handles media operations (play, pause, etc) as best as it can, and hands off to another state class as soon as possible.