You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prior to version 1 we had an option to pre-loading files (from different sources) into an "AudioCache".
This made a lot of sense. My app has 5 audio sound effects that play often. So it makes sense to pre-load them into a cache (from assets in my case) and play them from there instead of reading from storage every time. This is even more important if the sound is loaded from a remote network location.
When you say "AudioCache is dead", does that mean that the file is read form source every time? Or are you doing some caching in the background without developer having to manage it?
The text was updated successfully, but these errors were encountered:
Also AudioCache is only used for AssetSource. @luanpotter maybe we should explain this here in more detail, that this isn't needed for the AssetSource anymore.
For the network, we don't provide a mechanism (yet), to cache them, and audioplayers never did. This should be handled here: #374
Prior to version 1 we had an option to pre-loading files (from different sources) into an "AudioCache".
This made a lot of sense. My app has 5 audio sound effects that play often. So it makes sense to pre-load them into a cache (from assets in my case) and play them from there instead of reading from storage every time. This is even more important if the sound is loaded from a remote network location.
When you say "AudioCache is dead", does that mean that the file is read form source every time? Or are you doing some caching in the background without developer having to manage it?
The text was updated successfully, but these errors were encountered: