Chromecast Audio

[Davo]

Chromecast audio doesn't appear as a streaming option. Works ok with chrome & other apps

[Ludek]

Hi, I've tested and implemented support for "Chromecast 2" device, I haven't tested on "Chromecast audio" yet, but if there is an issue then I guess I should buy one

Could you please just ensure that the issue is still valid also with the newest build 2089 ?

EDIT: Before I buy one, could you please download this UPnP.dll : https://www.dropbox.com/s/0h844eagmlj9bl5/UPnP.dll?dl=0
and replace it over your current UPnP.dll in the MM5 install folder (build 2089) and generate debug log (item 4b here http://forum.mediamonkey.com/viewtopic.php?f=30&t=86643 ) ?? You can upload the debug log to a free file hosting service (Box, DropBox, RapidShare, FileDropper,...) and share just the link to the file here?

I just want to see whether there isn't a very easy fix for this (without a need for buying another Chromecast device).

Thank you!

[Davo]

https://www.dropbox.com/s/xfbray2nu3ru3 ... C.LOG?dl=0

Installed new dll - The PC Chromecast now appears on the MM5 streaming list but still no Chromecast Audio
Hope this helps.

[Ludek]

Thank you for the log!

I see, there are actually two devices detected on port 8008:

"Bedroom1" @ http://192.168.0.4:8008/ - I guess this is your Chromecast audio?
"chromecast [DAVID-PC] (OpenHome)" @ http://192.168.0.6:8008/

Could you please share content of these two links:
http://192.168.0.4:8008/ssdp/device-desc.xml
http://192.168.0.6:8008/ssdp/device-desc.xml
to compare? These are XML descriptors of the devices.

Feel free to open eSupport ticket to solve this privately (if you are not willing sharing this kind of info here).

Thank you!

EDIT:
Later in the log I see that these three devices were detected as renderers (including Bedroom1):

Bedroom1, Renderer UUID: 2fe4e257-2513-52af-9543-067752cd98c5
chromecast [DAVID-PC], Renderer UUID: 2a31c690-fdab-1de8-2c1c-be2ba7a8e37c
TV Room, Renderer UUID: 2f356227-f833-4d24-23bb-30d09f5f8e97

Are you really sure that the "Bedroom1" isn't in the list? Isn't it just a device name mismatch? i.e. maybe you have just expected another name than "Bedroom1" for the Chromecast device?

[Davo]

I have 2 Chromecasts for TV's named as you saw & a Chromecast Audio for hifi unit (named - Living Room speakers) this is the one i can't see
Not sure what you mean by "sharing" those xml's ? Sorry, but my technical knowledge is fairly limited

[Ludek]

I have 2 Chromecasts for TV's named as you saw & a Chromecast Audio for hifi unit (named - Living Room speakers) this is the one i can't see

OK, so neither of the Chromecast devices (TV Room - 192.168.0.6:8008, Bedroom1 - 192.168.0.4:8008) is the Chromecast audio device, right? So you have actually three Chromecast devices in total? I don't see a device name called "Living room speakers" or any "Living room" variant in the log, the device doesn't seem to be announced at all. Couldn't the device be part of another subnet? I guess you don't know IP and port of the device? Could you verify that it is logged into the same wireless network?

Not sure what you mean by "sharing" those xml's ? Sorry, but my technical knowledge is fairly limited

I meant just clicking those links in the browser to watch the XML content like this:
https://www.dropbox.com/s/ketkx937ifu4v ... 8.png?dl=0

[Davo]

It's running on the same wireless network
IP Address: 192.168.0.14
It shows up as a device on the Chrome browser casting & and other apps eg PLEX recognise it & stream ok to it

[Ludek]

OK,
If you put http://192.168.0.14:8008/ssdp/device-desc.xml into the adress bar of Chrome browser does it show the XML like in case of the others Chromecast devices (0.4, 0.6) ? If yes, what is the content?

Thanks!

[Davo]

Your search - http://192.168.0.14:8008/ssdp/device-desc.xml - did not match any documents.

[Ludek]

Your search - http://192.168.0.14:8008/ssdp/device-desc.xml - did not match any documents.

ok, thanks. It looks that Chromecast audio probably doesn't support SSDP discovery att all and we might need to switch to mDNS protocol, to be fixed as http://www.ventismedia.com/mantis/view.php?id=14645

Currently workaround for you is to locate your MM install folder/Portable/persistent.json file and edit section LAST_REMOTE_PLAYERS and add an entry for the device manually like this:

Code: Select all

    "LAST_REMOTE_PLAYERS": [
        {
            "udn": "6148f373-bfee-b1fe-2780-7ab564e338ad",
            "name": "Living room speakers",
            "ip": "http://192.168.0.14:8008/"
        }
    ],

then start MM5 and you should finally see the device in the list.

[Ludek]

Hi, I am just implementing the mDNS discovery method. Could you please do some tests for me to ensure that the Chromecast audio device works the same way as the others Chromecast devices?

1) Put this link to address bar: http://192.168.0.14:8008/setup/eureka_i ... ons=detail
Does it show the device description?

2) Run Windows command line (press WinKey and write 'cmd') and put following to the command line:
dns-sd -B _googlecast._tcp
Copy (or screencast) the command line output

Thanks!

[Davo]

1.The device name shows up when i put the link in address bar.
"54:60:09:C4:48:D4","name":"Living Room Speaker","noise_level":-96,"opt_in":

2. cmd output

Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\User>dns-sd -B _googlecast._tcp
'dns-sd' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\User>

[Ludek]

1.The device name shows up when i put the link in address bar.
"54:60:09:C4:48:D4","name":"Living Room Speaker","noise_level":-96,"opt_in":

Thanks, that's the expected content that I use for getting the name and ip, I suppose that it contains also "ip_address" , right?

C:\Users\User>dns-sd -B _googlecast._tcp
'dns-sd' is not recognized as an internal or external command,
operable program or batch file.

Thanks, my fault, I've just found that 'dns-sd' is part of Apple's Bonjour (that must be installed). I will need to find an alternative (as I used it in my solution for mDNS discovery).

[Davo]

Yes, all the device details are there including IP address

[Ludek]

Thank you,
mDNS discovery is implemented in build 2090, it should resolve your issue, so please test how it works in 2090 (once the build is available) and report back.

Thanks!