Results 1 to 6 of 6

Thread: how to do adaptive bit rate live streaming with multiple SMIL files on edge servers

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Feb 2015
    Posts
    27

    Default how to do adaptive bit rate live streaming with multiple SMIL files on edge servers

    Hi there,

    I want to usee Wowza origin-edge architecture to do adaptive bit rate live streaming. Currently I have one origin server, on which a Wowza transcoder is generating three streams with different bit rates. On the edge server, I created three stream files according to this article
    http://www.wowza.com/forums/content....-repeater-edge

    As far as I know, in the Wowza origin-edge architecture, we can introduce primary and second origin URLS for failover. And the origin URLs can be easily added on Wowza Engine manager webpage. It looks like this

    Primary Origin URL
    wowz://origin_server_ip:1935/applicationname
    Secondary Origin URL
    wowz://redundant_origin_server_ip:1935/applicationname


    I tried creating a second SMIL file containing streams from a redundant origin server and adding this second SMIL file to the origin URL. It doesn't work. My goal is that: when the origin server dies, the edge server can automatically switch to another SMIL file.

    Could anyone teach me how to introduce the second origin server into this architecture?

    Thanks!
    Yorick

  2. #2

    Default

    Yorick, you will need to follow this guide:
    How to create and play SMIL files with streams created by Wowza Transcoder

    NGRP do not get forwarded to the edge. The idea is that with this tool you can create a SMIL from using the medialist tool on the origin and create a file that you host in the content folder on the edge.

    Regards,

    Salvadore

  3. #3
    Join Date
    Feb 2015
    Posts
    27

    Default

    Hi Salvadore,

    I read that article and created a SMIL file on the origin server. But what do you mean by saying "and create a file that you host in the content folder on the edge."?

    Thanks!
    Yorick

  4. #4
    Join Date
    Sep 2011
    Posts
    1,933

    Default

    Hi,
    If you're using a .stream file to get the streams from the origin to the edge server it does not use the Primary or Secondary Origin URL.
    The stream will be published on the edge as it's own stream and the edge application should be "live" which means it will packetize the stream itself as the origin would do.

    To achieve adaptive bitrate (ABR) streaming with these streams from the Transcoder (on the origin) you will only reference the streams using a .smil file on the edge server.
    As the streams now being published on the edge will be called, for example, livestream_source.stream, livestream_360p.stream and livestream_160p.stream, the .smil file will need to use these stream names.

    In this scenario you're re-streaming a live source similar to how re-streaming from an IP camera works, the only difference being the multiple streams created will be keyframe aligned so they can be used for ABR streaming.
    Each edge server will need to have the same .stream files (livestream_source.stream, livestream_360p.stream and livestream_160p.stream) and .smil file in it's content directory.

    Regards,
    Jason

  5. #5
    Join Date
    Feb 2015
    Posts
    27

    Default

    Hi Jason,

    Thank you for your reply. But I want to use multiple origin servers and once an origin server dies, all the edge server "automatically" switch to the next origin server. I guess I can create multiple .smil files on the edge servers, each .smil file containing key frame aligned streams from an origin server. But when the currently working origin server falls down, I have to tell our clients to manually enter another URL and refresh their browsers (http://edge_server_ip:1935/applicati.../playlist.m3u8), which is not "automatic failover".

    Thanks,
    Yorick

  6. #6
    Join Date
    Sep 2011
    Posts
    1,933

    Default

    Hi,
    Using the live stream repeater Origin/Edge setup the edge will use the Primary Origin URL and if it doesn't receive a response, it will switch to the Secondary Origin URL. This does not mean that the clients connected at that time will automatically receive the new stream, they will have to connect to the edge server again as the stream will have stopped when the Primary Origin stopped responding in this scenario which will cause the client to disconnect.

    Regards,
    Jason

Similar Threads

  1. Add Text or Image Overlay to Adaptive Bit Rate SMIL file
    By nthoeming in forum Video On Demand Streaming Discussion
    Replies: 4
    Last Post: 07-10-2014, 09:38 PM
  2. Doubts in Adaptive Bit-rate Streaming
    By king407 in forum Tutorials
    Replies: 4
    Last Post: 06-12-2014, 09:25 AM
  3. Replies: 3
    Last Post: 01-10-2014, 10:46 AM
  4. can RTMP use nrgp for adaptive bit rate streaming?
    By andy_c in forum AddOn: Transcoder
    Replies: 9
    Last Post: 08-22-2013, 06:39 PM
  5. iOS Adaptive Bit Rate streaming using Smil file problems
    By grantk in forum AddOn: Transcoder
    Replies: 4
    Last Post: 05-23-2012, 01:18 PM

Posting Permissions

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