Skip to content
TheChatArchiveThe Chat Archive
Qwenqwen3-30b-a3b· Alibaba (Qwen)Hugging Face LMArena Human Preference 140K

It is a control signal, but I can read it with a 5.19 Readback, and 28.0 signals cannot…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with o4-mini-2025-04-16’s answer.
  1. User

    It is a control signal, but I can read it with a 5.19 Readback, and 28.0 signals cannot be readback this way...

  2. Qwen Assistant

    You're absolutely correct in observing that the flag output is a control signal, but the DSP Readback format (5.19) allows you to read it even though 28.0 is the standard format for control signals. Here's how to reconcile this and update the wiki accurately:


    Key Clarifications:

    1. Native Format of the Flag Output:

      • The Signal Detection block outputs a binary control signal (0 or 1), which is natively represented as a 28.0 integer in SigmaDSP systems (as per the context: "Control signals... represented with A = 28 and B = 0").
      • This means the raw value is stored as an integer (e.g., 1 for "signal detected," 0 for "no signal").
    2. Why 5.19 Readback Works for the Flag:

      • The DSP Readback block interprets the raw binary data based on its configured format (5.19 in this case). If the actual value is 1 (in 28.0 format), the Readback block will interpret it as: Value=1219×25=1.0(since the 5.19 format has 5 integer bits and 19 fractional bits).\text{Value} = \frac{1}{2^{19}} \times 2^5 = 1.0 \quad \text{(since the 5.19 format has 5 integer bits and 19 fractional bits)}.
      • Similarly, 0 will remain 0.0. This works because the flag values (0 and 1) are within the range of 5.19 (which can represent integers from -16 to +15.999...).
    3. Limitation of 28.0 Readback:

      • If you attempt to read a 28.0 integer (e.g., a value like 1) using a DSP Readback block set to 28.0, it would not display correctly on older SigmaDSP processors (like ADAU1701), which lack 28-bit accuracy. Instead, the value would be truncated to 0.000000000.
      • This is why the context emphasizes bit-shifting (e.g., multiplying by 4 twice) to convert 28.0 integers to 24.0 format for display.

    Wiki Update Recommendation:

    To reflect both the native format and the practical Readback behavior, update the wiki entry as follows:

    Name                    Format [int/dec] - [control/audio]    Function Description
    Pin 0: Trigger          28.0 - control                       Outputs a flag after no signal has been present for a given amount of time
    
    Note: The flag is a binary control signal in 28.0 format (integer representation). When read back using a DSP Readback block, it can be interpreted in other formats (e.g., 5.19) if the values are within the range of that format. For example, values of 0 and 1 will appear as 0.0 and 1.0 in 5.19 format. However, 28.0 is the native format for control signals.
    

    Why This Works:

    • Accuracy: The native format (28.0) is documented as the standard for control signals.
    • Practicality: The note explains how the flag can be read in 5.19 format due to its limited range (0 and 1), avoiding confusion about why the Readback works.
    • Avoids Misinformation: It clarifies that while 5.19 is used for display, the actual signal is 28.0.

    Additional Context for Users:

    • For older SigmaDSPs (e.g., ADAU1701): If you need to read 28.0 control signals, use 24.0 format with bit-shifting (e.g., multiply by 4 twice) to avoid truncation.
    • For newer SigmaDSPs: 28-bit accuracy is supported, so 28.0 format can be used directly.

    This approach ensures clarity for both technical and practical use cases.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.