Jump to content

jeeb

  • Posts

    10
  • Joined

  • Last visited

  • Country

    Canada

Retained

  • Member Title
    Newbie

Recent Profile Visitors

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

  1. I've updated the OS on my Mac Mini to Sierra, and the speed/pitch problems I was having in Exclusive Mode with TIDAL have disappeared.
  2. I inquired about the speed/pitch problem, and apparently TIDAL did see some of this behaviour in testing, but just with Mavericks, which is what I'm running. I may upgrade the OS, or try some of the workarounds they suggested.
  3. Nope, Mavericks. Apple has broken too many thing that worked just fine for me to change an OS that until now has been working just fine for me.
  4. I've experimented with Audio MIDI settings between 88.2 and 192kHz. And yes, it really is weird. My expectation was that by choosing Exclusive Mode, I'd bypass Core Audio, and that Audio MIDI settings would be irrelevant. Clearly, that's not the case.
  5. I'm running into some major weirdness using playing MQA content from TIDAL on a Mac Mini through my non-MQA DAC (the built-in DAC on a Simaudio Moon Neo 340i integrated amp). If I choose the Exclusive Mode option, TIDAL sends 88.2 or 96kHz data to the Moon DAC. But it plays music too fast or too slow, depending on the setting for the DAC in the Audio MIDI utility. Of course, I can leave the Exclusive Mode box unchecked, but then Core Audio is resampling the stream to whatever format I've specified in Audio MIDI. Another problem: if I try to use Audirvana Plus after giving TIDAL exclusive access to the DAC, it crashes even if the TIDAL app is not running (i.e. if I’ve quit TIDAL before launching Audirvana). To avoid this, I have to remember to uncheck the exclusive access box before exiting TIDAL. Anyone else running into these issues? Hopefully, they'll go away with the release of Audirvana 3.0. But right now, it's kind of a mess.
  6. +1 My experience with the Chord Mojo, which I use for headphone listening, is much the same. I was getting dropouts with DSD128 upsampling on the Mojo, and found that when I went back to PCM playback, I liked what I was hearing better. But on my main system (built-in D3 DAC on a Simaudio Moon Neo 340i integrated), I am really enjoying DSD up sampling (still playing around with filters), though fan noise is definitely still an issue.
  7. I came across a link on the BitPerfect blog to a story about the outrageous terms of Apple Music service, which allows the folks in Cupertino to hack your computer and delete files that you own: that you've bought and paid for, ripped from your own CDs, or created yourself. Have a read: https://blog.vellumatlanta.com/2016/05/04/apple-stole-my-music-no-seriously/
  8. My omission: yes both systems cycle. CPU usage will shoot up after several minutes on the Mac Mini, often when a new track is loaded. The MBP goes longer before shooting back up. Quick question: any opinions as to optimum memory allocation for pre-loading tracks on a 16GB and 8GB system?
  9. Long-time lurker and infrequent poster here. First of all, thanks to Damien for this great enhancement to a great product, one that I enjoy using almost every day. I'm been trying this on two systems. In the music room, I have a mid-2011 Mac Mini (2.3GHz Intel Core i5, 16GB RAM, 240GB SSD; music is on a 6TB LaCie RAID array), connected via USB to the D3 DAC board in a Simaudio Moon Neo 340i integrated amp. For headphone listening, I have a Chord Mojo connected via USB to an early 2015 MacBook Pro (2.9GHz Intel Core i5, 8GB RAM, 512GB SSD). My experience on both systems is much the same as others on this thread. On both systems when a track begins playing, CPU usage will shoot into the 240-260% range. After several minutes (it can vary from three to six), CPU usage settles down to a little over 2% on the Mac Mini, and a little under 2% on the MBP. The five-second delay I experienced with early builds is no longer an issue with version 2.5.0.9. On the Mac Mini, fan noise as the system heats up is quite audible, enough to break the spell. This is reason enough for me to consider going back to PCM upconversion, or perhaps some other solution: getting a long USB cable and moving the Mini to a location where the noise is less bothersome, or when funds permit, upgrading to a Core i7-based system (assuming that would keep CPU usage at a level where fan noise isn't an issue. There's one occasional artifact: occasional, I'll get a weird stuttering, where the system overlays a portion of the music that played a few seconds ago onto the current portion: it's as if my DAC is composing a canon on the fly. On the MBP, fan noise isn't an issue. The main problem is that I get momentary dropouts, which again break the spell.
  10. First post from an occasional lurker. Following Ted's SACD Ripping Guide Version 4.0 (Thanks, Ted!), everything has gone smoothly. I found a PS3 on eBay with firmware 2.41, and installing the hacked OS was no problem. The SACD Ripper also installed without incident, and I have successfully ripped about 20 SACDs from my library. But with a few discs, I get the following error message when I try to extract DSF files using the ISO2DSD app: libsacdread: Can’t stat [filename.iso] No such file or directory. The ISO file is certainly in the target folder, and I'm able to extract DSF files from other ISO files in the same folder. Does anyone have any idea of what's going on, and have any suggestions For some of the discs, I can just get rip the CD layer as I do normally. But I have a few non-hybrid discs, mainly from Sony, so this workaround obviously won't work for them. And in any event, I'd like to be able to play the DSD content on my SACDs from my Mac. My apologies if this has been addressed before. If it has, I haven't been able to find anything.
×
×
  • Create New...