MC2GO Product Version: 2.1
Last User Guide Update: December 9, 2019


Before installing MainConcept 2GO, please ensure Docker is installed correctly.

Installing Docker

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.

total 40
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
~/MainConcept/2GO/mc_2go_proxy_file_generator_demo# █

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_proxy_file_generator_demo# cd docker/
~/MainConcept/2GO/mc_2go_proxy_file_generator_demo/docker# ./install_image.sh
Installing MainConcept 2GO in your local Docker environment...
e6bc3d95b8d4: Loading layer [============================>] 28.87MB/28.87MB
Loaded image: mc_2go_proxy_file_generator_demo:latest
~/MainConcept/2GO/mc_2go_proxy_file_generator_demo# █

Verify whether the 2GO container is installed properly by using the “docker image ls” command:

~/MainConcept/2GO/mc_2go_proxy_file_generator_demo/docker# docker image ls
REPOSITORY                         TAG      IMAGE ID      CREATED      SIZE
mc_2go_proxy_file_generator_demo   latest   2e15d1d96bd9  3 hours ago  39.9MB
~/MainConcept/2GO/mc_2go_proxy_file_generator_demo/docker# █

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@m@mainconcept.com. We will get in touch with you about the necessary steps.


Supported Input Codecs & Formats

MainConcept 2GO Proxy File Generator supports the following input codecs and formats:

  • Video: MPEG-1/2, AVC/H.264, DVCPRO, JPEG 2000
  • Audio: PCM / LPCM, MPEG Layer 1/2, RAW / WAV, DV
  • Container: Elementary Streams, MPEG-2 Program Stream / Transport Stream, MP4, DV, DIF, MJ2, MXF, RAW

Supported Output Formats

MainConcept 2GO Proxy File Generator supports the following video and audio formats multiplexed into MP4:

  • AVC/H.264 SD: 720x576, PAL, 25 fps, Main Profile, 3 mbit
  • AVC/H.264 SD: 720x480, NTSC, 30 fps, Main Profile, 3 mbit
  • AVC/H.264 CIF: 320x288, PAL, 25 fps, Baseline Profile, 600 kbit
  • AVC/H.264 CIF: 320x240, NTSC, 30 fps, Baseline Profile, 600 kbit
  • AAC-LC: Stereo, 44.1 kHz, 160 kbps

Included Presets

Several built-in presets are included in the product for direct usage.

CIF AVC_AAC_CIF_25fps_600kbit
SD AVC_AAC_SD_25fps_3mbit

If you need to manually tune presets there is an *.mps file for each built-in preset located in the “volume/presets”. To specify a manually edited preset, use the PRESET parameter.


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.


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 helps you to 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” script.

MainConcept 2GO products require passing configuration parameters to the container at startup. These can include input and output filenames, serial keys, shared volume folders or external URLs. These parameters can be specified in a JSON file, a properties file or via the command line.

Using job description file
MainConcept 2GO v2.0 introduces a REST API and provides users an interface that is more suitable for integration with their existing environment or tools. This API covers functionality to create jobs and query their status using standard REST API calls over HTTP. A job description file is posted to the endpoint, which must be in JSON format. This JSON file must contain all the necessary parameters required for the submitted jobs.

Option Sample value Description
INPUT 0002CD.MXF Source filename for audio conversion; must be in or under SHARED_PATH_IN
OUTPUT out_sd_25fps.mp4 Target filename for encoded output; you also need to add; must be in or under SHARED_PATH_OUT

File Extension: *.mp4
PRESETNAME AVC_AAC_SD_25fps_3mbit Preset name for proxy generation when using original MainConcept preset(s) included in the Docker container. Note: When PRESETNAME is used, PRESET must not be used.
PRESET /AVC_AAC_CIF_25fps_600kbit.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.
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 information about input file, output file, preset. Prints information about REST API calls (target URLs with parameters, no BODY info).
  • FULL (2) - Prints all available information, including processing status, file transfer, REST API calls (target URLs with parameters with BODY info), complete information from processing step.
KEEP_CONTENT TRUE Prevents deletion of temporary content (e.g. downloaded, transcoded). Default value is FALSE.

To edit the parameters of the JSON file, use a text editor. Here are some examples:

    "INPUT": "",
    "OUTPUT": "",
    "PRESETNAME": "AVC_AAC_SD_25fps_3mbit",

    "INPUT": "test.mp4",
    "OUTPUT": "/volume_out/xavc_proxy.mp4",
    "PRESET": "AVC_AAC_CIF_25fps_600kbit.mps",

Using properties file
The easiest way to start MainConcept 2GO is by editing the “properties.txt” file to your needs and then executing the “run” script with this file.

~/MainConcept/2GO/mc_2go_proxy_file_generator_demo# ./scripts/run.sh scripts/properties.txt

The MainConcept 2GO Proxy File Generator supports the following configuration options:

Option Sample value Description
SHARED_PATH_IN /path/source_folder Optional: Folder where the input file is located
SHARED_PATH_OUT /path/target_folder Optional: Folder for the encoded output file
JOBS /path/to/json_file Optional: Specify a job JSON file for immediate processing
PORT 8082 Specify port for REST API. Default value is 8080.
AUTOSTART TRUE, FALSE Disable/enable job queue processing when Docker runs. FALSE sets the service to a stopped state after the Docker runs. Default value is TRUE.
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 information about input file, output file, preset. Prints information about REST API calls (target URLs with parameters, no BODY info). FULL (2) - Prints all available information, including processing status, file transfer, REST API calls (target URLs with parameters with BODY info), complete information from processing step.

To edit the parameters, use a text editor:

2  SHARED_PATH_IN=~/MainConcept/2GO/mc_2go_ proxy_file_generator_demo/volume
3  SHARED_PATH_OUT=~/MainConcept/2GO/mc_2go_ proxy_file_generator_demo/volume
4  JOBS=~/path/to/json_file
5  PORT=8082

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_proxy_file_generator_demo/docker# ./scripts/run.sh \
>    SHARED_PATH_IN=~/MainConcept/2GO/mc_2go_proxy_file_generator_demo/volume \
>    SHARED_PATH_OUT=~/MainConcept/2GO/mc_2go_proxy_file_generator_demo/volume \
>    JOBS=~/path/to/json_file \
>    PORT=8082 \
>    CUSTOMER_ID=xxx \

Using docker-compose
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 about 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 via Docker Compose are specified inside this YAML filer. To simplify deployment of MainConcept 2GO containers, setting environment variables for the 2GO configuration and then using them in the YAML file is recommended.

This is a basic “docker-compose.yml” file showing how to configure MainConcept 2GO.

1  version: '2.2'
2  services:
3    2go:
4      image: 2go_proxy_file_generator_demo
5      network_mode: host
6      volumes:
7      -${2GO_VOLUME}:/volume
8      environment:
9      -2GO_PARAMS=${2GO_PARAMS}

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_proxy_file_generator_demo/volume/
~# export 2GO_PARAMS="INPUT= 0002CD.MXF OUTPUT=out_file QUALITY=low CUSTOMER_ID=xxx"

After that starting 2GO using Docker Compose is as easy as:

~/MainConcept/2GO/mc_2go_proxy_file_generatordemo# docker-compose up -d
Starting mc2goproxyfilegeneratordemo_2go_1 ...
Starting mc2goproxyfilegeneratordemo_2go_1 ... done

Stopping MainConcept 2GO execution

MainConcept 2GO containers should be stopped using the convenience “stop” script provided in the scripts folder.

To execute the script on an active container you first need to know the container ID. This can be found from the first column of the docker ps command:

~/MainConcept/2GO/mc_2go_proxy_file_generator_demo# docker ps
CONTAINER ID   IMAGE                              COMMAND                    CREATED
bc45686deb0e   mc_2go_proxy_file_generator_demo   "/opt/bin/reporting_..."   4seconds ago

Then use the convenience “stop” script in the scripts folder to abort 2GO execution:

~/MainConcept/2GO/mc_2go_proxy_file_generator_demo# ./scripts/stop.sh bc45686deb0e
Stopping the Proxy File Generator...
Proxy File Generator stopped.
~/MainConcept/2GO/mc_2go_proxy_file_generator_demo# █

If you are using the REST API, you also have the opportunity to shut down the container by using DELETE /service. If a job is currently active, the container is not shut down and this function is ignored. In this case you need to abort the job first using POST /jobs/{jobID}/abort

Technical Support

If you need additional assistance, the MainConcept Technical Support team is standing by to help. Send an e-mail to apps.supportnoSp@m@mainconcept.com or go to the MainConcept Support page and we'll assist you as quickly as possible.


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.

MC2GO Product Version: 2.1
Last User Guide Update: December 9, 2019