[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-05-08 UTC。"],[],[],null,["# CTS Verifier multichannel mixdown test\n\n\u003cbr /\u003e\n\nThe Android audio system can support a large number of audio channel formats for\nplayback. Audio created for high channel count audio formats, such as 5.1\nsurround sound, must play back reasonably on a stereo 2-channel device.\n\nThe CTS Verifier multichannel mixdown test verifies that reasonable playback\noccurs over a variety of high channel count audio sources and over audio routes\nconfigured for 2-channel playback.\n\nMultichannel mixdown test UI\n----------------------------\n\nThe multichannel mixdown test UI, as shown in Figure 1, is comprised of the\nelements described in the following sections.\n\n**Figure 1.** Multichannel mixdown test ready to run.\n\n### Audio API selection\n\nThe user can select which audio API is used for playback and capture: Java API\nor Native API. Only one API needs to be tested to pass the test.\n\n**Figure 2.** Audio API selection.\n\n### Support utilities\n\nSee [Support utilities](/docs/compatibility/cts/audio-loopback-latency#support-utilities)\nfor more information.\n\n### Route selection\n\nWith this interface, the user can select which audio route is tested. Route\nnames are appended with the text *required* when the route is present on the\ndevice (even if the audio peripheral associated with that route isn't\nconnected). When the test sequence for that route is run,\nthe name is appended with the text *done*.\n\nRoute buttons are enabled when a device associated with a given route\nbecomes available, that is, an audio peripheral is connected to the DUT.\nTest the supported routes, as follows:\n\n- **Mic/Speaker:** Tests the built-in microphone and speaker on the DUT.\n\n- **Analog Headset Jack + Loopback:** The 3.5 mm analog headset jack\n (not present on all Android devices) must be connected to an\n [Audio loopback plug](/docs/compatibility/cts/audio-peripherals#audio-loopback-plug).\n\n | **Note:** A physical headset device can't be used to perform this test. This button is enabled only when an analog headset device (the audio loopback plug) is connected.\n- **USB Interface + Loopback:** Tests if the [USB audio interface device](/docs/compatibility/cts/audio-peripherals#usb-audio-interface)\n is properly configured for loopback. This button is enabled only when a\n USB audio interface device is connected.\n\n- **USB Headset Adapter + Loopback:** Tests a [USB-to-analog headset adapter](/docs/compatibility/cts/audio-peripherals#usb-analog-headset-adapter)\n connected to an audio loopback plug. This button is enabled only when a\n USB-to-analog headset adapter with an audio loopback plug\n is connected.\n\n | **Note:** A physical analog headset device connected to the USB-to-analog headset adapter can't be used to perform this test.\n\n**Figure 3.** Route selection.\n\n### Test process buttons, data display, and format specifications\n\n**Start:** Begins the test. The test generates signals from each of the formats\nspecified.\n\n**Stop:** Stops the test in execution.\n\n**Clear Results:** Clears the results panel.\n\n**Figure 4.** Start and clear buttons.\n\nThe captured signal is displayed as the test runs. When all the formats are\ntested, the results panel is displayed.\n\nThe following figure shows successful test results after running on a USB\nheadset:\n\n**Figure 5.** Multichannel mixdown test results.\n| **Note:** The left and right values are the same because the loopback adapter mixes the stereo output to mono. Other required routes aren't completed in this example.\n\nTest protocol\n-------------\n\nThe test protocol is as follows:\n\n1. Place the DUT in a quiet location.\n2. Select the API to test. Only one is required to pass.\n3. Select the **Mic/Speaker** route.\n4. Tap **Calibrate Audio** and ensure that an adequate signal is generated.\n5. Tap **Start** and allow the test to run for the various channel formats.\n6. When complete, a report is displayed indicating the result of each of the channel formats. For example, the **Mic/Speaker** route button displays *Done* to indicate that the test for that route is complete.\n7. Perform steps 4 through 6 for the remaining required routes.\n8. When the test for all the required routes has been completed, **Pass** is enabled to indicate that the test has passed.\n\n### Interpret the results\n\nYou might notice that certain channel positions have a low magnitude, indicating\nthat the surround sound stream's high channels are being eliminated. The high\nchannels are supposed to be *mixed down*, ensuring that all channels from the\ncontent are audible through the stereo output."]]