Sometimes the player stops and you will see this error
"The media playback was aborted due to a corruption problem or because the media used features your browser did not support."
This could be to a number of causes
Poor Internet connection
Website plugins not supported by browser
Cached data in the system
The video file has a problem
Irrespective of the browser you’re using – Chrome, Mozilla Firefox, or Opera – try the below fixes first to resolve the issue:
Refresh your webpage
Try opening the page in another browser
Check your Internet connection
Delete cookies, cache and browsing history
Disable all plugins on your browser
Restart the browser
If none of the above quick fixes work, there may be some deeper issues with the video.
Copying the link of the stream to VLC I can see the direct m3u8 file is opening in VLC, however the error displayed in Google Chrome is:
ERROR: (CODE:3 MEDIA_ERR_DECODE) The media playback was aborted due to a corruption problem or because the media used features your browser did not support
First what is a RTMP server and even before that what is RTMP?
RTMP (Real-Time Messaging Protocol) is an application-level protocol owned by Adobe. It was originally designed for delivering on-demand media and live media (i.e live audio, video, and data) over the Internet between a Flash player and RTMP Media Server. For example we have the HTMP protocol, that is the sites which you can see on the browser, so the HTMP protocol is for website. While the RTMP is for media, it allows media files, like video, audio, images which can be easily be transferred or streamed by other users.
So the a rtmp server is a normal server, or a vps, which has a rtmp software which can then be used to transfer this media files.
Now the important thing on all this is what is this software? And the main softwares that create the RTMP are
1- Flash Media Server, now changed to Adobe Media Server.
3- Wowza, now called, Live Streaming Engine.
And these are the 3 main RTMP servers or softwares, there are other like Nginx, but not so well known and not really used for production purposes.
How it all started, the RTMP?
It started with Adobe, they the ones who created this software with flash media server, it is a high quality software and it is very expensive, $4500 for the license.
But we must explain the issues with the RTMP, it is very popular some years ago, 2010 and about, every one wanted to make video chats, the problem is that flash is going to be disabled at the end of this year 2020 and video chats with flash will stop working.
But the RTMP has one incredible advantage, it is very fast between servers, a delay of 1 or 2 seconds of latency.
So RTMP will not go out soon because we can use for live streaming from the broadcaster to the server, using the RTMP and then on the server it is distributed on an.y device using instead of RTMP using HLS, which means HTTP Live Streaming.
The latency now is 20-25 seconds, so it cannot be used for video chats but is perfectly alright for live streaming and ondemand video streaming
Then we have Red5, which now has two versions the paid version called Red5 Pro and it is also expensive, difficult to manage but can be used for live streaming and for video chats.
Hosting Marketers uses the free open source software on all our servers, and it was the first shared hosting offering this service.
It is still used on some video chats but not sure what will happen after 2020….
Then we have Wowza, which is the one we mostly use on our RTMP servers, it is very stable, easy to manage and very high quality.
There are many reasons for using Wowza to provide HLS streaming services compared to a generic web server. You’ve essentially listed them yourself, though to provide a few specifics; Wowza’s HLS implementation includes robust DRM functionality, timed data events via ID3 tags, alternative audio tracks. More are listed here.
I would recommend reading our Quick Start Guide which covers the concepts involved. For more detail around the HLS capabilities I’d suggest you try our rtmp free trial account, on our site.
We also use it for live streaming on sports and Church services with live streaming, we adjust the server to reduce the latency, wecan reduce to 5-6 seconds by making some adjustments.
Hosting Marketers policy is that we do not offer discounts on yearly payments we prefer since our founding date to have our customers pay monthly, although we give the option to pay for a number of years. But our policy is that there is no discount with yearly payments, because our prices are already very low compared to other similar companies, and our main customers are experienced webmasters.
But Hosting Marketers in some cases is open to flexible terms, specially is the customer is an old client, we are happy is this case to offer a customized package which benefit the customer. Please contact us if you would like to talk with our sales team.
For RTMP services we also provide some discounts for older customers and even for yearly payments.
Our Price guide for customized package with the service remaining the same bitrate, is to increase $30 for each 100 viewers more up to 600 viewers and below the 720kbps bitrate.
If the same customer at RTMP 100 and he wants to upgrade to 400 viewers, the price would be ($50+ (30 X 3)= $140 a month.
This price of $30 for 100 viewers can be used for any package below 600 viewers, if more then 600 viewers, 100 viewers above this price would be $50 per 100 extra viewers.
Above 1000 viewers, the price would increase to $100 per extra 100 viewers.
In special package with bitrate above 1700kbps the price for each 100 viewers extra is $200 a month, so for example, a customers with the package RTMP 600 at 1700kbps paying $300 a month, if he wants to upgrade to 700 viewers keeping the same bitrate, the new price would be $500 a month. This price seems higher then the previous, this is because the higher bitrate will use much more bandwidth, which is much more expensive.
This is only a guide, if you would like to ask questions or ask for a specific custom package please do not hesitate to email us at
Real-Time Messaging Protocol or RTMP was developed originally by Macromedia, which then became Adobe. It was a system to implement streaming of video, text and audio over the internet between a flash player and a server with the RTMP setup.
Using fragments between the server and the user, it maintains a stable connection and because of that it has low latency, meaning that there is a very short delay, between the server and the user. The delay is perhaps 1 or 2 seconds.
The RTMP servers available are Adobe Media Server, Red5, Wowza Streaming Engine, Nginx RTMP server and a few more, but this 4 are the most common, although Adobe is very expensive and Red5 is difficult, personally I prefer Wowza RTMP, which has a number of advantages, we will talk about this on another post.
Going back to RTMP, it is a TCP-based protocol which maintains persistent stable connections and allows low-latency communication. To deliver streams smoothly and transmit as much information as possible, it splits streams into fragments, and their size is negotiated dynamically between the client and server.
RTMP servers are ideal for live streaming but also for Ondemand video streaming, it is also a necessary component for live video chats.
RTMP Server, how it works
The server must be setup with a media server, like Adobe or Red5, then the video stream connects to the RTMP installed on the server, the video stream could be a laptop with a software installed, this software is an encoder, there are a number of them, OBS Studio, but the most common is the Adobe, FMLE, which you can download free at http://hosting-marketers.com/flashmedialiveencoder_3.2_wwe_signed.msi (for windows computers, Mac computers you can download directly at Adobe site.)
On the encoder you enter the server RTMP, which would be something like this:
Then you connect and start the broadcast. this stream will go directly the RTMP server and you can now setup a player for your users, if you using a RTMP player you will need to use a flash player, but using Wowza Streaming Engine on the RTMP server it converts the stream to a HLS protocol which can be used on many other platforms as well, like smartphones and HTML5 Players. Although the HLS has the latency issue because of the flash players end of live it is nearly impossible not to use it. Nowadays, with a good configuration you can reduce the latency to 3 or 4 seconds.
So we have, YOU on your laptop with a camera and an encoder >>> your internet connection and the RTMP Server connection >>> and finally the player on your site broadcasting your live event. Or your video files.
I suggest you contact us with your requirements, because the bitrate on the packages are not very high and if you going to stream high quality videos you will need higher bitrate, we will customize your package by increasing the bitrate and reducing the number of users allowed.
The formula we use is as below:
package bitrate x viewers allowed = A
A / bitrate requested = new number of viewers
If your wowza package that you want to order is Wowza 300 you allowed 512kbps.
so you will have 2000kbps bitrate and 77 max. viewers.
Now for the instructions how to Stream to Roku using Wowza streaming engine.
So lets say you want to stream videos, you will need to order Ondemand Streaming. After you order and agree on the bitrate upload a few videos files in MP4 format and slightly below the bitrate allowed. Your HLS URL for any of your videos would be something like this
you will have your HLS URL from your wowza control panel, on it should click on “Media Player” and you will have on the left a player and on the right the code for the player, copy it to a notepad and find on it the “sourceURL” that will be it for the sample file. replace the sample file with the name of your uploaded video. For instructions on setting up the ondemand streaming check the tutorial here.
Now lets go basic instructions for packaging and uploading your application and creating a private channel on a Roku set-top box to stream videos from our Wowza to the Roku device.
If your stream only uses AC3 surround sound audio, set the Roku Audio mode (found in Settings > Audio > Audio) to Auto. If Audio is set to Stereo and the stream only contains AC3 audio, users unable to playback surround sound will not hear audio in the stream. Viewers can identify if their HDMI device can decode Dolby Digital AC3 surround sound by looking for a (DD) or (DD+) label next to the Autosetting. To increase accessibility of your stream, make sure you have both stereo and surround sound audio tracks in your stream.
Navigate to the Packaging Your Application section of the Roku SDK documentation, and then follow the instructions to set up a DevID and Password. These credentials are used when packaging your application before uploading to a channel.
Unzip the RokuSDK/examples/zips/simplevideoplayer.zip example and edit the simplevideoplayer/source/appMain.brs file as follows:
Comment out the following lines using an apostrophe (‘) character:
Uncomment and modify the following lines so that the urls line matches the one below:
' a test stream from Wowza
urls = ["https://11234566777778.streamlock.net:1937/8XXX/mp4:video.mp4/playlist.m3u8"]
qualities = ["SD"]
streamformat = "hls"
title = "my video file"
srt = ""
Note: To play your own content, change the urls value to the playlist URL of your content.
Select all files in the simplevideoplayer folder and compress these files (not the folder itself) into a zip file to upload to the Roku box.
Follow the Run the package Utility instructions in the Packaging Your Application section of the Roku SDK documentation to upload your package zip file and register your application to the Roku player. After successfully uploading the application to the Roku box, the application will show up as a channel.
After completing these steps, a prompt to run your application appears on your Roku box. After the application is running, you can refer to the Roku SDK documentation for information on how to set up a private channel and make it accessible to users to subscribe.