|
| 1 | +# EBU ADM Renderer (EAR) |
| 2 | + |
| 3 | +The **EBU ADM Renderer** **(*EAR*)** is a complete interpretation of the **Audio Definition Model (ADM)** format, specified in Recommendation [ITU-R BS.2076-1](https://www.itu.int/rec/R-REC-BS.2076/en). ADM is the recommended format for all stages and use cases within the scope of programme productions of **Next Generation Audio (NGA)**. This repository contains a Python reference implementation of the EBU ADM Renderer. |
| 4 | + |
| 5 | +This Renderer implementation is capable of rendering audio signals to all reproduction systems mentioned in ["Advanced sound system for programme production (ITU-R BS.2051-1)"](https://www.itu.int/rec/R-REC-BS.2051/en). |
| 6 | + |
| 7 | +Further descriptions of the *EAR* algorithms and functionalities can be found in EBU Tech 3388. |
| 8 | + |
| 9 | +## Test files |
| 10 | +A initial set of ADM files to test the *EAR* can be found under |
| 11 | + - https://ebu.io/qc/testmaterial and |
| 12 | + - http://cvssp.org/data/s3a/public/radiodrama_register.php |
| 13 | + |
| 14 | +## Installation |
| 15 | + |
| 16 | +To install the latest release from PyPi: |
| 17 | + |
| 18 | +```bash |
| 19 | +$ pip install ear |
| 20 | +``` |
| 21 | + |
| 22 | +### Python versions |
| 23 | + |
| 24 | +*EAR* supports Python 2.7 and Python >=3.6 |
| 25 | +and runs on all major platforms (Linux, Mac OSX, Windows). |
| 26 | + |
| 27 | +### Installation of extra packages |
| 28 | + |
| 29 | +If you want to run the unit tests you can install all extra requirements with pip: |
| 30 | +```bash |
| 31 | +$ pip install ear[test] |
| 32 | +``` |
| 33 | + |
| 34 | +## Getting started |
| 35 | + |
| 36 | +The *EAR* reference implementation comes with two command line tools: |
| 37 | + |
| 38 | +- `ear-render` Is the main tool to render BW64/ADM audio files |
| 39 | +- `ear-utils` Collection of useful ADM utilities |
| 40 | + |
| 41 | +### Command line renderer |
| 42 | + |
| 43 | +```bash |
| 44 | +usage: ear-render [-h] [-d] -s target_system [-l layout_file] |
| 45 | + [--output-gain-db gain_db] [--fail-on-overload] |
| 46 | + [--enable-block-duration-fix] [--strict] |
| 47 | + input_file output_file |
| 48 | + |
| 49 | +EBU ADM renderer |
| 50 | + |
| 51 | +positional arguments: |
| 52 | + input_file |
| 53 | + output_file |
| 54 | + |
| 55 | +optional arguments: |
| 56 | + -h, --help show this help message and exit |
| 57 | + -d, --debug print debug information when an error occurres |
| 58 | + -s target_system, --system target_system |
| 59 | + Target output system, accoring to ITU-R BS.2051. |
| 60 | + Available systems are: 0+2+0, 0+5+0, 2+5+0, 4+5+0, |
| 61 | + 4+5+1, 3+7+0, 4+9+0, 9+10+3, 0+7+0, 4+7+0 |
| 62 | + -l layout_file, --layout layout_file |
| 63 | + Layout config file |
| 64 | + --output-gain-db gain_db |
| 65 | + output gain in dB (default: 0) |
| 66 | + --fail-on-overload, -c |
| 67 | + fail if an overload condition is detected in the |
| 68 | + output |
| 69 | + --enable-block-duration-fix |
| 70 | + automatically try to fix faulty block format durations |
| 71 | + --strict treat unknown ADM attributes as errors |
| 72 | +``` |
| 73 | +
|
| 74 | +To render an ADM file, the following three parameters must be given: |
| 75 | + - `-s` followed by the target output format to render to |
| 76 | + - the name of the input file |
| 77 | + - the name of the output file |
| 78 | +
|
| 79 | +For example `ear-render -s 0+5+0 input.wav output_surround.wav` will render the BW64/ADM file `input.wav` to a `0+5+0` target speaker layout and store the result in `output_surround.wav`. |
| 80 | +
|
| 81 | +The *optional* `--layout` parameter allows to specify the real loudspeaker positions and screen dimensions of a reproduction setup. |
| 82 | +Refer to [the layout file documentation](doc/layout_file.md) for more information about its format. |
| 83 | +
|
| 84 | +`--fail-on-overload` makes the rendering process fail in case an overload in the output channels to ensure any signal clipping doesn't go unnoticed. Use `--output-gain-db` to adjust the output gain. |
| 85 | +
|
| 86 | +`--enable-block-duration-fix` automatically fixes durations of `audioBlockFormats` in case they are not continuous. |
| 87 | +**Please note** that the proper way to handle this situation is to fix the input file. |
| 88 | +
|
| 89 | +`--strict` enables strict ADM parsing mode. Some of the currently available |
| 90 | +ADM/BW64 files may not strictly adhere to the BS.2076 specification, for example by including xml attributes that are not part of the standard. |
| 91 | +The default behaviour is to output a warning and continue processing. |
| 92 | +When strict mode is enabled, warnings are turned into errors and processing is stopped. |
| 93 | +
|
| 94 | +
|
| 95 | +**Please note** that, depending on the size of the file, it may |
| 96 | +take some time to render the file. At the time of writing, the parsing of the ADM XML data is relatively slow when the ADM is large (>= a few megabytes). |
| 97 | +
|
| 98 | +### Command line ADM utilities |
| 99 | +
|
| 100 | +The `ear-utils` command provides various subcommands which can be seen on the help message |
| 101 | +when called with `ear-utils --help`: |
| 102 | +
|
| 103 | +Each subcommand may have its own command line options, which can be |
| 104 | +displayed using `ear-utils SUBCOMMAND --help`, where `SUBCOMMAND` is one of the supported subcommands. |
| 105 | +
|
| 106 | +```bash |
| 107 | +usage: ear-utils [-h] |
| 108 | + {make_test_bwf,replace_axml,dump_axml,dump_chna,ambix_to_bwf} |
| 109 | + ... |
| 110 | +
|
| 111 | +EBU ADM renderer utilities |
| 112 | +
|
| 113 | +optional arguments: |
| 114 | + -h, --help show this help message and exit |
| 115 | +
|
| 116 | +available subcommands: |
| 117 | + {make_test_bwf,replace_axml,dump_axml,dump_chna,ambix_to_bwf} |
| 118 | + make_test_bwf make a bwf file from a wav file and some metadata |
| 119 | + replace_axml replace the axml chunk in an existing ADM BWF file |
| 120 | + dump_axml dump the axml chunk of an ADM BWF file to stdout |
| 121 | + dump_chna dump the chna chunk of an ADM BWF file to stdout |
| 122 | + ambix_to_bwf make a BWF file from an ambix format HOA file |
| 123 | +``` |
| 124 | +
|
| 125 | +#### HOA ADM Creation |
| 126 | +```bash |
| 127 | +usage: ear-utils ambix_to_bwf [-h] [--norm NORM] [--nfcDist NFCDIST] |
| 128 | + [--screenRef] [--chna-only] |
| 129 | + input output |
| 130 | +
|
| 131 | +positional arguments: |
| 132 | + input input file |
| 133 | + output output BWF file |
| 134 | +
|
| 135 | +optional arguments: |
| 136 | + -h, --help show this help message and exit |
| 137 | + --norm NORM normalization mode |
| 138 | + --nfcDist NFCDIST Near-Field Compensation Distance (float) |
| 139 | + --screenRef Screen Reference |
| 140 | + --chna-only use only CHNA with common definitions |
| 141 | +``` |
| 142 | +
|
| 143 | +
|
| 144 | +To convert an ambiX file in an ADM one, the following two parameters must be given: |
| 145 | +- the name of the input file |
| 146 | +- the name of the output file |
| 147 | +
|
| 148 | +The optional parameters are : |
| 149 | +- The normalization of the signals (N3D, FuMa or SN3D, which is the default value) |
| 150 | +- The NFC Distance, i.e., the distance at which the HOA mix was created. A float value between 0 and 20 meters must be given. |
| 151 | + The default value 0 means no NFC processing. |
| 152 | +- The screenRef flag, which tells if the audio content is screen related or not. The default value is False, which means no screen scaling. |
| 153 | +
|
| 154 | +For example, `ear-utils ambix_to_bwf --nfcDist 2.53 input.wav output.wav` will create an ADM file called output.wav containing the audio samples of the input.wav file and the ADM metadata corresponding to an ambiX file with SN3D normalization, an 2.53 meters nfcDist, and no screen scaling. |
| 155 | +
|
| 156 | +**Please note** that the software implicitly assumes that all the HOA channels are in ACN ordering and that no channel is missing. For example, it will assumes the signal is a 4th order HOA signal if it finds 25 channels ((4+1)²=25). |
0 commit comments