-[Python scripts for Testing the IVAS code and Generating test items](#python-scripts-for-testing-the-ivas-code-and-generating-test-items)
-[Contents](#contents)
-[0. Requirements](#0-requirements)
-[- numpy and scipy for `generate_test_items.py`, `testBitexact.py` and `self_test.py`](#--numpy-and-scipy-for-generate_test_itemspy-testbitexactpy-and-self_testpy)
-[1. Scripts and classes for testing IVAS code](#1--scripts-and-classes-for-testing-ivas-code)
| ISM or ISMx | yes/no/no | Objects with metadata, description using pre-renderer metadata |
| ISM or ISMx | yes/no/no | Objects with metadata, description using renderer metadata |
| MASA or MASAx | yes/no/no | mono or stereo signals with spatial metadata !!!metadata must share same basename as waveform file but with .met extension!!! |
| FOA/HOA2/HOA3 or PLANAR(FOA/HOAx) | yes/yes/yes | Ambisonic signals or planar ambisonic signals |
| 5_1/5_1_2/5_1_4/7_1/7_1_4 or CICP[6/12/14/16/19] | yes/yes/yes | Multi-channel signals for predefined loudspeaker layout |
| META | yes/yes/no | Audio scene described by a pre-renderer config |
| META | yes/yes/no | Audio scene described by a renderer config |
---
@@ -585,17 +589,17 @@ The processing chain is as follows:
---
### 2.6. Pre-renderer Metadata definition
### 2.6. Renderer Metadata definition
To run, the pre-renderer requires a config file describing the input scene.The expected format of the config file is as follows:
To run, the renderer requires a config file describing the input scene.The expected format of the config file is as follows:
---
- Line 1: Path to a "multitrack" audio file. This should be a single multichannel wav/pcm file that contains all input audio. For example channels 1-4 can be an FOA scene,channel 5 - an object and channels 6-11 - a 5.1 channel bed. If the path is not absolute, it is considered relative to the pre-renderer executable, not the config file. This path has lower priority than the one given on the command line: *The path in the config file is ignored if the --inputAudio argument to the pre-renderer executable is specified.* When running together with the encoder using EVS_cod_prerenderer.sh, the path in the config file is ignored and the one provided as script argument is used instead.
- Line 1: Path to a "multitrack" audio file. This should be a single multichannel wav/pcm file that contains all input audio. For example channels 1-4 can be an FOA scene,channel 5 - an object and channels 6-11 - a 5.1 channel bed. If the path is not absolute, it is considered relative to the renderer executable, not the config file. This path has lower priority than the one given on the command line: *The path in the config file is ignored if the --inputAudio argument to the renderer executable is specified.*
---
- Line 2: Contains number of inputs. An input can either be an Ambisonics scene, anobject or a channel bed.This is NOT the total number of channels in the input audio file.The pre-renderer currently supports simultaneously: *Up to 2 SBA inputs, Up to 2 MC inputs* Up to 16 ISM inputsThese limits can be freely changed with pre-processor macros, if needed.
- Line 2: Contains number of inputs. An input can either be an Ambisonics scene, anobject or a channel bed.This is NOT the total number of channels in the input audio file.The renderer currently supports simultaneously: *Up to 2 SBA inputs, Up to 2 MC inputs* Up to 16 ISM inputsThese limits can be freely changed with pre-processor macros, if needed.
---
- Following lines:
@@ -625,7 +629,9 @@ ISM
## 3. Script for converting formats and binauralizing
The script audio3dtool.py can convert between different input and output formats and binauralize the signals.
The script audio3dtools.py can convert between different input and output formats and binauralize signals.
Execute `python -m pyaudio3dtools.audio3dtools --help` for usage.
### 3.1. Binauralizing with head rotation
@@ -642,3 +648,9 @@ Currently MC input signals are supported. The reference processing can be activa
### 3.3. Rendering ISM to Custom loudspeakers with auxiliary binaural output
ISM metadata can either be specified via an input text file in the Renderer Metadata definition format, or via the commandline using the same style as IVAS:
