Results 1 to 4 of 4

Thread: Push publishing origin server to watch server

  1. #1
    Join Date
    Sep 2013
    Posts
    11

    Default Push publishing origin server to watch server

    - Server 1 (origin server)
    Transcoder
    http stream / ngrp

    - Server 2 (watch server)
    not transcoder
    ngrp not working

    Server 1 -> push -> Server 2 (watch server)

    add parameters adaptiveStreaming:true,adaptiveGroups:"all"

    http://watchServer:1935/watch/ngrp:s.../playlist.m3u8
    not working ..

    I want to use the feature in the monitoring server adaptivegroup ..

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

    Default

    Hi,
    The NGRP group will only work when playing the stream from the origin and can't be used on any edges repeating these streams.
    On the edges you will need to use a .smil file for adaptive bitrate (ABR) streaming.

    Please see the How to do adaptive bitrate streaming article for more details.

    Regards,
    Jason

  3. #3
    Join Date
    Sep 2013
    Posts
    11

    Default

    Quote Originally Posted by JasonH View Post
    Hi,
    The NGRP group will only work when playing the stream from the origin and can't be used on any edges repeating these streams.
    On the edges you will need to use a .smil file for adaptive bitrate (ABR) streaming.

    Please see the How to do adaptive bitrate streaming article for more details.

    Regards,
    Jason
    Origin Server content/abr.smil
    Watch server copy origin content/abr.smil
    liverepeater server 1 copy abr.smil
    liverepeater server 2 copy abr.smil
    liverepeater server 3 copy abr.smil
    ..
    ...
    such as ..

    continuous copying method to different servers amateurish..
    streamname.stream file, I need to find a structure that works like.

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

    Default

    Hi,
    If you're using Push Publishing on the Origin to get the streams to the edges you will need a .smil file on each edge server.
    Once you have the .smil file on the edge server it can be copied to the other edges assuming the stream names are the same.

    If you're not familiar with PushPublishing please see the PushPublishing article for details.
    By using PushPublish on the origin this means you're not having to use multiple .stream files on all of the edge servers.

    Regards,
    Jason

Similar Threads

  1. log file on origin server is very large when connect with edge server
    By aiscript in forum Performance and Tuning
    Replies: 1
    Last Post: 10-01-2014, 12:01 PM
  2. Using push publishing plugin with new Wowza Server 3 on Amazon EC2
    By alarge in forum Wowza Media Server 3 for Amazon EC2 Discussion
    Replies: 9
    Last Post: 02-06-2012, 11:38 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
  •