Send correct Mimetype? (RaspberryPi, BubbleUPnP, Chromecast)
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Send correct Mimetype? (RaspberryPi, BubbleUPnP, Chromecast)
I'm trying to setup UMS on my RaspberryPi, so I can use BubbleUPnP on my Android devices as the DLNA-client to start the Video's on my Chromecast. Since almost all of my videos are in a Chromecast-compatible format (mkv & mp4) and since the raspberry is way too slow to do any transcoding, UMS should not do any transcoding at all. In the few cases where transcoding is required, this can be done by BubbleUPnP Server on my laptop.
While I have the basics working, I'm struggling with one problem: all videos (avi, mp4, mkv,..) seem to be sent with the incorrect Mimetype 'video/mpeg', as BubbleUPnP show all the video as being of type 'MPEG'. Since BubbleUPnP itself checks the Mimetype for Chromecast compatibilty it refuses to play the videos on the Chromecast (except when I have the BubbleUPnP sever running on my laptop).
If I configure the 'Android.conf' renderer with (as explained here)
Then BubbleUPnP sees all the videos as 'mp4' and succesfully plays them on the Chromecast. However this obviously breaks the transcoding features of BubbleUPnP, as it now basically can't detect incompatible videos anymore as they are all compatible as far as BubbleUPnP is concerned.
So I'm wondering how I can get UMS to send the correct Mimetypes for each videotype so BubbleUPnP can correctly play the compatible files and transcode the incompatible ones?
I have been trying many combinations with the 'Supported =' options in Android.conf, such as:
But those lines seem to be completely ignored by UMS. I'm completely lost as how to accomplish this. It can't be that hard, or such a strange idea, to just send the correct Mimetypes, so any help in what I'm doing wrong is appreciated.
While I have the basics working, I'm struggling with one problem: all videos (avi, mp4, mkv,..) seem to be sent with the incorrect Mimetype 'video/mpeg', as BubbleUPnP show all the video as being of type 'MPEG'. Since BubbleUPnP itself checks the Mimetype for Chromecast compatibilty it refuses to play the videos on the Chromecast (except when I have the BubbleUPnP sever running on my laptop).
If I configure the 'Android.conf' renderer with (as explained here)
Code: Select all
MimeTypesChanges = video/mpeg=video/mp4
So I'm wondering how I can get UMS to send the correct Mimetypes for each videotype so BubbleUPnP can correctly play the compatible files and transcode the incompatible ones?
I have been trying many combinations with the 'Supported =' options in Android.conf, such as:
Code: Select all
MediaInfo = true # (also tried false etc)
Supported = f:mp4 m:video/mp4
Supported = f:mkv m:video/x-matroska
Last edited by teranex on Fri May 30, 2014 6:30 am, edited 1 time in total.
Re: Send correct Mimetype? (RaspberryPi, BubbleUPnP, Chromec
You may be interested on this thread (viewtopic.php?f=4&t=1221 ) about Remuxing Only for low powered UMS servers.
Basically what I did was to raise the priority of TsMuxer as the preferred engine in UMS, and tweak any renderer profile I use to make sure the video formats aren't transcoded (most of the modern renderers can natively process any video stream around -h264, mpeg2, ...-, container is usually the offending component), audio transcode doesn't really take too much resources from the server anyways and may need to be converted due to renderer support/licensing (ie AC3, DTS, ...)
I hope it helps, Wolf
Basically what I did was to raise the priority of TsMuxer as the preferred engine in UMS, and tweak any renderer profile I use to make sure the video formats aren't transcoded (most of the modern renderers can natively process any video stream around -h264, mpeg2, ...-, container is usually the offending component), audio transcode doesn't really take too much resources from the server anyways and may need to be converted due to renderer support/licensing (ie AC3, DTS, ...)
I hope it helps, Wolf
-- UMS serving PS3, WDTV, Samsung H6400 + J5500 and Kalemsoft renderers! (no video transcoding but remuxing accepted
)

Re: Send correct Mimetype? (RaspberryPi, BubbleUPnP, Chromec



Please remember to Upload your debug logs!
Universal Media Server Wiki!
"...functionality before beautification..."
Re: Send correct Mimetype? (RaspberryPi, BubbleUPnP, Chromec
Wolfgan, DeFlanko, thank you for your answers. I'll keep an eye on the upcoming Chromecast support. For now I'll set up UMS to simply offer everything with the mp4 mimetype.
One other small problem I had, but that might as well be a BubbleUPnP problem, is that some subtitles do not work in BubbleUPnP (it gives "Subtitle convertion failed"). When I play videos + subtitles from the SDCard in the Raspberry (= root + home filesystem), it always works. But when I try to play a video + subtitle from my network disk (which is a Samba mount on my raspberry on /media/share), the subtitles never work. Even with exactly the same files on the SDCard and on the network disk, I see the difference.On the SDCard the video plays fine and I have subtitles, but on the network disk the video also plays fine but the subtitles don't work...
Could there be any difference in how UMS serves subtitle files from an Ext4 filesystem compared to a Samba (FAT32) filesystem?
One other small problem I had, but that might as well be a BubbleUPnP problem, is that some subtitles do not work in BubbleUPnP (it gives "Subtitle convertion failed"). When I play videos + subtitles from the SDCard in the Raspberry (= root + home filesystem), it always works. But when I try to play a video + subtitle from my network disk (which is a Samba mount on my raspberry on /media/share), the subtitles never work. Even with exactly the same files on the SDCard and on the network disk, I see the difference.On the SDCard the video plays fine and I have subtitles, but on the network disk the video also plays fine but the subtitles don't work...
Could there be any difference in how UMS serves subtitle files from an Ext4 filesystem compared to a Samba (FAT32) filesystem?