by Barry4679 » Mon Dec 21, 2020 5:57 am
I am not from MM, but have some knowledge about these issues.
pderwael wrote: ↑Mon Dec 21, 2020 5:16 am
At first glance (after the shock caused by the new colors scheme is gone)
pderwael wrote: ↑Mon Dec 21, 2020 5:16 am
- 1) Functionality: DB migration
Over 20+ years, I have accumulated quite a large library where the date added is of crucial importance for me
I've let MM5 scan a subset of my lib and obviously, as date-added is set to today, I'm losing the initial information
Being no SQL-whatever DB freak, I'm unable to update the MM5 DB from the info stored in the MM4 DB
The obvious question is: will there be any form of DB migration foreseen in future released MM5 versions?
If you install a fresh copy of MM5 on a PC which has an installation of MM4, it will offer to import data and settings from MM4.
The same thing happens if you force MM5 to create a fresh database ... ie you delete the existing MM5.db file, and then start MM5.
If you say yes, this will retain your Date Added values.
If no, you will get an empty database, and when you (re)scan in your files you will Date Added = today.
pderwael wrote: ↑Mon Dec 21, 2020 5:16 am
- 2) Functionality: Multi-artists albums
It seems the AlbumArtist field is gone
This brings the next obvious question: how do we handle multi-artists albums (eg for thematic compilations)???
The AlbumArtist tag is still there ... except they hide it by default (for some inexplicable reason) when they create a fresh database.
Go to Tools|Options|Library|Collections&Views to toggle on visibility of this subnode for each of your collections.
Or its visibility will be retained if you import your settings from MM4.
pderwael wrote: ↑Mon Dec 21, 2020 5:16 am
- 3) DB size
I'm also worried about the DB size...
My current MM4 DB size is 1.76GB for 75000 albums and the MM5 DB size is 1.59GB for only 136 albums
Considering the 1/550 ratio, if I let MM5 scan the whole lib, I can expect the DB size to reach something like 880GB
Please tell me I'm making a simple calculation mistake...
You are making a calculation mistake
My MM4 & MM5 databases are of similar sizes.
I am not from MM, but have some knowledge about these issues.
[quote=pderwael post_id=475888 time=1608545801 user_id=21388]
At first glance (after the shock caused by the new colors scheme is gone)
[/quote]
:D
[quote=pderwael post_id=475888 time=1608545801 user_id=21388]
[list=][b]1) Functionality: DB migration[/b]
Over 20+ years, I have accumulated quite a large library where the date added is of crucial importance for me
I've let MM5 scan a subset of my lib and obviously, as date-added is set to today, I'm losing the initial information
Being no SQL-whatever DB freak, I'm unable to update the MM5 DB from the info stored in the MM4 DB
The obvious question is: will there be any form of DB migration foreseen in future released MM5 versions?[/list]
[/quote]
If you install a fresh copy of MM5 on a PC which has an installation of MM4, it will offer to import data and settings from MM4.
The same thing happens if you force MM5 to create a fresh database ... ie you delete the existing MM5.db file, and then start MM5.
If you say yes, this will retain your Date Added values.
If no, you will get an empty database, and when you (re)scan in your files you will Date Added = today.
[quote=pderwael post_id=475888 time=1608545801 user_id=21388]
[list][b]2) Functionality: Multi-artists albums[/b]
It seems the AlbumArtist field is gone
This brings the next obvious question: how do we handle multi-artists albums (eg for thematic compilations)???[/list]
[/quote]
The AlbumArtist tag is still there ... except they hide it by default (for some inexplicable reason) when they create a fresh database.
Go to Tools|Options|Library|Collections&Views to toggle on visibility of this subnode for each of your collections.
Or its visibility will be retained if you import your settings from MM4.
[quote=pderwael post_id=475888 time=1608545801 user_id=21388]
[list][b]3) DB size[/b]
I'm also worried about the DB size...
My current MM4 DB size is 1.76GB for 75000 albums and the MM5 DB size is 1.59GB for only 136 albums
Considering the 1/550 ratio, if I let MM5 scan the whole lib, I can expect the DB size to reach something like 880GB
[b]Please tell me I'm making a simple calculation mistake[/b]...[/list]
[/quote]
You are making a calculation mistake :D
My MM4 & MM5 databases are of similar sizes.