Results 1 to 4 of 4

Thread: How does Wowza determine the frame rate and bit rate of a RTSP stream?

  1. #1
    Join Date
    Nov 2013
    Posts
    5

    Default How does Wowza determine the frame rate and bit rate of a RTSP stream?

    Wowza rookie here and I tried to look for this info in the forum threads...

    I have the following setup:

    source (RTSP h.264) > Wowza > VLC client

    If I have the source adjust the bit rate/frame rate midstream, where and how does Wowza look for these parameters?

    Should the info be in the SDP attribute (a=... sprop-parameter-sets)? Any link to tutorials?

    Appreciate the help!

  2. #2

    Default

    I don't think anything is necessary. Wowza just reflects streams, if the source bitrate changes, Wowza will continue to send that stream with the new settings.

    Salvadore

  3. #3
    Join Date
    Nov 2013
    Posts
    5

    Default

    Quote Originally Posted by salvadore View Post
    I don't think anything is necessary. Wowza just reflects streams, if the source bitrate changes, Wowza will continue to send that stream with the new settings.

    Salvadore
    Any idea why Wowza sends TEARDOWN command almost immediately after the stream PLAY command is sent when the source includes SPS and PPS information in each IDR frame?

    This is the Wowza log just before the stream tear down. Wowza's re-connection attempt will re-establish the session, but then immediately shuts down and just cycles.

    Where else can I look to find more debug information?

    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	  FU-A: tc:629199 st:false	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	rtp[track1:839] {80 60 14 f9 00 09 99 cf 25 71 0f ce 5c 01 e5 21 }	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	  FU-A: tc:629199 st:false	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	rtp[track1:1444] {80 60 14 fa 00 09 99 cf 25 71 0f ce 5c 01 a9 98 }	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	  FU-A: tc:629199 st:false	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	rtp[track1:1444] {80 60 14 fb 00 09 99 cf 25 71 0f ce 5c 01 da 61 }	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	  FU-A: tc:629199 st:false	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	rtp[track1:1250] {80 e0 14 fc 00 09 99 cf 25 71 0f ce 5c 41 d4 e6 }	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	  FU-A: tc:629199 st:false	-	-	-	567.109	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPMediaCaster.streamTimeout[17693510:live/_definst_:test.stream]: timeout:5000 diff:5500 reason:101	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPMediaCaster.resetConnection[17693510:live/_definst_:test.stream]: 	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPMediaCaster.closeRTPSession[17693510:live/_definst_:test.stream]	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	*** RTSPMessageSend ***
    TEARDOWN rtsp://192.168.9.2/live RTSP/1.0
    Session: 1840664311
    CSeq: 5
    	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	DEBUG	200	-	RTPSessionDescriptionDataProviderBasicRTSPWorker.send: command:TEARDOWN
    TEARDOWN rtsp://192.168.9.2/live RTSP/1.0
    Session: 1840664311
    CSeq: 5
    	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPSessionDescriptionDataProviderBasicRTSPWorker.close closeSession	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPUDPTransport.unbind[live/_definst_]: 0.0.0.0/0.0.0.0:7100 sent:0 recv:921	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPSessionTracker.remove[rtsp://192.168.9.2/live]: 0:true	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	IN: UDPHandler: unbind	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	RTPUDPTransport.unbind[live/_definst_]: 0.0.0.0/0.0.0.0:7101 sent:1 recv:1	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	IN: UDPHandler: sessionClosed	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	IN: UDPHandler: unbind	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	comment	server	INFO	200	-	IN: UDPHandler: sessionClosed	-	-	-	567.125	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2013-12-05	19:48:07	CST	unpublish	stream	INFO	200	test.stream	-	_defaultVHost_	live	_definst_	5.969	-	80	null	127.0.0.1	rtsp	-	known	2020592963	1158214	0	66	0	1158214	0	test.stream	-	-	-	-	-	null	null	-	null	-
    2013-12-05	19:48:07	CST	destroy	stream	INFO	200	test.stream	-	_defaultVHost_	live	_definst_	5.969	-	80	null	127.0.0.1	rtsp	-	known	2020592963	1158214	0	66	0	1158214	0	test.stream	-	-	-	-	-	null	null	-	null	-

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

    Default

    It is probably a connectivity issue with the camera. For debugging it is better to revert to INFO level logging, then turn on just RTSP debugging. You can do it in the .stream file:

    {
        uri:"rtsp://192.168.1.100:10000",
        rtpDebugSession:true
    }
    Or add to this Property to the Application.xml /MediaCaster Properties container:

    <Property>
     <Name>debugRTSPSession</Name>
     <Value>true</Value>
     <Type>Boolean</Type>
    </Property>
    Richard

Similar Threads

  1. live stream and frame rate displayed
    By nvanhaute1 in forum Media Players and Devices Discussion
    Replies: 1
    Last Post: 12-02-2013, 11:16 AM
  2. stream frame rate could not be calculated
    By pburke in forum AddOn: Transcoder
    Replies: 2
    Last Post: 09-16-2013, 02:07 PM
  3. Error- Source stream frame rate could not be calculated
    By markmn12 in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 07-23-2013, 07:12 AM
  4. does RTSP/RTP work with adaptive bit rate?
    By ctb041 in forum AddOn: Transcoder
    Replies: 1
    Last Post: 05-11-2013, 07:21 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
  •