MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

by **PeterHatoz** » Wed Aug 31, 2022 10:01 pm

OK, I uninstalled MMW5 once more, and removed all MM-related entries from the registry (there were a lot left there).

After I reinstalled MediaMonkey_5.0.4.2661_Debug (normal install), I searched in my AppData\Roaming\MediaMonkey5 directory and found references to the individual speaker names of the pair (like "Kitchen R") in the following files ...

persistent.json.bck
persistent.json
MM5.DB

So, it looks like it's not a Windows problem

I understand that these setting files are useful/required when doing an upgrade, but if the product is completely uninstalled, then they should all be removed ... no?

by **Peke** » Tue Aug 30, 2022 6:45 pm

Hi,
I suspect more to Windows VitualStore that can trigger some times and sometimes it decided MM should load normal settings

but again I wish I am wrong and there si a bug in MM caching of Chromecast clients.

At least one thing is certain Portable worked

If issue returns please let us know ASAP so that we can investigate fix.

by **Lowlander** » Tue Aug 30, 2022 6:37 pm

Certain user settings are not removed on uninstall: https://www.mediamonkey.com/support/kno ... diamonkey/

by **PeterHatoz** » Tue Aug 30, 2022 6:24 pm

Sorry, I've misled you by not testing thoroughly enough.

I've just done a normal install of MediaMonkey_5.0.4.2661_Debug and found that the fix had regressed!

When it "worked correctly", I was testing using a portable installation of MediaMonkey_5.0.4.2659_Debug (pretty sure).

So, I've now tried a portable install of MediaMonkey_5.0.4.2661_Debug and it was fixed again.

I then did a complete uninstall of MediaMonkey_5.0.4.2661_Debug (directory and shortcut were removed), and installed it again normally ... again, the problem was there. However, the portable installation continued to give the correct list of cast targets.

I noted that, following the complete uninstall then reinstall of MediaMonkey_5.0.4.2661_Debug, MMW remembered my volume setting, license details, folder settings etc. so maybe something is being left in the registry which is causing this problem?

by **Peke** » Fri Aug 26, 2022 4:52 pm

THX for update.

Happy Monkeying!

by **PeterHatoz** » Thu Aug 25, 2022 1:46 am

This is now working as I would expect in MMW 5.0.4.2660 Beta.

by **Peke** » Thu Jul 28, 2022 3:26 pm

Hi,
It is much better than we could do ATM, no one have stable setup of two same speakers supporting pairing

by **PeterHatoz** » Thu Jul 28, 2022 2:16 am

Peke wrote: ↑Mon Jul 25, 2022 5:46 pm After you have both logs please open support ticket and attach the compressed (ZIP/RAR/7z) logs. Thanks.

OK, Ticket #4588 opened.

As I mentioned in the ticket description, in MMW when preparing the "Speakers paired.log", the "Kitchen Pair" cast target did not appear the first two times that I tried. This is a common occurrence ... I normally have to try two or three times before the Pair appears. Or sometimes, one of the individual speakers is not listed, or other times the only thing in the list is "Internal Player". Maybe the scan timeout needs to be longer? This behaviour is not unique to MMW, but it is definitely much worse in MMW than in other apps.

Also, unpairing the speakers is not a simple thing. I was able to break the pair apart OK, but I had to factory reset "Kitchen L" before Google Home would recognise it again. Once I'd gone through the setup procedure for that speaker to add it to my Home again, I then had to rename it from "Kitchen Speaker" to "Kitchen L". Hopefully, this doesn't complicate the debugging for you.

by **Peke** » Mon Jul 25, 2022 5:46 pm

Hi,
Unfortunately I need to return speakers to owner (they were on repair with my friend and I loaned them for testing and setup for a friends client), so I don't have two same type speakers to be able to test them in a pair according to https://support.google.com/chromecast/a ... oid#zippy=

In order to make this faster can you please do this tests and create debug logs for us using latest MM5 Beta:
1) Pair the speakers
2) Start DbgView
3) Start MM5 and click the Cast icon on the player to list all speakers
4) Close MM
5) In DbgView use file -> save log as "Speakers paired.log"
6) Close DbgView

For second log:
1) Unpair the speakers
2) Start DbgView
3) Start MM5 and click the Cast icon on the player to list all speakers
4) Close MM
5) In DbgView use file -> save log as "Speakers unpaired.log"
6) Close DbgView

After you have both logs please open support ticket and attach the compressed (ZIP/RAR/7z) logs. Thanks.

by **PeterHatoz** » Sun Jul 24, 2022 4:31 pm

Great. Thanks for the quick response and for all the work that you and the team have done on this great product over the years. I've been a happy user since the beginning.

by **Peke** » Sun Jul 24, 2022 7:41 am

Hi,

PeterHatoz wrote: ↑Sat Jul 23, 2022 7:56 pm So ... Windows apps that support casting are a bit thin on the ground, however I found these:

I agree and that is the main problem, small set of apps to handle Casting.

PeterHatoz wrote: ↑Sat Jul 23, 2022 7:56 pm VLC
Spotify
Chrome
Desktop Audio Streamer.
All of the above list only the name of the stereo pair in the list of targets (not the members of the pair).

Discussion is moot anyway, because I tried casting from MMW5 to the individual speakers of the pair (e.g. to Kitchen L) and it failed to connect. It would only connect to the stereo pair.

Thank you for that info I raised priority of a bug to be fixed in 5.0.4. You are right Paired speakers (Stereo) fail when you try to connect to individual one, but like you said groups are different and you can ping/play to individual player at least in my tests.

by **PeterHatoz** » Sat Jul 23, 2022 7:56 pm

Peke wrote: ↑Sat Jul 23, 2022 6:46 pm Hmmm, please exclude Android apps and please focus on Windows only app that support casting.

Cast to on Android is controlled by Android OS not by MMA. On Windows we handle this mostly internally in MM5. Briefly Looking thru sources MM5 do not check devices info in the groups.

Personally I like teh choice that I can send to Group and also send to Individual speakers eg. having House party group and also send to current room only without breaking up The group.

OK, the difference between the two platforms is noted.

And I'm not saying to suppress the listing of all groups ... only stereo pair groups. You would still have your House Party group as well as your individual rooms. The Google Home process for creating a stereo pair is different to the process for creating a "normal" speaker group .

So ... Windows apps that support casting are a bit thin on the ground, however I found these:

VLC
Spotify
Chrome
Desktop Audio Streamer.

All of the above list only the name of the stereo pair in the list of targets (not the members of the pair).

Discussion is moot anyway, because I tried casting from MMW5 to the individual speakers of the pair (e.g. to Kitchen L) and it failed to connect. It would only connect to the stereo pair.

by **Peke** » Sat Jul 23, 2022 7:01 pm

Anyway I added https://www.ventismedia.com/mantis/view.php?id=19278 for discussion of implementation.

by **Peke** » Sat Jul 23, 2022 6:46 pm

Hmmm, please exclude Android apps and please focus on Windows only app that support casting.

Cast to on Android is controlled by Android OS not by MMA. On Windows we handle this mostly internally in MM5. Briefly Looking thru sources MM5 do not check devices info in the groups.

Personally I like teh choice that I can send to Group and also send to Individual speakers eg. having House party group and also send to current room only without breaking up The group.

by **PeterHatoz** » Sat Jul 23, 2022 5:55 pm

PeterHatoz wrote: ↑Sat Jul 23, 2022 5:29 pm Other casting apps that I use only display the pair, not the members of the pair (I don't currently have a group defined, but will test that as well).

OK, I've done some testing.

On Android, Spotify and RocketPlayer and MMA (surprise!) only display the stereo pair name. LocalCast displays the pair name plus the individual speakers (I believe this is also a bug and will report it).

I created a multi-room group containing all of my speakers (the two in the kitchen, and the one in the bedroom). Note that Google Home did not let me choose the individual speakers in the kitchen when creating the group, only the names of the stereo pair and the bedroom speaker were available.

All the apps listed above as well as MMW5 were able to play to the group, and also listed the individual group members as cast targets.

MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Post a reply

Expand view Topic review: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets

Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets