From 2bed3e7541f9f405f134d577d1a6a890762ff6e9 Mon Sep 17 00:00:00 2001 From: Andrea Bondavalli Date: Thu, 3 Mar 2022 08:46:15 +0100 Subject: [PATCH] Fix to README.md. See #70 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 046d160..2bc2400 100644 --- a/README.md +++ b/README.md @@ -209,7 +209,7 @@ The specified buffer size in frames starts from _tic_frame_size_at_1fs_ * 2 (128 For example, to test the typical AES67 configuration for 1 minute and a buffer size of 128 frames run: - ./run_test.sh S24_3LE 48000 2 60 128 + ./run_latency_test.sh S24_3LE 48000 2 60 128 If no underrun errors occurred during the test the requested buffer size can be used and the end-to-end latency measured is printed at the end: