Results 1 to 2 of 2

Thread: Understanding the necessary components

  1. #1
    Join Date
    Feb 2013

    Default Understanding the necessary components

    Forgive my ignorance as this is all pretty new to me. We currently use an analog camera, connected to a VBrick that sends an RTSP stream to a Darwin server that servers up a .mov stream that we embed in a web page. That .mov file point a player like QuickTime to view the RSTP stream.

    We are refreshing the solution end to end. We're going digital camera to h.264 encoder to Wowza. That part all makes sense to me. The part that I'm confused about is "what then"? Do I need a "player" like JWPlayer to embed the video in a website? Does the website need to decide what format the device will support or does the player do that (like HLS to iOS and Flash to Windows)?

    This part I know is probably better asked on a JWPlayer forum but is it licensed per server that's doing the embedding or per streaming (aka Wowza) server?

    Thanks for any input,

  2. #2
    Join Date
    Jul 2012


    You are correct, you will need to implement a player technology, like JW Player, that embeds in your website. You can implement Java script that can sense the user agent and deliver the appropriate stream based on the client. This is helpful when having to decide when a client is using Flash in a web browser, an iPhone, or an Android device.

    JW Player 6 provides an HTML 5 fallback option that works well with configuring the same player to work with conventional web browsers and also in iOS. As an example, see this article on How to use Longtail JW Player 6.x with Wowza Media Server.

    Think of Wowza as the mechanism that handles all of the video streams and the web players (like JW Player) and devices (like iOS, Android, etc.) as a separate, but integrated technology.


Posting Permissions

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