I am setting up multiroom audio. After looking at many MPD front ends I decided on Rompr. I'm glad you have been constantly improving it. It's still my favorite after all these years. My setup involves setting up Rompr in different folders named after each room in the house. I also named the database after each room so I could keep track of what is played in each room. Is there any way to make one master database while maintaining individual databases for each instance?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No.
You can have :
One Rompr - One Database - Multiple Players
Multiple Rompr - One Database - Multiple Players
Multiple Rompr - Multiple Databases - Multiple Players
but not Multiple Database AND One Database combined. That would require every database action to be performed twice by rompr, and that's not really something I'm going to do :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It has occurred to me that the difficulty of doing it depends very much on what you want the Master database to do. If you just want something that keeps a record of total playcounts across all the rooms then all you need to do is to do the 'increment' action (in userRatings.php) twice - once for each database. There is no need for the Master database to keep the full collection in it, as Hidden tracks will be created when a playcount is added to it. Similarly, Tags and Ratings will also be added on the fly if you want it to store those too. This comes as a side-effect of my support for adding Spotify tracks (via Mopidy) on the fly.
If you actually want it to keep a master copy of the entire collection then you're going to have to do the entire collection update twice, AND prevent two backends trying to update it simultaneously. The collection update code is quite heavily optimised for speed and memory usage and is... fragile :) I'd prefer not to mess with it, but I really don't think it's necessary.
Whether I decide to include any changes you do in releases depends on a number of things but yes in principle I think it's an interesting setup to have separate databases for each room in the house and if I had it I too would want a Master record of playcounts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the info. What I wanted is a master record of playcounts. I'm thinking I'll need to add a master database option so all instances would be aware and something like a master top 40 display. If all goes well I can start working on it next week.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I am setting up multiroom audio. After looking at many MPD front ends I decided on Rompr. I'm glad you have been constantly improving it. It's still my favorite after all these years. My setup involves setting up Rompr in different folders named after each room in the house. I also named the database after each room so I could keep track of what is played in each room. Is there any way to make one master database while maintaining individual databases for each instance?
No.
You can have :
One Rompr - One Database - Multiple Players
Multiple Rompr - One Database - Multiple Players
Multiple Rompr - Multiple Databases - Multiple Players
but not Multiple Database AND One Database combined. That would require every database action to be performed twice by rompr, and that's not really something I'm going to do :)
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
If I come up with the code is it something you would be interested in?
I'm always interested. :)
It has occurred to me that the difficulty of doing it depends very much on what you want the Master database to do. If you just want something that keeps a record of total playcounts across all the rooms then all you need to do is to do the 'increment' action (in userRatings.php) twice - once for each database. There is no need for the Master database to keep the full collection in it, as Hidden tracks will be created when a playcount is added to it. Similarly, Tags and Ratings will also be added on the fly if you want it to store those too. This comes as a side-effect of my support for adding Spotify tracks (via Mopidy) on the fly.
If you actually want it to keep a master copy of the entire collection then you're going to have to do the entire collection update twice, AND prevent two backends trying to update it simultaneously. The collection update code is quite heavily optimised for speed and memory usage and is... fragile :) I'd prefer not to mess with it, but I really don't think it's necessary.
Whether I decide to include any changes you do in releases depends on a number of things but yes in principle I think it's an interesting setup to have separate databases for each room in the house and if I had it I too would want a Master record of playcounts.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thanks for the info. What I wanted is a master record of playcounts. I'm thinking I'll need to add a master database option so all instances would be aware and something like a master top 40 display. If all goes well I can start working on it next week.