BBC radio streams not working

[bubbleguuum]

(05-03-2015 10:45)simoncn Wrote:  It sounds like you are sending the file to the renderer in a format that the renderer can't play, such as AAC ADTS. With MIME type checking enabled, BubbleUPnP shows the 714 message to tell you that you are doing this. With MIME type checking disabled, BubbleUPnP tells the renderer to play the file but the renderer can't handle it.

The 714 error has actually nothing to do with the "mime-type check" in BubbleUPnP. This error comes straight from the renderer as a SOAP error for action SetAVTransportURI or Play. It can happen due to the following reasons:

• it rejects the mime-type (or whole protocolInfo) specified in the protocolInfo in the DIDL passed to SetAVTransportURI
• in its SetAVTransportURI (or Play) implementation, it makes a HEAD (or GET) request to the media server and rejects the Content-Type returned in the response
• in its SetAVTransportURI (or Play) implementation, it makes a HEAD (or GET) request to the media server with the "getcontentFeatures.dlna.org: 1" request header and doesn't get the expected response header. That's for DLNA renderers mostly, that are super annoying with this.
  

Moreover, since renderers can be super picky with the DIDL that is passed to SetAVTransportURI, BubbleUPNP will retry with several variations of the DIDL, until one eventually works. The 714 error is probably the error of the last attempt although there's a good chance it is also the cause of the first failure.

The only way to know what happens is for the user to send me a log file (see here for instructions)

Disabling "mime-type check" is something entirely different: if disabled and BubbleUPnP cannot find a compatible resource to play, it will force play the first resource (which may or may not work). If enabled and it cannot find a compatible resource, it displays an error toast message about "no compatible mime-type" being found and doesn't attempt playback at all.