Sometimes you need to calculate the bitrate (in kbps) of a live stream to restrict the usage or manage to the bill of the user. As of today, there is no direct way to get the bitrate of a live stream in Red5 open source or Red5 Pro. Instead, you can use this old-school sampling technique to estimate the bitrate of a live stream which can be coded in any language for any platform.
The steps involved in evaluating the bitrate cab roughly be written as in the following manner :
On application startup, start a timer which will be running continuously (every 2 seconds), aiding in evaluation of bitrates of all candidate streams taken fro a list.
Detect publish start for a new stream
On publish start add the stream to a list as a candidate for evaluation
For each evaluation cycle inside the timer calculate the current estimated bitrate using bytes-transferred-inwards data
Store the evaluated bitrate sample in a tmp data structure. In the similar way capture about 4 or 6 data samples.
Take the average of all the data samples collected to get a average bitrate
Finally use this average bitrate data to calculate bitrate per second.
On unpublish remove the stream from list of candidates so that we dont get a NullPointerException
The code snippet below demonstrates how to calculate and log the average bitrate of a live stream in Red5.
The latest version of Wowza adeptly supports SRT ingest. Here is an article from Wowza that explains how to publish an SRT stream from Wirecast and get it into Wowza through Mediacaster. It is a fairly simple step by step to getting started with SRT. But now we are left with the dilemma of how to detect this on the server-side within a module. In other words how to know in a module if the publishing stream is an SRT stream or not. Here is a code snippet from the onPublish method of an IMediaStreamActionNotify implementation that demonstrates how to check if the stream is an SRT stream.
Reading configuration files from the conf directory within a module is a very common occurring in wowza. the following code snippet shows how to read a text file as string from the conf directory. If the file does not exist the code throws an IOException. this example makes use of the environment variable WMSCONFIG_HOME,
* Read a text file as string from the wowza conf directory give the filename
* @param filename file name of the file to read
* @throws IOException
private String readFileFromConfigDirectory(String filename) throws IOException
String conf_home = System.getenv("WMSCONFIG_HOME");
File conf_dir = new File(conf_home + File.separator + "conf");
// read the file contents here
File file_to_read= new File(conf_dir.getAbsolutePath() + File.separator + filename);
String content = new String(Files.readAllBytes(Paths.get(file_to_read.getAbsolutePath())));
throw new IOException("oops! file "+filename+" not found!!");
throw new IOException("oops! conf directory was not found!!");
Often we see ourselves troubled by latency issues in live streaming. There are several options to reduce latency…starting from finetuning broadcast settings to switching protocols. Irrespective of the steps taken, it is sometimes preferable to evaluate the latency in a simple way that is admissible to our eyes. In this video, we see how to use embedded timecodes to evaluate actual real-time latency in a live stream. <!–more–>Such testing is encouraged during development stages but might not be best for production.