Before installing MainConcept 2GO, please ensure Docker is installed correctly.
To download and install Docker on your server, please follow the instructions here: www.docker.com/community-edition
After successful installation you should be able to run the Docker “hello-world” container. Example output from the Docker hello-world container:
$ docker run hello-world
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64)
3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.
If you see different output, please refer to the Docker installation guide.
Resources for Docker
On Windows machines there is a default limitation of resources available for Docker. It could be adjusted in the "Settings > Advanced" section. For more information, please check the official website: docs.docker.com/docker-for-windows.
Installing MainConcept 2GO
1) Extract the MainConcept 2GO package
To install your MainConcept 2GO product, first unpack the ZIP file you downloaded into a new folder on your computer. The files within the folder depend on the 2GO product.
drwxrwxr-x 2 thomas thomas 4096 Apr 10 14:23 docker
-rw-rw-r-- 1 thomas thomas 17835 Apr 10 14:23 EULA.txt
-rw-rw-r-- 1 thomas thomas 77 Apr 10 14:23 info.txt
-rw-rw-r-- 1 thomas thomas 2721 Apr 10 14:23 readme.txt
-rw-rw-r-- 1 thomas thomas 4096 Apr 10 14:23 scripts
-rw-rw-r-- 1 thomas thomas 4096 Apr 10 15:10 volume
2) Install the MainConcept 2GO docker image
To install the MainConcept 2GO image in your local Docker environment, “cd” into the docker folder and run the “install_image” script:
~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo# cd docker/
Installing MainConcept 2GO in your local Docker environment...
e6bc3d95b8d4: Loading layer [============================>] 28.87MB/28.87MB
Loaded image: mc_2go_hevc_file_transcoder_demo:latest
Verify whether the 2GO container is installed properly by using the “docker image ls” command:
Note: For using both the demo and full version of MainConcept 2GO, you must allow the server running MC2GO a connection to https://taas-reporting-srv.mainconcept.com. If you want to use the products offline (i.e. without internet connection), please contact customer.carenoSp@firstname.lastname@example.org. We will get in touch with you about the necessary steps.
Supported Input Codecs & Formats
MainConcept 2GO HEVC File Transcoder supports the following input codecs and formats:
- Video: MPEG-1/2, MPEG-4 Part 2, H.263, VC-1, HEVC/H.265, AVC/H.264, DV / DVCPRO, JPEG 2000
- Audio: PCM / LPCM, MPEG Layer 1/2/3, AAC / HE-AAC, WMA, AMR, RAW / WAV, DV, AC-3, E-AC-3
- Container: Elementary Streams, MPEG-2 Program Stream / Transport Stream, MP4, 3GP, F4V, ASF, DV, DIF, MJ2, MXF, RAW
Supported Output Formats
MainConcept 2GO HEVC File Transcoder supports the following output formats:
- HEVC/H.265 8-bit
- HEVC/H.265 10-bit
Several presets are included in the product for direct usage. The preset files are in the “volume/presets” subfolder.
With Docker installed most of the MainConcept 2GO configuration is complete. However, some 2GO products require shared folders or specific parameters at startup.
The REST API in MainConcept 2GO is described in separate documentation. Click here to open the REST API user guide.
Configuring shared folders
To read and write files located on the host computer, MainConcept 2GO uses shared volumes to access the filesystem of the host. Docker uses mounted volumes to share host folders with 2GO containers.
The “run” convenience script in the scripts folder runs the MainConcept 2GO container and automatically maps the required folders from your host computer into the 2GO container.
MainConcept 2GO Dolby Audio Converter supports the following configuration options:
|ACCEPT_EULA||Y||The MainConcept End-User License Agreement (EULA) must be accepted before MainConcept 2Go can start. The license terms for this product can be found in provided package.|
|SHARED_PATH_IN||/path/source_folder||Folder where the input file is located|
|SHARED_PATH_OUT||/path/target_folder||Folder for the encoded output file|
|INPUT||8MBit.mp4||Source filename for audio conversion; must be in or under SHARED_PATH_IN|
|OUTPUT||out_8Mbit||Target filename for encoded output; the file extension will be created by 2GO; must be in or under SHARED_PATH_OUT|
|PRESETNAME||MC2Go_HEVC_Main10_4K||Preset name for Dolby conversion when using MainConcept original preset(s) included in the Docker container. Note: When PRESETNAME is used, PRESET must not be used.|
|PRESET||<folder_in_shared_path>/MC2Go_HEVC_Main10_4K.mps||Custom preset file(s) (MPS); must be in or under SHARED_PATH_IN volume outside of the Docker container. Note: When PRESET is used, PRESETNAME must not be used.|
|CUSTOMER_ID||Unique customer identifier provided by MainConcept. Customer ID parameter can be also represented as `CID`|
|VERBOSITY||SILENT||Sets verbose level.
Available options are:
- SILENT (0) - Prints only error messages
- DEFAULT (1) - Default level if verbose level is not specified. Prints out the copyright/version information
- FULL (2) - Higher verbose level. Prints all available information including command-line parameters INPUT / OUTPUT / PRESETS / SERIAL
Starting MainConcept 2GO
Make sure you have successfully installed your MainConcept 2GO product on the computer by following the Installation instructions.
The “run” script inside the scripts folder makes starting MainConcept 2GO easy and lets you understand how 2GO docker containers are actually run. If you plan to run MainConcept 2GO through container management tools like Docker Compose, Kubernetes or Docker Swarm it is recommended that you understand the parameters required for 2GO containers by reading the “run” scripts.
MainConcept 2GO products require configuration parameters at container startup. This can include input and output filenames, serial keys, shared volume folders or external URLs. These parameters can be specified in a properties file or on command line.
Using properties file
The easiest way to start MainConcept 2GO is by editing the “properties.txt” file to your needs and then call the “run” script with this properties file.
~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo# ./scripts/run.sh scripts/properties.txt
To edit the parameters, use a text editor:
Using command line options
Instead of editing a properties file, all configuration parameters can also be specified on the command line directly.
~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo/docker# ./scripts/run.sh \
> SHARED_PATH_IN=~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo/volume \
> SHARED_PATH_OUT=~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo/volume \
> INPUT=avchd_camera_testfile.mts \
> OUTPUT=out_file \
> PRESETNAME=presets/DDP_5.1ch_192kbps.mps \
> CUSTOMER_ID=xxx \
Docker Compose lets you start multiple replicas of the same image. It also significantly simplifies starting MainConcept 2GO products.
Docker Compose is a separate tool that must be installed in addition to Docker. Please refer to the documentation how to install and setup Compose: docs.docker.com/compose/
To run MainConcept 2GO with Docker Compose you create a compose file in YAML. All parameters to run the 2GO product are specified inside the YAML file for Docker Compose. To simplify deployment of MainConcept 2GO containers it is recommended to set environment variables for the 2GO configuration and then use these variables in the YAML file.
This is a basic “docker-compose.yml” file showing how to configure MainConcept 2GO.
1 version: '2.2'
4 image: 2go_hevc_file_transcoder_demo
5 network_mode: host
It uses two environment variables 2GO_VOLUME and 2GO_PARAMS. These must be set before starting docker-compose.
~# export 2GO_VOLUME=~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo/volume/
~# export 2GO_PARAMS="INPUT=avchd_camera_testfile.mts OUTPUT=out_file PRESETNAME=MC2Go_HEVC_Main10_4K CUSTOMER_ID=xxx"
After that starting 2GO using Docker Compose is as easy as:
~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo# docker-compose up -d
Starting mc2gohevcfiletranscoderdemo_2go_1 ...
Starting mc2gohevcfiletranscoderdemo_2go_1 ... done
Stopping MainConcept 2GO execution
It is recommended to execute a script inside the MainConcept 2GO container in order to stop execution properly.
To execute a script in an active container you first need to know the container ID from the first column of the docker ps command:
~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo# docker ps
CONTAINER ID IMAGE COMMAND CREATED
bc45686deb0e mc_2go_hevc_file_transcoder_demo "/opt/bin/reporting_..." 4seconds ago
Then use the convenience “stop” script in the scripts folder to abort 2GO execution:
~/MainConcept/2GO/mc_2go_hevc_file_transcoder_demo# ./scripts/stop.sh bc45686deb0e
Stopping HEVC File Transcoder...
HEVC File Transcoder stopped.
Copyright © 2019 MainConcept GmbH or its affiliates. All rights reserved.
MainConceptⓇ and its logos are registered trademarks of MainConcept GmbH or its affiliates. This software is protected by copyright law and international treaties. Unauthorized reproduction or distribution of any portion is prohibited by law.
This manual, as well as the software described in it, is furnished under license and may only be used or copied in accordance with the terms of such license. The information in this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment or representation by MainConcept GmbH or its affiliates. MainConcept GmbH and its affiliates assumes no responsibility or liability for any errors or inaccuracies that may appear in this book and use is at your sole risk.
Except as permitted by such license, no part of the publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of MainConcept GmbH.
Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein. Copyright 2018 Docker, Inc. All rights reserved.
Adobe and Flash are trademarks or registered trademarks of Adobe Systems Incorporated in the USA and other countries.
DTS, the Symbol, and DTS-HD are registered trademarks of DTS, Inc.
Dolby Digital codec manufactured under license from Dolby Laboratories. Dolby and the double-D symbol are trademarks of Dolby Laboratories. Unpublished work. Copyright 2003-2014 Dolby Laboratories, Inc. and Dolby Laboratories Licensing Corporation. All rights reserved.
AAC's HE-AAC and HE-AAC v2 versions are regarded as today's most efficient general perceptual audio codecs. AAC has been standardized by ISO and IEC as part of the MPEG specifications. It is understood that it may be necessary to execute a patent license with the appropriate AAC licensing entities in order to obtain all rights necessary to create and exploit products utilizing AAC and it is recommended to contact the appropriate licensing entities, e.g. Via Licensing (www.vialicensing.com), and negotiate in good faith the adequate contracts, if any.
Fraunhofer Institute for Integrated Circuits IIS
Attention: Audio and Multimedia Departments - MC AAC LL
Am Wolfsmantel 33, 91058 Erlangen, Germany
Microsoft, Microsoft Windows XP, Windows Media Player, and the Microsoft logo are registered trademarks of the Microsoft Corporation, Inc.
All other company or product names are trademarks or registered trademarks of their respective owners.