More > JRiver Media Center 32 for Windows
NEW: Faster and More Thorough Upgrade
Matt:
--- Quote from: Curtis on June 03, 2024, 04:59:02 pm ---I recently upgraded from MC31 to MC32. The MC31 library was found and installed, however the MC31 program settings were not. I ended up manually changing options by matching Tools/Options screens with both programs loaded. After reading the above, would the preferred way to import the settings from MC31 be to (1) backup the newly installed MC32 installed during the upgrade; (2) restore that just-created backup over the just backed-up library AND with the settings checkbox selected? That is, there is no way for the upgrade to carry over the settings during the upgrade itself?
--- End quote ---
Settings should be moved as part of the upgrade. However you can do a library backup in MC31 and restore in MC32 and include the settings if something is missing.
Vocalpoint:
--- Quote from: Matt on June 04, 2024, 08:35:42 am ---Settings should be moved as part of the upgrade. However you can do a library backup in MC31 and restore in MC32 and include the settings if something is missing.
--- End quote ---
Matt
I think the gist of these last few posts is to indicate that while settings "should" be migrated - in some cases they are not. Meaning - there are issues still occurring during an upgrade.
I know if my experience (a few posts up) - there was no difference onscreen in moving the v32 than when I moved to v26. I still had to do ten minutes of monkeying around to get the new version to behave.
The way you guys phrased this enhancement made it sound like it was "more thorough" - but unfortunately - at least for me - it was not.
Maybe I am misunderstanding the meaning of "thorough" in this context.
VP
JimH:
Sorry VP, it's working for most people. You're probably doing something "special". Can you think what it might be? Maybe we've missed a case.
The old installation needs to be local, in case that's the problem.
Vocalpoint:
--- Quote from: JimH on June 04, 2024, 09:10:17 am --- Sorry VP, it's working for most people. You're probably doing something "special". Can you think what it might be? Maybe we've missed a case. The old installation needs to be local, in case that's the problem.
--- End quote ---
Jim
Nothing out of the ordinary that I can see.
The only thing I can think of is this specific "local" library has been "migrated" through at least 7-10 versions of MC - starting way back in the v23 era. Maybe that has something to do with it?
Could be that your most recent "upgrade" processes and designs work better on say a "new-ish" library that was populated within the last few interations of MC.
I would not expect your internal testing would be against MC library structures first loaded up in 2015
Is there way to create a new empty v32 library container and move an existing set of library data into it? I would be down to try that if it has any benefits.
VP
JimH:
None of the should matter. My own library goes back a very long way.
Skipping more than 4 or 5 versions might be a problem. 24 to 32, for example.
Could you try to reproduce it?
At least, try saving a backup, clearing your library and loading a backup from a previous version. Try more than one.
Anything security related could be a suspect. Privileges maybe. Windows tweaks.
This just isn't a common problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version