Axinom Encoding is a highly scalable and flexible cloud encoding and packaging service. It offers a number of advantages that make it unique:
Supports modern packaging formats HLS, DASH, and CMAF
Enables DRM protection for Google Widevine, Apple FairPlay, and Microsoft PlayReady
Offers the best protection by enabling separate encryption keys for each video quality level and audio
Scales fast. Can encode hundreds of videos in parallel
Comes with a fully documented, developer-friendly Web API
Supports a broad variety of input formats
"Axinom VIP" was a previous name of Axinom Encoding before it was renamed in 2021.
Trivia: "VIP" is an abbreviation for "Video Ingest & Processing".
Processing an encoding job could take minutes or even hours. The job execution happens asynchronously. It involves several distinct phases, such as pre-validation, acquisition, media mapping, encoding, DRM protection, packaging, image extraction, and publishing. Read more about the different phases from the Axinom Encoding Overview article.
Axinom Encoding currently supports creating H.264/AAC and H.265/AAC adaptive bitrate streaming assets.
As input, it supports a broad variety of codecs and containers. Please find more information here:
Axinom DRM supports DRM protection across all output formats.
It offers granular control over the encryption process. Axinom Encoding offers important features to satisfy the latest content owner requirements:
Supports several content keys per asset
Separate content keys for different video quality levels
Separate content keys for audio
Uses modern CPIX standard for secure key material exchange
The supported subtitles formats include WebVTT, TTML, SubRip (SRT), and PAC.
The encoded video, audio, and subtitles could be packaged as MPEG DASH, HLS, or CMAF. The exact format is specified in the ContentProcessing section of a job description. Read more about content processing from the respective article.
One of our key goals for Axinom Encoding is interoperability. Another one is making it super easy for developers to integrate.
Axinom Encoding has a developer-friendly Web API and comes with comprehensive documentation and sample code. It supports standards, like CPIX, to ensure seamless integration. It also supports all major tools and protocols for acquiring source content and delivering the resulting output to its destination.
On top, we offer free evaluation of Axinom Encoding. Give it a try!
To encode a video without audio, you need to use a small inaudible (silent) audio file with the video. The audio track does not need to be the same length as the video. For instance, the audio track could be 1 second in length.
This approach also requires you to use the "AudioFileLanguageExpression" property inside the "MediaMappings"section of the job request. In such a case, the output would be a video stream as well as an audio stream, although the audio would be inaudible.
Read more about media mappings here: Media Mappings page.
Embedded audios in video streams are supported and extracted as required. To encode a video with embedded audio, i.e. without a separate audio track, remove the AudioFileLanguageExpression property from the MediaMappings section of the job request. If the Axinom system supports the video file, it should automatically detect and map the embedded audio tracks. Each embedded audio stream must have a language tag with a valid language code in the metadata.
Read more about Media Mappings from the documentation.
Axinom Encoding does not provide the functionality to encode an audio track only. It always expects a video track. To encode audio without video, you should simulate the audio to be a video. For example, you can generate a dummy video of the same length as your audio. It could consist of a still image or a single black frame. Next, encode the video as if it was a regular video. Your player could be built in a way that it does not display the video stream and only plays audio. However, when you use a still image, the player could also display this.