The headphone output of the Marantz cd 6006 is not good, Apple sounds better.
I tried the apple dongle with my ipad pro and it was as Amir said-sounded good but definitely lacked overall punch and low bass. I can’t find the Meizu pro dongle anywhere-only the standard model, so I’m going to wait for better portable products to release as we are in the golden era of amps and dacs. It’s not too bad to just use my airpods pro when I’m walking around my house and 6xx when I have my more powerful gear by my desk.I saw a reddit post of someone driving the 6xx with the apple dongle coming out of an iPad Pro saying it can drive them with most music at 80% volume and rarely needs to go up to 90-100% so I will be giving it a shot as a cheap portable solution. I have a heresy and modi 3+ at my desk but I always find myself wanting to walk around the house with them and I don’t want a bulky usb amp as a solution. If they’re not good enough I’ll probably go with the Meizu dongle.
It's definitely an electrical potential related problem, but not a classic ground loop like that with active speakers for example.
The RME is an IEC Class II device with an external DC power supply. The problem occurs with USB devices and the mainboard audio (is that run via the USB controller?), however it is very variable in quantity. With the Topping E30 (DAC meant for desktop applications with seperate data and power lines) for example it makes about a 2dB difference from 110.x to 108.x, repeatable and definitely measurable, but that wouldn't constitute an audible concern. With the Apple dongle the effect is far, far greater.
With the dongle run from the laptop that is then plugged in via its power supply (also Class II), a 50Hz spike (and its second harmonic) becomes visible in the measurements, but the noise floor doesn't really change (and yes, I should use averaging to investigate such effects).
I suspect the dongle is just very sensitive to any supply voltage irregularities - don't let the snake oil brigade read that though
With the perfectly clean DC from a battery powered device - the way it was intended to be used - it just simply works best.
Apple is known and has been for a long time as having better Dacs than your average Windows laptop.Despite a Hawthorne Stereo salesman telling me my Mac's built-in DAC probably sucks (in order to sell me a Bluesound Node 2i), I have some doubts that the audible clicks from the dongle are worth the (yet to be proven) possibility of worse sound from the Mac's motherboard. Maybe when I get some good speakers I'll be able to hear the difference. Now I just hear unnecessary clicks when the thing is supposed to be silent.
I wound up with a Topping EX5 DAC anyway. I doubt I notice the difference in DAC quality, but I wanted to eliminate an occasional ground loop and also power my HD600 headphones.Apple is known and has been for a long time as having better Dacs than your average Windows laptop.
I can imagine..It really does sound nicer at the correct speed
Surely it is the device sending the stream, ie the Raspberry Pi, which determines the sampling frequency communicated to the DAC?Ok fellow Apple USB-C DAC fans, following further testing, by default, this device, in Linux (only tested on Raspberry PI, under ALSA) runs at 48k.
It doesn't seem to matter what flags you give aplay, it just does 48k.
So if you feed it a 48k file, it's very happy and the timing is perfect.
But of you feed it a 44.1k file, it plays about 10% fast (48/44.1 x too fast).
I did wonder why the vocals seemed to be a higher pitch than I'd been used to - this is why!
The world is speeding up (spiritually, and physically, some days are almost 2ms faster...).. but not that fast..
So check how long your songs last, and make any bitrate changes you need to.
It really does sound nicer at the correct speed
Better bass too, a win-win!I can imagine..
Surely it is the device sending the stream, ie the Raspberry Pi, which determines the sampling frequency communicated to the DAC?
It may be that the DAC has a default of 48kHz if not flagged otherwise but I can't think of any reason why one would "blame" the DAC rather than the hardware (or at least its software) feeding it.
The DAC just plays the stream it is sent so I am pretty sure the solution would be in the software running on the PiI don't know, it's buried in the Linux ALSA sound system.
Aplay does allow the bitrate to be specified, and to be told to, or not not to resample... but none of that made any difference.
The only thing that worked was to feed it a 48k file.
Easy for me as it's just a setting (Although I did need to tighten up my 48k conversion LOL), but I'd be interested in the findings of others.
Perhaps that's a way of setting up the DAC, to nudge it into 44.1k native, but I didn't look for that, or how to apply it.
Previously I just used a SPDIF converter and a DAC (which told me the bitrate) and aplay faithfully passed the bitrate on, and it all played at the correct speed. So aplay knows and works properly with other things...
... but the Apple USB-C under ALSA does appear to be unusual, at least for me!
The DAC just plays the stream it is sent so I am pretty sure the solution would be in the software running on the Pi