Re: [codec] Tübingen Test plan

"Christian Hoene" <> Sun, 14 August 2011 19:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5E2E021F886A for <>; Sun, 14 Aug 2011 12:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.026
X-Spam-Status: No, score=-4.026 tagged_above=-999 required=5 tests=[AWL=-1.230, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, J_CHICKENPOX_52=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_72=0.6, J_CHICKENPOX_82=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CpVHe4Bu0gej for <>; Sun, 14 Aug 2011 12:33:45 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3383B21F87FA for <>; Sun, 14 Aug 2011 12:33:44 -0700 (PDT)
Received: from hoeneT60 ( []) (authenticated bits=0) by (8.13.6/8.13.6) with ESMTP id p7EJYQXh012989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <>; Sun, 14 Aug 2011 21:34:26 +0200
From: "Christian Hoene" <>
To: <>
References: <000001cc5a85$332ae0a0$9980a1e0$>
In-Reply-To: <000001cc5a85$332ae0a0$9980a1e0$>
Date: Sun, 14 Aug 2011 21:34:31 +0200
Organization: =?UTF-8?Q?Universit=C3=A4t_T=C3=BCbingen?=
Message-ID: <000d01cc5ab9$30ef71f0$92ce55d0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CC5AC9.F48672C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJY1EJe5EgQsYpPhmTqL6fGdHeAJ5QDyMjA
Content-Language: de
X-AntiVirus: NOT checked by Avira MailGate (version:; host: mx05)
Subject: Re: [codec] =?utf-8?q?T=C3=BCbingen_Test_plan?=
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 14 Aug 2011 19:33:46 -0000



Thanks for the input. I have updated the test plan:



Testplan for MUSHRA Listening Tests 
Focusing on a Conferencing Scenario

Mansoor Hyder, Christian Hoene
Universität Tübingen
14. August 2011
Version 2

Test setup

MUSHRA tests following the recommendation ITU-R BS 1584.1 will take place on August 16th, from 9:00 till 19:00 in the office B303/B304 at the building Sand 13 in Tübingen, Germany.

Tests will be done with Sennheiser HD 280 pro headphones, a PC and the software „RateIt“ version 0.1.

Twenty participants have been selected from employees and students of the University of Tübingen. They have well to very good hearing abilities. Participant will receive soft drinks and/or coffee and 8 € compensation. 

Each session will last at most 60 minutes. This includes 15 to 20 minutes for explaining and practicing the tests, 25 to 30 minutes of testing, and 5 to 10 minutes of questioning and farewell.

In total, 40 stimuli will be tested (in addition to the references).

Test stimuli

The focus of the stimuli is on a conferencing scenario, in which multiple persons speak at the same time. Only stereo test stimuli will be taken and only stereo coding modes will be tested.

Five different reference samples will be taken:

1.       Female German voice (stereo)

2.       Two female voices (stereo, cross talking)

3.       One female voice (binaural rendered, moving)

4.       Two female voices (binaural rendered, cross talking)

5.       Music (an acappella  song by “Die Prinzen”)

The following codec and codec modes will be tests

1.       Opus, Silk mode, stereo, high complexity, 20ms frame size, at 16 kbps.

2.       Opus, Hybrid mode, stereo, high complexity, 20ms frame size, at 32 kbps

3.       Opus, Celt mode, high complexity, stereo, 20ms frame size at 64 kbps

4.       Opus, Celt mode, high complexity, stereo, 5ms frame size, at 96 kbps

5.       G.719, stereo, at 2x32 kbps (Fix-point-200806-Release-1.0a)

6.       AMR-WB+, stereo, at 16 kbps (Code from TS 26304 Version 6.6)

7.       AMR-WB+, stereo, at 32 kbps (Code from TS 26304 Version 6.6)

8.        TBD, stereo at 64 kbps, 20ms frame size

In total, 5x8=40 stimuli are going to be tested.

Script to make stimuli






AMRWBPe="wine ../26304_ANSI-C_source_code_v6_6_0/encoder"

AMRWBPd="wine ../26304_ANSI-C_source_code_v6_6_0/decoder"



for file in ../reference\ items/*\.wav


    echo $I $file


    sox "$file" -r48000 -c2 input.sw

    $OPUS 0 48000 2 16000 -cbr -framesize 20 -bandwidth WB input.sw output.sw >/dev/null

    sox -r48000 -c2 output.sw $I-opus.16k.wav 

    $OPUS 0 48000 2 32000 -cbr -framesize 20 -bandwidth FB input.sw output.sw >/dev/null

    sox -r48000 -c2 output.sw $I-opus.32k.wav

    $OPUS 1 48000 2 64000 -cbr -framesize 20 -bandwidth FB input.sw output.sw >/dev/null

    sox -r48000 -c2 output.sw $I-opus.64k.wav

    $OPUS 1 48000 2 96000 -cbr -framesize 2.5 -bandwidth FB input.sw output.sw >/dev/null

    sox -r48000 -c2 output.sw $I-opus.96k.wav

    rm output.sw


    sox -r48000 -c2 input.sw -r48000 -c1 left.sw remix 1 0

    sox -r48000 -c2 input.sw -r48000 -c1 right.sw remix 0 1

    $G719e -r 32000 -i left.sw -o left.g192

    $G719e -r 32000 -i right.sw -o right.g192

    $G719d -i left.g192 -o outleft.sw

    $G719d -i right.g192 -o outright.sw

    sox -r48000 -c1 outleft.sw -c2 outleft.wav remix 1 0 

    sox -r48000 -c1 outright.sw -c2 outright.wav remix 0 1

    sox -m outleft.wav outright.wav $I-g719.64k.wav

    rm left.sw right.sw left.g192 right.g192 outleft.sw outright.sw 

    rm outleft.wav outright.wav input.sw


    $AMRWBPe -rate 16 -if "$file" -of out.wb+

    $AMRWBPd  -if out.wb+ -of $I-amrwbp.16k.wav


    $AMRWBPe -rate 32 -if "$file" -of out.wb+

    $AMRWBPd -if out.wb+ -of $I-amrwbp.32k.wav

    rm out.wb+


    sox "$file" -r48000 -c2 $I-reference.wav

    sox "$file" -r48000 -c2 $I-hidden.wav

    sox "$file" -r48000 -c2 $I-anchor.wav lowpass 3500


    let I=$I+1






Dr.-Ing. Christian Hoene, University of Tübingen, Computer Science, Chair of

Communication Networks, Research Group Interactive Communication Systems (ICS)

Sand 13, 72076 Tübingen, Germany, Tel +49 7071 2970532, <> 


From: [] On Behalf Of Christian Hoene
Sent: Sunday, August 14, 2011 3:22 PM
Subject: [codec] Tübingen Test plan




I was compiling the following tests plan for Tuesday.

Any comments and hint to improve the test plan?


With best regards,