- Category: Technology
- Category: Technology
Mediagration develops advanced software for transcoding, managing and streaming video and audio, Web site subscriptions and pay-per-view, pay-per-minute, pay-per-download, pay-per-live event, advanced eCommerce, eLearning, video conferencing, ad monetization.
Mediagration products fall into the following categories:
- Advanced eCommerce
- Pay Per View / Subscription billing
- Media Players
- Media Servers
- Media Integration
Our products are PHP-based, standards-compliant, operate in new or existing Joomla and Wordpress sites. MediaGration's Apache HLSe Setup script permits publishers to host Web sites and stream secure ABR HLSe video - on a single server. MediaGration software exploits Open Source Joomla, Virtuemart, FFMPEG, Video JS, and Apache; enabling publishers to deploy enterprise-class media services, with minimal startup and operational cost.
Our services seek to help our clients translate their eCommerce and streaming media requirements into powerful and cost effective solutions. We'll recommend the best solutions and approach.
- Streaming Media (Live and On-demand)
- Advanced eCommerce Development
- ABR HLSe / MPEG-DASH transcoding
- New Generation Television
- Advanced SEO
- Global Content and Media Management
- Consulting (Technology and Business)
The founders of Mediagration have over 80 years of collective experience in technology; our strengths are:
- Scalable Website Design and Deployment
- Network Design
- IT Security
- Pay Per View/Subscription billing software
- Alternative DRM technology (Simple DRM Plus (TM)
- Streaming Media
- Media Player Development
- Media Server Setup
- eCommerce Software Development'
- Web/Media Security
- Mobile App Development
- Tech Business Start-up Mentoring
Whether you are selling specialized merchandise to a large audience, streaming media, or building a start-up infrastructure that will involve advanced eCommerce, Mediagration has the technology and the knowhow to plan and deploy the required solution. Call or email us today, and let's talk about your plans.
- Category: Technology
In MMCart's transcoding process, the source content is encoded at multiple bit rates after the original video is uploaded, then each of the different bit rate streams is segmented into small multi-second parts. The video is then published on a media server that supports HLS, MPEG-DASH or other HTTP compatible protocol.
The viewing client is made aware of the available streams of differing bit rates, and segments of the streams by a manifest file.
When starting, the client requests the segments from the lowest bit rate stream. If the client finds the download speed is greater than the bit rate of the segment downloaded, then it will request the next higher bit rate segments. Later, if the client finds the download speed for a segment is lower than the bit rate for the segment, and therefore the network throughput has deteriorated, then it will request a lower bit rate segment. The segment size can vary depending on the particular implementation, but they are typically between two (2) and ten (10) seconds.
The underlying benefit of streaming video is that it can be viewed by a customer without having to download a video file. Instead of a large video file, small fragments or segments of media may be transmitted to a media player for playback in order to achieve the same effect. The media must be received as fast of the player plays. Furthermore, because the higher quality content consumes more storage and bandwidth; a faster network connection is able to play higher quality.
Because many customers access the Internet with a variety of devices and connection speeds, ABR was developed to deliver the best quality stream possible at any given time. The introduction of Adaptive Bitrate (ABR) streaming technology has revolutionized the delivery of streaming media. There are two fundamental ideas behind ABR:
Multiple copies of the content at various quality levels are stored on the server.
The client device detects its current network conditions and requests lower quality content when network speeds are slower and higher quality content when network speeds are faster.
These principles are quite simple, but there are many technical challenges involved in producing a functional design for an ABR system. First, the media segments on the server must be created in such a way that the client application is allowed to switch between higher and lower quality versions at any time without seeing a disruptive change in the presentation (e.g. video “jumps” or audio “clicks, pops”). Second, there must be a way for the client to “discover” the characteristics of the ABR content so that it knows what sorts of quality choices are available. And finally, the client itself must be implemented so that it can smartly detect network speed changes and potentially switch to a different quality stream.
Today, a large portion of video streaming over the internet is using one of several ABR formats. Apple’s HTTP Live Streaming (HLS) and MPEG’s Dynamic Adaptive Streaming over HTTP (DASH) are the predominant technologies. Adobe’s HTTP Dynamic Streaming (HDS) and Microsoft’s Smooth Streaming (MSS) were once quite popular, but have fallen out of favor recently. As you can see, most ABR technologies rely on HTTP as the network protocol for serving and accessing data due to the near-ubiquitous support in servers and clients. All ABR technologies specify some sort of descriptive file or “manifest” which describes the locations, quality, and types of content available to the client.
MPEG-DASH was developed through an open, standards-based process in an effort to incorporate input from all industries and organizations that plan to deploy it. CableLabs, once again, played a critical role in representing the needs of our members during this process. We will focus on the details of MPEG-DASH technology for the remainder of the article.
The MPEG-DASH specification (ISO/IEC 23009-1) was first published in early 2012 and has undergone several updates since. As in other formats, media segments are stored on a standard web server and downloaded using the HTTP or HTTPS protocols. While DASH is audio/video codec agnostic, there are profiles in the specification that indicate how media is to be segmented on the server for ISOBMFF and MPEG2 Transport Stream container formats. Additionally, both live and on-demand media types have been given special consideration.
- Category: Technology
With our basic MMCart Apache Package, we include all software and scripts necessary to set up a complete subscription/pay per view streaming media publishing site, supporting upload, transcoding, and sell streaming video from a single server platform; a single Apache server can host all the necessary components for streaming HLSe video and audio.
Upload - Product Creator uploads video/audio files to local or cloud storage
Transcode - Product Creator transcodes uploaded files into multiple ABR HLSe playlists
Media Management - Manage local, remote and cloud media files
Secure Storage - Keyed Access or hotlink protection for all files
Media Billing - Subscription, Pay Per View, Pay Per Minute, etc. billing
Media Server - Apache and FFMPEG perform ABR HLSe streaming
Media Player - API control for Video JS and other free media players
Encrypted Streaming - Configure and enable AES-128 encryption
User Access Control - CAPTCHA protected passwords
eCommerce Storefront - Responsive front end powered by AJAX
Here are the required components:
Apache - Open Source Web server and HTTP media server
CURL - Utility for Linux
Video JS - Open Source Media Player
FFMPEG - Open Source Video Conversion and Transcoding Utility, enables ABR HLSe transcoding
Joomla 3.X (PHP, MySQL)
Virtuemart - Open Source eCommerce
AJAX eShop - Superframework for Virtuemart
MMCart - Pay Per View Media Streaming Component
Apache HLSe Plugin for MMCart
When you purchase an installation package from Mediagration, we'll install the latest versions of all the above software, most of which is free and Open Source.
It should be noted, that MMCart for Joomla can use either native or third-party transcoding services and CDNs. Because there are no recurring costs associated with any of the above software, the MMCart Apache Package offers a significant advantage when compared to other solutions, when it comes to setup and operational costs.
- Category: Technology
In previous times, even a small streaming media publisher would employ two servers in order to power a pay per view or pay per stream or pay per session Web site. These would include:
- Web Server - most often apache or Windows
- Media Server - typically streaming RTMP and flash
For small and medium publishers, the additional cost and management responsibility associated with the care of a media server could be a significant challenge. But many of today's popular Web servers are capable of streaming the popular streaming format, HLS, making it possible for the same server to handle Web documents and stream videos.
MediaGration offers an Apache HLSe setup script; a set of two shell scripts that configure the below two applications:
- FFMPEG - video converter/transcoder, required for Apache HLS
- Apache Web Server - setup for HLS and HLSe streaming
...thus, making it possible for an existing Apache site to host a pay per view Web site, and a streaming media server. The script runs on the Ubuntu and Fedora Linux distributions (2016).
The setup script allows any apache Web site to stream secure HLS videos (HLSe using AES-128 encryption) from the same Apache server that serves their company Web site.
Apache HLS requires that Apache is configured to support HLS streaming and that the video files or m3u8 playlists, be located in a specific directory. Because HLS uses Http to stream video and audio, it doesn't require any type of modification to apache core (one of the most popular Web servers in the industry); it merely needs to be setup properly. In addition to setting up Apache, it installs and configures FFMPEG so that HLS conversion and segmentation is performed properly.
The MediaGration Apache HLSe Setup Script is available in our store; requires root access on Ubuntu or Fedora Linux servers. For other operating systems, contact our consulting service. Read more about it in this article.