Nowadays, many people use audio-on-demand content on a daily basis. Podcasts, music services, online audio libraries, and similar platforms are providing on-demand content. As more people grow up in an “on-demand society” and the technological means of our media systems expand, on-demand content is replacing a large share of scheduled content. Thus, when customers asked us for an aixtream-based solution that allows users to handle on-demand processing—including metadata and file ingest—themselves, we developed it!
What is our audio-on-demand workflow process?
The actual configuration is kept as simple as possible through a handy step-by-step configuration wizard. The input, which includes the actual audio as well as any associated metadata, is either pulled from an external server or pushed to the encoder system. Both the audio and metadata can be ingested either locally(from the Archive menu in aixtream), with HTTP(S), FTP(S), SFTP, rsync, or Samba. The audio input and metadata for one job can even use different methods and sources. Notably, the local input could be relevant for aixtream systems used for other audio applications besides on-demand. For example, recording SIP calls and then processing them for a podcast or audio library.
Once the audio input and metadata has been received, it is encoded with the desired codec algorithms. The aixtream encoder is infinitely scalable, but usually customers only need 2 simultaneous encoding instances (primary and backup) since the audio only needs to be encoded once and is then uploaded to its destination. Even large amount of content can usually be processed quickly enough. More encoding instances are usually only necessary when extra fast provisioning of high volume on-demand content is required.
The aixtream on-demand processing has also been made very error-resistant. Any defective inputs are collected in a special folder in the Archive menu. This makes it easy for the user to recognize any issues the inputs may be having while preserving the files for repair or reuse.
After the audio has been encoded and the metadata embedded in it, it is then uploaded to any number of destinations via any of the transport options mentioned above. The output can be a simple file, HLS (including CMAF) or DASH. A simultaneous local backup in the Archive is also possible and jobs can be restored from there if required. This action may be taken as a precaution against failure on the CDN side or for legal compliance.
Get more with aixtream
As always, aixtream offers multiple and expansive options for monitoring. There is a Dashboard widget for easy visualizationof the ongoing processes and any errors that may have been encountered and the REST API can be used to fully monitor and automatizethe on-demand processing. Another hallmark of aixtream is its extreme customizability and this applies to this functionality as well. New transport protocols could be added, and new features implemented to handle a greater share of the overall on-demand workflow, especially if our customers are interested in directly combining their on-demand with any live audio applications.
If you want a simple solution for your audio on demand content that is fully under your control our aixtream systems are the alternative you want.
www.ferncast.com/aixtream
