Hrm.
Have you done a similar comparison with audio that's actually recorded in GarageBand vs what's coming straight from the VU2?
Also, do you have speakers connected to the Scarlett's line outs? And if so, how's the difference there? I'm wondering if maybe the issue is the headphone monitoring circuit. It's not impossible that preserving the low latency with high-fidelity audio involves some manipulation of the signal to reduce bandwidth.
I haven't heard any such issues with my Clarett 4Pre, but I know that's not quite the same beast. You could have a faulty unit, or the headphone monitoring could be filtered a bit by design.
Another test is: does your computer have a separate onboard audio output? If so, you could record some stuff, export that to .wav or .mp3 or whatever format works, and play it in a media player using the onboard drivers. If it's still thin, that's proof there's a real problem with the Scarlett's actual recording functionality.
Have you done a similar comparison with audio that's actually recorded in GarageBand vs what's coming straight from the VU2?
Also, do you have speakers connected to the Scarlett's line outs? And if so, how's the difference there? I'm wondering if maybe the issue is the headphone monitoring circuit. It's not impossible that preserving the low latency with high-fidelity audio involves some manipulation of the signal to reduce bandwidth.
I haven't heard any such issues with my Clarett 4Pre, but I know that's not quite the same beast. You could have a faulty unit, or the headphone monitoring could be filtered a bit by design.
Another test is: does your computer have a separate onboard audio output? If so, you could record some stuff, export that to .wav or .mp3 or whatever format works, and play it in a media player using the onboard drivers. If it's still thin, that's proof there's a real problem with the Scarlett's actual recording functionality.