Cast does not see Google Speakers but does see Chromecast (and Chrome sees all)

[Linwood]

I was running and older V5 version (not sure which as I rarely use MM on windows). I needed to cast, and could not find my google speakers (a bunch of individual mini's, a paired pair of Home, and a paired pair of Max).

I could find chromecast devices, mostly (two did not appear but they appeared as DLNA devices, so maybe MM filtered the duplication).

On a whim I downloaded the latest beta 2024 version and tried again - same result.

Before people ask: The PC is on the same network subnet, and same VLAN as the google speakers. They do not go through a router (only AP's to a switch). There is no igmp snooping or other special handling turned on. But more to the point:

On the same PC, both Edge and Chrome see all the devices. Only MM does not.

I am absolutely sure this worked in MM some time ago. I don't remember exactly when, but I THINK it was the same version that did not work last night (before I did the 2024 update).

Before I head down the rathole of debug versions and network sniffing.... it also occurs to me Google has been pushing out updates. So is anyone else having issues casting to google home speakers? All mine are the older, original versions.

But again -- edge and chrome on the same PC where MM is running work fine.

Linwood

[Lowlander]

Can you please confirm the build number of MediaMonkey (Help > About) you're using?

[Linwood]

I can't tell you which one stopped working last night, unless it's stored somewhere, but the current one that fails is 2024.2.0.3175 installed portable and license NOT activated (that's a different problem I've written in about, lifetime license would not activate).

I don't think cast is affected by license though, right?

Here's an example, the first is the browser showing cast (more than will fit in the window but you can see both groups and individual google speakers), followed by what MM shows. This is on the same PC at approximately the same time (just a mouse click different).

The Living Room Speaker and Office TV are devices that do both DLNA and also Cast, but for reasons a bit unclear don't show the cast. The ones that say "Cast" are actual original Chromecast devices (well, one is an Ultra I think).

I realize it's a different implementation but Media Monkey on android shows all the devices.

[Lowlander]

Please capture the launch, several minutes of idle sitting and then attempt to open cast devices list a few times in the a debug log (step 4b) and attach the log to a a Support Ticket: https://mediamonkey.com/forum/viewtopic.php?t=86643

This will help a developer analyze why this happens on your setup.

[Peke]

Hi,

I can't tell you which one stopped working last night, unless it's stored somewhere, but the current one that fails is 2024.2.0.3175 installed portable and license NOT activated (that's a different problem I've written in about, lifetime license would not activate).

I don't think cast is affected by license though, right?

Casting for free versions is limited to 30 Min.

Please write support ticket and follow MM 2024.2.0.3175 license retrieval and we will try to help.

[Linwood]

Casting for free versions is limited to 30 Min.

Please write support ticket and follow MM 2024.2.0.3175 license retrieval and we will try to help.
[/quote]

I have sent the email it automates for the license issue, but it sounds like the license is unrelated to this.

I need to do some more experimenting. I installed MM (same version) on a laptop which had never had it, and started it up (with no media) and just hit the cast button -- it shows all the mini speakers.

So it's specific to my desktop. So I rebooted the desktop and it worked.

So I have no idea what's happening, but I have a suspicion. I frequently have additional NIC's on my desktop active, for example as a HyperV guest NIC, or a wifi nic for checking AP connections or similar. Plus there are a couple of NIC's there which are disabled. I know years ago there were issues with MM and multiple NIC's and mDNS because MM (or some library it used) did not choose the right NIC. This happened to me when the NIC's were multi-homed, i.e. they had different real subnets connected. It would pick the wrong NIC (it picked the one for the subnet on which the devices were NOT).

But that was when they had multiple active NIC's. I do not have that now (except the dedicated hyperV guest NIC which is not available to windows itself). So it should not be that case. But... something threw it off.

At any rate, I can't debug a problem I do not have, and at present it is working, so let me experiment a bit more.

Thank you for the quick (and weekend!) response.

Linwood

[Peke]

Hi,
Sure, we are not going anywhere.

Even it is not related to License, it i snot fair that you do not have full Monkeying experience