similar to: [PATCH] Config: Rename mp3-metadata-interval to icy-metadata-interval

Hello, I didn't want to have to choose between Icecast running on port 80 and all my Apache virtual hosts, running also on port 80, on my sole external IP address. I didn't want either to open port 8000 on my firewall because I wanted all users being able to reach Icecast even the ones behind enterprise firewalls. So I managed to run Apache 2.2 listening on port 80 and Icecast 2.3.2

So, I'm in the middle of understanding how the icecast.xml file is parsed, and how the settings for a specific mount point are read. In cfgfile.c - _parse_mount() I've added the following lines: } else if (xmlStrcmp (node->name, XMLSTR("playlist-notify-uri")) == 0) { mount->playlist_notify_uri = (char *)xmlNodeListGetString (doc, node->xmlChildrenNode, 1); }

On 06/09/10 16:42, Nicholas Young wrote: > So, I'm in the middle of understanding how the icecast.xml file is parsed, > and how the settings for a specific mount point are read. > > In cfgfile.c - _parse_mount() I've added the following lines: > > } else if (xmlStrcmp (node->name, XMLSTR("playlist-notify-uri")) == 0) { > mount->playlist_notify_uri =

Attached you will find a patch against the icecast-2.0.0 released source code which implements listener time limits on a global or mount-specific scope. Two new configuration elements are added with this patch: client-time-limit: This is a GLOBAL directive which covers all connections. Its value is given in seconds. So for example, if you want to limit all listeners on all mount points to 1

Hi, You don't check for malloc failure. I've made a patch that is possibly wrong but it saves the program from SIGSEGV and replaces it with SIGABRT. -peter diff -ru icecast-2.3.2-ORIG/src/admin.c icecast-2.3.2/src/admin.c --- icecast-2.3.2-ORIG/src/admin.c Fri May 2 17:40:00 2008 +++ icecast-2.3.2/src/admin.c Thu Apr 28 19:53:03 2011 @@ -291,6 +291,9 @@

hem here it is the patch. ;) bye kysucix -------------- next part -------------- Index: conf/icecast.xml.in =================================================================== --- conf/icecast.xml.in (revisione 10365) +++ conf/icecast.xml.in (copia locale) @@ -62,6 +62,7 @@ <port>8001</port> </listen-socket> --> +

Hi, A radio is being developped at school, and we wanted to avoid eating too much bandwidth, so we had a look at RTP. I first implemented it in icecast1 and it worked well (although we had to apply a patch to make RTP work with xmms). We are indeed saving a lot of bandwidth. I then adapted it to icecast2, here is the patch. The biggest trouble for now is the configurability. I added 3 global

I wrote a patch which makes client connections retain info about which socket they connected to - this way, you can change the server's behavior based on which <listen-socket> is being connected to. In addition, I added a field to the <listen-socket> section of the config file called <default-mount> which specifies a default file in the case that one isn't specified (it

source.c, function source_reserve() : Function avl_tree_wlock(global.source_tree) call must be placed before do-while, not inside the cycle. My correction in block _DIGI: #define _DIGI ... if(mount[0] != '/') ICECAST_LOG_WARN("Source at \"%s\" does not start with '/', clients will be " "unable to connect", mount);

Hey all, Got a bit of a long one here, so bear with me while I try to hash out the details... better to give too much than not enough. So we''re using the ActionWebService in order to communicate with a 3rd-party software client. We''ve created the API as discussed in Agile Web Development, and, in fact, invoke actually works perfectly. We have three example XML posts... they

> SOURCE $mountpoint ICE/1.0\n > ice-password: $password\n > ice-name: $name\n > ice-url: $url\n > ice-genre: $genre\n > ice-bitrate: $bitrate\n > ice-public: $public\n > ice-description: $description\n\n > Cool - I'll code this in right now.... There's no brains to this code right now, it just modifies the encoder example to read from teh soundcard and send

Hi all again... I did a chroot patch with ability to change uid and gid. I dunno if you all approve with the current implementation but the patch is small and it works here. remember to CC, since i'm not on this ml... //Ian Kumlien PS. To anyone on vorbis-dev, I'm *REALLY* sorry must be tired or something.. =) DS. <p><p><p> -------------- next part -------------- A

Reimplementation of my earlier patch - more proper aliasing - at the suggestion of Mike -Paul -------------- next part -------------- diff -ur icecast/CVS/Entries IceCast/CVS/Entries --- icecast/CVS/Entries 2003-04-18 11:00:19.000000000 -0400 +++ IceCast/CVS/Entries 2003-04-17 22:14:16.000000000 -0400 @@ -1,4 +1,3 @@ -/.cvsignore/1.3/Wed Jan 15 05:36:15 2003// /AUTHORS/1.2/Fri Aug 9 15:55:01

At 07:12 PM 5/21/2004, you wrote: >2. This is a project where all the broadcasters, myself included, are >blind. Last time I tried it, and admittedly it was a long time ago, >Oddcast presented some issues with regard to screen reader accessibility. >I should really run it up the stick again to see what it's like nowadays. I released a blind-friendly version of oddcast a long

Normally icy-metaint is a line in the http header, but some stream only sends it in the response data is self. Where can I find such a stream? Is that compliant to the standard? Implementation that also parses the response data http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadata-in-android-2-2 Thank Stig -- Best Regards / Mvh Stig Christensen stig

UTF-8 is now the universal standard. It supports ALL character sets. /greg. StreamS HiFi From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Fred Gleason Sent: Saturday, December 01, 2018 15:14 To: Icecast streaming server user discussions Subject: [Icecast] Character encodings in ICY metadata Available Attachments * Untitled attachment 00015.txt

UTF-8 handles ALL character sets. That’s the whole idea of Unicode. We have encoder users all over the world using UTF-8. Handles all Asian languages with no problem, including Burmese which is a more recent addition to the current Unicode version due to additional complications. Requires Operating Systems with the latest Unicode version. Here is an HLS stream with metadata done right:

Hello, I have a request for an additional header. This header is needed to inform the client of the burst it is going to receive. Why ? This header could be very usefull for the streaming-client to have an idea of it's delay, and (much more important) to be able to do early-on streaming. The question is not on how to implement this in code (probably send the header in the

Good morning, On Sat, 2018-12-01 at 16:20 -0800, Greg Ogonowski wrote: > UTF-8 is now the universal standard. (ICY context:) Expect if you are in Asia. Or in central Europe. Or maybe in Africa. I'm not aware of servers on the poles, maybe they use..., ... > It supports ALL character sets. As long as "ALL" is defined as what English people need plus all emoji in all skin

Hi all: I'm looking at some of the features in SVN Icecast, particularly the ability to reclaim fallbacks. This feature would be very useful for a project I work with, and could see us switching to icecast from Shoutcast compatible technology. One problem arises, however. Some of our broadcasters use the legacy Shoutcast DSP plugin, which can only perform ICY-style connects. My problem