John Curl's Blowtorch preamplifier part II

Status
Not open for further replies.
Pavel, are you saying that you used Audacity to do the recording?

Oh no! :)
Thanks for clarification re dither.

One more remark. The ADC input range was 200 mVrms. (0dBFS = 200 mVrms). This makes it close to standard volume setup of the preamp, 200 mV would make about 4V at the ouput of the power amplifier.
 
Last edited:
Administrator
Joined 2007
Paid Member
Rerun with Foobar. On the third run I thought I would try and detect any difference in the piano envelope in the quieter parts. I would like to say that I was onto something but the concentration needed is huge and beyond this point the score fell away. But it was all as it happened.
 

Attachments

  • Rerun 1.PNG
    Rerun 1.PNG
    17.2 KB · Views: 147
  • Rerun 2.PNG
    Rerun 2.PNG
    16.9 KB · Views: 144
  • Rerun 3.PNG
    Rerun 3.PNG
    17.3 KB · Views: 142
Comparison of distortion of the loaded and unloaded preamp. It is measured at higher amplitude than used in the test, otherwise everything would remain in noise even with narrow band FFT. Measured with notch filter, to see anything. Distortion components have changed from about -125dB (re fundamental) for unloaded to -120dB for loaded preamp. The output stage is biased at 40mA, it is very deeply in class A even if loaded.
That might be very nice in theory, but the reality, on the ground, of what the full chain of playback/preamp/record is doing is somewhat different - it was very easy for me to find an obvious distortion between the source file and its copy:

Direct,Bolton02.png
 
Rerun with Foobar. On the third run I thought I would try and detect any difference in the piano envelope in the quieter parts. I would like to say that I was onto something but the concentration needed is huge and beyond this point the score fell away. But it was all as it happened.

I unfortunately cannot share Pavel's enthousiasm about this score. The 'low probability that you are guessing' test only involves 5 tries. This makes it statistically more insignificant than the ones with a 'high probability that you are guessing', which consist of 9 tries.

Therefore, the outcome of the whole test - to me - is that you cannot discern an audible difference. Which is to be expected given the almost identical distortion profiles of both wav files.

The problem is that it is just very difficult psychologically to acknowledge a null result.
 
That might be very nice in theory, but the reality, on the ground, of what the full chain of playback/preamp/record is doing is somewhat different - it was very easy for me to find an obvious distortion between the source file and its copy:

View attachment 447290

And what is the source of distortion, Frank? Is it DAC, is it ADC, is it your sample rate conversion, it it a reconstruction filter used to display the samples, is it non-simultaneous sampling, time shift of the samples or anything else? At least the distortion measurement is quite accurate, same for time domain measurements. Everything else, like sampling errors and data manipulation is out of control.
 
And what is the source of distortion, Frank? Is it DAC, is it ADC, is it your sample rate conversion, it it a reconstruction filter used to display the samples, is it non-simultaneous sampling, time shift of the samples or anything else? At least the distortion measurement is quite accurate, same for time domain measurements. Everything else, like sampling errors and data manipulation is out of control.
Somewhere in your copy chain, Pavel. Have a look at the size of the glitch - do you think software capable of 190dB and 1u sec resolution is going to inject that sort of anomaly? I've done much very high resolution work with Audacity, and in this sort of thing it's rock solid.
 
Somewhere in your copy chain, Pavel. Have a look at the size of the glitch - do you think software capable of 190dB and 1u sec resolution is going to inject that sort of anomaly? I've done much very high resolution work with Audacity, and in this sort of thing it's rock solid.

You are comparing the original data, 44.1kHz/16bit, with one of my recordings, performed at 48kHz/16 bit.
How was my recording done? 1st, 44.1kHz/16 bit was converted to 96kHz/24bit in foobar. Even this operation itself may change the envelope visually. The 96kHz/24 bit data were feeding the DAC (it works with smallest errors at 96/24) and two recordings, Bolton (unloaded) and Blomley (loaded) were done in 48kHz/16bits. Please do not compare Bolton/Blomley to Direct WAV, compare Bolton to Blomley only.
 
The editing software is doing exactly what a replay chain does when it is working perfectly - forming an analogue construct from the data points; joining the dots. At any specific time from the start of the waveform, a correct, analogue reconstruction of the audio signal will always look identical, irrespective of the sample rate or anything else - if it doesn't, then the signal has been distorted - on that image I posted the dots are so close together because of the level of oversampling that they are not shown, they perfectly fall on the path shown, they are all immediately adjacent. Look at the timeline, and the level of oversampling - they are continuous on the shown curve.

Interestingly, the distortion is worst at the beginning, it settles down and is far less obvious further along the clip - but has problems with DC offset, and gain.
 
Interestingly, the distortion is worst at the beginning, it settles down and is far less obvious further along the clip - but has problems with DC offset, and gain.

Once again I would like to emphasize that Bolton x Blomley should be investigated. This is where the change (load added) was done. We are not exploring the SRC/DAC effect, we are exploring preamp under added load condition.
 
Status
Not open for further replies.