External Playlist use results only in 403 on /ext/stream location

[DutchComputerKid]

Problem description

While using the (legacy) feature of external playlists for problem-free DSD and ASIO playback, any file played using the external player feature is given a 403 by the server. I have tried to change the link to just /stream? instead of /ext/stream? but the output is the login page.

Status
    403
Error
    Forbidden
Message
Path
    /ext/stream

Steps to reproduce

1. Turn on external playlists in legacy features
2. Set the player to use external player/playlists, both will result the same
3. Try to play in software such as Foobar or try opening the link in a browser.

System information

• Jpsonic version: Docker: Jpsonic 111.5.11 – 2022-12-08, build b43f422d838a50bc21c62b2e21a1080edb5c058d
• Operating system: Debian 11 amd64
• Java version: openjdk 17.0.4 2022-07-19
• Proxy server: None
• Client: Firefox & Edge
• Language: English
• Tomcat/standalone: Docker

[tesshucom]

I use UPnP when checking with foobar, but I was able to confirm "Network error" even though I didn't change the settings. something might be happening, Browsing with UPNP is possible, but as you pointed out, "Network error" seems to occur when connecting via /ext. For curl or browser, "Timeout". This is serious, so if we investigate and find the problem, there is a high possibility that a fixed version will be released.

[DutchComputerKid]

Subsonic never really worked API-wise with files like DSD when using MusicBee, so for a couple years now external playlists have worked flawlessly instead. In any case, good to see all of this! If anything pops up to help debugging, I'd love to help

[tesshucom]

Thank you. Haven't seen it yet, but I think it can probably be fixed. Before the trouble occurred, normal operation was confirmed with the local renderer of BubbleUPnP. DSD is a slightly strange format, but I think there is a possibility that it can be played with foobar2000. Please wait a little bit ...

[tesshucom]

When I tried to access from the m3u URL, I was able to confirm the phenomenon you pointed out.

It may be a problem with the URL generation. Probably not so serious.

---

UPnP doesn't seem to have any issues. It was a feature that had a lot of degradations, so I thought something else had happened. It was just a mistake in the UPnP URL setting ....

In this way, there are some PC version software that can be linked with DSD.

Playable: UPnP&foobar2000

When I checked with foobar2000, I can confirm that streaming is possible.  foobar2000 may be relatively easy to check. Here's what it looks like on the taskbar: 

Playable: Subsonic API&MusicBee

It looks like it can be played via the Subsonic API. There is a Subsonic plugin called [MB_SubSonic](https://github.com/BlitterStudio/MB_SubSonic).  Sorry for my Japanese, but you can check it in the track information window.

Playable: UPnP&BubbleUPnP

In the case of smartphones, we check with BubbleUPnP. BubbleUPnP is important because it allows you to send to Openhome devices.  I think there are some Android devices like Experia where works well with high resolution files. I don't know about the iPhone. . . It may not be compatible with FLAC.

[DutchComputerKid]

If you use PCM conversion, maybe.

But in any case, UPnP shows me:

Unable to open item for playback (Object not found):
"http://192.168.2.182/ext/stream?id=5455&player=4&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJwYXRoIjoiL2V4dC9zdHJlYW0_aWQ9NTQ1NSZwbGF5ZXI9NCIsImV4cCI6MTY3MjUyNjgzOX0.4dKZdUSjRL8_s_d7BOaV3YOUQ4dXePUSrRWWmt11AWE.flac"

or

Unable to open item for playback (Object not found):
"http://192.168.2.182/ext/stream?id=49543&player=4&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJwYXRoIjoiL2V4dC9zdHJlYW0_aWQ9NDk1NDMmcGxheWVyPTQiLCJleHAiOjE2NzI1MjY4MjB9.N1_g3b9HqrRgi7hPPaRuGtL13WE4NqaK3yLXDDaSiBw.dsf"

No errors being logged either to give any sense of where in the chain this is happening.

[tesshucom]

It's worth to try adding Port designation... If there is no problem with network settings such as firewall, I think it will work.

Certainly the help explanation was not good. May need fix.

If you are deploying to Tomcat etc. and the context path is specified, it will be as follows.

http://192.168.2.182:8080/jpsonic

[tesshucom]

Fixed version v111.5.13 released. It will improve the cooperation with foobar2000 by m3u.

Plese use "External player with playlist".

We are considering deleting "External player" in the future. (no longer maintained) "External player with playlist" will be kept.

I'm not sure many users understand the exact difference between them...

• "External player" issues a static URL and dynamically responds with the "currently playing song" on the server side.
  • Twenty years ago, the function might have had some significance. With this function, it was possible to "operate the play queue in the browser and let foobar2000 or Real Player play". For security reasons, most browsers do not allow m3u to operate external programs nowadays. So it's already a rotten feature.
  • It's an anti-pattern to randomly reply different resources to a unique URL. Not well designed. In fact, it adds unnecessary complexity to many features. It is also outdated in this regard.
• "External player with playlist" assumes that the full list of songs by m3u is loaded into foobar2000 etc. and controlled by an application such as foobar2000. As long as it works correctly, I think it will probably meet the needs of users. Most people using m3u today have this use case in mind.