by spaghettijim » Tue Feb 11, 2025 7:01 pm
Hey MediaMonkey,
I love the software, but there's always been issues for me with using Chromecast so I figured I'd chime in since it's ongoing. It has sometimes worked, but it's rare and like magic since I can't pinpoint the exact cause of failure. I've managed to find my own work-around in the past when it did happen by directly editing the persistent json, which I'll detail here in hopes it points to something. Each update I load up MM hoping it'll "just work" this time, but I just installed v2024.1.0.3106 and no luck. This time however, my workaround is no longer working either. I can't recall the exact version I last successfully did this, it could have been 4+ versions ago that I tried (including betas).
My workaround involved keeping an old copy of persistent.json from when I did get it to work. I navigate to the user folder and load up \AppData\Roaming\MediaMonkey5\persistent.json. I load my old copy and the current copy up in Notepad++ with the JSON Viewer plugin. Using the plugin I "format" them to read and edit more easily, and then "compress" again once finished before saving. With MediaMonkey closed, all I would do is copy over the LAST_REMOTE_PLAYERS array over and overwrite the empty array in the current copy and save. In the past it would take and start working next app boot, but now it simply wipes the array. Perhaps the data model changed, or the app now just overwrites with it's results and isn't finding any.
I believe if I completely wiped MM and reinstalled, it might work again for a bit. It has worked in the past after doing such drastic measures, and worked well. But it's always been short lived and inevitably gets stuck in this bad state where it simply can't do it again. Issue in my opinion lies in scanning or dealing with the scan results. I don't believe it occurs on fresh installation or initial scan, but rather scans after some usage, since that's been my experience.
Please let me know if I can help in any way, this bug has been an annoyance to me for years, and is the only thing I encounter continuously that's broken. Thanks!
Hey MediaMonkey,
I love the software, but there's always been issues for me with using Chromecast so I figured I'd chime in since it's ongoing. It has sometimes worked, but it's rare and like magic since I can't pinpoint the exact cause of failure. I've managed to find my own work-around in the past when it did happen by directly editing the persistent json, which I'll detail here in hopes it points to something. Each update I load up MM hoping it'll "just work" this time, but I just installed v2024.1.0.3106 and no luck. This time however, my workaround is no longer working either. I can't recall the exact version I last successfully did this, it could have been 4+ versions ago that I tried (including betas).
My workaround involved keeping an old copy of persistent.json from when I did get it to work. I navigate to the user folder and load up \AppData\Roaming\MediaMonkey5\persistent.json. I load my old copy and the current copy up in Notepad++ with the JSON Viewer plugin. Using the plugin I "format" them to read and edit more easily, and then "compress" again once finished before saving. With MediaMonkey closed, all I would do is copy over the LAST_REMOTE_PLAYERS array over and overwrite the empty array in the current copy and save. In the past it would take and start working next app boot, but now it simply wipes the array. Perhaps the data model changed, or the app now just overwrites with it's results and isn't finding any.
I believe if I completely wiped MM and reinstalled, it might work again for a bit. It has worked in the past after doing such drastic measures, and worked well. But it's always been short lived and inevitably gets stuck in this bad state where it simply can't do it again. Issue in my opinion lies in scanning or dealing with the scan results. I don't believe it occurs on fresh installation or initial scan, but rather scans after some usage, since that's been my experience.
Please let me know if I can help in any way, this bug has been an annoyance to me for years, and is the only thing I encounter continuously that's broken. Thanks!