Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: mediastreamvalidator media segment bandwidth exceeded

  1. #1
    Join Date
    Apr 2014
    Posts
    19

    Default mediastreamvalidator media segment bandwidth exceeded

    I am using a transcoder stream name group for Apple HLS streaming. It works, but the Apple mediastreamvalidator tool doesn't like the reported bitrate in the playlist vs. the actual average bitrate ie. it is exceeded by more than 10%. Is there a way that I can change the bitrate tag in the playlist to be different than what the transcoder is targeting, or otherwise fix this problem? Thank you

  2. #2

    Default

    If you adjust the system-bitrate to what the validator is reporting, you won't get that warning.

    Salvadore

  3. #3
    Join Date
    Apr 2014
    Posts
    19

    Default

    Quote Originally Posted by salvadore View Post
    If you adjust the system-bitrate to what the validator is reporting, you won't get that warning.

    Salvadore
    Sorry, does that mean I need to use a SMIL file? Right now I'm just using a transcoder stream name group and I can't find any examples where the system-bitrate is configured in a transcoder template.
    Last edited by aegeli; 04-11-2014 at 09:09 AM.

  4. #4

    Default

    Yes, you will need to do this test within a .smil file.

    Salvadore

  5. #5
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    It is difficult to say why the ngrp MediaList system-bitrate is not agreeing with the validator, but reverting to a smil to give you the control you need to adjust to it is a good solution.

    Richard

  6. #6
    Join Date
    Apr 2014
    Posts
    19

    Default

    I have a large number of streams and by using 'ngrp', I can easily make one template that can be used for all of the streams by string matching in the URL. It looks like with SMIL files I have to actually go and make a SMIL file for every single stream, and if I want to change the settings, I would have to change all of the SMIL files for every stream. So it's really too bad that I can't do this with ngrp

  7. #7
    Join Date
    Apr 2014
    Posts
    19

    Default

    For the first ~5 segments after the stream starts, the bandwidth used is greatly higher. For example I have a stream that passes validation when I set the SMIL bitrate to 63Kbps, but it fails if I try to validate soon after the stream is started, with bitrates of around 180-200Kbps. Why does this happen?

  8. #8
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    It would probably have something to with the source. The bitrate of Wowza Trancoder renditions are variable but constrained within limits. If you enable "cupertinostreamingpacketizer" in the Application.xml /LivestreamPacketizers list (or in the Manager Application setup), then Wowza will log the first 10 chunks it packetizes for HLS, and you can look at those in the log file, see how many audio, video and key frames (a/v/k) are in each chunk, and their duration, Or you can use JW player's HLS playback and look at details of each .ts chunk in the Console > Network tab, which is nice because you can see size and download time, and you can download the chunks directly.

    You can look at chunks being created from the source, and ones created from a rendition. You might look at source with Transcoder turned off, and look at one rendition at a time when you turn it on

    Richard

  9. #9
    Join Date
    Apr 2014
    Posts
    19

    Default

    Thank you. I have been looking at the log trying to find useful information, but if it's there I don't know how to see it. This is the log of the packets being made; 22503.stream is the source and 22503.stream_050 is transrated to 50 Kbps video.

    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.init[mobile-phone-hls/_definst_/22503.stream_050]: chunkDurationTarget: 10000	-	-	-	4.566	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.init[mobile-phone-hls/_definst_/22503.stream_050]: audioGroupCount: 3	-	-	-	4.566	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.init[mobile-phone-hls/_definst_/22503.stream_050]: playlistChunkCount:3	-	-	-	4.567	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	MediaStreamMap.getLiveStreamPacketizer[mobile-phone-hls/_definst_/22503.stream_050]: Create live stream packetizer: cupertinostreamingpacketizer:22503.stream_050	-	-	-	4.567	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	CupertinoPacketHandler.startStream[mobile-phone-hls/_definst_/22503.stream_050]	-	-	-	4.568	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.handlePacket[mobile-phone-hls/_definst_/22503.stream_050]: Video codec:H264 isCompatible:true	-	-	-	4.569	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:21	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.handlePacket[mobile-phone-hls/_definst_/22503.stream_050][avc1.66.21]: H.264 Video info: {H264CodecConfigInfo: codec:H264, profile:Baseline, level:2.1, frameSize:320x240, displaySize:320x240, frameRate:12.0, PAR:1:1}	-	-	-	4.57	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:23	PDT	comment	server	INFO	200	-	firstPacket: TCP:$1	-	-	-	6.257	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:31	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:1 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10397	-	-	-	13.97	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:31	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:1 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10397	-	-	-	14.763	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:41	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:2 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	24.333	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:42	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:2 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	25.115	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:51	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:3 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	34.598	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:11:52	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:3 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	35.398	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:02	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:4 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	44.918	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:02	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:4 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	45.677	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:12	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:5 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	55.276	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:13	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:5 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	56.03	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:20	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:6 mode:TS[H264,NOAUDIO] a/v/k:0/87/3 duration:7758	-	-	-	63.04	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:20	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:6 mode:TS[H264,NOAUDIO] a/v/k:0/87/3 duration:7758	-	-	-	63.83	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:30	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:7 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10397	-	-	-	73.389	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:31	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:7 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10397	-	-	-	74.182	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:40	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:8 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	83.709	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:41	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:8 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	84.459	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:51	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:9 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	94.072	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:12:51	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:9 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	94.886	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:13:01	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:10 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	104.391	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:13:02	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:10 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10317	-	-	-	105.162	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:13:11	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream]: Add chunk: id:11 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	114.667	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    2014-04-17	14:13:12	PDT	comment	server	INFO	200	-	LiveStreamPacketizerCupertino.endChunkTS[mobile-phone-hls/_definst_/22503.stream_050]: Add chunk: id:11 mode:TS[H264,NOAUDIO] a/v/k:0/116/4 duration:10318	-	-	-	115.439	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
    I tried viewing the stream in safari with JW player and I couldn't see the chunks under Network Requests. Were you talking about the console in Safari or something else?

  10. #10
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    It looks okay. Each chunk is very uniform, most are 10.3 seconds, with 4 key frames, and 116 video frames. They are probably close to the same size. So there is not apparently higher bandwidth. But these chunks are delivered as fast as possible, they are not throttled like RTMP, which might be what you are seeing?

    You can add maxChunkLogCount Property to the Application.xml /LiveStreamPacketizer Properties container set to "0", Wowza will log all chunks (be sure to disable in production), so you can see this data for the entire stream. It looks fairly consistent, but look at the a/v/k and duration numbers to verify.
    <Property>
     <Name>maxChunkLogCount</Name>
     <Value>0</Value>
     <Type>Integer</Type>
    </Property>

    Richard

Page 1 of 3 123 LastLast

Similar Threads

  1. Replies: 14
    Last Post: 03-19-2013, 07:24 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
  •