Results 1 to 10 of 10

Thread: cupertinostreamingpacketizer

  1. #1

    Default cupertinostreamingpacketizer

    When re-streaming from shoutcast and the mp3 audio is still filling the shoutcast server's buffer (at this stage, the mp3 audio is not yet available for playing), the cupertinostreamingpacketizer on Wowza is showing "hunting" on the screen and sending the CPU to a 100% spike.

    Hope this is clear. Both servers are running on the same machine though.

    Thanks guys for this magnificent product.

  2. #2

    Default

    Does it work properly once the SHOUTcast buffer is full?

    Charlie

  3. #3

    Default

    Quote Originally Posted by charlie View Post
    Does it work properly once the SHOUTcast buffer is full?

    Charlie
    Yes it does, it goes back to normal once the stream is available.

  4. #4

    Default

    I am surprised the cpu goes up to 100%. Does it log a ton of error/warning messages very, very quickly?

    Charlie

  5. #5

    Default

    Quote Originally Posted by charlie View Post
    I am surprised the cpu goes up to 100%. Does it log a ton of error/warning messages very, very quickly?

    Charlie
    That's exactly what happens. I tested it on several computers.

  6. #6

    Default

    So does it log a ton of error messages, is that what is leading the 100% cpu. Can you send me a log file with the logging so I can see what is going on (support@wowzamedia.com).

    Charlie

  7. #7

    Default

    When I get a chance I will dig into this. It probably will not be until mid-January.

    Charlie

  8. #8

    Default

    Hi Charlie,

    According to the change log, this issue has been fixed, correct?

    Thank you

  9. #9

    Default

    Maybe, I really didn't have a good way to test it. I did change the SHOUTcast reconnector to try and alleviate the problem. Is there anyway you can test and let me know.

    Charlie

  10. #10

    Default

    I tested it again, this time with Patch2 and the issue is still there. It only happens with shoutcast mp3 streaming though, and I believe it's the logging part causing this issue as it tries to log too many 'WARN ... Hunting' messages.

    Quick fix: change the logging config param from INFO to ERROR.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •