Jellyfin->DLNA woes on B&O devices

Support
22

No problem, I totally get you.
And if you get completely sick of it just tell me to piss off :grin:

Response Headers

Accept-Ranges: bytes
Content-Length: 48237039
Content-Type: audio/flac
contentFeatures.dlna.org: DLNA.ORG_PN=FLAC;DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=01D00000000000000000000000000000
Date: Tue, 21 Jun 2022 18:25:55 GMT
Last-Modified: Sun, 06 Mar 2022 17:02:23 GMT
realTimeInfo.dlna.org: DLNA.ORG_TLAG=*
Server: Kestrel
transferMode.dlna.org: Streaming
X-Response-Time-ms: 24

URL with blank DeviceProfileID:

http://192.168.1.2:8097/audio/b3c951bb-15e0-f92b-3a98-eca4a01ba331/stream.flac?DeviceProfileId=&DeviceId=test&MediaSourceId=b3c951bb15e0f92b3a98eca4a01ba331&Static=true&Tag=1380246717a218aca41ba396ac250656&dlnaheaders=true

Response Headers without DeviceProfileID (also works)

Accept-Ranges: bytes
Content-Length: 48237039
Content-Type: audio/flac
contentFeatures.dlna.org: DLNA.ORG_PN=FLAC;DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=01D00000000000000000000000000000
Date: Tue, 21 Jun 2022 18:29:02 GMT
Last-Modified: Sun, 06 Mar 2022 17:02:23 GMT
realTimeInfo.dlna.org: DLNA.ORG_TLAG=*
Server: Kestrel
transferMode.dlna.org: Streaming
X-Response-Time-ms: 65
23

Just noticing the 8097 port that’s strange or you changed from before?

Anyway what are the headers from:
http://192.168.1.2:8096/Audio/949b6f2224705465748cde99272e34ac/stream.flac?static=true&dlnaheaders=true

And don’t worry I’m known to have no bugs and fix what I can :stuck_out_tongue:

24

Yeah, I spun up a second Jellyfin Docker-container to experiment with. So needed a different port.
Don’t change things in production :smiley:

This is the Response Headers from server on port 8096

URL:

http://192.168.1.2:8096/Audio/949b6f2224705465748cde99272e34ac/stream.flac?static=true&dlnaheaders=true

Music plays fine.

Accept-Ranges: bytes
Content-Length: 44014990
Content-Type: audio/flac
contentFeatures.dlna.org: DLNA.ORG_PN=FLAC;DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=01D00000000000000000000000000000
Date: Tue, 21 Jun 2022 18:36:13 GMT
Last-Modified: Sun, 05 Jun 2022 00:05:55 GMT
realTimeInfo.dlna.org: DLNA.ORG_TLAG=*
Server: Kestrel
transferMode.dlna.org: Streaming
X-Response-Time-ms: 86
25

Please provide the headers for the other url I just gave that would be a Symfonium one :slight_smile:

26

That is the response from the url you gave me.

27

Ok so that’s the part where I ask again: Did you test to checl / uncheck the alternative dlna flags in the advanced settings?

28

Yes, I did.
No change.

29

That makes no sense when unchecked it does generate the same flags as bubble.

Can you try again and provide Symfonium logs with it disabled?

All mimes are similar yet they says invalid mime …

30

Here’s one.
It takes a while to sanitize the debug logs.

Gonna look for the other also, I tried it with on and off.

31

What do mean by sanitize ? All private tokens and everything should already be removed automatically.

32

Anyway I think I found the hidden difference please test attached APK

app-final.apk (5.6 MB)

33
34

Public server URL and IP’s are always present.

35

Yes they are needed to be able to see all the ip / certificate issues and identify who talks to who :frowning:

Hiding them by default would make support insanely more complicated way too often.

Have you seen the test APK message earlier ?

36

Thank you!

Here’s the log, cause it didnt work :frowning:

debug.log (26.4 KB)

37

I get it, no problem. It just takes longer time for me :slight_smile:

38

Ok so yes please test when casting from Jellyfin :slight_smile: This is a quick hack the internal web server does not return the ORG_PN yet

39

Didnt work either im afraid.
Gonna get you the logs

debug.log (26.1 KB)

40

Well lack of idea for today.

Just in case there’s no profile tricks / tests on that instance ? Same result on prod?

41

Yeah, I need to call it a day as well.
I just tried on the real server, no difference.

I get a feeling the solution is within reach, it’s probably something stupid like a syntax preference by B&O.
That’s the curse with the shitty DLNA protocol, every manufacturer implements it its own way.

BIG thank you so far for putting up with my crap! :smiley: