Results 1 to 5 of 5

Thread: Stop chunking HLS stream after x retries

  1. #1
    Join Date
    Nov 2012
    Posts
    8

    Default Stop chunking HLS stream after x retries

    Hi,

    I have some difficulties to set up correctly one of our wowza applications. We use this application to create an HLS stream for the iphone. We send a request to the wowza API to start or stop chunking a live stream which is straightforward. But sometimes, the stop chunking request doesn't reach wowza. The consequence is that even after few days, wowza still tries to chunk a stream which is not live anymore.

    In the logs, I can see this:
    MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: cupertinostreamingpacketizer:542270_1653320_73bd3c12_1_198@85524
    then
    MediaStreamMap.removeLiveStreamPacketizer[livestreamiphone/_definst_/542270_1653320_73bd3c12_1_198@85524]: Destroy live stream packetizer: cupertinostreamingpacketizer

    Is there anyway to stop chunking a live stream after x retries?

    Thanks for your help.

    Cheers,
    charly (yeah I know :-))

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Welcome, Charly,

    It's possible that some device made a request. For example a page with html5 video tags was refreshed. The video tag behavior is to check the stream. If it does not exist there are WARN messages.

    Richard

  3. #3
    Join Date
    Nov 2012
    Posts
    8

    Default

    Quote Originally Posted by rrlanham View Post
    Welcome, Charly,

    It's possible that some device made a request. For example a page with html5 video tags was refreshed. The video tag behavior is to check the stream. If it does not exist there are WARN messages.

    Richard
    Hi Richard,

    Thanks for you answer. So to be more precise, I can see this sequence of logs everywhere in the logs:
    MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: cupertinostreamingpacketizer:542270_1653320_73bd3c12_1_198@85524
    CupertinoPacketHandler.startStream[livestreamiphone/_definst_/542270_1653320_73bd3c12_1_198@85524]
    LiveStreamPacketizerCupertino.resetStream[livestreamiphone/_definst_/542270_1653320_73bd3c12_1_198@85524]
    onConnectStart: 542270_1653320_73bd3c12_1_198@85524
    onConnectSuccess: 542270_1653320_73bd3c12_1_198@85524
    LiveStreamPacketizerCupertino.resetStream[livestreamiphone/_definst_/542270_1653320_73bd3c12_1_198@85524]
    and then 30 seconds after: MediaStreamMap.removeLiveStreamPacketizer[livestreamiphone/_definst_/542270_1653320_73bd3c12_1_198@85524]: Destroy live stream packetizer: cupertinostreamingpacketizer

    I guess that the stream packetizer is destroyed because there is nothing to chunk.

    It might be triggered by a client trying to fetch the stream but if I manually send a stopChunking call to our Wowza api, I don't see anymore this sequence of logs for a specific stream. I'd like to get rid of those stopChunking calls and force wowza to stop chunking a stream which is not live anymore automatically.

    Does it make sense? I'm sorry not to be more precise.

    Cheers,
    charly

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Do you have a "stopChunking" method in a custom module? I don't see that in the Wowza api. Is there some adverse affect to this? Wowza is not packetizing streams that don't exist.

    Richard

  5. #5
    Join Date
    Nov 2012
    Posts
    8

    Default

    Quote Originally Posted by rrlanham View Post
    Do you have a "stopChunking" method in a custom module? I don't see that in the Wowza api. Is there some adverse affect to this? Wowza is not packetizing streams that don't exist.

    Richard
    Yes we have a stopChunking method in a custom module. A colleague gave me the answer that I needed:

    There is no way right now in wowza to remove invalid streams (not found, ended, missing etc.). Until we remove these invalid streams wowza servers will be unnecessary reconnecting to the stream frequently at a rate define by reconnect interval which may freeze wowza. when the stream ends we need to do a stopChunking call which may not ensure clearing all those invalid streams.
    There is no solution except running a background task flushing all the invalid streams.

    Thanks for your help anyway.

    Cheers,
    charly

Similar Threads

  1. Setting up Wowza for HLS chunking and streaming
    By spence in forum General Forum
    Replies: 5
    Last Post: 10-24-2013, 12:07 PM
  2. StartupStreams retries
    By sc4venger in forum Server Administration Discussion
    Replies: 2
    Last Post: 01-09-2013, 06:52 AM
  3. Live stream chunking through different application
    By -TheYOSH- in forum Live Streaming and Encoder Discussion
    Replies: 2
    Last Post: 05-07-2012, 01:55 AM

Posting Permissions

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