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?
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.
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.
I have seen that in the last update the hook was added to the API,
but unfortunately you get the following response for every track, no matter if the hook is set or not:
HookIn="-1" HookOut="-1"
As said, in our case (and certainly others as well) it really makes no difference if the path starts with C:/ or D:/, because these are two identical hard disks. So it makes no difference if other RadioBOSS instances on the same server access the database or on different ones...
You probably mean that: https://www.sqlite.org/howtocorrupt.html#_filesystems_with_broken_or_missing_lock_implementations
I already know this problem, therefore all our VM's have access to a hard disk instead of a network drive. So it makes no difference on which drive the database is located.
I'm talking about the position of an item in the playlist, not the position within an item.
So you can directly query with getplaylist2 which elements were played next and last without asking playbackinfo each time.
Exactly, I'm just missing a variable like %position, that's what I meant all along. I accidentally wrote "URL reports" and when I noticed that it was actually the title format variables, the 20 minutes had already expired.
This is of course understandable, I just found the idea quite good because you can already get all other important values via the title format variables.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.