Albert FR said:
For me this version is more a 2.4.5 than a 2.5
a lot of features needed since a long time ago are always not present...
Albert Santoni said:I'm very pleased to announce that the first beta of Airtime 2.5.0 is now available for download!
This release includes a highly requested new Playout History feature for logging what you've aired, and allows for CSV and PDF export. The playout history format can be customized to comply with the broadcasting regulations in your country, and also lets you see playback statistics on each file and show in your library. This release also includes a fair number of bug fixes and stability improvements (a full list of bugfixes will come later).Change Log:2.5.0 - October 8th, 2013* New features* Playout History feature overhaul.- custom templates for log sheets.- ability to manually log an item.- ability to edit a history item.- 3 history views: log, file summary, show summary.- hosts can now view/log their own show history.* Ubuntu 13.10 Saucy Salamander support (PHP 5.5)* Bug Fixes* Several important timezone handling improvements* Rebroadcast shows bugfix* Reduce likelihood of playout stalls under high memory pressure* Fixed calendar not loading sometimes* Fixed webstream disconnections due to Now Playing page* Prevent admin password changes in demo mode* Plus dozens of other bugfixes!Thanks to the entire Airtime team here at Sourcefabric for making this release happen, and we're looking forward to your feedback! We're quickly pushing towards a 2.5.0 final release, for which we've already begun final QA testing.If you're interested in trying out Airtime 2.5.0 Beta 1, we expect a smooth upgrade to the 2.5.0 final release (no schema changes), though please backup your database before trying the beta just in case. Any feedback on the new release would be greatly appreciated!Thanks guys!Albert
Cliff Wang said:@Thomas+Hackett,
I have tried to play webstream for 20 mins and I can't reproduce it.But I did see this overrun before, like 2.4.x. It used to happen during a long time show, for instance 24 hours webstream.I will run a 24 hours show to catch it.
Voisses Tech said:@Thomas Hackett suggest
"Perhaps buffer overrun happens by design. Or perhaps it's another LS limitation that cannot be fixed. Airtime webstream links seem to be subject to many liquidsoap quirks which make them less functional than your average player."
I was hesitant to comment about this,because maybe I was wrong but let me give my 2cents.
I think I read some where that because of the "hop" nature [that is the send and receive communication] of http stream,then http streams are inheritently buffered streams.
The design approach is to buffer some streams ahead that you will have smooth playback.
It is what was done for mobile stream and this has enhance the user experience.
Proof of Concept
If you play anystream in vlc and check the tools==>codec information then you see this information
I do not think its a bug or design by LS but rather an inherent feature of streaming.
VOISSES
I might be wrong but I hope I can be educated some more
If the problem were a trait of all streaming, then why is it that only Airtime's implementation suffers playout interruptions and has such a hard time resolving a variety of stream URLs where other clients work?
An example of a web player without interruptions (albeit Flash):
http://native.flashradio.info/
Also found that Streamripper (both Windows and Linux versions) does a good job of relaying to a port that can be distributed by Shoutcast using StreamURLs (even ones with keys) that Airtime cannot.
Buffering isn't a bad thing, as long as it doesn't overrun.
Daniel James said:Hi Thomas, very little software is bug free, the Flash player you linked to above crashed my Firefox :-)
It is quite possible that some streaming formats can be played better in other players than Airtime does, we support Icecast-style input streams by default. We welcome bug reports from any streams that don't work, and the more detailed the reports are (such as the name and settings of the streaming client) the more likely we are able to fix those bugs.
As for buffering, that is an issue for live relaying because the few seconds of delay which may be acceptable in a desktop stream player are not usually acceptable in broadcast, particularly if they cause dead air.
Cheers!
Daniel
Daniel James said:Hi Thomas, in general, Liquidsoap relays streams with no problems here. We would like to find the root cause of your issues so that we can fix them. Could you supply URLs for the streams you are relaying please?
Cheers!
Daniel
Daniel James said:Hi Thomas, it sounds like the issue is that streams added to the Library do not support this particular type of listener authentication at playout time (which seems different from the Icecast method shown at http://www.icecast.org/docs/icecast-2.3.3/icecast2_listenerauth.html). This is perfectly possible since I don't think we ever officially supported relaying of authenticated streams.
I have opened a ticket http://dev.sourcefabric.org/browse/CC-5445 for this bug. If you could let me know which version of Airtime you have tested on (2.4.1?) that would be helpful. Please message me with a genuine authenticated URL that we can use for testing.
Cheers!
Daniel
http://dev.sourcefabric.org/browse/CC-5342
http://forum.sourcefabric.org/discussion/15934/need-help-for-new-webstream-with-listenkeys
Albert Santoni said:Ok Thomas, so it sounds like for your authentication problem, you think the parameters and values at the end of the stream URL are getting cut off by Airtime? Sounds like we should be able to reproduce that in the lab.
It looks like you're new here. If you want to get involved, click one of these buttons!