DLNA profile help for Oppo 103D

[DingDong 0]

Hello,

 

would greatly appreciate any help offered towards my understanding of how MB is executing the play to function for video. I have created a profile for my oppo, recognized by MB server under push and pull conditions. I am able to play transcoded files to the oppo, but as of yet not direct play files. My questions and issues are as follows...

 

I have observed, while experimenting with profiles, that I must have a transcoding container specified, otherwise when trying to play a video file I get an "argument not supported error" for containers specified under direct play. When viewing the server logs, the error appears because the stream file is presented without a file extension (in this case m2ts). Only after specifying a transcoding contain will the stream file be presented with an extension, and it is the transcoding extension. It then appears that the transcoded file extension is tested against the players protocols for compatibility. Is this proper behaviour or am I doing something wrong? Why is the direct play container extension not being tested against the player first?

 

Since I can't seem to get MB to present the direct play container extension, any container protocols defined in the profile response section are being applied to the transcoded container only. Is there a way of defining the protocols for the direct play extension in order to avoid the "argument not supported error"and have them apply to the direct play container?    

 

I have attached my profile and welcome feedback as I clearly need help understanding how this all works.

Thanks!

 

 

 

OPPO BDP-103.xml

[Luke 37086]

direct play is checked first but all of the conditions under codec profiles have to be satisfied as well as the bitrate setting

[DingDong 0]

direct play is checked first but all of the conditions under codec profiles have to be satisfied as well as the bitrate setting

 

Hello...thank you for your response

 

To be clear...are you saying that direct play is being checked and the "argument not supported error" is in response to the fact that all conditions are not being met? (see log below)

 

My thinking was, that if I create a profile with nothing in the profile other than the direct play container (m2ts), the log would indicate that stream.m2ts was checked and it either passed or failed. and when checked it would be checked with the profile response included in the profile for an m2ts file extension. This doesn't appear to be the case.

 

The second log attached is the log when the transcode container is added to the profile ( the "ts" file extension) and it appears to be the only extension being checked and it uses the correct "DLNA.ORG_PN=MPEG_TS_SD_NA" protocol specified. In the original profile (above) I use m2ts as the trancode container, the reason being is that, when that container is used with "all" set for either video or audio the transcode is basically a pass through of either audio or video and I get the full original bitrate (which works for select codecs). If the protocols work for the high bitrate copy...why not for the direct play?

 

I basically want to have the direct play stream.m2ts file sent to the player with "DLNA.ORG_PN=MPEG_TS_SD_NA;DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=01700000000000000000000000000000" and I can't figure out how or whether it will even make a difference. anyone have any suggestions?

 

Thanks       

 

 

 

 

  

log with no transcoding:

 

 

2015-01-04 21:53:38.6161 Debug - Dlna: OPPO BDP-103 - Received PlayRequest: PlayNow

2015-01-04 21:53:38.6161 Debug - Dlna: Found matching device profile: OPPO BDP-103

2015-01-04 21:53:38.6161 Error - DtoUtils: ServiceBase<TRequest>::Service Exception

    *** Error Report ***

    Version: 3.0.5464.40000

    Command line: C:\Users\Media Player\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe

    Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1

    Processor count: 8

    64-Bit OS: True

    64-Bit Process: False

    Program data path: C:\Users\Media Player\AppData\Roaming\MediaBrowser-Server

    Application Path: C:\Users\Media Player\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe

    Argument not supported: http://192.168.2.14:8096/mediabrowser/videos/18d2130ef18aa4a6367db24a6af9580c/stream

    System.ArgumentException

     at MediaBrowser.Common.Net.MimeTypes.GetMimeType(String path)

     at MediaBrowser.Dlna.Didl.DidlBuilder.AddVideoResource(XmlElement container, IHasMediaSources video, String deviceId, Filter filter, String contentFeatures, StreamInfo streamInfo)

     at MediaBrowser.Dlna.Didl.DidlBuilder.AddVideoResource(XmlElement container, IHasMediaSources video, String deviceId, Filter filter, StreamInfo streamInfo)

     at MediaBrowser.Dlna.Didl.DidlBuilder.GetItemElement(XmlDocument doc, BaseItem item, BaseItem context, Nullable`1 contextStubType, String deviceId, Filter filter, StreamInfo streamInfo)

     at MediaBrowser.Dlna.Didl.DidlBuilder.GetItemDidl(BaseItem item, BaseItem context, String deviceId, Filter filter, StreamInfo streamInfo)

     at MediaBrowser.Dlna.PlayTo.PlayToController.CreatePlaylistItem(BaseItem item, User user, Int64 startPostionTicks, String serverAddress, String mediaSourceId, Nullable`1 audioStreamIndex, Nullable`1 subtitleStreamIndex)

     at MediaBrowser.Dlna.PlayTo.PlayToController.CreatePlaylistItem(BaseItem item, User user, Int64 startPostionTicks, String serverAddress)

     at MediaBrowser.Dlna.PlayTo.PlayToController.<SendPlayCommand>d__1d.MoveNext()

log with transcoding container added (TS):

 

2015-01-04 22:08:03.1007 Debug - Dlna: OPPO BDP-103 - Received PlayRequest: PlayNow

2015-01-04 22:08:03.1007 Debug - Dlna: Found matching device profile: OPPO BDP-103

2015-01-04 22:08:03.1007 Debug - Dlna: OPPO BDP-103 - Playlist created

2015-01-04 22:08:03.1007 Debug - Dlna: OPPO BDP-103 - Playing 1 items

2015-01-04 22:08:03.1007 Debug - Dlna: OPPO BDP-103 - SetAvTransport Uri: http://192.168.2.14:8096/mediabrowser/videos/18d2130ef18aa4a6367db24a6af9580c/stream.ts?Params=47d4c8a33b05fe8c29e70b8894c93929;uuid:140479c0-58f3-1cef-84bf-0022de8c8e2f;18d2130ef18aa4a6367db24a6af9580c;false;h264;ac3;1;;49680000;320000;;30;1920;1080;0;41;635560240831057110;;;; DlnaHeaders: DLNA.ORG_PN=MPEG_TS_SD_NA;DLNA.ORG_OP=10;DLNA.ORG_CI=1;DLNA.ORG_FLAGS=01D00000000000000000000000000000

2015-01-04 22:08:03.1007 Info - App: HttpClientManager POST: http://192.168.2.17:2870/control/AVTransport

2015-01-04 22:08:03.3757 Info - App: HttpClientManager POST: http://192.168.2.17:2870/control/AVTransport

2015-01-04 22:08:03.6027 Debug - HttpServer: HTTP HEAD http://192.168.2.14:8096/mediabrowser/videos/18d2130ef18aa4a6367db24a6af9580c/stream.ts?Params=47d4c8a33b05fe8c29e70b8894c93929;uuid:140479c0-58f3-1cef-84bf-0022de8c8e2f;18d2130ef18aa4a6367db24a6af9580c;false;h264;ac3;1;;49680000;320000;;30;1920;1080;0;41;635560240831057110;;;;

Ip: 192.168.2.17:35273. Headers: Host=192.168.2.14:8096,range=bytes=0-,transferMode.dlna.org=Streaming

2015-01-04 22:08:03.6027 Debug - HttpServer: HTTP Response 200 to 192.168.2.17. Response time: 3.0002 ms.