In the DLNA XML file you need to remove lines between </Profile> and </Profiles>. It's part of some test profile that edited out wrong.Pushed some minor fixes
In the DLNA XML file you need to remove lines between </Profile> and </Profiles>. It's part of some test profile that edited out wrong.Pushed some minor fixes
Yep - that's the way. Our httpserver does AFAIK not support multithreadingit would probably be best solved during the OWIN / Katana / vNext migration.
Thank you!In the DLNA XML file you need to remove lines between </Profile> and </Profiles>. It's part of some test profile that edited out wrong.
You hit the nail - time is currently the issue.I don't know whats on your to do list right now and how much time you have.
Too bad. But I think nothing we can change^^You hit the nail - time is currently the issue.
You should know that this is not 100% reliable. For example every generation of a smart TV support different DLNA profiles and therefore it requires a new profile. But in the header information sent from the TV it might not be possible to see which generation the TV is an therefore an invalid profile could be detected. It should still be possible for the user to select the correct profile.I changed the client detection to use http headers for now
Not so sure about that.What about a combination of IP address and user agent (or hostname and user agent)?
MP4 container is not designed for streaming during transcoding. After transcoding is completed it should be possible though.MP4 seems to be a bad choice for streaming
Yes the profile does support inheritance. You will see when I push the profiles.I guess we don't support to inherit from other profiles etc.
I know That's why I implemented the movtags. It should make this possible, it was better, but not working 100%.MP4 container is not designed for streaming during transcoding. After transcoding is completed it should be possible though
Nice!Yes the profile does support inheritance. You will see when I push the profiles