Thank you, Lowlander. I did update to 5.0.1.2422 and I'm still getting an error message, which reads "Playback failed: Living Room stereo (Chromecast Ultra) cannot decode uuid://*.m4a.
I will send a debug log to you via PM.
Harrison
Chromecast hangs while trying to connect [#13277]
Moderator: Gurus
-
- Posts: 13
- Joined: Mon Jul 16, 2018 9:23 pm
Re: Chromecast hangs while trying to connect [#13277]
Hi, based on the uuid:// prefix it looks that you are trying to cast a track from DLNA/UPnP server that is no longer accessible on your local network (to translate uuid:// to http://...)
Re: Chromecast hangs while trying to connect [#13277]
Supposing that ticket #2130 is yours and analyzing the log I see that you was casting a file from a DLNA server (as http://192.168.86.22:50002/m/NDLNA/876773.m4a )
Your "Chromecast Ultra" sent: {"requestId":1,"type":"LOAD_FAILED","detailedErrorCode":104,"itemId":1}
Based on the detailedErrorCode 104 it is that the media type was not suitable: https://developers.google.com/android/r ... dErrorCode
Solution could be to set up auto-conversion, but currently the auto-conversion works only for tracks served by MM5 server, but you are serving track from a third party server ( http://192.168.86.22:50002/m/NDLNA/876773.m4a ) -- not sure whether the third party server supports transcoding though?
Your "Chromecast Ultra" sent: {"requestId":1,"type":"LOAD_FAILED","detailedErrorCode":104,"itemId":1}
Based on the detailedErrorCode 104 it is that the media type was not suitable: https://developers.google.com/android/r ... dErrorCode
Solution could be to set up auto-conversion, but currently the auto-conversion works only for tracks served by MM5 server, but you are serving track from a third party server ( http://192.168.86.22:50002/m/NDLNA/876773.m4a ) -- not sure whether the third party server supports transcoding though?
Re: Chromecast hangs while trying to connect [#13277]
Ahh, ok, seeing your previous replies on the forum you are serving from NAS.
So the issue is that you added the track into MM5 library from the NAS DLNA/UPnP server and not as UNC paths.
Adding it as UNC paths (like //NAS/...) will resolve your issue -- as such a track will be served by MM5 server and transcoded accordingly according to the default Chromecast auto-convert rules.
So the issue is that you added the track into MM5 library from the NAS DLNA/UPnP server and not as UNC paths.
Adding it as UNC paths (like //NAS/...) will resolve your issue -- as such a track will be served by MM5 server and transcoded accordingly according to the default Chromecast auto-convert rules.