@LakersFan:
Indeed, I think the nightly version you are using is important. The custom executable I linked is for the Dharma version of XBMC (10.1). Thus, I don't think the library format will match if you are using a newer version (pre-Eden I think). Problems could occur as I think library will not be downgraded, but I could be wrong.
If you tell me which nightly version you are using, I could probably compile a custom version with the changes I made in the Dharma version so you could test it.
For the Windows x64, I don't think they will be any problem since it seems that XBMC is 32 bits only (same thing for my custom version). Just use the right path as you mentionned in your previous post.
Moreover, note that mkv still don't stream correctly, at least on my samsung blu-ray player and on my samsung tv. I know what to do to make it work but I'm not there yet. This version is a quick hack to enable streaming on Samsung AllShare products (those I can test in fact
).
Don't hesitate to ask other questions if you feel the need to.
@vdrfan:
jhsrennie is right, changes are at this location on github. But to do a quick sum up, what I did is to add two custom HTTP response headers when a particular HTTP request header is present. This is a quick hack and the response headers I added should be customized depending on the content-type that need to be streamed. Moreover, mkv movies still don't stream at all, as I mentioned previously.
Also, I added a post in the development forum related to this post as suggested by CrystalIP. Check
here for the post.
HTTP request header:
Code:
getcontentFeatures.dlna.org: 1
HTTP response headers added when request header above is found:
Code:
contentFeatures.dlna.org: DLNA.ORG_PN=MPEG4_P2_MP4_SP_AAC;DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=01500000000000000000000000000000
TransferMode.DLNA.ORG: Streaming
Regards,
Matt