smoothquark 5 Posted August 19, 2015 Posted August 19, 2015 I would be very grateful for some help.... I have been desperately trying to get DLNA working with my Samsung Series C TV (46C5100). The "Samsung Smart TV" profile is detected OK, and I also tried to make a start with my own modified version which is also picked up correctly. However, EVERY single file comes up as "not supported file format". Neither DirectPlay nor transcoding works. I had to make some modifications to mediatomb to allow it to work with my samsung TV... <custom-http-headers><add header="transferMode.dlna.org: Streaming"/><add header="contentFeatures.dlna.org: DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=017000 00000000000000000000000000"/></custom-http-headers> <map from="avi" to="video/mpeg"/> <map from="mkv" to="video/mpeg"/> I have figured out the <map from... bit - I think the changes need to go under ResponseProfiles How do I incorporate the custom-http-headers? Thanks.
Luke 42077 Posted August 19, 2015 Posted August 19, 2015 Well i guess the first thing to do before a custom profile for your device is figure out if actually needs to be different from the regular samsung profile, or if the profile for all samsung devices requires adjustment. Secondly, rather than ask about profile changes, I would instead point out the format/codec requirements of your TV just in case there might be a better way.
smoothquark 5 Posted August 19, 2015 Author Posted August 19, 2015 Thank you. The trouble with the samsung series C is that it expects all video as video/mpeg and changes to the headers as above - hence those changes in mediatomb, and similar changes in minidlna as well. The Series C supports all the codecs as in the current Samsung range.
Luke 42077 Posted August 19, 2015 Posted August 19, 2015 will that break other models if the change is made to all?
smoothquark 5 Posted August 19, 2015 Author Posted August 19, 2015 I am pretty sure it will, at least looking at mediatomb and patches to minidlna, that's why I think I need a custom profile. I am trying to play with and create a minimal profile but not having any success whatsoever. There is no thumbnails and the files do not play. I can browse the videos so DLNA presentation itself is working. I am trying to figure out what does contentFeatures.dlna.org: actually refer to.
Happy2Play 9780 Posted August 19, 2015 Posted August 19, 2015 (edited) I am pretty sure it will, at least looking at mediatomb and patches to minidlna, that's why I think I need a custom profile. I am trying to play with and create a minimal profile but not having any success whatsoever. There is no thumbnails and the files do not play. I can browse the videos so DLNA presentation itself is working. I am trying to figure out what does contentFeatures.dlna.org: actually refer to. Not positive but isn't it the same as Emby's protocol info? DLNA-Profiles-select a profile-Info-Expand Server Settings-Protocol Info Edited August 19, 2015 by Happy2Play
smoothquark 5 Posted August 20, 2015 Author Posted August 20, 2015 Not positive but isn't it the same as Emby's protocol info? DLNA-Profiles-select a profile-Info-Expand Server Settings-Protocol Info Tried it but did not work. Have a few more thoughts and shall just have to keep trying different things...
smoothquark 5 Posted August 23, 2015 Author Posted August 23, 2015 After much trial and error I seem to have made some progress.... This is on a linux system and I directly copied and modified the "Samsung Smart TV.xml" in /var/lib/emby-server/config/dlna/system to /var/lib/emby-server/config/dlna/user... <Name>Samsung Smart TV</Name> to <Name>Samsung Series C</Name> and <HttpHeaderInfo name="User-Agent" value="SEC_" match="Substring" /> to <HttpHeaderInfo name="USER-AGENT" value="SEC_HHP_TV-" match="Substring" /> The above changes are only for recognition purposes. I do not have another Samsung TV to test and hope that the above is unique enough to apply only to the Series C. Seems that it is case-sensitive and I had to change "User-Agent" to "USER-AGENT". Furthermore, I think emby-server needs to be restarted everytime a DLNA profile is modified? It would also help if "Enable DLNA debug logging" turns on ALL DLNA logging rather than having to turn on "Enable debug logging" under "Advanced" as well as it creates a huge amount of debugging which is not required. For the Series C to be recognised and profile to be applied, I had to add the the following changes as it appears that different headers are found at different points for DLNA identification... <HttpHeaderInfo name="USER-AGENT" value="DLNADOC" match="Substring" /> <HttpHeaderInfo name="getcontentFeatures.dlna.org" value="1" match="Substring" /> <HttpHeaderInfo name="transferMode.dlna.org" value="Streaming" match="Substring" /> I ran tests using the following files.... ChannelCheck.m2ts Dolby\ Digital\ 5.1Ch\ Sound\ Test.avi DolbyHD.m2ts Dolby.vob DTS-HD.m2ts Elysium_trailer_1-1080p-HDTN.mp4 Elysium_trailer_1-4K-HDTN.mp4 Dolby.vob and Elysium_trailer_1-1080p-HDTN.mp4 did not play at all whilst the rest were "transcoded" I then removed all the <DirectPlayProfile ... /> and replaced with <DirectPlayProfile container="all" audioCodec="all" videoCodec="all" type="Video" /> ALL the above test files are now "transcoded" I don't really know the difference between DirectPlay and DirectStream - I presume the former is for playing media directly from its source like as if it was installed on a USB stick and connected to the TV, perhaps using SMB or NFS, whereas DirectStream is via http (which I think what UPNP/DLNA is all about)? If so, then I guess when it is "transcoding", it is actually "streaming" without changing the file at all? How do I tell the difference in the logs? I then removed <DirectPlayProfile container="all" audioCodec="all" videoCodec="all" type="Video" /> This does not seem to make any difference whatsoever to the files played. Looking at the transcode logs... For Dolby.vob: Stream mapping: Stream #0:1 -> #0:0 (mpeg2video (native) -> h264 (libx264)) Stream #0:2 -> #0:1 (ac3 (native) -> ac3 (native)) For DTS-HD.m2ts: Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) Stream #0:1 -> #0:1 (dts (dca) -> ac3 (native)) I guess this indeed means that both files are being truly transcoded (video for the former and audio for the latter). Is there a way of specifying transcoding options depending on file extension / file format to try and keep as much of it native to reduce CPU usage? Obviously, formats not supported by the TV have to be transcoded. 2
lamero 1 Posted September 22, 2015 Posted September 22, 2015 Thanks smoothquark. Now my Samsung C Series works with Emby
delirio 0 Posted January 10, 2016 Posted January 10, 2016 Thk a loot smoothquark My serie C now work .
MuF 0 Posted February 14, 2017 Posted February 14, 2017 Can you upload changed Samsung Smart TV.xml here, please. THX
Luke 42077 Posted February 14, 2017 Posted February 14, 2017 hi @@MuF, what are you looking to do? Thanks !
MuF 0 Posted February 14, 2017 Posted February 14, 2017 (edited) Hi I looking modificed file to download XML for Samsung C Series TV Edited February 14, 2017 by MuF
Luke 42077 Posted February 15, 2017 Posted February 15, 2017 Hi @@MuF, what changes exactly are you looking for?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now