I spent some time building a .NET service that uses UPNP/DLNA to offer media to local devices. I got it working reasonably well, but the problem is that the client interfaces are absolutely garbage.
replyThe better architecture is to push content over HDMI using an endpoint you control. This doesn't have to be the actual media server. We could invent a new system role and control multiple endpoints centrally. I don't want the TV to do anything more intelligent than display the video and audio frames it is receiving.
They don't all support it well, however. My Blu-ray player, for example, mangles filenames about 10% of my media. And my TV just simply doesn't list all the files in a directory, regardless of size.
replyI also found browsing directories and files through DNLA slow and annoying.
replyMy solution that I came up with is to make a companion mobile app or mobile web site, where I pick what movie I want to play, and then my server will serve only that one file via DNLA. When I want to watch something else after that I pick up the mobile app / mobile web app again and choose again and then the files for that movie or TV series is served instead
[dead]
reply