Daniel James said:Hi Nat, thanks for the feedback! The sentence about sub-second precision is meant to emphasise the 'time' aspect of 'Airtime', that tight timing is what the program is all about. Compare this to typical desktop audio applications which can be quite imprecise about track duration, silent gaps etc. This imprecision can have a significant cumulative effect when used in a 24/7 schedule.
OK, so why is it that we can't actually program a show to start with sub-second precision?
The diagram shows audio going to the transmitter via Pypo, Liquidsoap and the studio mixer, I will try to make this more clear. I could also make a simpler diagram showing a typical web radio use case.
The reason we mention the database used etc. is to give credit to the teams behind the many different Free Software programs we rely on. I agree it could be an overwhelming level of detail for new users. I'll see how we can improve that section.
Yes, the title of this manual is Airtime for Broadcasters. Broadcasters are not generally techy, so perhaps there should be another manual called Airtime for Programmers?
I brought up this point about the assumptions involved in recording elsewhere. The manual does not clearly say what the assumptions are for the recorder. Explicitly tell the user what recording is for would help prevent misunderstanding. I know this feature is changing but the current situation could improve.
Thanks!
John Chewter said:A nice API for frontend section with all options exposed would be nice.
It looks like you're new here. If you want to get involved, click one of these buttons!