Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: mpeg2-ts h.264 for BrighSigns

  1. #1
    Join Date
    Oct 2011
    Posts
    20

    Default mpeg2-ts h.264 for BrighSigns

    We are using bright signs for our campus and want to stream to them. We use wirecast to push to an amazon ec2 feed (for our web feed). Does wowza output mpeg2-ts in h.264 codec on it's rtsp feed? see link below:

    http://support.brightsign.biz/entrie...ayers-Support-

    I've also tried outputting straight from wire cast (local rtsp stream), but I'm not getting anything.

    ANy help would be appreciated!

    -Ben

  2. #2
    Join Date
    Jun 2011
    Posts
    1,047

    Default

    Hi,
    There is a way to stream MPEG-TS using RTSP, there are properties discussed in this article here that enable
    this.
    According to your link, HLS is also supported.
    Wowza can deliver HLS streams to supporting HLS players.
    A typical URL would look like this:
        http://[wowza-ip-address]:1935/live/myStream/playlist.m3u8
    There's more information here, on how to playback HLS streams for iOS and other supporting devices

    Daren
    Last edited by daren_j; 03-05-2014 at 10:56 PM. Reason: placed example url in code box

  3. #3
    Join Date
    Oct 2011
    Posts
    20

    Default

    Quote Originally Posted by daren_j View Post
    Hi,
    There is a way to stream MPEG-TS using RTSP, there are properties discussed in this article here that enable
    this.
    According to your link, HLS is also supported.
    Wowza can deliver HLS streams to supporting HLS players.
    A typical URL would look like this:
        http://[wowza-ip-address]:1935/live/myStream/playlist.m3u8
    There's more information here, on how to playback HLS streams for iOS and other supporting devices

    Daren
    Yeah, after MUCH trial and error, I ended up using the HLS. It seems to work well for this application. I just wonder how it will fair during peak network hours.

    I'll be testing this weekend! Thanks for your help!

    -Ben

  4. #4
    Join Date
    Oct 2011
    Posts
    20

    Default

    It looks like this is not a viable option for us. The webstream stops playing sometime after 10 mins.

    Here is our scenario: We use an Amazon Machine Image from wowzas website (launch Sun morn, terminate Sun afternoon), so our options are limited on forcing MPEG2-TS. Can this be done (using the mentioned article above ) with an devpay AMI? I wonder if we need to create our own AMI to launch each weekend? This is getting a little over my experience level, but def up for the challenge...

    TIA.

    -Ben

  5. #5
    Join Date
    Sep 2011
    Posts
    1,920

    Default

    Hi,
    Be sure to restart after editing the application. If you're using Wowza Streaming Engine 4, you can add these Properties using the Wowza Streaming Engine Manager.
    You may need the correct permissions to add Properties, please take a look at the Managing Sign-In credentials in our Quick Start Guide.


    The logging below will only appear when a RTSP client connects to Wowza after configured using Properties in the above MPEG-TS article.

    comment	server	INFO	200	-	RTPPacketizerMPEGTS.handleAMFPacket: mpegtsFlushEveryPacket:true
    tc[0]: 2816:2816:48000
    tc[0]: 2837:2837:48000
    tc[0]: 2859:2859:48000
    The Properties which log the above will need to be set as true for the logging to take place, they are both false by default.

    Regards,
    Jason

  6. #6
    Join Date
    Oct 2011
    Posts
    20

    Default

    Quote Originally Posted by JasonH View Post
    Hi,
    Be sure to restart after editing the application. If you're using Wowza Streaming Engine 4, you can add these Properties using the Wowza Streaming Engine Manager.
    You may need the correct permissions to add Properties, please take a look at the Managing Sign-In credentials in our Quick Start Guide.


    The logging below will only appear when a RTSP client connects to Wowza after configured using Properties in the above MPEG-TS article.

    comment	server	INFO	200	-	RTPPacketizerMPEGTS.handleAMFPacket: mpegtsFlushEveryPacket:true
    tc[0]: 2816:2816:48000
    tc[0]: 2837:2837:48000
    tc[0]: 2859:2859:48000
    The Properties which log the above will need to be set as true for the logging to take place, they are both false by default.

    Regards,
    Jason
    I have tried to get the Streaming Engine Manager to work with Amazon AMIs, but it doesn't come up. It may be as simple as a security port not set, so I'll dig a little...

    - Ben

    //EDITED - I launched our usual DevPay AMI, and it looks like the stream engine manager is disabled on DevPay. I guess I need to call Wowza to see what our best option is.
    Last edited by volkswatson; 03-18-2014 at 08:43 AM.

  7. #7
    Join Date
    Jun 2011
    Posts
    1,047

    Default

    Hi,
    You just need to add a Custom TCP Rule to your Security Group to open port 8088.
    Once that's open, if you you go to http://[YourEC2IPaddress]:8088
    You'll be Presented with the Wowza Streaming Engiine Manager intro page.
    You can skip the intro if you wish and go to the login page.
    Enter username: wowza
    password: (yourAmazonInstance ID) <- get this from your Amazon AWS console)
    You should then be taken to the manager home page.
    You can then configure, as Jason directed, from there.

    Daren

  8. #8
    Join Date
    Oct 2011
    Posts
    20

    Default

    Quote Originally Posted by daren_j View Post
    Hi,
    You just need to add a Custom TCP Rule to your Security Group to open port 8088.
    Once that's open, if you you go to http://[YourEC2IPaddress]:8088
    You'll be Presented with the Wowza Streaming Engiine Manager intro page.
    You can skip the intro if you wish and go to the login page.
    Enter username: wowza
    password: (yourAmazonInstance ID) <- get this from your Amazon AWS console)
    You should then be taken to the manager home page.
    You can then configure, as Jason directed, from there.

    Daren
    Hey Daren,
    Tried this again today after adding the TCp rule and using DevPay AMI again, but nothing happens. I'm thinking the stream manager is disabled in DevPay.

    I used this AMI:

    https://console.aws.amazon.com/ec2/h...i=ami-f50e0f9c

    Which is the first one in the DevPay AMI listing here:

    http://www.wowza.com/forums/content....hine-images%29

    -Ben

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

    Default

    Ben,

    The classic StreamManager is still there, but it uses port 8086:

    http://[wowza-ec2-public-dns]:8086/streammanager/index.html

    The default username is "wowza" and the password is the instanceid. You can change or add in /conf/admin.password file, or in the manager.

    Richard

  10. #10
    Join Date
    Oct 2011
    Posts
    20

    Default

    Quote Originally Posted by rrlanham View Post
    Ben,

    The classic StreamManager is still there, but it uses port 8086:

    http://[wowza-ec2-public-dns]:8086/streammanager/index.html

    The default username is "wowza" and the password is the instanceid. You can change or add in /conf/admin.password file, or in the manager.

    Richard
    Nope. same thing. nothing running on that port either. Both 8088 and 8086 are open.

    http://23.23.114.227:8086/streammanager/index.html

    I'll leave it running for a few hours.

Page 1 of 2 12 LastLast

Similar Threads

  1. H.264 flash works but H.264 MP4 doesn't
    By MAXDigital in forum Live Streaming and Encoder Discussion
    Replies: 2
    Last Post: 08-29-2012, 01:20 PM
  2. Replies: 1
    Last Post: 05-07-2012, 05:29 AM
  3. rtmp H.264 input TO HLS/http (iOs) H.264 out
    By ecropolis in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 05-02-2012, 01:07 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
  •