ryanheise
Support for SAF URI (`content://`) as AudioSource Input on Android
Is your feature request related to a problem? Please describe.
Currently, there isn't a direct issue. However, as Android continues to enforce stricter permissions and security policies regarding file access, managing files outside of the application sandbox has become more strict in the newer versions. Specifically, for files that need to be stored or accessed externally on Android devices, the Storage Access Framework (SAF) using URI paths like content:// are used.
The challenge arises from the fact that there doesn’t appear to be any straightforward way to use these SAF file URIs as an input for AudioSource.
Describe the solution you'd like
It would be ideal to have native support or a feature within the library to directly use SAF URIs (e.g., content://) as input for AudioSource.
Describe alternatives you've considered
As a temporary solution, I’ve tried copying the audio files from their SAF location into the app’s private storage or a shared storage location that is accessible for the current AudioSource implementation. While this workaround is functional, it does not really work for many files or big files.
This approach also feels inefficient, particularly for larger files or scenarios where users expect instant playback/editing of an audio track they have selected. Having to copy files each time adds latency.
Additional context I hope I did not oversee something reagarding this is already possible. Anyways thanks for the awesome software.
