My name is Neskie Manuel. I operate a small community radio station in BC. Originally I used a Mac computer with iTunes as the playout system. The music was selected hourly by an AppleScript that was called by cron everyhour. Really simple, but it worked.
These past two years we have an Ubuntu machine, that uses Rhythmbox as the playout system, with a similar script written a a Rhythmbox Plugin [1]. Instead of using a cronjob, the scripts uses a gobject timeout. The format that I read is a JSON, file that is read from our website [2], which is written in Django.
Reading Paul Baranowski's blog post on the Django software stack is interesting, to me since I'm already working in this area. I don't have the code up for the site yet, but will soon, put it up on github.
Another interest in this project is seeing a tight integration, but loose coupling, where different components could be swapped out. I really like how the Django database support works, since it can work on sqlite, mysql, or postgres. If campcaster treats the playout system in the sameway that would be ideal.
Posts: 389Member, Administrator, Sourcefabric Team
Hi Neskie --
Please let us know when you post the code. We definitely want to design it
to have pluggable playout systems, as well as pluggable storage engines for
the files. Thanks for the ideas and I hope we can work together in the
future.
- Paul
> Weytk (Hello),
>
> My name is Neskie Manuel. I operate a small community radio station in BC.
> Originally I used a Mac computer with iTunes as the playout system. The
> music was selected hourly by an AppleScript that was called by cron
> everyhour. Really simple, but it worked.
>
> These past two years we have an Ubuntu machine, that uses Rhythmbox as the
> playout system, with a similar script written a a Rhythmbox Plugin [1].
> Instead of using a cronjob, the scripts uses a gobject timeout. The format
> that I read is a JSON, file that is read from our website [2], which is
> written in Django.
>
> Reading Paul Baranowski's blog post on the Django software stack is
> interesting, to me since I'm already working in this area. I don't have the
> code up for the site yet, but will soon, put it up on github.
>
> Another interest in this project is seeing a tight integration, but loose
> coupling, where different components could be swapped out. I really like how
> the Django database support works, since it can work on sqlite, mysql, or
> postgres. If campcaster treats the playout system in the sameway that would
> be ideal.
>
> Cheers
>
> [1] - http://github.com/neskie/rb-schedule
> [2] - http://secwepemcradio.ath.cx/show/schedule/json/
>
I'm looking into the possibility of using Mixxx as a live playout
interface for music tracks and jingles, with JACK combining the output
of Mixxx and a software microphone mixer into one output for JAMin
post-processing, before going on to the transmitter.