More > JRiver Media Center 32 for Windows

Settings Missing When Upgrading from MC 28 to MC 31 [Solved]

<< < (3/4) > >>

lepa:
Backup saves settings automatically, it only asks if thumbnails will be also saved.

I think MC28 backs up the settings, so you should be fine. Just try to restore it. Restore will then ask if settings and such should be also restored from backup

E:

15.0.1 (03/04/2010)
1. NEW: When restoring a library backup, user settings can also be restored.

FenceFurniture:
So I restored into MC 31 the backup that I took out of MC 28, and so far it looks good (haven't checked everything yet). Thank you lepa for your assistance.

This begs again the question that I asked Jim earlier, but that went unanswered. "Why doesn't it do this automatically?"
I don't do my backups to where JRiver suggests, as I keep all my music stuff on a detachable SSD, which is also backed up to a separate detachable spinner drive, which is only ever attached during the backup process.

However, if the MC 31.exe was smart enough it would have looked for this, but it is still trying to go to its default position in "Documents". I also note that my choice of site for backups has always been the case for the last several years, which included at least the upgrade to MC 28, which went smoothly.

Furthermore, given that at least lepa and myself know that things do not always go according to plan with an upgrade, the instructions for doing an upgrade should say, in letters as big as you like:

"DO A LIBRARY BACKUP OF YOUR CURRENT MC VERSION BEFORE YOU INSTALL AN UPGRADE!
You should not rely only on the .exe doing a backup.
If your settings are not correct after the upgrade you may need to restore your backup into the new version"

That would have saved me quite a bit of anxiety and frustration, and also saved lepa and Jim the time to assist me through this. I was particularly anxious because I had never had such difficulties in previous upgrades.

FenceFurniture:
Just a footnote to that:
I have done a huge amount of programming etc in my MC a few years ago. It all works really well, but because it works so well, and was a few years ago, it all goes out of my head. I then just enjoy listening to tunes and doing other stuff. Reworking everything that has left my head is not at all pleasant, especially if it is unnecessary (I had spent some hours unnecessarily correcting stuff until I realised just how much was wrong, and put out the call for help).

Matt:
The install process should copy the existing loaded library from any copy of MC version 20 or newer to the new location.

This works for lots of users, so I'm not sure why it didn't work for you.

Was there some other library loaded in MC?

Thanks.

FenceFurniture:

--- Quote from: Matt on December 18, 2023, 07:57:52 am ---The install process should copy the existing loaded library from any copy of MC version 20 or newer to the new location.

Was there some other library loaded in MC?
--- End quote ---
No, I only have one Library. It's also set to "Audio Only". It copied, shall we say, a "half job" of the Library.
What was copied was:

* all of the expressions (numerous),
playlists (not too many),
Library views (about 30),
probably other stuff
* What was NOT copied was:

* Black on Black Skin,
the ten tabs across the top that I had assigned my most used Library Views to (along with the specific column widths),
DSP Studio (10-12 Equalisers, Para Eq, and all other settings I have changed,
Zones (4),
Action Window and topline buttons,
customised display (headline),
probably other stuff that I hadn't discovered missing before posting in here.
*
31 was also not aware that my backups had been set to a different location (drive & folder name). It was still using Documents ► JRiver, so I'm blessed if I know how it picked the few settings that it did. There was no interruption to the process – it ran under its own steam.

It turns out to be no big deal by doing a library backup of 28 and restore into 31, but my major point is that for those of us who "set and forget" (years ago in my case) a simple extra instruction (BU & Restore) inserted into the upgrade routine would have saved the situation from occurring.

Navigation

[0] Message Index

[#] Next page

[*] Previous page