Hmm, maybe that didn't fix it after all. Just ran latest update and it happens again on 1st launch. Will just ignore it from now as it's fine if I quit and then relaunch again but strange that it keeps coming back only on the first launch after an update:
I followed your steps and all seems OK on launch so I've renamed persistent.json.old back to its original filename and tried installing the latest install again on top.
It seems to me this step has reinstalled the problem for next time.
How many settings would you have to redo, if you actually kept the replacment persistent.json and just tried to re-create what you have from scratch?
It seems to me your issue might be buried in your settings file someplace, and the only way to get rid of it permanently is to lose that.
Using V2024 LATEST alpha or beta build on Windows 11, HP laptop, managing 13k tracks
Rob_S wrote: ↑Sat Jul 06, 2024 12:34 pm
It seems to me your issue might be buried in your settings file someplace, and the only way to get rid of it permanently is to lose that.
I did wonder if there's something it doesn't like in my settings file. If I can be bothered at some point I might reset it to default and try to recreate it step by step to how I have it now. I guess if I keep a backup of my json file I can always look through it to see what changes I made.
Can you share your .json file. I wonder if i could find the cullprint of the issue by validating the json file, or compairing it to my file or the default file.
I am using MediaMonkey on my Retro Systems, using the latest Beta build on Windows 11. Managing ~54k files
tbm72, reading through this thread, it sounds as if the issue is specific to your .json file and that it doesn't occur if you delete it.
If that's the case (and considering that bugs #20946 and #21054 are already tagged as fixed), and given that it isn't occurring for anyone else, would it make sense to:
- send the file to our helpdesk so that we can have a look and try to replicate / open a new bug
- workaround the problem by renaming the .json file so that MM recreates a clean one that doesn't have the problem (you'll have to recreate some UI settings)
rusty wrote: ↑Fri Jul 12, 2024 9:38 am
tbm72, reading through this thread, it sounds as if the issue is specific to your .json file and that it doesn't occur if you delete it.
If that's the case (and considering that bugs #20946 and #21054 are already tagged as fixed), and given that it isn't occurring for anyone else, would it make sense to:
- send the file to our helpdesk so that we can have a look and try to replicate / open a new bug
- workaround the problem by renaming the .json file so that MM recreates a clean one that doesn't have the problem (you'll have to recreate some UI settings)
Thanks!
-Rusty
Thanks Rusty, yes it's not a big deal so I'll either just leave it alone and put up with the bug after each update or reset the .json file and try to recreate the settings I have. Just to clarify, does the persistent.json file simply hold UI/layout preferences or is there anything else in it? I'll keep a backup of it in case.
Well I just deleted my json file so it reset itself, changed skin to default (just to make sure it's not my slightly modified skin) and restarted MM. Then ran the latest installer again but it still happens on first run through. I think I'll just live with it!
Looks like it also happens when changing skins (again only on first runthrough after switching skin - if I quit and restart MM then it doesn't happen again until next change of skin or update of MM).
Just to clarify, does the persistent.json file simply hold UI/layout preferences or is there anything else in it?
It's mainly UI settings, but it also includes other transient elements such as search and fmfs history.
Well I just deleted my json file so it reset itself, changed skin to default (just to make sure it's not my slightly modified skin) and restarted MM. Then ran the latest installer again but it still happens on first run through.
So that rules out a problem with your UI settings. Can you try a clean portable install (i.e. portable install to a temp directory, and don't import data/settings from your existing installation) and see if it still occurs with that? If it does, then it likely means that the issue is specific to your OS/hardware.
Thanks Rusty. Well I just tried a fresh portable install to a different folder (C:\MediaMonkeyTEMP) and that was fine. And just to make sure, I ran the installer a 2nd time but still pointing towards the same temp folder. Couldn't get it to replicate there.
But if I run the same installer on top of my main (existing) portable install (C:\MediaMonkey) then the bug always happens on the first run but goes away on subsequent launches. Very strange. Anyway it's not really a big issue as it only happens first time after updating so I can live with it.