onsionsi
100+ Head-Fier
- Joined
- May 1, 2016
- Posts
- 196
- Likes
- 49
Has anyone compare this amazing DAC to Mojo or even read any comparison between those DACs'?
Has anyone compare this amazing DAC to Mojo or even read any comparison between those DACs'?
I did, as I stated in my too-long post on the previous page. And in quick succession since they were literally next to one another at a Jam last week-end. The setting was not ideal, and I could not listen to the same songs, but I had the same iems plugged into each, the well-balanced Nuforce HEM8. Honestly I was more impressed by the Pro-Ject, of which I had no expectations, than by the Mojo, whose fearsome reputation I was well aware of. The sense of ambient presence was better through the Pro-Ject, which also sounded a tad more energetic. In terms of decoding, as @Left Channel has stated the S2 is a wonderful toy full of possibilities, more so than the 2-year-old Mojo.
The S2 is small but still way bigger than the Mojo, however, so the Mojo will cover more use scenarios. That said, I also preferred RHA's very mobile Dacamp L1 to the Mojo. Obviously many will disagree, but looking at the recent price cut on the Dacamp L1 (down from Mojo price to $300, went for $255 last w-e on Amazon.com) a discount would seem in order over at Chord's. It is hard to consider the Mojo $200+ better unless you are an über-fan of its signature, want to drive very high-impedance phones yet need a super-small DAC/amp, or need the 2 headphone outs. Of course, since many argue that the Mojo isn't far from the Hugo (to which I would concur), that could pose a problem all along the line...
Thanks for your feedback, Sorry I missed your previous post.
I received a quick reply from Pro-Ject, saying "Hello! Thank you for your message. We're working on this issue. So far it seems like an ESS bug, hopefully it can be resolved by a firmware update."
More reports to Proj-Ject would be helpful. In addition to work on this bug, I see on another forum that they are working on DSD issues. I haven't seen reports of the channel imbalance mentioned by @ReignofError so perhaps that is something that was resolved by the full design early on.
I've tested the beta firmware update, and the clock change "popping" sound appears to be fixed. At least three or four other end-users have tested it as well. There's been no further announcement, but I'm sure we'll see a final release soon. The update is loaded via the control panel. (The control panel was already placed in your Windows system tray when the driver was installed).
I can't comment on the sound, as I have not heard the unit ...yet. My thought was more to use it as a DAC. I think at some point I will try it. But we often fixate too much on numbers. at 110 DB SNR, noise should be inaudible. So what does more inaudible by achieving 117, or 120 DB SNR really get us? I think, nothing! I do agree though, MQA is not required. Unless streaming in a bandwidth limited scenario, I don't see its value.
MQA, for all of the hype, is still a lossy compression algorithm. If I am listening to locally stored music already in a High Res format, it really brings nothing to the party... except making Meridian a bunch of money.