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.

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?

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://...)

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

Please update to build 2422 as some bugs in this area have been fixed: viewtopic.php?f=30&t=86639&sd=d

Let us know if the problems persist in which case a debug log (step 4b) would be helpful: viewtopic.php?f=30&t=86643

Good morning. I have a new issue that appears similar to my previous problem. I am using MM 5.0.0.2338. Otherwise, no change to the system specs that I provided before. I was having problems with my MM library on the NAS with duplicates etc., so I reset the NAS and the MM5 library and started fresh.

Now when I try to Chromecast certain files with .aif or m4a extensions, I get the message "Playback failed: [filename] cannot be decoded." The files play ok (although with some distortion) when I play them via the Internal player. The affected files include the same file that we discussed before, which was an ALAC file in m4a format (Rikki Don't Lose That Number). So far, I have not encountered problems with other file formats.

I have checked the conversion rules for the Chromecast devices and have verified that the files are all being converted to MP3 format before casting, per the conversion rules that solved my problem last time..

This may or may not be related/part of the issue: The filename shown in the error message is a uuid://*.m4a. The filename shown in the track properties is http://192.168*.m4a. I don't understand networks or NAS file handling to know whether this is normal or whether I perhaps made an error when I restored the NAS and MM5.

I will try to send a debug file.

Thanks for any help you can provide.
Harrison

Awesome - thanks Ludek! Just to clarify though, my MM isn't successfully reverting to the player, it is actually freezing the player and requiring a forced quit in most curcumstances.

When do you think MM5 will be ready for general release? Must be getting close now?

Hi,
thanks for the new log!

I see the issue now, your "Lounge" player has not replied its transport status for 4 seconds and MM5 thus considered it as "Turned off or inaccessible" and reported the message per: https://www.ventismedia.com/mantis/view.php?id=16671

i.e. starting from build 2260 if Chromecast is turned off during the playback then MM5 shows "The 'xxx player' is turned off or inaccessible." within 2 seconds, stops the playback and switches to the internal player.

I re-opened the issue to increase the timeout to 10 seconds (which should resolve your issues) and will be fixed in 2266.
So any build higher than 2265 (or lower than 2260) should work for you now.

Hey Ludek

I downloaded the latest MM just now and generated this bug report: https://1drv.ms/u/s!AoM1UrOaoKUMkZoPOia ... g?e=rr17C8

The player stopped streaming. It didn't freeze MM this time which is what is has usually done. I see the report did note an error when the casting stopped. I clicked play again and it cast again fine.

This is an ongoing issue between MM and my Chromecast. The cast constantly falls away. I don't have this issue with any other player (android phone or Google's cast on Chrome).

Hope you can figure it out.

Still nothing, I added more debug messages to see more once you generate the debug log using 2265, the build should be available shortly.
Please subscribe this thread https://www.mediamonkey.com/forum/viewt ... 25#p471525 to be notified once 2265 is there.

Does this one show anything?

The MM stopped. the strange whilte line appeard over the screen and I had to force quit to close it. There is no error message. Just a frozen screen as per the image sent earlier.

https://1drv.ms/u/s!AoM1UrOaoKUMkZlX2FC ... g?e=qJOFoF

Hi, I've analyzed your logs, but the logs didn't give me enough info why the issue is happening for you. And I also haven't been able to replicate the issue.
I added more debug masseges though for the next build, so please generate a new debug log once the new build is available.

Thanks!

Hi

I'm casting to Chromecast Audio. The debug is here: https://1drv.ms/u/s!AoM1UrOaoKUMkZIepeO ... w?e=u5mtlI

And a second one here in case that shows anything different: https://1drv.ms/u/s!AoM1UrOaoKUMkZIiVsv ... Q?e=6bMDUb

I can't reproduce on 2264, it casts without issue here. What exact device are you casting to? Also capture you casting experience in a debug log (step 4b) and attach it to a Support Ticket: https://www.mediamonkey.com/forum/viewt ... 30&t=86643

Connection is stable. Everything else can cast without issue. This wasn't an issue until about two MM5 releases back. It is definitely an issue with new releases of MM