if you have a special setup -like if you want to keep the database on a removeable disk along with all your music- there are already means on all OS to link it manually, as well as the entire Mixxx settings folder, with custom mappings etc.
This is my use case and I don't see how this can be done easily on Windows.
I also saw warnings about old Mixxx config files when upgrading to a new version.
Separating the database from the other configuration could help to improve the situation.
A use case is using a drive with the database in another computer with another controller or Mixxx version.
Each Mixxx installation should have its own configuration but use the same database.
The database should be something more permanent but exchangable.
Thanks for the info.
Yes, it is also useful to switch between different profiles.
However, I find it even more basic to switch between different databases.
I don't even know, if Windows profiles are compatible with a Linux profile.
So I think the database should be portable, so that it can be used with any other Mixxx computer without changing its settings.
And a user should always be able to know where his database is located, check how big it is, delete, copy, backup, and restore it without worrying about his other settings.
One database should be usable with different settings (or user profiles).
What's the use case yo need this for?
if you have a special setup -like if you want to keep the database on a removeable disk along with all your music- there are already means on all OS to link it manually, as well as the entire Mixxx settings folder, with custom mappings etc.