Minim Server - BubbleUPnP - Cabasse Abyss – Playback doesn't work

[Cavaradossi]

Hello Simon,
unfortunately the playback via BubbleUPnP on my Cabasse Abyss doesn't work. I get the error message "The specified resource has a mime-type that is unsupported. (code: 714)". The support team by Bubble said the problem is with the minim server. Could you please help? BubbleUPnP-Log and Server- Log are attached.
Thank you very much.
Best regards
Cavaradossi

[simoncn]

I don't see anything in these logs indicating a MIME type problem with MinimServer. The Abyss is sending a HEAD request for a FLAC file and MinimServer is correctly returning a MIME type of audio/x-flac.

[bubbleguuum]

(31-10-2023 19:17)simoncn Wrote:  I don't see anything in these logs indicating a MIME type problem with MinimServer. The Abyss is sending a HEAD request for a FLAC file and MinimServer is correctly returning a MIME type of audio/x-flac.

Does MinimServer get a GET request on the same URL after that HEAD request ?
If not, that renderer does not like something in the HEAD reply.

[simoncn]

I don't see a GET request in either of the log files. The response from MinimServer to HEAD looks fine to me.

I see this in the BubbleUPnP log file:

Code:

[qtp253034216-1604 (1604)                ] INFO     - 0:00:17.126    - decode params: {"convert24BitTo16Bit":false,"convertMonoToStereo":false,"defaultSamplerate":48000,"downmixMultichannelToStereo":true,"ext":"flac","forcedSamplerate":-1,"itemId":"0$albums$*a1$*i6","maxSamplerate":-1,"padEndOfTrack":false,"rendererUdn":"f87f1a6a-3355-4c89-97bc-3aff28196ff7","replaygain":"drop","soxResamplePrecision":28,"supportsL16":true,"supportsL24":false,"supportsWAV":true,"trialDurationSec":0,"url":"http://192.168.188.60:9790/minimserver/*/minim_test/Igor*20Levit*20(2019)*20-*20Beethoven*20*c2*b7*20Complete*20Piano*20Sonatas*20(24bit-96,0kHz*20-*202*20Channel)/01*20-*20I.*20Allegro.flac"}

Could the "downmixMultichannelToStereo":true part of this be related to the problem? For some reason, ffmpegpcmdecode is being called and is producing this message:

Code:

no current decode info found for item key: f87f1a6a-3355-4c89-97bc-3aff28196ff7_0$albums$*a1$*i6

[bubbleguuum]

That BubbleUPnP log file is playing to the local renderer, not to that Cabasse renderer. So this log file does not correspond to the MinimServer log where that HEAD request is coming from the Cabasse (whose ip is 192.168.188.59).
In the minim log, I can see the HEAD request but the fact that there is no subsequent GET request from the Cabasse to get the stream means that there is something it does not like in the HEAD response and stops there. Maybe it does not like the value of the contentFeatures.dlna.org header. DLNA renderers can be super picky.
I asked OP to send me a log file playing that FLAC stored on his Android device to the Cabasse (which I was told was working). It will allow to compare the HEAD response.

[simoncn]

Thanks for your help with this.

I was a bit concerned about DLNA.ORG_PN= in the response. MInimServer is sending this because FLAC is not a valid DLNA type. This renderer might need something here or might need DLNA.ORG_PN to be omitted completely.

[Cavaradossi]

(31-10-2023 21:25)bubbleguuum Wrote:  That BubbleUPnP log file is playing to the local renderer, not to that Cabasse renderer. So this log file does not correspond to the MinimServer log where that HEAD request is coming from the Cabasse (whose ip is 192.168.188.59).
In the minim log, I can see the HEAD request but the fact that there is no subsequent GET request from the Cabasse to get the stream means that there is something it does not like in the HEAD response and stops there. Maybe it does not like the value of the contentFeatures.dlna.org header. DLNA renderers can be super picky.
I asked OP to send me a log file playing that FLAC stored on his Android device to the Cabasse (which I was told was working). It will allow to compare the HEAD response.

Log is attached

[Cavaradossi]

Possibly interesting: When I enable FFmpeg in BubbleUPnP, playback works fine. Log is attached.

[simoncn]

I have made a change in MinimServer update 243 that I hope will fix this problem. Please try it and let me know.

[Cavaradossi]

(03-11-2023 21:30)simoncn Wrote:  I have made a change in MinimServer update 243 that I hope will fix this problem. Please try it and let me know.

Big Thanks, playback is working fine now.

Best regards,
Cava