Hugo M Scaler by Chord Electronics - The Official Thread
Jan 6, 2019 at 7:51 AM Post #4,816 of 18,627
I took my lid off to update to the current IR remote window glass . . . . there isn't much to see though.


It would funny if under that heatsink was just a 4g micro sim card :)

Although I can’t see the underside, it would be good if it was all copper and with aluminium on the top for heat dissipation.

Copper is much better at drawing heat from the cpu and aluminium is much quicker at getting rid of the heat.

Which makes welding aluminum very challenging.
 
Last edited:
Jan 6, 2019 at 9:36 AM Post #4,818 of 18,627
Maybe possible using this process, because this mixes the metals in a fluid state.
Would probably double the price of the MScaler though.
:)

Probably, even though I haven’t yet looked at the link yet. I was just meaning trying to manually weld a piece of cast aluminum, as the metal needs to be at a certain temp for the welds to be good, but cast aluminum loses heat very quickly and can be a pita to weld.
 
Jan 6, 2019 at 2:54 PM Post #4,822 of 18,627
It would definitely help for some types of RFI, but not for others. Remember, the issue isn't something corrupting the digital stream (if that happened, you hear drop outs and pops...very very obvious problems) The issue is unwanted signal being injected into the DAC, usually impacting the ground plane. Remember, that in the D to A stage, the reference is the ground plane. If the ground plane is bouncing around, then there is a definite audible impact on the analog output

So in managing RFI, where are all the places that it can get injected into your DAC? Those are your soft spots. The DAC designers build in a lot of shielding and isolation for those soft spots, but stuff can still leak through.

For mScaler and a DAC, you work backwards from the DX inputs on the DAC: the cables can pick up ambient signal in the air (shielding can help here), the cables can be touching something (power cord, etc) and picking up some stray fields (shielding can help here), or the cables can be transmitting RF from the mScaler (shielding **won't** help here).

It is the last case where the ferrites made a huge difference. The mScaler is a pretty serious compute engine and is generating RF at particular frequencies. Some of that leaks through the BNC cables to the DAC.

Based on their geometry and the materials they are built from, the ferrites are basically dampeners for particular frequency ranges (think of them as filters). A lot of the early experiments with ferrites was looking for the frequencies that needed to be filtered out (turned out to be in the 2.5GHz range, IIRC) Putting these on the BNC cable basically absorbs the RF energy in this frequency range so it doesn't get to the sensitive DAC. More ferrites tuned to the frequencies you want to filter, the more you filter out. Eventually, you filter out so much that you can't hear the impact any more.

Now different ferrites dampen to different degrees at different frequency ranges. Even if a ferrite is a weak filter at some rogue frequency, enough of them and you can filter stuff out. As long as the core digital signal (384MHz) remains strong enough for the DAC to lock on to it, filter away. There is no value outside of that 384MHz signal. If the DAC loses its lock on that signal, you will hear it in a big way (its a cliff, not a gradual degradation).

Now it so happens that WiFi (and microwaves and a bunch of other wireless equipment) really hammers on the 2.4GHz band. Well shielded BNC cables would definitely help here (keep the cables from being an antennae), but they won't help with RF being generated in the mScaler itself.

As always, very very environment dependent. Ferrites (and BNC cables) are relatively cheap. For <$100, you can experiment with cables and ferrites and see what you hear (see my big Blu2 review linked below, where I documented my ferrite experiments...I included some links there). If you add ferrites and you don't hear a difference, that's awesome, you're all set. If you do, keep adding them until you don't any more.

RF is insidious though. Upstream from your mScaler is USB (and the computer behind it) and power supplies to both your DAC and the mScaler. These are all potential vectors for RF to leak into your DAC and impact SQ. When evaluating things upstream from your HMS, your reference (At least with respect to RF) should be against an optical input. When you get your usb to sound as good as optical, you’ve arrived.
But not clipp on ferrites on mscaler...Rob said.....
 
Jan 6, 2019 at 5:39 PM Post #4,826 of 18,627
supposed to be a drop of 3DB at least with blu2
 
Jan 6, 2019 at 5:47 PM Post #4,828 of 18,627
With the Qutest, I’m not seeing any difference in the indicator lights for SR when going from 44.1 to 96khz. My Brooklyn DAC is showing me a jump from 352.8 to 384.0 so the MScaler is sampling those properly, but I don’t see it going between 705 to 768 on the Qutest. I know the lavender color indicators up that high are similar, but I can’t see a shift in color.
 
Jan 6, 2019 at 5:58 PM Post #4,829 of 18,627
I noticed that the volume level dropped by around 6 db when I added the Mscaler to Hugo TT2. I drive Omega speakers directly from the TT2.
Is this normal?
A lot of people are interested in how the omega perform with tt2. If you had a few minutes to comment, that would be amazeballs.
 
Jan 6, 2019 at 7:16 PM Post #4,830 of 18,627
With the Qutest available there’s simply no need to either ask the question or look elsewhere

Some of you guys don’t realize the obvious

Can we connect an headphone directly to Qutest? Even if we could there would not be volume control. So you are not realizing the obvious: the Qutest is useless for the majority of people.
 

Users who are viewing this thread

Back
Top