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
HTTP Live Streaming (HLS) is here to stay, it works everywhere, high quality and stability, but latency or delays between the stream and the end user can be 60-90 seconds, if you streaming live events that can be a very big issue, imagine Sports betting? But with Wowza Streaming Engine it is possible to reduce the latency to 3 to 5 seconds. It is not good enough but for now there is no other solution.
Below we have some adjustments that using the Wowza Streaming Engine Manage, we can easily improve, although of course there are some negative components.
This risks inherent of the configuration adjustements are due to smaller chunk sizes may result in playback errors if you fail to increase the number of seconds built into the playlist. If a stream is interrupted, and the player requests the next playlist, the stream may be interrupted when the playlist doesn’t arrive.
Additionally, by increasing the number of segments that are needed to create and deliver low-latency streams, you also increase the server cache requirements. To alleviate this concern, ensure that your server has a large enough cache, or built-in elasticity. You will also need to account for greater CPU and GPU utilization resulting from the increased number of keyframes. This requires careful planning for load balancing, with the understanding that increased computing and caching overhead incurs a higher cost of operation.
Lastly, as chunk sizes are smaller, the overall quality of the video playback can be impacted. This may result into either not being able to deliver full 4K video to the player, or small playback glitches with an increased risk of packet loss. Essentially, as you increase the number of bits (markers on the chunks), you require more processing power to provide smooth playback; without it, you get packet loss and interruptions.
A- In Wowza Streaming Engine Manager, click the Applications tab and then click live in the contents panel.
On the details page Properties tab, click Cupertino Streaming Packetizer in the Quick Links bar.
In the Cupertino Streaming Packetizer area, click Edit, and change the values for the following properties:
1- cupertinoChunkDurationTarget- Set the duration of each chunk in milliseconds. The default value is 10000, but the chunkDurationTarget must be smaller to reduce the latency of Apple HLS streams. For a one-second chunk size, set the value to 1000.
2- cupertinoMaxChunkCount- Sets the maximum number of chunks Wowza Streaming Engine stores in the available chunk list. The default value is 10, but for reduced latency streaming we recommend storing 50 seconds worth of chunks. For one-second chunks, set the cupertinoMaxChunkCount to 50; if you’re using half-second chunks, the value should be doubled (100).
3- cupertinoPlaylistChunkCount- Sets the number of items returned to the player in the playlist. The default value is 3, but for reduced latency streaming we recommend returning 12 seconds of data to the player. This prevents the loss of chunks between chunklist requests. For one-second chunks, set the cupertinoPlaylistChunkCount to 12; if you’re using half-second chunks, the value should be doubled (24).
B- On the Properties tab, click Customin the Quick Links bar.
In the Custom area, click Edit.
Click Add Custom Property, specify the following custom property settings in the Add Custom Property dialog box, and then click Add:
1- In Path, select /Root/Application/LiveStreamPacketizer.
2- In Name, enter cupertinoMinPlaylistChunkCount.
3- In Type, select Integer.
4- In Value, specify the minimum number of chunks required before Wowza Streaming Engine provides a playlist to the player. The default value is 1, but for reduced latency streaming we recommend requiring a minimum of 6 seconds worth of chunks. For one-second chunks, set the cupertinoMinPlaylistChunkCount to 6; if you’re using half-second chunks, the value should be doubled (12).
Click Save and restart the application to apply the changes.
Done, try now. Or just contact Hosting Marketers and order our RTMP Wowza with our shared hosting Wowza Engine.
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.
After you order TV Station you will receive an email with the link to the wowza control panel and login information, login to the control panel click on the overview icon and you enter your service overview:
click on the image to see the full picture.
There are a number of links on the right menu, configure, restart, stop, reporting, TV Station, File manager and player links.
I suggest you don’t make any changes on the configuration, the important buttons are “File Manager” were you upload your video files, and “TV Station” were you create a playlist and schedule when to start it date and time and when to stop it. You should create 2 or 3 playlists.
Reporting will give you information on the videos seen, traffic, connections and so on. On the top menu there are some links which provide information on how many viewers you have online which countries and bandwidth used.
Click on File Manager to upload or drag your videos to the server. Videos must be in flv or mp4 format. You can use a ftp software to upload the videos, but the but click on the video and drag it to the server is probably easier.
Now go back to Service Overview and click “TV Station”
on the TV station page you create a playlist, and schedule the date and time to start and date and time to stop. Add the videos and save the playlist, after that you need to restart the service so changes take effect.
When adding the videos you will see on the left the videos uploaded “Available Media” and you need to move the ones you want to the right “Build Your Playlist” some videos may have a exclamation mark, that means the bitrate on the video is higher then the allowed on your package, you better delete this videos from the server and convert them again with the correct bitrate.
after you moved the videos you want to your playlist, save it then restart the server, now at schedule time your videos will start streaming, we suggest that you create at least 3 or 4 playlists.
Go back to the service and click Media Player so you can grab the jwplayer code to paste it on your site.
But the TV Station is not only schedule playlists, you can interrupt and make a live broadcast, on service overview at the bottom there is the RTMP for the FMLE or wirecast, whatever encoder you use, the stream name, username and the password. For instructions on how live streaming is done see this post.
For further instructions on how to use our wowza control panel check the links below: