Feature description
It would be very useful to have a “Share file” option for tracks coming from remote media providers such as Emby (and ideally Jellyfin and other supported providers).
Currently, when using the normal Share action on an Emby track, Symfonium shares the track information/artwork, but not the actual audio file.
The existing “Share file” function works perfectly for tracks from the Local device provider, so it would be great to have similar behavior for remote tracks.
When “Share file” is selected, Symfonium could:
- use the existing offline/permanent cached copy if the track is already cached;
- otherwise temporarily download the track from the media server;
- share the resulting audio file through the standard Android share dialog;
- optionally delete the temporary file afterwards.
Whether the file is stored temporarily in the app cache or exported to the Downloads folder is not important from the user’s point of view. The important part is being able to send the actual audio file directly from Symfonium.
Problem solved
Sometimes I find a track in my Emby library that I want to send to someone through Telegram, WhatsApp, Quick Share, etc.
At the moment I have to manually export/download the track, open a file manager, find the file and share it from there.
Another workaround is adding the Downloads folder as a Local device provider, where “Share file” works, but this is inconvenient and can also create duplicate entries in the library.
Brought benefits
Sharing a track would become a simple one-step action directly from Symfonium.
It would also make better use of files that are already stored in the permanent/offline cache and avoid having to maintain a separate local media source just for sharing files.
Other application solutions
Android file managers can share downloaded audio files normally, but this requires manually exporting the track first and leaving Symfonium.
Device type
All
Additional description and context
My media provider is Emby.
I tested the existing “Share file” option with a Local device provider and it works exactly as expected. I would like to have the same user experience for tracks stored on Emby.
Ideally this could work with other remote providers too, if technically possible.
I searched existing feature requests
on