audio overrun

w2dbw2db
in Problems and Issues

Hi folks, this happens a lot on my kiwi. I'm on the latest version 1.611 set up for 8 channels (2+6) and get 8 users usually every morning from 8AM-10AM local (CST). Looking at stats page I get frequent "audio overrun" red alerts. When this happens the audio and waterfall freeze for a moment. Is this normal, or do I have a problem?

Thanks

GeorgeC W2DB

Crowley, TX

Comments

  • jksjks

    Do you really mean "overrun" and not "underrun"? Underruns are common when the Kiwi is overloaded and cannot supply audio data to all the connections on-time (under/over is from the perspective of the browser audio).

    Overruns mean the Kiwi was supplying audio faster than expected and overflowed the buffering on the browser side. This shouldn't happen unless the Kiwi javascript code on the browser is running slow for some reason.

  • NU6FNU6F
    edited October 31

    Hi John

    I realized I'm having the same problem....lots of Audio underruns AND overruns and the kiwi freezed waterfall and audio

    Is it a symptom of the network side or webserver side?




    I hadn't correlated it on the Status page..

    ...but yes,this is my problem Both Ted OVERRUN and followed buy underruns..Happen all the time .Sometimes it runs without clusters of lockups for 15 or 20 minutes..but seldom longer than a half hour without freezing.




    Ron


    NU6F

  • NU6FNU6F

    And CPU usage at those times is still only at 45%

  • NU6FNU6F

    Ok I saw another thread...and then I guess it's a sign of my 4G router or service provider.


    I'll go up and swap out routers tomorrow to see if there is any difference


    Ron

Sign In or Register to comment.