1) ability to manually start a playlist in case a live event goes over the scheduled time
2) the concept of scheduler codes for tracks that should only be played during certain time periods, or should expire after a certain date.
--manual start/live show - this might do what I am thinking. By live event, I mean just that, live analog audio. We will be using airtime as our automation system but we also have two full studios with turntables, cd players, Mixxx, etc. and we stream live remote content back to the studio using liquidsoap, and bring it into the mixing console through a studio PC. The goal is to have a playlist ready to go and then allow an on-air programmer to start it at the right time when a rigid clock is too inflexible.
Any thoughts on reading the 'LABEL' tag if set in an ogg/flac file on import?
I was running our sandbox on a deb-testing install. When I tried updating to 2.0.3 after applying other system updates the airtime package wouldn't finish installing. It was throwing an error during the post-install script that was python related. I didn't investigate to far, but think it is probably due to updating to python 2.7 and the virtualenv issue that is seen on ubuntu 12.04. I rolled our sandbox back to squeeze and installed 2.0.3.
It looks like you're new here. If you want to get involved, click one of these buttons!