janis/aes67-daemon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/bondagit/aes67-linux-daemon

Browse Source
This commit is contained in:
Andrea Bondavalli 2021-02-17 20:41:06 +01:00
commit 3e2b439193
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -115,6 +115,7 @@ The daemon and the test have been tested with **Ubuntu 18.04** distro on **ARMv7
* Avahi service discovery (if enabled) >= 0.7 * Avahi service discovery (if enabled) >= 0.7
The following ARM platform have been used for testing: The following ARM platform have been used for testing:
The BeagleBone® Black board with ARM Cortex-A8 32-Bit processor. The BeagleBone® Black board with ARM Cortex-A8 32-Bit processor.
See [Ubuntu 18.04 on BeagleBone® Black](https://elinux.org/BeagleBoardUbuntu) for additional information about how to setup Ubuntu on this board. See [Ubuntu 18.04 on BeagleBone® Black](https://elinux.org/BeagleBoardUbuntu) for additional information about how to setup Ubuntu on this board.
@ -139,7 +140,11 @@ The script performs the following operations:
Before attempting to use the AES67 daemon on a specific host or board it's highly recommended to run the platform test. Before attempting to use the AES67 daemon on a specific host or board it's highly recommended to run the platform test.
This test can be executed using the [run\_test.sh](run_test.sh) script. See [script notes](#notes). This test can be executed using the [run\_test.sh](run_test.sh) script. See [script notes](#notes).
<<<<<<< HEAD
The script allows a user to test a specific configuration and it can be used to ensure that the daemon will be able to operate smoothly with such config on the current platform. The script allows a user to test a specific configuration and it can be used to ensure that the daemon will be able to operate smoothly with such config on the current platform.
=======
The script allows a user to test a specific configuration and it can be used to ensure that the daemon will be able to operate smoothly with such config on the platform.
>>>>>>> 0ba03dda759fc1a5df175c7acafb1a3d4b140d67
Usage run_test.sh sample_format sample_rate channels duration Usage run_test.sh sample_format sample_rate channels duration
sample_format can be one of S16_LE, S24_3LE, S32_LE sample_format can be one of S16_LE, S24_3LE, S32_LE
@ -156,7 +161,7 @@ The test performs the following operations:
* check that all the required executables are available * check that all the required executables are available
* stop the running daemon instances and remove the ALSA RAVENNA/AES67 module * stop the running daemon instances and remove the ALSA RAVENNA/AES67 module
* compile the test tools under the test folder * compile the test tools under the test folder
* validatesthe input parametersi, prepare the raw input file to be played *./test/test.raw* and the configuration files under the test folder * validates the input parameters, prepare the raw input file to be played *./test/test.raw* and the configuration files under the test folder
* stop PulseAudio (if installed). This opens and keeps busy the ALSA playback and capture devices causing problems. See [PulseAudio](#notes). * stop PulseAudio (if installed). This opens and keeps busy the ALSA playback and capture devices causing problems. See [PulseAudio](#notes).
* install the ALSA RAVENNA/AES67 module * install the ALSA RAVENNA/AES67 module
* start the ptp4l as master clock on the network loopback interface * start the ptp4l as master clock on the network loopback interface
@ -167,7 +172,8 @@ The test performs the following operations:
* wait for the recording and the playback to complete * wait for the recording and the playback to complete
* check that the recorded file contains the expected audio samples sequence * check that the recorded file contains the expected audio samples sequence
* terminate ptp4l and the AES67 daemon * terminate ptp4l and the AES67 daemon
* print the test result that can be either *OK" or *failed at {location}* * print the test result that can be either *OK" or *failed at (location)*
If the test result is OK it means that the selected configuration can run smoothly on your platform. If the test result is OK it means that the selected configuration can run smoothly on your platform.