PowerAQ User Manual

1  Overview

Power AQ is a graphical user interface for designing post-processing chain (PPC) on MediaTek platform. The main functions of Power AQ tool are as follows:

  • Design post-processing signal flow and set post-processing parameter graphically without MTK platform.
  • Perform run-time tuning of post-processing parameters with MTK platform.
  • Generate configure file for updating the design to MTK platform
  • Generate header file for building the design into SW load.
  • Support integrating customized post-processing modules.

1.1  System Overview

This section describes the system design of Power AQ tool and MTK platform. 












                             Figure 1-1. Power AQ System.


In Figure 1-1, Power AQ system is composed of 6 parts:

  • Post-processing chain model: Build post-processing signal flow described in header file or config file. Control post-processing and buffers.
  • Post-processing: Implement main post-processing algorithm. Connect to element by global interface.
  • Config file: Describe post-processing signal flow and parameters. It’s generated by Power AQ tool and used for tuning, which can be applied on platform by USB.
  • Header file: Describe the built-in post-processing signal flow and parameters. It’s generated by Power AQ tool.
  • Driver/framework: Control the post-processing chain model and receive CLI command from Power AQ tool.
  • Power AQ tool: Design post-processing signal flow and parameters.

1.2  Tool Overview

This section introduces the basic concept of Power AQ tool.                                                                                                                               












                     Figure 1-2. Scenario Page.


One of the main functions in Power AQ Tool is allowing user to design their own post-processing signal flow. However, it might need different signal flows in different scenarios. For example, MOVIE mode and MUSIC mode. So we introduce the concept of the scenario page. The scenario page is composed of the signal flow and page conditions. The system selects one scenario page in runtime according to system current state and page conditions, and runs the corresponding signal flow. 

In Figure 1-2, the scenario page, signal flow and page conditions are shown on Power AQ tool. We can create multiple scenario pages and define their scenario by designing their page conditions.

The signal flow consists of elements and links.

                                                                                                                              







                                                 Figure 1‑3. Signal Flow.


The element is the specific post-processing, which can be generated by double-clicking the element type. The element type means what kind of post-processing algorithm the element connected to. For example, we can double-click the filter element type for adding a filter element on signal flow. Note that one element type can produce multiple elements with independent parameter values and buffers.

                                                                                                                               





                          Figure 1‑4. Input and Output Node.


Input and output nodes are used to represent input and output channel of the element. In Figure 1-4, the add element contains input nodes of L/R channel and the output node of C channel. 

                                                                                                                                           





                                                 Figure 1‑5. Channel Link.


The link is for connecting the element nodes to show the signal direction of each channel. The link arrow must starts from an element output node and ends in an element input node. In Figure 1-5, the L output node of the input element is connecting to the L input node of the add element by a link. It’s acceptable that one output node is linked to multiple input nodes, while multiple output nodes linked to one input node is unsupported. 

1.3 Tool UI

Figure 1-6 shows the Power AQ tool user interface. The explanation of each block is as below:

                                                                                                                                               

















                                                       Figure 1‑6. Tool UI.


  • Function Bar: The menu of the Power AQ tool functions. See the Functions chapter for detailed function description.
  • Short Cut Menu: It contains shortcut buttons of the functions frequently used. See the Functions chapter for detailed shortcut description
  • Element: The specific post-processing object.
  • Link: The channel link for showing the signal direction of each channel.
  • Element Type: The kind of post-processing. One post-processing algorithm is mapped to one element type.

Element Type Info: The window shows the element type information, including type name, ID and description.

                                                                                                                                       












 Figure 1‑7. Element Type Info.


  • Scenario Page: A scenario page is composed of a signal flow and page conditions. The system chooses one scenario page according to the system status and page conditions, and use the corresponding signal flow as post-processing chain.
  • Page Info: The information of a scenario page with the following items:
  • MCPS/ Memory: The “Total” column means the maximum MCPS/ Memory for post-processing chain of the MTK platform. The “Used” column means the used MCPS/ Memory of the signal flow in this page.
  1. Page Name: The scenario page name.
  2. Page Id: The unique ID for the scenario page.
  3. Frame Size: The number of processed samples for one process.
  4. Default: The setting of the default page. If setting default as yes, the system will choose this page when fail to meet all page conditions. Note that it must have one default page for one project.
  5. Input Support Channel: The supported input channel of this page. If the input channel is unsupported, it will automaticallt convert into one supported input channel by default channel mapping.

                                                                                                                                     






                                                  Figure 1‑8. Page Info.


Page Condition: The system conditions for applying this scenario page, which can set condition of input channel, output channel, output device and system mode. Page condition supports multi-group settings. In Figure 1-9, there are two conditions for this page: One sets the input channel as L/R or C and the mode as MOVIE. The other sets the mode as MUSIC. In this case, the system will choose this page when matching one of the following condition:

  1.   (Mode = MOVIE) and (Input Channel is L/R or C)
  2.    Mode = MUSIC










            Figure 1‑9. Page Condition


  • Debug Window: Power AQ tool debug log.
  • Log Window: It prints the platform log and sends command when connecting to platform. 


                          Figure 1‑10. Log Window.


In addition, each element has an element setting window for private setting. It pop-up when double-clicking the element, and contains three sub-windows:

                             Figure 1‑11. Element Setting Window.

  • Elemtype: The element type information with the following items:
  1. Name: Element type name.
  2. Element Type Id: The unique ID for the element type.
  3. Description: The effect description of the element type.
  4. Multiple Instance: If the element type supports multiple instance or not. If yes, the element can be used synchronously by different threads.
  5. MCPS: MCPS of the element type in the worst case.
  6. Memory: Memory of the element type.
  7. Max Input Channel: The supported input channel of the element type.
  8. Max Output Channel: The supported output channel of the element type.


                                Figure 1‑12. ElemType.

  • ElemSetting: The setting of the element includes:
  1. Element Name: Name of the element. Note that it’s different from element type name. For example, the gain ctrl element type can generate multiple elements which named ELE_GAIN_0, ELE_GAIN_1, ELE_GAIN2…, while all these elements have same element type name “gain ctrl”.
  2. Element Id: Element unique ID. Its high 16 bit is same as element type id.
  3. Input Channel: Element input node.
  4. Output Channel: Element output node.
  5. Default Bypass: If yes, the system bypasses this element by default.
  6. Default Dump: If yes, the system dumps the input and output buffer to USB by default.

After setting, clicking “OK” for saving or clicking “Cancel” for ignoring the change. 

                                 Figure 1‑13. ElemSetting.


  • Parameter: The element parameters. Parameter types are based on the element type, while parameter values are independent of each individual element. There are for buttons on the button of the parameter page:
  1. Set Para: Set and save the parameter. When connecting to platform, it can change the platform parameter in run-time.
  2. Set Disable: It can enable/ disable the element with platform connection.
  3. Default Para: Return to default parameter.
  4. Dump Element: It can dump the element input and output buffer to USB with platform connection.

                            Figure 1‑14. Parameter.


2  Quick Start

This chapter offers some examples of Power AQ tool in common use, which helps user to get started quickly.

2.1  Design PPC

Follow these steps to design post-processing chain(PPC) with Power AQ tool:

Step1: New PPC Project

  •   File-> New project.
  •   Fill the project information as Figure 2-1.


                                Figure 2-1. New Project Window
  • Press OK.
  • The new PPC project will be created as Figure 2-2.

                                            Figure 2‑2. New PPC Project.

  • The folder named as project name will then show up in the project path, which contains PPC project files as Figure 2-3.


                                             Figure 2‑3. New Project Folder.

 Step2: Design Scenario Page

  • Double-click element type. The corresponding element will show up in the design canvas.

      

                                                            Figure 2‑4. New Element.

  • Double-click element to enter element setting window, set its input channel and output channel, and then press OK. The corresponding input and output node will show on the element as Figure 2-6.
  • Set all element input and output channel as well.

                                   Figure 2‑5. Element Setting.



                              Figure 2‑6. Element Input and Output Node.


  • Design links to connect element nodes.

                                     Figure 2‑7. Design Link.



  •    If you have multiple signal flow for different scenario, use “Edit-> New Page” or “Edit->Duplicate Current Page” to create new scenario page as Figure 2-8.
  •    Set the page condition in the condition window to design what scenario this page for. See Figure 2-9.
  •    Design the page conditions and the signal flow for each scenario pages. 


                                     Figure 2‑8. New Page.


                                           Figure 2‑9. Page Condition.


Step3: Adjust Element Paramete

  • Double-click the element to enter parameter tuning page.
  • Set parameters and press “Set Para”.
  • Design all element parameter

                            Figure 2‑10. Element Parameter.


Step4:Save project

  • During step 2 to step 4, use “File-> Save” for saving latest project status.

Step5: Generate Config file

  • File-> Gen Config File.
  • Select file path for saving config file and press OK.
  • If generating config file successes, debug window will show “=== Generate Config File Success! ===”. Otherwise, debug message would show in debug window for tips of fixing post-processing design.
  • The following two config files will be generated in the selected directory (default output path: PowerAQ/debug/$(proj)/$(proj)out).
  1. element_pool.cfg
  2. page_list.cfg

                                                   Figure 2‑11. Generate Config File.


Step6: Test post-processing chain by config file:

Create ppc_cfg folder on USB

  • Copy “element_pool.cfg” and “page_list.cfg” to ppc_cfg folder.
  • Insert USB into MTK platform.
  • Connect PC and MTK platform with UART.
  • Set platform information on Power AQ tool
  1. Platform-> Com Port : choose correct comport
  2. Platform->Baud Rate: 115200*8
  3. Platform->Choose correct platform


                  Figure 2‑12. Platform Setting.


  • Turn on MTK platform and wait log getting stable.
  • Platform-> Connect
  • tools-> Update Config File

Now config file has been updated on MTK platform. The PPC design can be tested by playing test files.

If you want to re-design signal flow, back to step 2-6.


Step7Real-time parameter tuning:

This step is used to fine-tune element parameters in real-time. You can skip it if all the parameter has been determined in previous steps.

  •  Double-click the element to enter parameter tuning page.
  •   Set the parameter value.
  •   Press “Set Para”, the parameter would be set to platform in real-time.

                           Figure 2‑13. Real-time Parameter Tuning.


The following functions can also be used on the real-time tuning and debugging:

  • Press “Set Disable/ Set Enable” to real-time enable/ disable the element.
  • Press “Dump Element” to dump element in/out buffer in USB.
  • Press “Tools-> Save Platform Status” to dump current platform signal flow in USB as config file.
  • Press “Tools-> dump ppc” to dump in/out buffer of the signal flow to USB.

Note: it ONLY temporarily saves parameter value setting on platform during real-time tuning. As long as the platform is turned off, the setting value will disappear. That is, the platform should be keep awake during real-time tuning, and update new config file from Power AQ tool once the platform being turned-off.


Step8: Generate Header file for SW load:

  • File-> Generate Header File
  • Select file path for saving header file and press OK.
  •  If generating header file successes, debug window will show “Generate Header File Success”. Otherwise, debug message would be shown on debug window for tips of fixing post-processing design.


                                                 Figure 2‑14. Generate Header File.

  • The following files will be generated in the selected directory

element_pool.h

page_list.h

 id.h

ppc_app_para.h

peq.h

  • Update header files to

vendor/mediatek/library/ppc/model/inc

  • Build load

2.2  Customized Post-Processing

For integrating customized post-processing into MTK platform, first, refer to the SWIP example in the following path for system integration:
vendor/mediatek/library/ppc/model/SWIP_example

After system integration, create a new element type of customized post-processing in Power AQ tool, and design signal flow with this new element type as follows.

Step1:

  1. Tools->New Element Type:
    Please refer to Function-> Tools->New Element Type section for more detail.
  • Fill in element type information: 

                                                 Figure 2‑15. New Element Type.


  •  Fill in element parameter: 


                                             Figure 2‑16. New Element Type Parameter.

  •  Press OK.


Step2: Design PPC

After creating the new element type, the corresponding element type will show on the element pool with type name. Just treat the new element type as other default modules. For example, double click the element type to create new element and design PPC with it. Moreover, the config file can be generated and updated for testing and tuning. Remember to generate header file with final design for updating software load. 


                            Figure 2‑17. Design PPC with New Element Type.


3. Function

This chapter introduces the items of function bar and short cut menu. 


Figure 3-1. Function Bar and Short-Cut Menu.

3.1 File

  • New Project: Create new PPC project. 
    Figure 3-2 is the new project window which contains the project information need be filled.
  • Project Name: The name of this project
  • Project Path: The file path of project saved.
  • Element Pool File: Choose a specified element_pool.cfg, or check the “Use Default Element Pool” to use default element pool.
  • Page List File: Choose a specified page_list.cfg, or check the “Create Default Page” to use default page list.
  • Platform: Choose the MTK platform you designed for.


                                        Figure 3-2. New Project.

After creating PPC project, the folder named as project name will show in the Project Path. Taking NewProj0 as an example, Figure 3-3 is the composite of the project folder.

  • NewProj0.ppcproj: PPC project file
  • NewProj0element_pool.cfg: The element pool which described element types the project used.
  • NewProj0page_list.cfg: The page list which described scenario pages the project saved
  • NewProj0out: The default output folder for saving the file generated by this project, like config file or header file.

                                                           Figure 3‑3. Project Folder

  • Open Project: Open existed PPC project by choosing *.ppcproj.
  • Save: Save PPC project status.
  • Gen Config File: Generate config file for testing. Choose output folder for saving config file.
  1. Element_pool.cfg: Element types used in this PPC project.
  2. Page_list.cfg: Scenario pages of the PPC project.
  • Gen Header File: Generate header file for final load, including:
  1. Id.h: Element id and parameter id used in scenario pages.
  2. Ppc_app_para.h: The parameter info that allowing app to set and get.
  3. Element_pool.h: Element types used in PPC.
  4. Page_list.cfg.h: Scenario pages of PPC.
  5. Peq.h: The parameters of different modes of peq element.


3.2  Edit

  • New Page: Create a new scenario page.
  • Duplicate Current Page: Duplicate current page to a new page.

                                          Figure 3‑4. Duplicate Current Page.


3.3  Tools

  • New Element Type: Create a new element type mapping to customized post-processing. It can generate elements and tune parameters as default element types. The new element type window containing two pages:
    • Element Type Page: Define the element type information.

                               Figure 3‑5. Element Type Page.

    1. Type name: Element type name.
    2. Type id: Element type id. New element type can set ID in range of 0x0080-0x00ff
    3. Description: the Element type description.
    4. Multiple Instance: Whether the element type support multiple instance.
    5. MCPS: The maximum MCPS of the element type.
    6. Memory: The memory need by the element type.
    7. Maxinput Channel: The input channel set which supported by the element type. Table 3-1 is the channel mapping list:

Channel

Mapping value

Front Left

0x0001

Front Right

0x0002

Front Center

0x0004

Back Left

0x0008

Back Right

0x0010

Back Center

0x0020

Left Surround

0x0040

Right Surround

0x0080

Low-Frequency (LFE)

0x8000

                                    Table 3‑1. Channel Mapping List.

For example, if it supports Front Left, Front Right and LFE, the “Maxinput Channel” value should be equal to
0x0001 (FL) + 0x0002(FR) + 0x8000(LFE) = 0x8003

8. Maxoutput Channel: The output channel set which supported by the element type.


  • Parameter Page: Define element parameters.

                                   Figure 3‑6. Parameter Page.

    1. Parameter Num: The number of parameters.
    2. Name: Parameter name.
    3. Num: The number of value for the parameter.
    4. Integer Value: The default value of the parameter. Support integer only. Multiple values should be separated by commas.
  • Update Config File: Make MTK platform download the config file in USB:/ppc_cfg/.
  • Save Platform Status: Make MTK platform save current PPC in USB.
  • Dump PPC: Dump PPC input and output buffer to USB as __PPC_INPUT.pcm and __PPC_OUTPUT.pcm.

Note that “Update Config File”, “Save Platform Status” and “Dump PPC” should be used after platform connecting to Power AQ tool (Refer to Platform section).


3.4  Platform

This section introduces the environment and functions for platform connection. Note that all control from Power AQ tool to MTK platform should be executing  after connecting to platform.

Equipment

  • MTK platform
  • Power AQ tool (on PC)
  • USB
  •  UART debug board

Environment

Connect MTK platform to UART debug board with UART, and connect UART debug board to USB port of PC with USB.

Connect to Platform

  • COM Port: Choose correct USB COM port.
  • Baud Rate: Select Baud Rate of UART, default 115200*8.
  • Platform: Select MTK platform.
  • Connect:  Connect platform to Power AQ tool.

After turn on the MTK platform, press “Connect”. “CLI is ON ” message will be shown on log window as Figure 3-8. Otherwise, the debug message will be shown in debug window.
Note that as long as platform is turned-off, it should be reconnected by clicking “Connect”.

                                         Figure 3‑8. Connect Platform.

  • CLI prefix: Add CLI prefix in commands send from Power AQ tool. Keep it in checked for MTK platform.

3.5  Help

  • User Guide: The user manual to describe Power AQ tool functions and examples.
  • About: Power AQ tool information, including supported platform and tool version.


3.6  Short-Cut Menu

The Short-Cut Menu includes the short-cut of common-use functions. Some short-cut simplifies the steps for using function.

                 Figure 3‑9. Short-Cut Menu.


  • New Project: Same as “File->New Project” but simplifies the step of filling in project information. It automatically uses default project information:
    1. Project Name: NewProjx
    2. Project Path: $(PPC_Tool)/debug/
    3. Element pool: use default element_pool.cfg in $(PPC_Tool)/debug/
    4. Page_list: use default page_list.cfg in $(PPC_Tool)/debug/
    5. Platform: 8507
  • Open Project: Same as “File->Open Project”.
  • Save: Same as “File-> Save”.
  • Gen Config File: Same as “File->Gen Config File” but simplifies the step of selecting output folder. It automatically uses default output folder in PPC project folder.
  • Gen Header File: Same as “File->Gen Header File” but simplifies the step of selecting output folder. It automatically uses default output folder in PPC project folder.
  • Update Config File: Same as “Tools->Update Config File”.
  • Save Platform Status: Same as “Tools-> Save Platform Status”.
  • Connect Platform: Same as “Platform-> Connect”.



4  Element Type

Introduction

Input is the first element of the signal flow. It controls the sample rate, sample type and input channel supported by the signal flow.

Performance

Performance Index

Performance

MCPS

14 (48kHz, 2ch to 5.1ch)

Dynamic Memory

268

Code

1620

RO

52

RW

0

ZI

0

         Table 4‑1. Input Performance.



Parameter 

  • Support sample rate: The sample rate supported by the signal flow. If the sample rate of input signal is not supported, input element will return fail to make driver bypass PPC.
  • Support sample type: The sample type supported by the signal flow. If the sample type of input signal is not supported, input element will return fail to make driver bypass PPC.
    • 16 bit, MSB: The sample type that represents sample in high 16-bit of the 32 bit.
    • 24 bit, MSB: The sample type that represents sample in high 24-bit of the 32 bit.
    • 32 bit: The sample type that represents sample in 32 bit.

Note that in 8507 platform, all samples are “24 bit, MSB” format before entering PPC.

  • Support channel: The input channel supported by the signal flow. If the input channel is not supported, input element will transfer it automatically to one of the supported channel by default channel mix table.

In parameter tuning page, set support channel number in “support channel” first, and fill channel in “support channel 1”, “support channel 2”… etc. 


                               Figure 4‑1. Input Parameter.


4.2  Output

Introduction

Output element is the latest element of the signal flow. It controls PPC output format. Currently, it simply bypasses signal to driver.

Performance

Performance Index

Performance

MCPS

5 (48kHz, 2ch)

Dynamic Memory

176

Code

1284

RO

52

RW

0

ZI

0

Table 4‑2. Output Performance.

Channel mode: To control PPC output channel. Currently fix to bypass mode for bypassing signal to driver. 

                          Figure 4‑2. Output Parameter.

4.3  Add

Add is the element type to weighted-add all channels into center channel output. 



Performance


Add parameters are represented as channel weight in range of 1~-1. For example, in Figure 4-3, the value of L channel represents the weight(L) in equation (1).

                                Figure 4‑3. Add Parameter.


4.4  Channel Mix

1.1  Channel Mix

Introduction

Channel Mix is to mix input channels into output channels. In equation (2), input channel L/R/C/LFE is mixed into output channel L/R by channel mix matrix. Note that it supports multiple input channel setting but single output channel layout. That is, for one channel mix element, its output channel is fixed but can accept different kind of input channel layout.

Performance

Parameter

Channel mix parameters are introduced to set channel mix matrix. The setting steps are as follows.

  1. Before parameter setting, make sure you have decided the channel mix output channel. It should be same as the layout of element output node.
  2. Press “Add Channel Matrix”.
  3. Select input channel.

                                    Figure 4‑4. Add Channel Matrix.

4. Press Coefficients to enter channel matrix page.

5. Set channel-mix matrix coefficients in range of 1~-1.

6. Press “OK” to turn-off coefficients.

You can add up to 10 channel matrix of different input channel layout. Or delete channel matrix by clicking the corresponding cross. After all, don’t forget press “Set Para” for saving your setting

                         Figure 4‑5. Channel Mix Matrix.

4.5  Gain Control

Introduction

Gain Control controls the gain of each channel.

Performance


Parameter 

Below is the Gain Control parameter:

  • Gain Control Bar: Gain for each channel.
  • Smooth Order: How many samples are used to smooth volume change.

                Figure 4‑6. Gain Control Parameter.

4.6  Master Volume

Introduction

Master Volume controls the volume of all channels.

Performance

Parameter

Below is the master volume parameter:

  • Master Volume Bar: Master volume for all channels.
  • Mute: When mute is checked, all channels will be muted.
  • Smooth Order: Can adjust how many samples are used to smooth volume change.

                   Figure 4‑7. Master Volume Parameter.


4.7 Filter

Introduction

Filter module let user to apply filtering on each channel. It use a series of 2nd order IIR filters for implementation

Performance

  • Order : User can set how many orders of a channel is processed, When order is 2, one 2nd order IIR filter is processed, when order is 4, two 2nd order IIR filter is processed, and so on. All filter parameters are the same for all order
  • Type: User can choose the type of filter to apply
    • PF: Low pass filter
    • HPF: High pass filter
    • BPF: Band pass filter
    • Notch: Notch filter
    • PEQ: Equalizing filter
    • LSH: Low shelving filter
    • HSH: High shelving filter
  • On/Off : Set filter on/off for each channel. When off, filter will bypass processing for that channel.

                                   Figure 4‑8. Filter Parameter.

4.9  PEQ

Introduction

PEQ can let user modify EQ settings

Performance

Parameter

  • Mode : Define mode for current setting, and can add or remove a mode
  • Band Num: Define now many band are utilized to process a channel
  • Channel setting : Adjust EQ parameters for each channel by channel setting
  • PEQ parameters: Set FC, Q value, and gain for each band

                                           Figure 4‑9. PEQ Parameter.

4.9  Delay

Introduction

Delay is to control delay of each channel.

Performance

Parameter 

Delay of each channel can be tuned independently with range of 0~250.

                                    Figure 4‑10. Delay Parameter.


4.1 0  SRS Effect: Csdec

Introduction

Csdec is SRS Circle Surround Decoder version 1.0.1.0. Please refer to the SRS Circle Surround Decoder Opt Design Specification for additional details.

Performance

Parameter 

Please refer to SRS CS Decoder Opt Usage Document.

                          Figure 4‑11. Csdec Parameter.

4.11               SRS Effect: Tshd

Introduction

TSHD is the DTS TruSurround HD version 4.2.0.0. Please refer to the DTS TruSurround HD Universal Usage Document for additional details.  

Parameter 

Please refer to DTS TruSurround HD Universal Usage Document.

                                   Figure 4‑12. Tshd Parameter.

4.12  SRS Effect: Tvol

Introduction

Tvol is SRS Multichannel TruVolume HD version 1.0.1.0. Please refer to the SRS Multichannel TruVolume HD Universal Usage Document for additional details.

Performance

Parameter 

Please refer to SRS Multichannel TruVolume HD Universal Usage Document.

                           Figure 4‑13. Tvol Parameter.


4.13  SRS Effect: HardLim

Introduction

Hardlim is the Hard Limiter algorithm from SRS PureSound version 3.0.0.0. Currently, Hardlim supports stereo input and stereo output only, but can supports mono channel in/out with the signal link as Figure 4-13. Please refer to the SRS PureSound Universal Usage Document for additional details

                   Figure 4‑14. HardLim mono case.

Performance

Parameter 

Please refer to SRS PureSound Universal Usage Document.

                              Figure 4‑15. HardLim Parameter.

4.15 SRS Effect: mb_hardLim

Introduction

Mb_hardlim is the multi-band Hard Limiter algorithm from DTS StudioSound version 2.219.1.0.11707. Hardlim supports stereo input and stereo output only, but can supports mono channel in/out with the signal link as Figure 4-14. Please refer to the DTS_StudioSoundv2_Design_Specification document for further details. 

                 Figure 4‑16. mb_hardLim mono case.

Performance

Parameter 

Please refer to SRS DTS_StudioSoundv2_Design_Specification document.

                     Figure 4‑17. mb_hardLim Parameter.



4.15  Multiband DRC

Introduction

Multiband DRC improves the loudness of audio signal by applying dynamic range control. Please note that Multiband DRC process audio data with the block size of 512 frames, so the Frame Size should be set equal or higher than 512 when this module is applied in the signal flow.

Performance

Parameter 

Below is the multiband DRC parameter:

  1. Band Num: Adjust the number of subbands.
  2. Cros Freq:  Adjust DRC band setting by changing crossover frequencies.
  3. Limiter TH: Threshold of the limiter after multiband DRC process. This value ranges from 0 ~ 32767, which means -∞ ~ 0dB.
  4. Limiter Const: Adjust the recovery speed when the signal energy drops below the limiter threshold. The speed will be faster when this value increases and the range is 1 ~ 100.
  5. Limiter Gain: Adjust the makeup gain setting after the limiter process. This value ranges from 0 ~ 32767, which means -∞ ~ 0dB.
  6. SubBand Makeup Gain: The subband energy upper bound after DRC adjustment
  7. Threshold: Adjust the energy level threshold
  8. Gain: Adjust the additional gain on each energy range

                                    Figure 4-18. Multiband DRC

Global parameters:

  1. Band Num: Adjust the number of subbands.
  2. Cros Freq:  Adjust DRC band setting by changing crossover frequencies.
  3. Limiter TH: Threshold of the limiter after multiband DRC process. This value ranges from 0 ~ 32767, which means -∞ ~ 0dB.
  4. Limiter Const: Adjust the recovery speed when the signal energy drops below the limiter threshold. The speed will be faster when this value increases and the range is 1 ~ 100.
  5. Limiter Gain: Adjust the makeup gain setting after limiter process. This value ranges from 0 ~ 32767, which means -∞ ~ 0dB.

Sub-band parameters:

  1. TH: Adjust the energy level threshold (range: -70 ~ 6dB).
  2. Gain: Adjust the additional gain on each energy range. This value can range from -90.25dB to 96.33dB.
  3. Limiter/Gain: Switch the applying mode of SubGain.
  4. SubGain: In Limiter mode, this value means the subband energy upper bound after DRC adjustment; In Gain mode, this value means the additional subband gain after DRC adjustment. The range of this value is -90.25 ~ 96.33dB.
  5.  ATTTime: Adjust the attack time
  6.  RELTime: Adjust the release time


5  FAQ

5.1 USB does not exist

  • Create ppc_cfg folder on USB
    1. If  USB does not exist ,please make a new file under /mnt/ppc_cfg
    2. adb push D:/page_list.cfg /mnt/ppc_cfg/
    3. adb push D:/element_pool.cfg /mnt/ppc_cfg

                                                  Figure 5-1. Multiband DRC

问题提交