The software is a Java application that offers transcoding services for various types of media. It can convert audio, video, and image files into different formats with ease.
The Alembik Media Transcoding Server is a powerful Java application that delivers transcoding services for varied media types, including images, audios, videos, and more. The server waits for requests that contain lists of transcoding jobs, each consisting of an URL path to the given media resource and a set of parameters that determine how the appointed media file should be transformed.
The transcoding parameters will depend on the input media type, dictating size, dimension, duration and format of the desired output file. There are two options for server-side customization: pass a user-agent identifier to generate a set of parameters based on the requesting device capabilities or associate a job with an id of a predefined parameter set called a transcoding profile that the server internally maintains.
Upon validating and receiving requests, the server starts the transcoding process that includes a response object containing a list of results for all requested transcoding jobs. Essentially, each result includes an URL pointing to the transcoded file location or an error code that provides clear justification behind the transcoding job failure.
Depending on the mode, the server can either wait for completion of transcoding processes before sending a response (synchronous mode) or may return control immediately (asynchronous mode). In the latter, the client may ask the server about the status and result properties of its scheduled jobs and, provided with a positive response, obtain the output media.
Alembik architecture is fully compliant with the OMA STI (Open Mobile Alliance Standard Transcoding Interface) specification (version 1.0) enabling access to transcoding functionality for Java clients via two configurations. The first involves the Java Transcoding API, with the org.alembik.transcoding manager class serving as an entry point. The second possibility is the JSP Transcoding Tag Library, which provides support for WAP page development and also utilizes the TranscodingManager instance.
The TranscodingManager connects to the server through either RMI calls or SOAP requests based on the configuration generated with the Transcoding Client Library, consisting of a set of JAR archives built and bundled specifically for a client environment. For non-Java clients, direct connections to the transcoding SOAP service or the HTTP servlet-based API are available.
The transcoding parameters will depend on the input media type, dictating size, dimension, duration and format of the desired output file. There are two options for server-side customization: pass a user-agent identifier to generate a set of parameters based on the requesting device capabilities or associate a job with an id of a predefined parameter set called a transcoding profile that the server internally maintains.
Upon validating and receiving requests, the server starts the transcoding process that includes a response object containing a list of results for all requested transcoding jobs. Essentially, each result includes an URL pointing to the transcoded file location or an error code that provides clear justification behind the transcoding job failure.
Depending on the mode, the server can either wait for completion of transcoding processes before sending a response (synchronous mode) or may return control immediately (asynchronous mode). In the latter, the client may ask the server about the status and result properties of its scheduled jobs and, provided with a positive response, obtain the output media.
Alembik architecture is fully compliant with the OMA STI (Open Mobile Alliance Standard Transcoding Interface) specification (version 1.0) enabling access to transcoding functionality for Java clients via two configurations. The first involves the Java Transcoding API, with the org.alembik.transcoding manager class serving as an entry point. The second possibility is the JSP Transcoding Tag Library, which provides support for WAP page development and also utilizes the TranscodingManager instance.
The TranscodingManager connects to the server through either RMI calls or SOAP requests based on the configuration generated with the Transcoding Client Library, consisting of a set of JAR archives built and bundled specifically for a client environment. For non-Java clients, direct connections to the transcoding SOAP service or the HTTP servlet-based API are available.
What's New
Version 1.0 Beta 4.1: N/A