rstcologne
Registered
Thread Starter
- Joined
- Nov 23, 2021
- Posts
- 2
Hi all,
likely my question is related to a user error but I can't figure it out.
I'm running 5.20.4 and I'm trying to measure Thiele Small parameters following a mix of the audio judgement tutorial and the manual. I have built the cable and measured it thorugh a couple of times, no short circuits, near zero ohms where expected and the 100 ohm also where expected.
When trying to run the short circuit calibration, I get the following error:
Measurement input should be much lower than the reference input for the short circuit calibration but it is not - the measurement peak is -32,8 dBFS, the reference peak is -21,2 dBFS.
If I switch left and right on the input side (hardware), I get the same error but the values change, measurement is -21, reference is -32.
As I do see different values for the channels, it looks to me like my cable is ok and that my soundcard is indeed picking up two separate channels. However I'm really confused that I get the error in both cases. Is this a bug or am I missing something?
Thanks,
Richard
likely my question is related to a user error but I can't figure it out.
I'm running 5.20.4 and I'm trying to measure Thiele Small parameters following a mix of the audio judgement tutorial and the manual. I have built the cable and measured it thorugh a couple of times, no short circuits, near zero ohms where expected and the 100 ohm also where expected.
When trying to run the short circuit calibration, I get the following error:
Measurement input should be much lower than the reference input for the short circuit calibration but it is not - the measurement peak is -32,8 dBFS, the reference peak is -21,2 dBFS.
If I switch left and right on the input side (hardware), I get the same error but the values change, measurement is -21, reference is -32.
As I do see different values for the channels, it looks to me like my cable is ok and that my soundcard is indeed picking up two separate channels. However I'm really confused that I get the error in both cases. Is this a bug or am I missing something?
Thanks,
Richard