Results 1 to 3 of 3

Thread: Adobe HDS over port 80

  1. #1

    Default Adobe HDS over port 80

    We're using adaptive bitrate streaming with JWPlayer. We have it setup to use HDS first, then fallback to HLS, then fallback to progressive download. Everything is working great, but I noticed that even though our ULR for HDS streaming is like this:


    The actual request for the media file is using rtmp, like this and is going over port 1935:

    I want all the traffic going over port 80, so I went in to vhost.xml and removed port 1935 from the list and left only port 80. Now, videos take like 20 seconds to start whereas before they would start in under 2 seconds. Once they're playing everything works great, but that start time is unacceptable. I don't see anything weird in the logs.

    Why is it doing this? Can I force HDS to go over port 80 and get the same performance as port 1935? (not sure why the port would matter).


    Little more info:
    I just looked at the resulting smil file that is served back to the player from wowza and here's what it looks like (I replaced the actual URL with dummy data):

    <meta base="rtmp://<domain>/ApplicationName/_definst_"/>
    <video src="mp4:2013/1358-lawrence_solo/1358_lawrence_1024.LG.mp4" system-bitrate="1956000"/>
    <video src="mp4:2013/1358-lawrence_solo/1358_lawrence_1280.HD.mp4" system-bitrate="2285000"/>
    <video src="mp4:2013/1358-lawrence_solo/1358_lawrence_320.SM.mp4" system-bitrate="751000"/>
    <video src="mp4:2013/1358-lawrence_solo/1358_lawrence_640.MD.mp4" system-bitrate="1451000"/>

    Could the problem be caused by that meta base entry not specifying a port of 80?
    Last edited by seanngreen; 03-14-2014 at 11:18 AM.

  2. #2
    Join Date
    Jul 2012


    Hi Sean,

    Do you have any other service onboard that may be vying for priority on port 80? Perhaps a web server or other app? Typically, Wowza will log a bind error at startup, however, I thought to check on this regardless.

    Does this improve when you append :80 to your RTMP base URL in your SMIL file?


  3. #3


    Hi Tim,
    No, nothing else running on port 80 on the IP I'm using for wowza. The HLS streaming works fine and starts pretty quick on that same IP over port 80.

    Regarding the SMIL file. The one I pasted above is what wowza serves when this URL is requested (notice the jwplayer.smil at the end):

    The actual smil file (1358-lawrence_solo.smil) looks like this:
    <video src="mp4:1358_lawrence_1024.LG.mp4" system-bitrate="1956000"/>
    <video src="mp4:1358_lawrence_1280.HD.mp4" system-bitrate="2285000"/>
    <video src="mp4:1358_lawrence_320.SM.mp4" system-bitrate="751000"/>
    <video src="mp4:1358_lawrence_640.MD.mp4" system-bitrate="1451000"/>

    Little confused about why jwplayer.smil is needed instead of manifest.f4m, so I'm just following what I've found in the documentation...

Similar Threads

  1. Replies: 1
    Last Post: 09-26-2014, 10:55 AM
  2. Problem with Adobe HDS!
    By Atmapuri in forum Wowza Transcoder
    Replies: 4
    Last Post: 07-21-2014, 11:27 AM
  3. Wowza StreamLock RTMPS vs Adobe FMS Protected HDS
    By bennyfatwai in forum AddOn: Other AddOns
    Replies: 2
    Last Post: 09-08-2013, 11:56 AM
  4. Protected Adobe HDS streaming?
    By silver2003tl in forum General Forum
    Replies: 1
    Last Post: 05-15-2013, 04:11 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