Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Posted: Thu Aug 25, 2022 1:46 am
This is now working as I would expect in MMW 5.0.4.2660 Beta.
THX for update.
Happy Monkeying!
MediaMonkey forum
The Music Manager for Serious Collectors
https://www.mediamonkey.com/forum/
MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Page 2 of 2
Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Posted: Fri Aug 26, 2022 4:52 pm
Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Posted: 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?
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?
Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Posted: Tue Aug 30, 2022 6:37 pm
Certain user settings are not removed on uninstall: https://www.mediamonkey.com/support/kno ... diamonkey/
Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Posted: 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.
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.
Re: MMW5 - Individual speakers from a Google Cast Pair should not be shown as cast targets
Posted: 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?
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?