Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: LiveStreamRecord - Stops for some reason???

  1. #1

    Default LiveStreamRecord - Stops for some reason???

    Hi There,

    I have an XL CPU 64 Bit instance running on AWS EC2 w/ Lickey Licensing.... I'm transcoding usually 6 Streams using the transcoder Add on... I'm also using the LiveStreamRecord Module and HTTP commands via a cron job to start and stop .MP4 recordings which are saving the content into folders created in the [WowzaInstal]/content folder. Each record session is setup for 2 hours at a time at either 1280x720 Res, 2Mbps BR and 12 or 15FPS or 1024x576, 1.5Mbps BR and 15 or 12 FPS. This instance (Northern CA) which I call Transcoder1 is pulling the streams directly from Sony SNC H.264 Network cams located in China and Denmark. Transcoder1 is setup to transcode the source stream to 640x360 (_360p) and 942x530 (_942p). The HTTP command triggers the LiveStreamRecord Module to record the _source stream which is setup to simply pass through the H.264. The _360p and _530p streams are pulled from Transcoder1 by another instance called origin1 which is also running the loadbalancer sender... 10+ Edge servers pull the streams from origin1 and that is working great.

    Now my problem... Unfortunately, I am seeing the recording just stop at random times. In Denmark, we are pulling two streams. It seems that one stream is more stable and records longer than the other before just stopping.

    I'm seeing entries like the following in the error log:

    WARN server comment 2012-03-23 13:45:01 - - - - - 319265.159 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_source
    WARN server comment 2012-03-23 14:00:01 - - - - - 320164.614 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_942p

    WARN server comment 2012-03-24 13:45:01 - - - - - 405664.921 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_source
    WARN server comment 2012-03-24 14:00:01 - - - - - 406564.892 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_942p

    WARN server comment 2012-03-24 13:45:01 - - - - - 405665.124 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear2_source
    WARN server comment 2012-03-24 14:00:01 - - - - - 406565.124 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear2_942p


    I can send you the full log file if you like.... Any assistance or direction you can point me in would be appreciated.

    Thanks,

    Tim

  2. #2

    Default

    I originally posted this issue about a week ago but didn't get a response. I am still seeing the issue. Some log entries that may be relevant from today.


    WARN server comment 2012-04-02 12:45:01 - - - - - 257750.627 - - - - - - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear2_source
    WARN server comment 2012-04-02 13:00:01 - - - - - 258650.818 - - - - - - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear2_942p

    WARN server comment 2012-04-02 12:45:01 - - - - - 257750.368 - - - - - - - - ModuleStreamRecord.stopRec
    ording: stream recorder not found: exp-d-bear1_source
    WARN server comment 2012-04-02 13:00:01 - - - - - 258650.539 - - - - - - - - ModuleStreamRecord.stopRec
    ording: stream recorder not found: exp-d-bear1_942p

    Thanks,

    Tim

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

    Default

    I suspect that there is a network factor. Take a look at ModuleMediaCasterStreamMonitorAdvanced
    http://www.wowza.com/forums/content....onitorAdvanced

    See if that helps keep the IP camera stream better connected.

    Richard

  4. #4

    Default

    Quote Originally Posted by rrlanham View Post
    I suspect that there is a network factor. Take a look at ModuleMediaCasterStreamMonitorAdvanced
    http://www.wowza.com/forums/content....onitorAdvanced

    See if that helps keep the IP camera stream better connected.

    Richard
    Hi Richard,

    Thank you. That is what I suspected the issue to be... I imagine when there are network issues because the ingest servers are 200+ ms away (Northern CA AWS EC2 Region) and the cams in Denmark, the connection gets lost and the recording stops... Thinking out loud and asking a question(s) at the same time,... If I install this new Module suggested (ModuleMediaCasterStreamMonitorAdvanced), does it act more aggressively to reset the stream quicker so that recording doesn't stop? It seems now that recording just stops and the stream just resets itself...

    Thanks,

    Tim

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

    Default

    I guess that will depend on the severity of the problem. This module does add more aggressive monitoring and resetting than default.

    If you are recording several streams at once you might want to add disks in RAID 0 array.

    Richard

  6. #6

    Default

    Hi Richard,

    I added the suggested ModuleMediaCasterStreamMonitorAdvanced module.

    Below are my property settings within the application as well as some access logs data. The streaming video seems to be a bit jumpy... My guess is that wowza is continually resetting the stream. Do you have any suggestions on how I might tweak the settings? This is an XL EC2 instance running the trancoder/tranrate add-on pulling a feed from a Sony SNC H.264 camera without audio. The camera is set to 1024x576, 15fps and 1024Kbps bit rate. The internet access to the camera is 2Mbps uplink speed.

    Thank you,

    Tim


    <!--
    Monitor incoming packets (stream, audio, video) to be sure packets continue to flow from encoder to stream. The
    streamMonitor[type]StartTimeout controls the timeout (milliseconds) for the first packet. The streamMonitor[type]Timeout
    controls the timeout (milliseconds) for packets after the first packet. The stream type refers to a catch all of any packet of
    any type (audio, video, data). If any of these values are set to zero, the test is turned off.
    -->
    <Property>
    <Name>streamMonitorStreamStartTimeout</Name>
    <Value>0</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorStreamTimeout</Name>
    <Value>0</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorVideoStartTimeout</Name>
    <Value>20000</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorVideoTimeout</Name>
    <Value>12000</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorAudioStartTimeout</Name>
    <Value>0</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorAudioTimeout</Name>
    <Value>0</Value>
    <Type>Integer</Type>
    </Property>

    <!--
    Monitor the incoming packet timecodes (audio, video or data) to be sure packets do not arrive out of order or late. The
    streamMonitor[type]TCPosTolerance and streamMonitor[type]TCNegTolerance (milliseconds) values define a sliding window
    based on the timecode of the previous packet. For example if these values are set to -500 and 3000 respectively then the
    timecode difference between the current arriving packet and the previous packet of that type must fall within
    -500 and 3000 milliseconds. If not and streamMonitor[type]TCToleranceEnable is set to true then stream will be considered
    unhealthy and will be reset.
    -->
    <Property>
    <Name>streamMonitorVideoTCToleranceEnable</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
    </Property>
    <Property>
    <Name>streamMonitorVideoTCPosTolerance</Name>
    <Value>3000</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorVideoTCNegTolerance</Name>
    <Value>-500</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorAudioTCToleranceEnable</Name>
    <Value>false</Value>
    <Type>Boolean</Type>
    </Property>
    <Property>
    <Name>streamMonitorAudioTCPosTolerance</Name>
    <Value>3000</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorAudioTCNegTolerance</Name>
    <Value>-500</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorDataTCToleranceEnable</Name>
    <Value>false</Value>
    <Type>Boolean</Type>
    </Property>
    <Property>
    <Name>streamMonitorDataTCPosTolerance</Name>
    <Value>3000</Value>
    <Type>Integer</Type>
    </Property>
    <Property>
    <Name>streamMonitorDataTCNegTolerance</Name>
    <Value>-500</Value>
    <Type>Integer</Type>
    </Property>


    <!--
    Monitors the time difference between the audio and video channel of a stream. If the difference between the currently arriving
    video packet and the previous audio packet (or vice-versa) is greater than streamMonitorAVSyncTolerance and streamMonitorAVSyncToleranceEnable
    is set to true, then the stream will be considered unhealthy and will be reset.
    -->
    <Property>
    <Name>streamMonitorAVSyncToleranceEnable</Name>
    <Value>false</Value>
    <Type>Boolean</Type>
    </Property>
    <Property>
    <Name>streamMonitorAVSyncTolerance</Name>
    <Value>1500</Value>
    <Type>Integer</Type>
    </Property>

    <!--
    If set to true, then when a stream is reset and it belong to a MediaStreamNameGroup all streams in the group will be reset. If
    false only the unhealthy stream will be reset.
    -->
    <Property>
    <Name>streamMonitorResetNameGroups</Name>
    <Value>false</Value>
    <Type>Boolean</Type>
    </Property>

    <!--
    Turns on debug logging of the monitoring.
    -->
    <Property>
    <Name>streamMonitorDebug</Name>
    <Value>false</Value>
    <Type>Boolean</Type>
    </Property>
    </Properties>


    Some Access Logs Data:
    us-redwoods1_360p]: Add chunk: id:6 a/v/k:0/150/5 duration:10067 - - - 157630.75-
    2012-04-12 18:01:58 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:6 a/v/k:0/151/5 duration:10067 - - - 157631.05-
    2012-04-12 18:01:58 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:6 a/v/k:0/150/5 duration:10067 - - - 157631.05-
    2012-04-12 18:02:07 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:7 a/v/k:0/151/5 duration:10000 - - - 157639.761 --
    2012-04-12 18:02:07 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:7 a/v/k:0/150/5 duration:10000 - - - 157639.76-
    2012-04-12 18:02:08 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:7 a/v/k:0/151/5 duration:10000 - - - 157640.52-
    2012-04-12 18:02:08 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:7 a/v/k:0/150/5 duration:10000 - - - 157640.52-
    2012-04-12 18:02:08 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:7 a/v/k:0/151/5 duration:10000 - - - 157640.82-
    2012-04-12 18:02:08 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:7 a/v/k:0/150/5 duration:10000 - - - 157640.82-
    2012-04-12 18:02:08 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:7 a/v/k:0/151/5 duration:10000 - - - 157640.82-
    2012-04-12 18:02:08 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:7 a/v/k:0/150/5 duration:10000 - - - 157640.82-
    2012-04-12 18:02:17 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:8 a/v/k:0/151/5 duration:9967 - - - 157649.741 --
    2012-04-12 18:02:17 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:8 a/v/k:0/150/5 duration:9967 - - - 157649.742 --
    2012-04-12 18:02:18 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:8 a/v/k:0/151/5 duration:9967 - - - 157650.51-
    2012-04-12 18:02:18 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:8 a/v/k:0/150/5 duration:9967 - - - 157650.51-
    2012-04-12 18:02:18 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:8 a/v/k:0/151/5 duration:9967 - - - 157650.74-
    2012-04-12 18:02:18 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:8 a/v/k:0/150/5 duration:9967 - - - 157650.74-
    2012-04-12 18:02:18 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:8 a/v/k:0/151/5 duration:9967 - - - 157650.74-
    2012-04-12 18:02:18 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:8 a/v/k:0/150/5 duration:9967 - - - 157650.74-
    2012-04-12 18:02:27 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:9 a/v/k:0/151/5 duration:10000 - - - 157659.721 --
    2012-04-12 18:02:27 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:9 a/v/k:0/150/5 duration:10000 - - - 157659.72-
    2012-04-12 18:02:28 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:9 a/v/k:0/151/5 duration:10000 - - - 157660.51-
    2012-04-12 18:02:28 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:9 a/v/k:0/150/5 duration:10000 - - - 157660.51-
    2012-04-12 18:02:28 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:9 a/v/k:0/151/5 duration:10000 - - - 157660.81-
    2012-04-12 18:02:28 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:9 a/v/k:0/151/5 duration:10000 - - - 157660.81-
    2012-04-12 18:02:28 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:9 a/v/k:0/150/5 duration:10000 - - - 157660.81-
    2012-04-12 18:02:28 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:9 a/v/k:0/150/5 duration:10000 - - - 157660.81-
    2012-04-12 18:02:37 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:10 a/v/k:0/150/5 duration:10066 - - - 157669.73-
    2012-04-12 18:02:37 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1]: Add chunk: id:10 a/v/k:0/151/5 duration:10066 - - - 157669.731 --
    2012-04-12 18:02:37 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:10 a/v/k:0/151/5 duration:10066 - - - 157670.48-
    2012-04-12 18:02:37 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_source]: Add chunk: id:10 a/v/k:0/150/5 duration:10066 - - - 157670.486 - - - - - - - - - - - - - - - - - - - - - - - - -
    2012-04-12 18:02:38 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:10 a/v/k:0/151/5 duration:10066 - - - 157670.78-
    2012-04-12 18:02:38 UTC comment server INFO 200 - LiveStreamPacketizerSanJose.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:10 a/v/k:0/151/5 duration:10066 - - - 157670.78-
    2012-04-12 18:02:38 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_942p]: Add chunk: id:10 a/v/k:0/150/5 duration:10066 - - - 157670.78-
    2012-04-12 18:02:38 UTC comment server INFO 200 - LiveStreamPacketizerCupertino.endChunkTS[transratelive/_definst_/exp-us-redwoods1_360p]: Add chunk: id:10 a/v/k:0/150/5 duration:10066 - - - 157670.78-

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

    Default

    I don't see re-setting in the log snip, which looks okay, no evident problems.

    It shows chunk size of about 10 seconds, which follows key frame frequency. Try reducing key frame frequency to 2 seconds

    Richard

  8. #8

    Default

    Quote Originally Posted by rrlanham View Post
    I don't see re-setting in the log snip, which looks okay, no evident problems.

    It shows chunk size of about 10 seconds, which follows key frame frequency. Try reducing key frame frequency to 2 seconds

    Richard
    Key frame is set to 2 seconds... Strange. What would I be looking for in the logs to see if the stream is resetting?

    Thanks again,

    Tim

    [IMG]/Users/Tim/Desktop/CamSettings.png[/IMG]

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

    Default

    Does reducing bitrate help? It might just be bitrate too high.

    Is playback in Flash client okay?

    Also, see if reducing cupertinoChunkDurationTarget following this guide helps:
    http://www.wowza.com/forums/content....rameters-(iOS)

    With key frame frequency of 2 seconds, following that guide, you could set cupertinoChunkDurationTarget to 2000, 4000, 6000, 8000. Default is 10000, which is what is showing in the log output.

    Richard

  10. #10

    Default

    Quote Originally Posted by rrlanham View Post
    Does reducing bitrate help? It might just be bitrate too high.

    Is playback in Flash client okay?

    Also, see if reducing cupertinoChunkDurationTarget following this guide helps:
    http://www.wowza.com/forums/content....rameters-(iOS)

    With key frame frequency of 2 seconds, following that guide, you could set cupertinoChunkDurationTarget to 2000, 4000, 6000, 8000. Default is 10000, which is what is showing in the log output.

    Richard
    I will try reducing the bitrate and the cupertinoChunkDurationTarget.

    Curious.. why do you believe that reducing the bitrate would help? I figured lowering the max bitrate in the camera would cause more problems. Meaning.. for example - if sending good quality video at 15fps and 1024x576 res required more than 768Kbps bit rate and the camera was set to a max bit rate of 768Kbps... The video would look jumpy or pixelate???

    Thanks again,

    Tim

Page 1 of 2 12 LastLast

Similar Threads

  1. LiveStreamRecord - app stop recording for no reason
    By Volive in forum AddOn: Other AddOns
    Replies: 3
    Last Post: 10-09-2012, 05:24 PM
  2. LiveStreamRecord Module - Recording randomly stops
    By IPVSINC in forum AddOn: Other AddOns
    Replies: 1
    Last Post: 06-08-2012, 08:26 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
  •