fokidisc.blogg.se

The nicecast
The nicecast












  1. #The nicecast mac os
  2. #The nicecast full
  3. #The nicecast software
  4. #The nicecast series

I'm not selling or promoting anything, just trying to help you out.2.) make sure the button next to the server you've configured is clicked on, selecting this as the server you'll be streaming to.ģ.) click window>show broadcast.

the nicecast

PS - Not real sure why Centova pulled my original post. I'm sure that this is what is causing you to get dumped at speeds of 128 - 256 kbps.

the nicecast

Also a high latency (over 100 ms) will cause the signal to 'drop and re-buffer'. The lower the latency, the better the signal and less buffering you will have. If you are in the US, find a host in the US. So, bottom line, is you should find a Stream Host that is closer to your PC. At higher speeds like 128 kbps and above, you should keep it under 100 ms to avoid buffering. The lower the latency (ping time) the better the signal and less buffering. Going from the US to Europe is (don't quote me) usually about 170 ms from West Coast US and about 90 ms from the East Coast US. So, it takes about 1/4 of a second to receive your signal, worst case and about 1/8 of a second best case. However, the average time is 114.8 ms and the worst is 257.8 ms at the Stream Host end. But there is a 1% loss at the final hop, not real bad. You sent 211 packets and your Stream Host received 210 packets, which is good. Thanks much in advance for the assistance! Anyone have any idea what the issue might be? I’ll reiterate that I did in fact stream successfully from this location using this gear in this configuration for the better part of a year.

the nicecast

I have no idea what else I can or should change.

  • Different bitrates, sample rates and channel formats in the streaming clients.
  • Adjustments to the internal computer audio (44.1 kHz and 48 kHz).
  • Using a different streaming client, Nicecast, then Ladiocast.
  • Swapping wireless routers (from Linksys to the Airport mentioned above).
  • Streaming from 2 different computers, one ethernet cabled to the wireless router, one on wi-fi.
  • I tried these things which had no effect:
  • Switching from Icecast to Shoutcast (which we did.
  • The host suggested these fixes (none of which worked):

    #The nicecast full

    I never lose connection to the server, it doesn't shut down, but the stream is full of glitches and errors. Usually after that, I’ll hear some streamed audio that skips forward, sort of like scanning a digital file, interruptions in the audio, etc. With the second host, I haven’t had any server shutdowns, but instead will stream successfully for 10 to 30 minutes, then start getting intermittent ‘blinks’ of AutoDJ content. I tried mono vs stereo, never could get a stable stream going, tech support could only tell me the problem was ‘on my end’, and I eventually decided to switch hosts. I couldn’t find the source of this alleged data doubling.

    #The nicecast series

    I first experienced a series of server shut-downs - the host told me I was ‘over streaming’, 256 kbps to a 128 kbps account. The modem feeds a wireless router (and I’ve tried 2, a Linksys EA7500 v2 and an Apple AirPort Extreme). We have a Comcast cable modem with d/l speeds of over 100 mbps and upload of around 12 mbps.

    #The nicecast mac os

    I’m on Mac OS and have been using Nicecast (later trying Ladiocast). I’ve recently tried to launch a new streaming project, so I purchased precisely the same streaming product I’d had before, with the same host, same gear, only this time, intermittent issues have plagued me from the start.

    #The nicecast software

    I was involved in a streaming project that operated with CentovaCast software (Icecast 2) for about 7 months with no issues, for whatever that’s worth. A little background, I have a lot of audio engineering experience, and a little audio streaming experience.














    The nicecast