Skip to content

Releases: karlheyes/icecast-kh

icecast-2.4.0-kh20.3

21 Mar 17:19
Compare
Choose a tag to compare
icecast-2.4.0-kh20.3 Pre-release
Pre-release

worker update for processing clients. Should be solid but not tested in many setups.
stats cleanup showing on web pages
fixes for some bitrate specifications for fallback.
some switchover handling cleanup
xslt caching cleanup.

icecast-2.4.0-kh20.2

13 Mar 01:32
Compare
Choose a tag to compare
icecast-2.4.0-kh20.2 Pre-release
Pre-release

flush out fixes and internal cleanups for inactive client handling.

icecast-2.4.0-kh20.1

08 Mar 13:16
Compare
Choose a tag to compare

The .1 release is just to include some missed release version details after pushing

icecast-2.4.0-kh20

07 Mar 20:33
Compare
Choose a tag to compare

important lock imbalance fix in kh19. Some minor changes for handling odd cases, not common though.

The windows builds are fine, but for tree sync up use kh20.1

karl

icecast-2.4.0-kh19: cut release kh19

05 Mar 21:49
Compare
Choose a tag to compare

mostly fixes in this.

improvements to xml parsing with changes in recent releases, people who have had issues with empty tags should be ok without the xml parser rejecting it.
The tag fallback or fallback-mount can now take original name or in a block with a mount tag and rate tag or take mount and rate as parameters (rate being a bitrate eg 128k).
some legacy shoutcast settings on the ports were an issue now fixed.

the rest is essentially internal code fixes for crashes, non-playback in chrome, excessive logging and some relay handling changes

I have added a new option on mount, hijack (bool, as tag or param) which allows for an incoming source client to override an existing stream, effectively to swap in, dropping the existing stream without affecting the listeners. The initial use case is for hijacking a relay, and when the source client disconnects, the relay is restarted. You are still limited to same stream parameters or else player apps could get confused. This feature should be considered as a replacement for fallback, ie you have a fallback stream already there but a source client jumps in and takes over. This allows your mountpoint to be anchored, listeners don't move to another mountpoint and allows for the fallback to be from another server or if need be using the multi-host feature within the relay. This anchor aspect may be useful for external stream listings or stats collection and helps avoid problem cases with shared fallbacks (ie mount A and mount B both fall back to mount C can now become mount A and B both relay C and then sources overrides the relays, no fallback specified).

While the hijack code can work with one source client replacing another, there are certain aspects that need more consideration, namely the first source client can attempt to reconnect causing a bouncing effect. In such cases some extra selection criteria is required like auth via URL.

karl

icecast-2.4.0-kh18

02 Feb 12:53
Compare
Choose a tag to compare

mostly bug fixes from previous releases. Cleans up a number of http header related issues, utilises the same code for work on POST. A more complete switch over update (the ability for one stream to be swapped with another, eg source client replacing a relay). A new mount setting (linger-for in seconds), to keep a stream around after termination for cases where you want either someone else to jump in (switch over) or add a delay if you expect the feed to re-establish in some short time frame.

Karl

icecast-2.4.0-kh17

18 Jan 00:44
Compare
Choose a tag to compare

Updates for processing HTTP headers, XML parsing updates. Relay processing features. Various small fixes

v2.4.0-kh16

07 Dec 16:41
Compare
Choose a tag to compare

2.4.0 kh16

Release has bug fixes and speed improvements in specific areas

icecast-2.4.0-kh15

01 Jul 10:02
Compare
Choose a tag to compare

This is a bug fix release, no new features over kh14. Should resolve stability reports and some incorrect behaviours.

karl

2.4.0-kh14

04 May 00:48
Compare
Choose a tag to compare

Mostly fixes. Trying out allowing multiple icy sources on same port. Included windows builds here as well