ΣSigmaStudio Ask AI Русский Log in

Mute module issue at ADAU1401A

SigmaDSP & SigmaStudio takepiro Sep 26, 2011 00:00 5 replies Original on forum ↗
Subscribe
takepiro Question
Sep 26, 2011 00:00

Dear support team,

Mute module(with SW RC type Slew) occasionally outputs wrong data.

Could you tell me cause and measures,please?

Symptom:

Please check attatched file (wrong_data.PNG, wrong_data2.PNG,nomal_data.PNG).

Test project file is also attatched.(Mute_clip_dspproj)

This issue is shown in every about 100~200 times in this project.

(The waves of normal_data.PNG is almost observed.)

Though I do not understand of why,

when IIR filter( low frequency band pass filter) is placed in before mute module,

The incidence increases.

Environment:

Sigma Stadio 3.4

EVAL-ADAU170XEBZ

Best regards,

Takehiro Yabune

adau1401a

Audio Signal Processors

adau1401

mute

SigmaDSP Audio Processors

ADIApproved Reply
Sep 27, 2011 00:00

Hi Yabune-san,

Thanks for your report. Do you have a specific project that shows this problem? Perhaps we can try to use the project and simulate in software to debug the issue. Since this is software slew, it probably means that there is no hardware issue involved.

Best Regards,

Brett

takepiro Reply
Sep 27, 2011 00:00

Dear Brett-san,

Thank you for your supports.

I attatched the specific porject in this thread.

Mute_Clip.dspproj.zip

You can show the issue,when you try to change Off to On at Mute module 100 ~ 200 times.

Best regards,

Takehiro Yabune

ADIApproved Reply
Sep 30, 2011 00:00

Hi Yabune-san,

I was able to reproduce the issue. Our software manager is investigating the issue now.

ADIApproved Reply
Sep 30, 2011 00:00

Hi Yabune-san,

We discovered the root cause of the issue. The reason why sometimes the gain jumps to a very large value is that SigmaStudio is not using Safeload when it writes the Mute parameters.

When using Block Write, there is a chance that a parameter will be half-way updated when the instruction is executed, meaning that the value will be corrupt for that frame.

In order to avoid this issue, Safeload must be used. Safeload is described in detail in the datasheet.

To use safeload in SigmaStudio, open the capture window and the sequencer.

Click the control in the schematic in the Block Write will show in the Capture window.

Highlight the writes in the Capture window and drag them to the Sequencer side.

Change to Safeload by right-clicking and selecting from the menu:

Click the Download Mode to Hardware button:

The writes now occur as Safeload instead of Block Write.

I ran the test 500 times with no clipping:

6f1a7b721353218223ec95322288c319.jpg
6f1a7b721353218223ec95322288c319.jpg
6f1a7b721353218223ec95322288c319.jpg-450x25.jpg
6f1a7b721353218223ec95322288c319.jpg-450x25.jpg
9b9c0483a002ab40752a8e6f7c2d5989.jpg
9b9c0483a002ab40752a8e6f7c2d5989.jpg
9b9c0483a002ab40752a8e6f7c2d5989.jpg-450x64.jpg
9b9c0483a002ab40752a8e6f7c2d5989.jpg-450x64.jpg
0207df471935470d62142448e330563e.jpg
0207df471935470d62142448e330563e.jpg
0207df471935470d62142448e330563e.jpg-450x152.jpg
0207df471935470d62142448e330563e.jpg-450x152.jpg
9f03154456b47922b9913744b284435e.jpg
9f03154456b47922b9913744b284435e.jpg
9f03154456b47922b9913744b284435e.jpg-450x54.jpg
9f03154456b47922b9913744b284435e.jpg-450x54.jpg
966d4d7e4f2c0b675702d2bae652794c.jpg
966d4d7e4f2c0b675702d2bae652794c.jpg
966d4d7e4f2c0b675702d2bae652794c.jpg-450x206.jpg
966d4d7e4f2c0b675702d2bae652794c.jpg-450x206.jpg
1c0cdd222412093727419a97203deca3.jpg
1c0cdd222412093727419a97203deca3.jpg
1c0cdd222412093727419a97203deca3.jpg-435x113.jpg
1c0cdd222412093727419a97203deca3.jpg-435x113.jpg
e83c7225a7479d064f6118298c3cf8ac.jpg
e83c7225a7479d064f6118298c3cf8ac.jpg
e83c7225a7479d064f6118298c3cf8ac.jpg-450x99.jpg
e83c7225a7479d064f6118298c3cf8ac.jpg-450x99.jpg
f361c53dbc7d2f74da0afda05b411b21.jpg
f361c53dbc7d2f74da0afda05b411b21.jpg
f361c53dbc7d2f74da0afda05b411b21.jpg-450x130.jpg
f361c53dbc7d2f74da0afda05b411b21.jpg-450x130.jpg
ADIApproved Reply
Sep 30, 2011 00:00

We will make the mute cell use Safeload writes by default in the next beta.

Note that in a production system, it is advised to use safeload for all real-time parameter changes.