similar to: xspf.xsl

Hi all, I posted this message before on icecast-dev, but I guess it's more appropiate here. First of all thanks again for icecast2. It keeps surprising me how easy and stable it is to use! I'm working with icecast2 from SVN now (revision 10692) and it's mount point features. I've created the top mount point '/play.ogg' so we have only one main mount point for users

I have figured out, that it is possible to get a xml file, if you add .xspf to the end of the stream url. This file includes the number of current listeners and max connections, what I don't want that this information goes public! How can I edit the information, which is displayed in the xsl file? Thanks for your support, Hans-Georg -- Diese E-Mail wurde von

On 7/18/07, Thomas B. Ruecker <ruecker@ruecker-itk.de> wrote: > Does XSPF have a logo we could use as a button? (I'm not referring to the > valid-xspf thing) Well, I created a logo last year, but the community voting wasn't favorable, so it has never become official. If you would like to use it, however, it's available under the Public Domain, so go for it. > I'm

This is to announce the release of Icecast 2.3.2 2.3.2 is mainly a bug fix release with a couple of new items that may be of interest to a few of you. Even if the new features are not of interest, it is still highly recommended that you update to 2.3.2. Downloads are here : http://downloads.xiph.org/releases/icecast/icecast-2.3.2.tar.gz

On Thu, 13 Jan 2005, Joel Ebel wrote: > it increased by 113, and it has stayed that high since then. I find it > especially odd since I have clients set to 100 in icecast.xml, and this > constantly exceeds it. > Where does this number come from, and what does it mean if it isn't the > sum of the clients for each stream? I know it should include static > content as well,

Infomaniak Network SA / Guy Baconniere wrote: > Hi Karl, > >> While I think most of this is fine, I think in the fserve part (where >> the checks to see if there is a playlist file in webroot), they all >> seem to follow the same pattern so that would tend to indicate a >> function to reduce duplication. >> >> At the moment I'm wondering whether these

Hello! In order to be able to permanently "register" the #xspf channel I need to be approved as a Xiph.org contact, either a general or XSPF-specific one, not sure. I guess some Xiph person has gone through the process filling out http://freenode.net/group_contact_form.shtml before? Would be great to hear how you want me to do that or if there's anything I should know about

I'm just checking. Icecast is supposed to export M3U playlists, as far as I know. I have to confess, I have never used the program, so get ready for lots of me saying ignorant crap. OK, ready? Does Icecast support anything to do with XSPF? If it does, does it do it by default? I mean, we are supposed to set the example and provide the user with our formats by default, right? What's

On Mon, 19 Jun 2006, Dennis Heerema wrote: > The nice thing of dir.xiph.org [http://dir.xiph.org/] was the fact that it > supported more or less all formats, this way we were able to send out > different formats, where the listener was able to choose his appriciated > format from and listen to it, also the way it all got listed made it very > easy for a listener to see all te

Hello, I'm currently testing Icecast 2.4.99.1 in regards to Opus metadata support. I have a Ogg Opus stream located here: http://50.31.159.156/64.opus When I playback the stream in VLC I see the expected metadata displayed in the client. ffprobe and mediainfo also return the expected metadata. # mediainfo http://50.31.159.156/64.opus General Complete name :

I don't want to receive your e-mails anymore.Thanks,Caio From: icecast-request at xiph.org Subject: Icecast Digest, Vol 61, Issue 4 To: icecast at xiph.org Date: Mon, 22 Jun 2009 12:00:01 -0700 Send Icecast mailing list submissions to icecast at xiph.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.xiph.org/mailman/listinfo/icecast or, via email, send a message

This is to announce the release of Icecast 2.3.3 It's been almost to the day 4 years that 2.3.2 was released, but all good things have to come to an end. So here's a new Icecast release. Let's hope it is as stable as 2.3.2 was. 2.3.3 is mainly a bug fix release with a couple of new items that may be of interest to a few of you. Even if the new features are not of interest, it is

I mean this one: http://lists.xiph.org/pipermail/xspf/ It has 6 messages in total. The reason why I think we should kill it is that it potentially confuses people looking the XSPF mailing list. What do you think? Who has is able to such a cleanup task? Sebastian

Hi Ivo, This program is basically a configurable automation system for Ices. You can (will be able to) use it to control what Ices plays and when. As such, it really doesn't have anything to do with playlist file formats such as XSPF, as all its data will be contained in a database. It may be desirable for the system to be able to import lists of tracks etc from existing playlist

I assume you have already tried setting the <hostname> section in the config, and that it doesn't work? http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#misc In that case, perhaps Icecast is picking up the server name from the http headers. Can you get your proxy to re-write the headers in the request? Otherwise, you could just generate local m3u/xspf files for each

Have now set the log to level 4 and viewed the output when the stream stops/starts. Can't see any errors though. I'm getting: source/source_move_clients passing 1 listeners to "/fallback.mp3" on stream stop and: source/source_move_clients passing 1 listeners to "/studio" when the stream starts again, so looks like it's working. Could it be the client at

Hi Karl, > While I think most of this is fine, I think in the fserve part (where > the checks to see if there is a playlist file in webroot), they all > seem to follow the same pattern so that would tend to indicate a > function to reduce duplication. > > At the moment I'm wondering whether these responses could be > automatically generated from xslt files? like xspf is.

On 3 Mar 2017, at 14:53, Roger Hågensen wrote: > On 2017-03-03 13:37, Marvin Scholz wrote: >> >>> I'd like to suggest adding history to status-json.xsl or to reduce >>> the size of the json to the bare minimum that a Web base mediaplayer >>> might need >>> Add a new one at http://127.0.0.1:8000/playing-json.xsl?mount=/live >>> Which will

Hi, I installed icecast2 on Debian 10 via backports for buster so that I could get ssl support. I’ve successfully configured iceacst to stream via ssl within the browser. No problems there. For instance I can successfully open a https link to the stream with a URL like https://domain-name.net:8433/mountname <https://domain-name.net:8433/mountname> However, the same URL with .m3u at the

I solved the issue by adding my own m3u files to /usr/share/icecast/web but I am not sure if this is icecast best-practice. This also raises a few other issues as well… http stream links don’t appear on the icecast stream directory and stream titles and track metadata does not display when opening m3u files created in this way. I assume that there are various reasons for this…mainly that https