Re-stream RPT to HTTP Live streaming

[Richard_Lanham]

If you are doing origin-edge (?) and this is a liverepeater-edge, yes, use the appropriate LiveStreamPacketizer

With the auto-generate you don’t need a smil file if you play one video that has an 64kbs AAC audio track. Wowza auto-generates it. You can use a smil where one video has the 64kbs AAC audio track that you mark with wowza-audio-only=true, but you wouldn’t also make its system-bitrate 64000. In your example above, you might as well not use the smil.

Richard

[Richard_Lanham]

On the edge, only use cupertinostreamingrepeater. Remove the others.

Completely take out the auto-generate configuration since you don’t need it. Use the smil item pointing to the 64kbs audio stream, as you were doing but without the wowza-audio-only=“true”

Richard

[Richard_Lanham]

The StreamType should be “liverepeater-edge”

Richard

[Richard_Lanham]

For Wowza’s role in your process, this is the essential guide:

https://www.wowza.com/docs/how-to-publish-and-play-a-live-stream-mpeg-ts-based-encoder)

Richard

[Richard_Lanham]

You see “killed” in the logs, as below?

Wowza only logs the first few chunks. But chunking should continue.

Richard

[Richard_Lanham]

Great, thanks for the update, glad it’s working.

Richard

[Ian_Beyer]

One way to test it in a browser would be to use Safari and an HTML5

http://www.w3schools.com/html5/tag_video.asp

If you do src=“http://…m3u8”, you should be able to see the HLS video. Only works in Safari/Mac, though, and you need a pretty recent version of OSX.

[Ian_Beyer]

Thanks for the info!

[rich_mavrogeanes]

See http://discovervideo.com/transcoder

Now working with adaptive bit rate streaming (Smoothstreaming)

[rich_mavrogeanes]

ping me at rmavro@discovervideo.com and I’ll send you a live link. Don’t want to post it here (it is bandwidth limited right now).

[Sergey_Bolbat]

Thanks for the reply.

Original RTP stream is encoded as H.264/MP3, I’m not sure that iPhones would “understand” this, but I’m ready to try.

As I understood you the right way, you’re advicing to use this guide: http://www.wowza.com/quickstart_2_1_2.html#live-ip-camera step-by-step, but enabling cupertino and streamer, right? Is that guide is fully for me?

Could you advice, how to set Wowza for listening 8888 RTP stream on port? I should put rtp://@:8888 into [install-dir]/content/camera.stream?

Thanks again.

[Sergey_Bolbat]

Ok, now that’s what I’ve done.

I’ve followed this guide: https://www.wowza.com/docs/how-to-publish-and-play-a-live-stream-mpeg-ts-based-encoder - it contains rtp stream as input and mpeg-ts stream as output, so I’ve decided to use this guide.

In step: “4. Using a text editor create the file [install-dir]/content/mpegts.stream set the contents of this file to udp://0.0.0.0:10000 (if you are receiving a multicast stream, change the 0.0.0.0 part to the multicast address of the stream)”

I’ve typed rtp://0.0.0.0:8888

I made everything the same as in that guide and when I’m trying to open http://[wowza-address]:1935/live/mpegts.stream/playlist.m3u8 in browser, it says that page not found.

Why is that? What I’ve done wrong? I’ve opened 1935 port and 8086 - is it necessary to open any other ports?

Original RTP stream is encoded with VLC and it’s H.264/AAC (RTP/MPEG Transport Team as destination).

Help me if somebody met with such case of using Wowza.

Thanks.

[Sergey_Bolbat]

Thanks to everybody who helped me.

I’ve done it - with the guide I linked above, I recieve RPT/MPEG-TS packed stream with H.264/AAC and successfully re-stream it to iPhone app.

But there is one more thing - I have mistiming of sound and video. Sound has a delay in ~0.5-0.8 sec. It’s quite a big amount. Is there a way to avoid this?

[Sergey_Bolbat]

Hi again. I’ve done with sound delay and now I’m going to approve my iPhone application.

I’m running media validator and it says that my playlist is wrong. Here are the warnings:

WARNING: INF tag with duration 2 seconds or more above the playlist’s target duration (10.000 seconds).

5: #EXTINF:17,

~~

WARNING: INF tag with duration 2 seconds or more above the playlist’s target duration (10.000 seconds).

7: #EXTINF:18,

~~

WARNING: INF tag with duration 2 seconds or more above the playlist’s target duration (10.000 seconds).

9: #EXTINF:17,

~~

WARNING: Media segment bitrate outside of target playlist bitrate by 78.100 % (113984 vs. 64000 bps, limit is 10 %).

6: media_1709.ts?wowzasessionid=329465679

WARNING: Media segment bitrate outside of target playlist bitrate by 68.377 % (107761 vs. 64000 bps, limit is 10 %).

8: media_1710.ts?wowzasessionid=329465679

WARNING: Media segment bitrate outside of target playlist bitrate by 100.224 % (128143 vs. 64000 bps, limit is 10 %).

10: media_1711.ts?wowzasessionid=329465679

WARNING: INF tag with duration 2 seconds or more above the playlist's target duration (10.000 seconds).

5: #EXTINF:18,

~~

WARNING: INF tag with duration 2 seconds or more above the playlist's target duration (10.000 seconds).

7: #EXTINF:17,

~~

WARNING: INF tag with duration 2 seconds or more above the playlist's target duration (10.000 seconds).

9: #EXTINF:16,

~~

WARNING: Media segment bitrate outside of target playlist bitrate by 49.130 % (95443 vs. 64000 bps, limit is 10 %).

10: media_1712.ts?wowzasessionid=329465679

WARNING: INF tag with duration 2 seconds or more above the playlist’s target duration (10.000 seconds).

5: #EXTINF:17,

~~

WARNING: INF tag with duration 2 seconds or more above the playlist’s target duration (10.000 seconds).

7: #EXTINF:16,

~~

WARNING: Media segment bitrate outside of target playlist bitrate by 46.371 % (93677 vs. 64000 bps, limit is 10 %).

10: media_1713.ts?wowzasessionid=329465679

WARNING: INF tag with duration 2 seconds or more above the playlist's target duration (10.000 seconds).

5: #EXTINF:16,

~~

WARNING: Media segment bitrate outside of target playlist bitrate by 49.681 % (95795 vs. 64000 bps, limit is 10 %).

10: media_1714.ts?wowzasessionid=329465679

WARNING: Media segment bitrate outside of target playlist bitrate by 84.836 % (118295 vs. 64000 bps, limit is 10 %).

10: media_1715.ts?wowzasessionid=329465679

The content of my playlist is (I’ve downloaded it with browser):

#EXTM3U

#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=64000

http://ip:1935/live/mpegts.stream/playlist.m3u8?wowzasessionid=1459010386

How it knows what BANDWIDTH option to use? I didn’t set it up.

Can I modify playlist settings for my stream to be correct? And if yes, then how?

Thanks for the help.

[Sergey_Bolbat]

Huh. I’ve used search and had found that I’m not alone with this problem.

Here are the topics, where was discussed this theme:

iPhone App Rejected -- M3U8 File is invalid

Hi there, I’m having trouble submitting my app to the AppStore. Apple is telling me that I need a baseline stream of 64k in order for my app to be approved for both WiFi and the cellular network (3G, Edge). They told me to download the mediastreamvalidator tool (mac only) to run tests against my streams. To download, go to connect.apple.com, click “Downloads”, click “iPhone”, and click “HTTP Live Streaming Tools (Disk Image)”. In bash, I’m running the following: mediastreamvalidator validat…

https://wowza.com/forums/showthread.php?9099-m3u8-file-issue

I think, the way to solve this problem is making multiple bitrate stream. What program I can use to encode one stream to multiple? And how I should configure this program and Wowza?

Thanks.

[Sergey_Bolbat]

Richard. Great thank you for help.

I’ve made changes that you adviced.

1. I’ve reduced keyframe frequency from 25 to 15 and changed the value of chunkDurationTarget to 15000.

2. I’ve downloaded and extracted zip with patch.

3. I’ve created multi-bitrate using smil with one audio-only stream and audio-video.

After doing all of these operations, I’m starting three streams: audio only, audio+video, smil.

Here is smil text:

[Sergey_Bolbat]

Did you use a text editor for the smil? One possibility is that there are word processor characters in the file.

Richard

Yes, I’ve used nano (linux editor). Just in case, I’ve created it again, using text editor and used option “Convert to UTF-8 without BOM”, but result is the same.

One more thing is this smil doesn’t work it iPhone - iPhone says “Can’t open file”, but I can mark that this smil works properly with application without settings for auto-64K-audio-generating settings in Application.xml.

[Sergey_Bolbat]

By the way, I didn’t paste cupertinostreamingrepeater property - can it be the reason? I’m not sure, if I have repeater or not.

[Sergey_Bolbat]

Richard, here is the scheme:

Server with TV-tuner encodes with VLC video and sends it to my server. It sends two different streams:

1. Audio AAC 64K

2. Video H.264 200K and Audio AAC 40K

On my server, I recieve it on two different udp ports.

My idea is to stream 64K audio for Apple approvement (for 3Gs) and to stream live video for those, who wanna watch normal TV. So, I suggest, I have to use smil so that 3G or GPRS users could listen audio and others could watch TV. Or I’m wrong?

The other way I see is to stream two udp ports to different applications in wowza: one for audio and one for video, without any smil. I dunno what is more right.

So, I wonder, if my server is edge, but I think it is. I’ll try to add “cupertinostreamingrepeater” and let u know the results. Thanks again.

[Sergey_Bolbat]

Well, no, cupertinostreamingrepeater, which I’ve added to cupertinostreamingpacketize r,smoothstreamingpacketizer didn’t help.