search for: unosonic

wilderzone.radio.2: > Hello, unosonic, > > Okay, we'll do it this way as it appears to be the only sane way... > THIS is the xml config file that I've been using for ONE STREAM ONLY. but it's not the config file you're using actually at your site. can't find any mountpoint called /rock ... there must be...

Thank you for reply. And in wich folder put tig PEM file V V sre., 31. jul. 2019 ob 16:04 je oseba unosonic <un at aporee.org> napisala: > Ervin Bizjak: > > Hello! > > > > Where do I find tutorial how to install and setup ssl and which > certificate > > is for icecast? > > > > hi, don't know if there's info esp.on SSL, > > I've just compi...

Thomas B. Rücker: > After all, Icecast is just another web server. > > Please note the absence of 8000 and 8443. Neither are officially > specified for WWW type HTTP(S). They are commonly used as such, but 80 > and 443 are *much* better choices and should be preferred. makes sense, but if my webserver needs to serve http/s from the same IP, that would not work. Unless I want to

Hi unosonic, Cool Mic's primary advantage to other source clients out there is that it streams in the patent-free, high quality Ogg Vorbis format (BroadcastMyself only supports MP3). We will be adding opus support in the future as well. Re: Feature requests: Re-connect sounds like the next feature that w...

...t;/ssl> >         </listen-socket> > > I don't think it's possible to have both encrypted and unencrypted > traffic to the same port, but maybe somebody will correct me if that's > possible. > > Regards, > > Per Gunnarsson > On 2019-07-31 14:49, unosonic wrote: > > hello, > > > > > > I've icecast 2.4.4 /w SSL support, and when i enable SSL in the config file: > > > > <ssl>1</ssl> > > and > > <ssl-certificate>my-all-inlusive.pem</ssl-certificate> > > > > I can co...

hello, I've icecast 2.4.4 /w SSL support, and when i enable SSL in the config file: <ssl>1</ssl> and <ssl-certificate>my-all-inlusive.pem</ssl-certificate> I can connect via https://my-server:8000/my_stream but only via https, no longer http. Is there an option to have both? Also my source clients seems to be unableto connect anymore via http, but have to look

...t;/ssl-certificate> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> I don't know what can I do wrong V V pet., 2. avg. 2019 ob 03:47 je oseba <webmaster at berean-biblechurch.org> napisala: > On 2019-07-31 09:44, unosonic wrote: > > Thomas B. Rücker: > >> After all, Icecast is just another web server. > >> > >> Please note the absence of 8000 and 8443. Neither are officially > >> specified for WWW type HTTP(S). They are commonly used as such, but 80 > >> and 443 are...

Hello, unosonic, ======= At 2019-09-09, 04:54:14 you wrote: ======= >wilderzone.radio.2: >> >What is the use case that you are trying to address? Icecast is well >> >suited to running multiple streams in parallel and offers complex >> >configuration options for many use cases. >&...

Hi, On 7/31/19 1:56 PM, unosonic wrote: > > thanks, that makes sense and works! > btw: is port 8443 sort of standard, which clients do consider? The RFC standardized ports for HTTP are: 80, alternatives: 8008, 8080 For HTTPS: 443 After all, Icecast is just another web server. Please note the absence of 8000 and 844...

Hi, On 9/9/19 12:31 PM, wilderzone.radio.2 wrote: > Hello, unosonic, > > Actually that IS one of the 2 config files being used. (This one named icecast.xml) > > (so far, oddly enough, NO ONE has mentioned the usage of the 2nd config file by name of icecast_run.xml) I am not familiar with a file called "icecast_run.xml". Could this be a local...

hi there, let's say I have a mountpoint /important with a source a, and a mountpoint /notimportant with source b now I have to switch source a and b so that the content of source b plays on mountpoint /important mountpoint /notimportant is, well, not so important of course I can do it manually, but I wonder if there is a trick to accomplish that programmatically or within icecast. ideas

Which Icecast Version are you using? This sounds like a bug that was fixed in recent versions. 2.4 is not exact enough, we need to know the full version number, please :) On 2 Nov 2016, at 10:52, unosonic wrote: > > hello, > > this is a bit special I guess... > Icercast 2.4 > > I have several mounts of type=normal, with staticly defined > user/password > as well as dynamic authentication via url, e.g.: > > <mount type="normal"> > ... > <p...

...1</ssl> > </listen-socket> > > I don't think it's possible to have both encrypted and unencrypted > traffic to the same port, but maybe somebody will correct me if that's > possible. > > Regards, > > Per Gunnarsson > On 2019-07-31 14:49, unosonic wrote: > > hello, > > > > > > I've icecast 2.4.4 /w SSL support, and when i enable SSL in the config > file: > > > > <ssl>1</ssl> > > and > > <ssl-certificate>my-all-inlusive.pem</ssl-certificate> > > > > I c...

...ation for that, like a different source password or such. Of course if your broadcast software does not support Icecast but just SHOUTcast, things are more complex as SHOUTcast had no concept of different streams on the same server. On 9 Sep 2019, at 13:31, wilderzone.radio.2 wrote: > Hello, unosonic, > > Actually that IS one of the 2 config files being used. (This one named > icecast.xml) > > (so far, oddly enough, NO ONE has mentioned the usage of the 2nd > config file by name of icecast_run.xml) > > ======= At 2019-09-09, 08:20:24 you wrote: ======= > >> wi...

Wow, thank you so much! I completely forgot about the status-json.xsl file... :D 2018-01-23 15:38 GMT+01:00, unosonic <un at aporee.org>: > Danijela Popović: >> Hi all, >> Basically there's my question in the subject. I need a simple example >> of now playing artist, song, and listeners. Can somebody write it down >> for me? > > no time, sorry > http://icecast.org/docs...

I've been directing the development for a new Icecast 2.x source client for Android called "Cool Mic". It's designed to be simple and elegant with an easy to use interface. It uses the device's microphone to broadcast live audio in Ogg Vorbis format. It's come to the point in development where I'd like to ask for anyone interested in helping give feedback. All core

...gh a powered hub such as the PiHUB should also work. The only thing I kinda missed was a recording level control. The only control alsamixer is giving me, is the pcm playback level. So you'd have to make sure the audio you send to it is somehow sane. Best, Maarten On Thu, 22 Jan 2015, unosonic wrote: > Maarten Bezemer: >> >> Shouldn't USB2.0 ports be able to connect to USB1.1 devices without >> changing the entire stack to USB1? > > according to my experience, no. here are my personal notes when i'd set it > up: > > # Xenyx 302 USB > > p...

hello, now that html5 audio becomes usable in some browsers, for example http://webaudiodemos.appspot.com/AudioRecorder/index.html ... has anybody thought about to implement a web based source client for icecast? that's for now beyond my coding skills, unfortunately... thx, uno

Hi u, On Thu, 22 Jan 2015, unosonic wrote: > well, sort of, with a PI, Ices2 as a client, and an USB audio device as > input, e.g. a "class compliant" audio recoder like Olympus LS5, Zoom H2 > etc., but also a little mixer like the Behringer Xenyx 302 USB. > The problem i've encountered is with USB class1 d...

Hi, In our design of Icecast2, our multiple sources will stream their high quality audio via a dedicated audio encoder (not a computer): Live audio > L+R microphone > pre amplifier > audio encoder > Icecast2 VPS So far I have a shortlist of 4 possible brands of audio encoders: Sonifex PS-SEND, Barix Instreamer, Bric-Link, Outcaster OC100. All have their pro's and cons.