You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm imagining text files with the correct metadata for tracks that need to be marked (most likely by album/artist). Johnny-six then checks if a song matches those fields before marking as new/rotation. This would allow automation to help chart songs, especially useful for summer.
The text was updated successfully, but these errors were encountered:
there's 2 sides to this: we shoud have a way for johnny-six to prioritise rotation tracks; we could do this with e.g. azuracast's scheduling features, by adding a higher-priority queue that is played ever 5 tracks or whatever during "new music" hours and ever 10 tracks otherwise, and we need a way to log these as new/rotation tracks for charting purposes.
If we implement all of it in johnny-six and create an interface for selecting those tracks, the MD (or IT staff or whomever is responsible) need only update info in one location
The johnny-six component that will be needed here will be to extract the metadata and send it to Trackman. Trackman will need to accept the metadata. Then, of course, pload or whatever is being used for input will need to provide this metadata.
I'm imagining text files with the correct metadata for tracks that need to be marked (most likely by album/artist). Johnny-six then checks if a song matches those fields before marking as new/rotation. This would allow automation to help chart songs, especially useful for summer.
The text was updated successfully, but these errors were encountered: