similar to: Icecast v2.5

Hey Roger and everyone else commenting – I appreciate all the advice and questions. I now have more work than before 😊! Greetings from sunny South Africa! Sent from Mail for Windows 10 From: Roger Hågensen Sent: Thursday, May 2, 2019 12:12 PM To: icecast-dev at xiph.org Subject: Re: [Icecast-dev] Webm files written without duration in header On 2019-05-01 11:58, Sytze Visser wrote:> I am

I am a software developer myself. We develop a Radio Automation System/Broadcasting. Hence we are using the reference encoders. For OGG there is LUCKILY still the admin interface working to update meta data mid-stream. That is why my post is related to the other ogg based formats: FLAC and OPUS! Tractor Pro is btw not supporting FLAC or OPUS and alao uses the admin update interface! As such

Many Thanks for your answer. Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) I have tried most of them (except liquidsoap). However, even the mentioned apps like RadioDJ or Mixxx do NOT support meta data changes via the encoder (they all use the admin interface)! And as you correctly pointed out: none of the reference encoders support this. Not even the FLAC, OGG

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 only hold the current info: > > Right now I personally don't think

Does anyone have a Linksys WPC11 v2.5 running under CentOS 4? If so, were there any special tricks that you had to perform? Any information would be most helpful. Thanks, Barry Brimer

While http://127.0.0.1:8000/status-json.xsl?mount=/live is fine for info on the server itself and the current track played it's missing a played history. 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 only

Thanks for your clear answer. I'll try to contact the OGG, FLAC a Opus encoder developers at xiph.org. As it currently seems, that there is no direct support for chained streams on the 'client-side' (encoder side) when using the reference encoders as provided by xiph.org. As such I find it a bit odd to have no 'out-of-the-box' solution available at all. Even if all/you say:

Hi. Is it possible (legally) to stream MP3s on Icecast that have been encoded with LAME encoder (http://lame.sourceforge.net/license.txt)? So if a composer writes a track, then saves in MP3 with LAME, and wants to distribute with Icecast server, is it legal? Must he get license for MP3 (http://mp3licensing.com/royalty/emd.html) and pay any royalties for MP3 DISTRIBUTING or STREAMING as it stated

you can try tracktor pro and see how it streams. cause it handles it well: track's info updates in ogg without rupture.. regards renan waves.pw On 15/08/2019 20:48, bn at radio42.com wrote: > Many Thanks for your answer. > > Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) > I have tried most of them (except liquidsoap). > However, even the

Hi Philipp, While you might logically/theoretically be right with what you say, it is not really practical and unfortunately not user friendly. Let me try to explain my standpoint: Most users do use ICEcast to stream a continuous stream, e.g. they stream a live DJ or radio program. I.e. they setup a single encoder on a single audio stream. Still this logical stream contains different tracks being

On 2019-08-14 08:35, Bernd wrote: > Most users do use ICEcast to stream a continuous stream, e.g. they stream a live DJ or radio program. > I.e. they setup a single encoder on a single audio stream. > Still this logical stream contains different tracks being played over its time, and as such those users would like to update ICEcast to inform their listeners about the changing tracks

Hi, thanks for your e-mail and detailed description. On 3 Mar 2017, at 12:51, Roger Hågensen wrote: > While http://127.0.0.1:8000/status-json.xsl?mount=/live > is fine for info on the server itself and the current track played > it's missing a played history. > > > I'd like to suggest adding history to status-json.xsl or to reduce the > size of the json to the

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, On 8/16/19 6:10 AM, Bernd Niedergesäß wrote: > I am a software developer myself. We develop a Radio Automation System/Broadcasting. Hence we are using the reference encoders. > > For OGG there is LUCKILY still the admin interface working to update meta data mid-stream. As previously noted this does not do what you may think it does and its use for Ogg/Vorbis is discouraged by us.

On 04/20/2015 05:47 AM, Ralph Giles wrote: > On 19/04/15 08:15 PM, "Thomas B. R?cker" wrote: > >> If anyone happens to know about proven secure settings, just like the >> Mozilla labs settings for server side, please let us know. > You mean like https://wiki.mozilla.org/Security/Server_Side_TLS ? Yes, that's what we used for the Icecast server default cipher

Dear all I am streaming live with webm with ffmpeg to icecast 2.4.2. After the stream ends, I am unable to determine the duration of the file using ffprobe or mediainfo. Not sure but it seems that this has to do with headers? Should icecast be writing the duration into the header or should this somehow be passed from ffmpeg? The requirement is really to determine the duration of the streamed

Dear all I am streaming live with webm with ffmpeg to icecast 2.4.2. After the stream ends, I am unable to determine the duration of the file using ffprobe or mediainfo. Not sure but it seems that this has to do with headers? Should icecast be writing the duration into the header or should this somehow be passed from ffmpeg? The requirement is really to determine the duration of the streamed

I have node.js script, which works in daemon mode. The script reads IceCast ogg stream itself (on the fly) and sends audio tags to website. But sometimes (exactly once per 2 days) the script fails end exit. Error log of the script says: Error: getaddrinfo ENOTFOUND stream_url stream_url:8182 at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26) Emitted 'error' event at: at

On 2019-08-16 08:10, Bernd Niedergesäß wrote: > I am a software developer myself. We develop a Radio Automation System/Broadcasting. Hence we are using the reference encoders. > > For OGG there is LUCKILY still the admin interface working to update meta data mid-stream. > That is why my post is related to the other ogg based formats: FLAC and OPUS! > > Tractor Pro is btw not

On 2019-05-01 11:58, Sytze Visser wrote:> I am streaming live with webm with ffmpeg to icecast 2.4.2. After the > stream ends, I am unable to determine the duration of the file using > ffprobe or mediainfo. Not sure but it seems that this has to do with > headers? > > Should icecast be writing the duration into the header or should this > somehow be passed from ffmpeg?