Jump to content


  • Posts

  • Joined

  • Last visited

  • Country

    United Kingdom

Personal Information

  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Double check your device volume itself isn't <100. For some reason ALSA / Linux sets a lot of devices to 45/100 by default. Many dacs the hardware addressable volume won't do anything. But some like the may do have dsp vol control on the USB implementation so it will indeed make it quieter. In Windows check the device volume is set to 100. For Linux check device volume too. (I just told roon to use 'device volume' and set it to 100 and that sorted it). I had the same thing in the terminator plus but the hardware vol control doesn't do anything on it so it didn't actually make anything quieter
  2. An extension cord/physical distance would only potentially help emi. But it could make ground/rf noise worse due to... Well... Much more wiring to pick up the noise :P And will not help a dc offset. A dc offset has to be addressed with a dc blocker. (or ignored if its minor enough)
  3. This is caused by DC offset on your mains, which saturates the transformer core and causes it to hum. Its annoying, but not harmful. Just means the transformers are slightly less efficient. But the ones in the may are specced for 400% of what it draws anyway. I get dc offset every day from about 9am to 11am. Not sure why but its there every day. Everything I have with a big transformer just starts humming :P You can buy something like the humX or ifi dc blocker to address the issue
  4. Denafrips Gaia measurements, including testing clock-syncing with Terminator plus are up here: https://goldensound.audio/2021/10/04/denafrips-gaia-measurements-with-terminator-clock-sync-test/
  5. You can convert 16 bit source info to 24 bit to apply DSP with less loss of accuracy/dynamic range. There is no reason you have to keep 16 bit as 16 bit (and internally the vast majority of dacs will not) No I'm not. The serene is an active preamp. https://www.l7audiolab.com/f/measurements-of-holoaudio-serene-preamplifierpre-retail/ As mentioned, I'll do a practical demonstration showing the effect of dynamic range in a preamp in the next few days.
  6. The issue is that whilst most music might be 16 bit, the DAC in most modern examples will have THD, SNR and AES17 Dynamic range higher than that, and oversampling/dsp volume control will likely be being done at a higher bit depth than the source material too. Which is why 96dB isn't enough to call something 'perfect'. Dithering and noise shaping also have enormous effects Additionally, I understand that the preamp doesn't affect the source material, but it is part of the playback chain. If you have a DAC with say 120dB dynamic range, and you attenuate 10dB in DSP, you will lose 10dB dynamic range (in most cases, some dacs with non-linear THD+N/level performance might be slightly different). But if you have say a preamp with 140dB dynamic range. Now, you could attenuate by 10dB, and it's entirely likely that the noise floor of the preamp is still well below that of the DAC. Meaning you might still have the full 120dB dynamic range as you'd be limited by the DAC not the preamp. I did a few tests with this on the spring 3 and found that I got about 5dB extra headroom before dynamic range was affected (and the spring 3 has exceptionally high dynamic range anyway so could attenuate further before dynamic range reaches the level of many other similarly priced dacs). The Holo Serene is probably the most drastic example of this due to the quite frankly ridiculous dynamic range it has. I'll take it out of my chain and do some practical demonstrations of the above in the next few days. Need to wait for a new headphone amp to arrive then I can take the serene out and put it on the measurement bench
  7. I am! For the money it's a crazy good option IMO. L1/L2 spring 3 have the 'normal' usb card. Still has galvanic isolation, but no titanis chip and not as advanced. How much of a difference that makes I cannot say as I've not compared the two. I said $2500 cause L2 is $2500. (L1 being cheaper and KTE being a bit more). Having tried the KTE and L2 may though, there is a very subtle difference but not enough to change anything I said in my may video for example. The spring 3 l1/2/3 have some slight component upgrades but they're the same design, same dac. It's not going to make it a drastically better/worse product or anything.
  8. Posted my full review of the spring 3 with some comparisons to May and Spring 2 :) :
  9. This is just on the spring 3. It's not just an attenuator though it's an actual class A preamp module. Spring 3 max output with the preamp at max is 11v I think. For the may though the intention is to pair it with serene
  10. You have to replace the kernel with the appropriate modded one from miska. https://www.sonarnerd.net/src/ Unfortunately this is not too straightforward so the easiest option is use the HQP OS image if possible.
  11. This is likely your Linux install. Linux cannot do 1.536mhz stock. You either need to replace the kernel with Jussi's modified one, or use the hqp naa x64 image. HQP naa image is the easiest one. Kernel install can be a bit of a hassle but is handy if you want to be able to use roon Bridge and hqplayer without changing os.
  12. It's basically due to the maths of how FFT works/what it is showing. Here is an example of an analog signal, with many different tones: Now, you can see that on the top right in the FFT, each individual tone is only up to about 200mv (0.2v). But our peak and RMS values are MUCH higher. This is because as you can see in the scope view in the top left, all these individual tones combine to create a waveform that will have a higher amplitude than just one of those tones. And so that waveform peaks at about 2.89V. The FFT is showing us a clearer view of what the signal contains, but it's showing us the level of each individual frequency/part of the signal (Bin), not the level of the signal as a whole. The exact same thing happens when looking at the spectrum/waveform of jitter. And the problem is worse because the stuff we are looking at is so close to the noise floor. For a signal where the main 1khz tone etc is going to be >100dB above noise and harmonics, then any noise/harmonics are going to be 0.0001% or so of the whole signal, and will have almost no impact on the peak/rms values. But when we are looking at stuff where there is lots of content of a similar/close value, like with the above example of lots of tones, or in the case of jitter, where there is a noise floor and some small spikes just a little tiny bit above it, then everything has a noticeable impact. Here's another analog signal example. 25uV 1khz sine, just slightly above the noise floor: Here we can see the 25uV 1khz sine, but we also have a lot of noise not too far below it. Meaning that is having a noticeable effect on the peak/RMS value. You can see on the scope how much it's impacting it. And as a result the waveform is peaking at about 76uV, with an RMS value of 26.48. And in a situation where we have no main signal and are just looking at noise: The noise floor on the FFT might look like it's at about 20nV. But all of that is combining to make a waveform that peaks at almost 9uV, wayyyy higher than the FFT shows. This is also why you should never judge the noise floor of a device based on FFT, it can be changed/altered depending on how the FFT itself is set up. TLDR: FFT shows you the level of individual parts of the signal by dividing it into different frequencies. It does not show the absolute peak value of the signal. Hope that helped!
  13. So the ALSAmixer volume might not actually address the hardware's inbuilt vol control I don't think. I'm not actually sure what the best way to do it on linux is. I've had a few dacs where the volume was not 100%, so in roon I had to change to 'device volume', set to 100%, then go back to 'fixed volume' and it was fine. (Or on windows just adjust vol to 100) I'm using a linux streamer atm and vol on the spring 3 is fine
  14. Not sure if you can change hardware vol via hqp os. You might need to temporarily plug it into a Windows machine to check its at 100 and then swap back.
  15. Double check you've not got the hardware vol set to a low value? May's USB implementation has hardware vol so in roon set vol control to 'device volume' and make sure it's at 100%. In windows check that the windows vol is 100%
  • Create New...