• Get Status of Recordings

    You can check the status of a recording by leveraging the HTTP provider provided here and adding a bit of code

  • Script to fetch your s3 objects

    I thought it’d be useful for a small script (in this case php) to fetch your s3 objects. There is a cost involved for each download and API query but this should help those of you whom use s3 for streaming fetch these assets for your website or otherwise.

  • How-to publish to Wowza using FFMPEG

    A simple way to publish a file or live stream to Wowza is to use FFMPEG. This guide will show you some basic steps in doing so.

  • Add CPU and Memory info to your HTTP Provider

    Wowza provides a couple of useful HTTP Providers to obtain serverinfo and connection counts. You could extend those to add some relevant information regarding system resource utilization etc.

  • Build an http provider that lists recordings

    Below is a simple mechanism that will allow you to open up external scripts to seeing what recordings you have in progress.

  • Take a screenshot of a live stream via FFMPEG

    This is a simple technique to grab a screenshot of a live stream.

  • How-to reload properties on-the-fly

    This how-to article will demonstrate a way to get the on-the-fly update property values from a configuration file.

  • Create a simple player for your iOS applications

    This article is to detail how you might go about playing back a stream from within your app using Wowza as your streaming engine.

  • How-To utilize MTR to help realize packet loss

    MTR represents a branch of the traceroute functionality by providing a greater data sample, as if expanding traceroute with ping to obtain realtime results. This utility helps determine if there are potential network related issues in regards to packet loss or configuration problems with routers.

  • How-to use HAProxy with Wowza

    This is a starter guide on how to implement HAProxy with Wowza. There are various deployments around the ‘net that suggest this integration is successful. Despite the obvious bandwidth bottleneck, you can couple several instances of this load balancer together to make a scalable solution.