New Custom DlnaMap or change DefaultDlnaMap?
#1
Hi, I'm testing streaming to a device that sends out the following rather generic User Agent: NSPlayer/4.1.0.3856.

The device appears to require a non "*" protocolInfo 4th field. (I think that the "*" is causing problems.)
Would it be better to create a new custom DlnaMap mapped onto "NSPlayer", or is it "safe" to add to the PLT_HttpFileRequestHandler_DefaultDlnaMap map a new line, which would be much simpler:
audio/flacBig GrinLNA.ORG_OP=01;DLNA.ORG_FLAGS=01700000000000000000000000000000

Any thoughts?
TIA
Reply
#2
OK, I did the latter as NSPlayer is too generic IMHO. Will test and if OK do a pull request.
Reply

Logout Mark Read Team Forum Stats Members Help
New Custom DlnaMap or change DefaultDlnaMap?0