Icecast Streaming Media Server

[Nonapeptide]

I've had numerous occasions where the on-connect and on-disconnect tags would have helped me immensely on the Windows implementation of IceCast. I know, I know. "Just use the Linux version!" However, some clients just won't change. In those cases, having connection/disconnection tasks run would really be a help.

One example: At one client of mine, archives are kept of certain broadcasts using the dump-file tag per mount point. However, to keep things sane, there is a limit to the size of an archive that can be kept. Currently 120MB per archive is the limit for this client. For their source bitrate, that allows for sources to have about 5 hours of broadcasting saved. A PowerShell script runs each night on the Windows Servers, looks for files in the archives folder that are over a certain size, and deletes them.

But what of sources that truly need to stream for long periods? Perhaps marathon broadcasts, shows, events, etc.? What I've done is made a simple PowerShell script that runs every 5 minutes (the lowest amount of time that a scheduled task can run on Windows) and seeks out any archive file and attempts to rename it based on the mount point name and a timestamp. See how that works? If a mount point is still streaming, the file is still open and can't be renamed. The task silently moves on to the next archive file, dutifully naming files based on mount and time every 5 minutes. Thus a source client only has to stop streaming for five minutes at the most before the archive is renamed. Then they can re-connect and the dump file is created afresh.

However, that's a bit irksome and I'd love to be able to tell source clients that they can merely disconnect and reconnect to interrupt their archive. <on-disconnect> would help that goal, and unfortunately this client is invested in Windows Server to an extent that I can't really get them on Linux implementations of IceCast.

Ah well - I'll get by.

[karlH]

you could use the auth url mount_add and mount_remove triggers. To get the same functionality as on-connect etc on win32 then an underlying function needs to be utilised for creating the process, no one has been interested in doing it for windows.

karl.

[Nonapeptide]