#Nicecast and wifi professional
SAM Broadcaster is a professional computer-based internet radio broadcasting solution. Often running a lower sample rate will reach trans oceanic listeners better, around 96KBPS seems to be good most of the time.Gives Winamp the possibility to connect to a shoutcast streaming server by transmitting the music played or audio from any selected input. This cause quite a few issues trying to broadcast from Europe to the Americas and vice versa. Streaming trans-oceanic is extreamly troublesome, most of the backbone cables have been there for 50 years or more and are not the most effeciant data conductors anymore. If the internet is spotty where the listeners are or you are trying to broadcast to a continental audience, maybe kick it down to 112-96KBPS. If your target audience is fairly local (Same city, region, maybe country.) to your broadcast servers and the internet infestructure is good where your listeners are, you should be able to boadcast at 128KBPS, much higher than that is really a waste. That may indicate an issue with the internet links between you and the broadcast server.Īlso note your target audience as well and their location geographically. See if you get any excessive packet loss or ping times there. Next run a trace route to your broadcasting service server (Not their website.). These may indicate that your router or modem are a problem. If you are using an ethernet cable, try sending a set of pings against your router or ISP server, see if you get excessive packet loss or ping times. If Wifi when try connecting directly to the Router or Modem with an ethernet cable. So first thing is how is your computer hooked to your router and/or modem: Any bottle necks anywhere along the line will affect the listeners. Also you have to look at the broadcasting network as a whole from your computer through the Radionomy servers and on to the listeners. WiFi even 5Ghz dual-dand systems are much more sencitive to interfearance and interuptions while streaming. This might bring me close® to a solution, and if someone could confirm it had something to do with that I might be completely there.įirst of all it’s always better to be plugged in directly to your modem or router rather than using WiFi. However (coincidence or not?) I upped the latency, the buffer underrun stays at 0 and I tried broadcasting at a higher samplerate again and this afternoon, my live broadcast of 2 hours long went flawlessly.ĭo you think the settings latency-buffer underrun-sample rate would effectively have contributed to the problem? Until I read about the relationship between latency and buffer underrun and I did some experimenting, as, before I was broadcasting at a sample rate of 48 kbps. Solution 2 I have tried, but not always with success. Solution 1 I am not so sure about as I now have fibre optic broadband running at around 30 Mbps. I should connect to the router using an Ethernet cable rather than broadcasting wirelessly. This used to happen regularly lately, and the explanation Radionomy gave was that either: if there is some silence in your live) the non-stop can take over. However, when you go live, the non-stop interrupts and your live streaming goes through.įor certain reasons (eg. You plan your programs and then upload the lists, and Radionomy broadcasts your non-stop streams 24/7. I was wondering (this might help a lot with my problem):Ĭould it have something to do with buffer underruns that, when I broadcast live (through Radionomy), listeners sometimes message me that different songs start playing through the music that is playing live at the time. But I don’t like the nicecast working-place with very small knobs… Changing a directory or something like that will end in buffer underruns.Īt least I’ve tried Nicecast - and everything works fine and without any probs at all. If I take a more less one, it will be a little bit better but not good at all. Ahhh, the bitrate I have to select to 192 kbps. I’ve also tested my internet-connection, the uplooad is something like a little bit more than 1900 kbps - so I could send a lot of streams. I’ve changed Latency up to 92,9, the results are the same.Īny idea, what I can do? I use mixxx on a macbook air, 1st generation with ssd, 1.6 GHz Intel Core 2 Duo. Now I’ve “investigated”: The “buffer underruns” on listeners-side happen if i do nearly nothing on my machine - for example scrolling any hd-directory.
Yesterday I started to make a serious radiocast - and got into problems.Īgain locally everything seemed to be ok., but listeners talked about buffer underruns more and more. I also did a simple teststream to broadcast. I’ve used mixxx locally up2now - everything worked fine.