I recently discovered Airtime after a year and a half of scripting liquidsoap by myself to get it to (sort of) do what I wanted. I'm really impressed with what's been done with this software so far, and I've already implemented it into our station's workflow for pre-recorded shows. That said, Airtime is still a young project, and there's a healthy list of things that it either doesn't do, or doesn't do well. What would be the best way to submit a list of feature requests? Should I do it here in the forum, or is there a better way?
Also - as a developer, I'd love to work on extending Airtime to get it to do what I want since I understand that the development team may not have the same priorities or preferences as I do. I looked around but was not able to locate any clear instructions on the best way to go about downloading the source, forking, and then eventually re-submitting the changes I've made. If somone could point me in the right direction on that I would appreciate it.
Thanks for the info on forking - I saw that page, just missed the bit at the bottom.
As far as the feature requests, I'll take some time later to look through the items listed in the roadmap on the dev page you linked to, but here's the short list (for now):
aac/m4a support
music library organization (folders and smart playlists and such)
Incoming live streams - preferably with the ability to fallback to a playlist in case of stream dropout
Recording of live streams (archiving) - with options for scheduled rebroadcast, upload of archives to a remote site via SFTP/FTP, and selectable bitrate for archive recording (we broadcast at 96k, but would prefer to record incoming live streams at 192k or better)
Granularity of soundcloud updates - being able to select on a show by sow basis
flexible shuffle/autodj/fallback - keyed off of metadata with ability to periodically insert station IDs, bumpers, advertising, etc.
advanced playlist metadata
full play counts - station logs - and the ability for live remote shows (or pre-recorded extended mixes) to submit detailed play logs for sets. (Required for royalty reporting in U.S.)
I could write a paragraph or two on each of these points, but this is a start.
Thanks for the feedback. I think a lot of our priorities do intersect, we are planning on smart playlists + rebraodcasting incoming streams + recording live streams in the future.
Been doing some training, playing and process flow stuff today.
Here's a feature request from one of our team members (I actually like this one so I'm passing it on! Usually this guy is a pain in the rump and has silly ideas!).
Make it possible for a user to upload his show tracks *and* a .pls file into his watched directory and have it picked up. The he/she just needs to go to the calendar and schedule it.
Brain dead simple, not sure about on your end though...
If you are using Icecast2 as your target, a little bit of scripting will get you an archived audio file that contains a single live show and is auto updated every time a show ends.
I have added the following to my live broadcast mount in icecast.xml:
Hi - like the idea of dumping the live feed to a file, would be good to have this since I'm running off a server which of course doesn't have a sound card...
But I tried to add the <dump-file> to say the showmount and it just cut off all streaming dead. Anyone have an example icecast.xml on how to do this?
Especially the poster above with the example that creates a webpage - this is pretty much what I want for DJs that are streaming live to be able to automatically record their shows - ideally as a special mount, but if it's all live shows that would be OK, just need to watch that folder or script something to copy the files elsewhere then remove them.
And +1 on this being in the next version of Airtime.
Tim
Post edited by Tim RadioClash at 2013-03-01 20:25:06