[FEEDBACK] Adding file path output support

[jaredtrent]

Thank you for taking the time to provide feedback! This is incredibly valuable for fine-tuning the software.

1. What were you trying to do?
I'm working on an integration of AudioMuse and Sonos. My app can detect current playing song, communicates with AudioMuse to create a similar playlist from the track or artist (or just has a text input to generate a playlist) and then replaces the current Sonos queue with those tracks.

2. What did you like?
I just love the idea of a fast offline track or artist radio!!!

3. What was confusing or could be improved?
a. It'd be nice to communicate with AudioMuse using an API key. And over HTTPS.
I host it behind a reverse proxy and gate with pocketid normally. But for this workflow I have to keep the communication wide open over the local network. Some security options built in to AudioMuse would be appreciated. To be fair I haven't looked into how to route it securely yet at all beyond wanting the above security settings.

b. It'd be nice to be able to export the playlist as an actual playlist file, configurable to a file location. As in, write the playlist as a file to my NAS.

c. OR It'd be nice to be able to get a direct response of the file locations directly from AudioMuse.

5. Any Other Thoughts or Ideas?
My app also has MacroPad support. So what's cool about this workflow is I can press a button (or a macro like a double or triple press) and automatically play this AudioMuse playlist!

[jaredtrent]

And... I realized this morning that Navidrome purposefully doesn't expose file paths. To workaround for now I just submit some progressively staggered searches from AudioMuse's results to Sonos, and totally bypass Navidrome. Modified C above. Anyway, thanks again!

[jaredtrent]

Nice work adding authentication support! https://github.com/NeptuneHub/AudioMuse-AI/releases/tag/v0.8.13

[NeptuneHub]

Yes now it support both user authentication with username+password and server to server authentication with api token.

Https is also suggested but need to be added on top with a reverse proxy or similar.

Let me know if you tested and how do you think about.

[rendyhd]

• Regarding point B, local filesupport (use a folder with files, without provider as source, and save back to .m3u) is something we're working on. I want to use it for Music Assistant (which i use to control my sonos setup :))
• Point C, the last version now grabs the file path, however, it's not exposed via API (yet). It's currently only present in the internal data. I'll try to add file path as response and file path to lookup as API endpoints for the local file support source.

To make filepath work with navidrome:
*Navidrome by defaults reports an "Internal path", this is artist/album/track but not your real file path. If you want to match files across services, it's advised to turn on Report Real Path:

• Log into the Navidrome web interface
• Go to Players in the right sidebar
• Click on the AudioMuse player entry (it appears after AudioMuse first connects)
• Toggle "Report Real Path" to enabled

You can also change this as a default setting by setting ND_DEFAULTREPORTREALPATH=true