nick_l44.1
Member
- Joined
- Jan 11, 2024
- Messages
- 44
- Likes
- 31
You would need to charge the Quedelix if you weren't powering it from the phone which would be a bit of a nuisance.Thank you for the replies, I actually prefer it to a dongle because it is powered by electricity and doesn't drain my smartphone, so for me it's much more convenient that way.
Actually, given the DL200 static background noise, which is basically due to BT data transmission (having tried airplane mode, no Wi-Fi, but only BT on), in my case it would have been better if I had opted for a Qudelix 5K always connected via USB to the current (preserving its battery). Much smaller, with superlative EQ features and it would have cost me a lot less too.
Mine unit arrived yesterday and at first I got some noise when using BT (did not matter the CODEC) like a repeating pop sound. But if I toggled the input to another one and go back to BT the noise was mitigated - mainly with LDAC.Thank you for the replies, I actually prefer it to a dongle because it is powered by electricity and doesn't drain my smartphone, so for me it's much more convenient that way.
Actually, given the DL200 static background noise, which is basically due to BT data transmission (having tried airplane mode, no Wi-Fi, but only BT on), in my case it would have been better if I had opted for a Qudelix 5K always connected via USB to the current (preserving its battery). Much smaller, with superlative EQ features and it would have cost me a lot less too.
I've reported earliear about bluetooth issues. Maybe it's the same thing.Mine unit arrived yesterday and at first I got some noise when using BT (did not matter the CODEC) like a repeating pop sound. But if I toggled the input to another one and go back to BT the noise was mitigated - mainly with LDAC.
SBC has some inerent noise that's hard to remove.
I did some measurements using REW and an audio interface and I had no clipping problems.I've reported earliear about bluetooth issues. Maybe it's the same thing.
My "problem" (I can't reproduce it anymore) was different but I happy for you to be able to sort it outGuys, the problem is the antenna which comes with the DL200. I've replaced it with one all in plastic and there's no static, no noise at all.
Solved.
Hi Olivia, can you attach the firmware file here? ThanksFor those (like myself) who have inadvertently installed that firmware available on this thread and found their DL200 to have become less stable, I have just obtained a firmware numbered V1.2 from SMSL itself (upon requesting the original firmware).
Now, according to the text below (translated by Copilot from interface gibberish), Device Model, Firmware Version, and Timestamp listed in V1.2 are rigorously the same as those of the firmware above, which in turn are the same as those shown in a C200 update manual also previously linked to in this thread. Device model, however, seems to refer to an STC MCU, and not to the DL200 itself. I am then not sure if all the info refers just to the controller itself for the firmware update rather than to what is actually being updated. If so, might there also be something else happening in the background that is not being shown in the log below? No clue! If you do not hear from me again, though, assume my DL200 has become stable!
Device Model: STC8G2K64S4
- Firmware Version: 7.3.12U
- Current Configuration:
- ISP Clock Frequency: 24.089 MHz
- Internal RC Oscillator Frequency: 12.001 MHz
- Timer1 Frequency: 35.850 KHz
- EEPROM Size: 10 K
- Port P3.2 and P3.3 are not used for UART communication.
- High-level input during reset.
- I/O Port Configuration: General-purpose I/O
- Low-level input detection.
- Low-level output detection voltage: 3.00 V
- UART communication with automatic baud rate detection.
- UART communication with automatic parity check.
- UART communication without hardware flow control.
- Analog input voltage range: 1189 mV (specified range: 1100~1300 mV)
- Firmware timestamp: July 31, 2021
- Post-Update Configuration:
- ISP Clock Frequency: 24.089 MHz
- Internal RC Oscillator Frequency: 11.998 MHz
- Timer1 Frequency: 35.850 KHz
- EEPROM Size: 10 K
- Port P3.2 and P3.3 are not used for UART communication.
- High-level input during reset.
- I/O Port Configuration: General-purpose I/O
- Low-level input detection.
- Low-level output detection voltage: 3.00 V
- UART communication with automatic baud rate detection.
- UART communication with automatic parity check.
- UART communication without hardware flow control.
- Analog input voltage range: 1189 mV (specified range: 1100~1300 mV)
- Firmware timestamp: July 31, 2021
- Device ID: F764C5240B0397
- Additional Information:
- User-defined oscillator frequency: 12.000 MHz
- Post-update oscillator frequency: 11.998 MHz (deviation = -0.020%)
Is IMD via headphone out or line out? If, line out SE or balanced?I got DL200 HPA THD+N under different loads.
Low gain
View attachment 343053View attachment 343055View attachment 343057
High gain
View attachment 343052View attachment 343054View attachment 343056
I should note that due to the high UHF noise, clipping occurred in my notch filter, and not in the DL200. And my measurement does not refute the official data on maximum power output.
And finally IMD SMPTE vs Level at Low/High gain
View attachment 343059View attachment 343058
That's all for now
Thanks. What's the difference in test signal or setup between the two graphs?It was HPA output with HPF. Please note that REW results can't be directly compared to AP ones. REW calculates imd without noise.
Here's standard SMPTE TRS results (still without noise):
View attachment 356138View attachment 356139
If you mentioned my smpte ffts, these are just left and right channels.Thanks. What's the difference in test signal or setup between the two graphs?
The hump always exists. It's just not masked by noise in my measurements. The AP results always take noise into account, so the hump may not be visible.Yeah, I did. The whole reason I asked was that those IMD vs. level plots on the HPA seem to show an ESS hump. Is that present on the balanced line outs, too?
Can you share this firmware please ?For those (like myself) who have inadvertently installed that firmware available on this thread and found their DL200 to have become less stable, I have just obtained a firmware numbered V1.2 from SMSL itself (upon requesting the original firmware).
Now, according to the text below (translated by Copilot from interface gibberish), Device Model, Firmware Version, and Timestamp listed in V1.2 are rigorously the same as those of the firmware above, which in turn are the same as those shown in a C200 update manual also previously linked to in this thread. Device model, however, seems to refer to an STC MCU, and not to the DL200 itself. I am then not sure if all the info refers just to the controller itself for the firmware update rather than to what is actually being updated. If so, might there also be something else happening in the background that is not being shown in the log below? No clue! If you do not hear from me again, though, assume my DL200 has become stable!
Device Model: STC8G2K64S4
- Firmware Version: 7.3.12U
- Current Configuration:
- ISP Clock Frequency: 24.089 MHz
- Internal RC Oscillator Frequency: 12.001 MHz
- Timer1 Frequency: 35.850 KHz
- EEPROM Size: 10 K
- Port P3.2 and P3.3 are not used for UART communication.
- High-level input during reset.
- I/O Port Configuration: General-purpose I/O
- Low-level input detection.
- Low-level output detection voltage: 3.00 V
- UART communication with automatic baud rate detection.
- UART communication with automatic parity check.
- UART communication without hardware flow control.
- Analog input voltage range: 1189 mV (specified range: 1100~1300 mV)
- Firmware timestamp: July 31, 2021
- Post-Update Configuration:
- ISP Clock Frequency: 24.089 MHz
- Internal RC Oscillator Frequency: 11.998 MHz
- Timer1 Frequency: 35.850 KHz
- EEPROM Size: 10 K
- Port P3.2 and P3.3 are not used for UART communication.
- High-level input during reset.
- I/O Port Configuration: General-purpose I/O
- Low-level input detection.
- Low-level output detection voltage: 3.00 V
- UART communication with automatic baud rate detection.
- UART communication with automatic parity check.
- UART communication without hardware flow control.
- Analog input voltage range: 1189 mV (specified range: 1100~1300 mV)
- Firmware timestamp: July 31, 2021
- Device ID: F764C5240B0397
- Additional Information:
- User-defined oscillator frequency: 12.000 MHz
- Post-update oscillator frequency: 11.998 MHz (deviation = -0.020%)
This is strange because i ask for the last firmware to SMSL and they said it is the 1.1 not 1.2Can you share this firmware please ?
Thanks
Don't stick the multimeter probes into the sockets, you may short the outputs.Is it save to take a multimeter to the socket in order to measure output voltage (to volume match the two, I mean)