radiodungog said:Dave,
Is your station going to be an Internet streaming station ?
Our community station transmits in the FM band on "Top of the Dial" 107.9
Night ... Jamie C.
radiodungog said:This is where the "Comment" field tagging will help us - and Playlist Generator Pro will give us sone additional smarts to make it even better. Perhaps even something like this - but done entirely from filtering tags for the end result:
2 easy listening songs from chart 1960 - 1990
1 Australian song from chart from any date
1 Country Music song from chart from any date
1 station ID
... repeat ...
As they say "It's all about the music" ...
Jamie C.
Even without this stuff, Playlist Generator Pro produces steady amount of support requestsdave-t said:If you want to go to the 'N'th degree RB would have to have full SQL type query facilities such as < = > than, AND/OR etc.
First version of API (in RB 4.9) will be about getting info from RB (event list, library, playback state, ...) and little playback control: start/stop, add/remove track and so on.dave-t said:One thing we have not considered here is the possible introduction of an API which, in theory, will allow a clever person to take information from a database or online resource and pass it to RB - now THAT would be a powerful tool![]()
We have similar system for TV here: Like/Dislike a program; programs on demand. But I've never used those features... Probably others doradiodungog said:That API idea is a good idea and mobile phone apps and ipad apps would be better if they had a lister feedback mechanism like:
1. A button to like or dislike the current song
2. A small list of half a dozen suggested songs where the listener could select one as their preference
Yes, there's a command to insert a song.nelson c said:for us, for now, would be enough to create a command is sent in the direction of a song to insert radioboss and this the act after the song (Example: radiobos.exe to "c :/ ... mp3")
The current solution only to insert a track or list at startup.
djsoft said:Even without this stuff, Playlist Generator Pro produces steady amount of support requestsdave-t said:If you want to go to the 'N'th degree RB would have to have full SQL type query facilities such as < = > than, AND/OR etc.Adding scripting language of any sort is a can of worms - it will multiple support requests 10 times... Well, I think this can be added as an "Advanced" feature in the future for those who know what they're doing.
Currently there's Year filter like this, when you set From and To fields, actually it works as "Year <= 2000 and Year >= 1990".
I think we just add more filters like this for BPM and other fields.
First version of API (in RB 4.9) will be about getting info from RB (event list, library, playback state, ...) and little playback control: start/stop, add/remove track and so on.dave-t said:One thing we have not considered here is the possible introduction of an API which, in theory, will allow a clever person to take information from a database or online resource and pass it to RB - now THAT would be a powerful tool![]()
Allowing 3rd parties to remotely edit library is a dangerous thing IMO.