I'm just thinking around here, but I wouldn't be surprised that some other users could see a use in having multiple DB's for MM. This would probably come in even handier when considering video files.
Here are some reasons why:
- Local DB & Network DB (A user could connect to a networked DB whenever on a network, allows for switching networks and using different song DB's. The local DB would come in handy when disconnected from any network.)
- Adult DB & Child DB (A user could have a DB with adult content for himself and a Child DB for childeren stuff.)
In the ideal system there would be an item in options for this.
* First an option enabling/disabling this.
* Than a list of DB's that are available (added by user).
* Than an option to start MM with Option Box to select which DB to use or auto start with main DB (needs to be selected in step 2).
I would be nice to also have the possibilty of password protecting the individual DB's (I don't need it myself) or make them read only without password.
It would be nice to be able to show multiple (maybe just 2) DB's. The reason being that a user has a local DB and connects to a network DB. The user doesn't want to populate (time adding and non-availabilty when disconnected) his local DB, but still have it available when using networked DB.
It would also be nice to be able to synchronize between DB's. In case a file is in multiple DB's it would be nice to have the attributes show up the same in all. (In this case I'm mostly thinking about attributes only stored in MM DB (volume levelling) and not in file tags.
I would like to invite everyone to post their thoughts about using multiple DB's and if they need them, why so?
Multiple DB's
Moderator: Gurus
Multiple DB's
Last edited by Lowlander on Wed Oct 01, 2003 6:23 pm, edited 1 time in total.
Current MM
This whole story does raise another issue, the way non-available files are displayed. I would like to see another tree item added that's called currently not available files. And an option in the Library options to show non-available files or not in rest of library.
I understand that the dead links would be the same and that works too, but my question is if songs become available that the dead links are automatically updated to reflect the songs being available again?
These thoughts all have to do with networking and song management. On a network songs come on- and off-line as users come and go. I would like that MM and the DB reflect this in a decent way without user interference and without taking to much time. Here the File Monitor might come in handy, but I don't know how long this all would take considering thousands (or more) songs getting connected and disconnected to and from the network.
I hope this can be answered.
I understand that the dead links would be the same and that works too, but my question is if songs become available that the dead links are automatically updated to reflect the songs being available again?
These thoughts all have to do with networking and song management. On a network songs come on- and off-line as users come and go. I would like that MM and the DB reflect this in a decent way without user interference and without taking to much time. Here the File Monitor might come in handy, but I don't know how long this all would take considering thousands (or more) songs getting connected and disconnected to and from the network.
I hope this can be answered.
Hi all,
several people (including me) have expressed their wish for multiple DB support. I don't even need the fancy stuff you're talking about - after all if I want to merge the databases, why have them separate in the first place?
My reason for multiple database support is that I have different requirements for different collections: I have
- pop and jazz music where the standard artist/album/track scheme is okay
- classical music where I'd have composer/piece/artist
- audio books and plays where I'd have author/title/director
or something of the kind. Obviously, I wouldn't want to merge these - I'd be quite happy if I could just open them from a "File" menu without having to mess with any .ini files.
Cheers, Susanne
several people (including me) have expressed their wish for multiple DB support. I don't even need the fancy stuff you're talking about - after all if I want to merge the databases, why have them separate in the first place?
My reason for multiple database support is that I have different requirements for different collections: I have
- pop and jazz music where the standard artist/album/track scheme is okay
- classical music where I'd have composer/piece/artist
- audio books and plays where I'd have author/title/director
or something of the kind. Obviously, I wouldn't want to merge these - I'd be quite happy if I could just open them from a "File" menu without having to mess with any .ini files.
Cheers, Susanne
Merging
In this case I'm just talking about the possibility of program level merging. The DB's would remain seperate DB's, but in the program you can select multiple and they would be displayed as one. Maybe another location tab by DB could be useful.