Save "related artists" in the database

Hello, would it be possible to add a function so that related artists entered in playlist generator pro can be shared across multiple instances?
We use this function and currently have to synchronize the artists for each instance manually, although they remain the same.
 
Hello, would it be possible to add a function so that related artists entered in playlist generator pro can be shared across multiple instances?
We use this function and currently have to synchronize the artists for each instance manually, although they remain the same.
We can add export/import feature to allow moving the list between the instances. What do you think?
 
Is there some way you can make the playcount be stored in the dedicated SQLite database and all other things in the shared one?
Because the "Use the Last Played Tag" function in Playlist Generator Pro is a really good idea, but doesn't quite work with multiple stations.
 
Is there some way you can make the playcount be stored in the dedicated SQLite database and all other things in the shared one?
Because the "Use the Last Played Tag" function in Playlist Generator Pro is a really good idea, but doesn't quite work with multiple stations.
Currently not, it only uses one database. Using multiple database at the same time is calling for problems.
 
Is there any other way to realize this?
I don't think so, and I'm also not sure what's the point? RadioBOSS uses all this information for building playlists and tracks selection. Reading from different databases will make the process much slower and complicated.
 
I currently have the problem that songs are not played on one station because they have already been played on another. So I can avoid this only by disabling the function?
 
I currently have the problem that songs are not played on one station because they have already been played on another. So I can avoid this only by disabling the function?
In this case, you should use dedicated databases for each instance.
 
Back
Top