Jump to content


  • Content Count

  • Joined

  • Last visited

  • Country

    United States

About Torq

  • Rank

Personal Information

  • Location
    Seattle, WA

Recent Profile Visitors

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

  1. Listen from ~1:18:30 for the new stuff ... The first is an update on the rumored circumaural version of the SR1a, the second is about a new, tube-driven, amplifier.
  2. Just bear in mind that this won't stop Chronosync seeing them as changed, nor BackBlaze wanting to push them up to the cloud again. Even resetting the file modification date back as to what they last had (as well as the above change) likely won't do it at this point, either.
  3. Roon is a very different situation. You can only have one Core logged in at a time, but you can have any number of clients and end-points, all controlling and playing different things, in different places, at the same time. Just has to be on the same network. Once license covers all of the devices and users in my home simultaneously. If I wanted to use Audirvana Studio for just TWO different users, suddenly Roon is cheaper (among other things).
  4. If it did, it's an optional thing ... I think you have to turn on volume leveling and/or initiate the "Albums Replay Gain analysis" process, as those tags are used for Replay Gain, and are not present in my files.
  5. Yes. It adds a "MUSICBRAINZ_TRACKID" tag to each file.
  6. Not "out of the box". It might be possible to use the "External Script" rule-type in Chronosync's inclusion/exclusion rules (Rules | Advanced) to do it, but there would be limitations. Mostly because your custom script can't see the existing backed-up file to do a comparison against. Which means all you could do is, for example, say "exclude if this tag is present", rather than "exclude if this tag was newly added", and even then it's fiddly and involved to do.
  7. It will. If you're lucky, and your backup solution is smart enough, it may only backup the changed blocks rather than the entire file, but it'll be backing up something for every touched file. File backup systems generally aren't built to be conditional on what has changed, beyond block-level change-detection and deduplication.
  8. Mine don't. Only the ones that show updated in the last 20 hours or so. All of those touched have the "MUSICBRAINZ_TRACKID" added.
  9. It's a deal-killer issue for me. Not withstanding that at that rate of progress, it would take 166+ days to finish processing my library, I just am not willing to have a useless tag addition (no reason it can't live in Audirvana's database) cause my entire library to have to be re-backed up to the cloud.
  10. Despite finding a near-completely-faithful porting of all the issues/bugs I had with Audirvana 3.5 into Studio, and working around various library-related issues (Studio wanting to import my 3.5 library, and totally pooching it ... requiring deleting the entire library and rebuilding from scratch) ... I have to pressing questions ... 1. WTF is it doing that it is taking HOURS to do its "Analyzing audio files ..." thing, and what is the end result of that? 2. How does Studio behave in the face of not having an internet connection? My primary use-case for 3.5
  11. Thanks ... though that's how it looked when I was in the midst of doing the comparisons between the M-Scaler options and Hugo TT 2/Hugo 2. In actual use, today, it looks like this (since the M-Scaler and Hugo TT 2 are now in the office): The amps are Woo WA234 MKII MONOs (with a Chord Étude nestled under the Blu Mk2/DAVE to drive the SR1a).
  12. I think a proper answer to this depends on what you plan to do in the future, but lets start with the present. And for some context, I own a Hugo TT 2 and M-Scaler (office rig), Hugo 2 (portable) and a Blu-Mk2 and DAVE (primary rig), so I've had the opportunity to compare all of the combinations directly, and in my own system and at leisure (picture is from when I was doing the comparisons): My personal opinion, is that the hierarchy of performance is as follows: Blu Mk2 -> DAVE | Hugo M-Scaler -> DAVE DAVE Hugo M-Scaler > Hugo TT 2 H
  13. No. I use the RME as a consistent and neutral reference. Mostly because it’s affordable, relatable, and is both objectively and subjectively a very high performer. And its relatively low price and small size makes it easy to keep around for long-term consistency. Yggdrasil (and later Yggdrasil A2) used to be my reference DAC for such purposes ... again because it is relatable and relatively affordable (if less so than the RME). It was taking up more space than I wanted for that purpose. Oh, and I do not consider the Chord DAVE or TT 2 or Klimax DSM to be
  14. Yggdrasil A2 remains one of my favorite DACs for simply enjoying music with. When fed with either the Blu-Mk2 (as an M-Scaler) or Hugo M-Scalers I wound up preferring DAVE. Subsequent firmware updates to the Klimax DSM (when used as a DAC for analog output) and to the Exakt-equipped speakers pushed them ahead also. Though conventional DACs aren’t useful (don’t work) in an all-Exakt setup anyway.
  15. To be fair, I haven’t posted in that thread for over a year. And a lot has changed in my systems in that time. My primary headphone rig is now a Chord Blu-Mk2 feeding DAVE which then feeds both a Chord Étude (to drive my SR1a) and Woo WA234 MkII Mono for all other headphones (though I do use the direct headphone output on DAVE when I want solid-state output with non-pathologically-power-hungry cans). My office rig is a Chord Hugo M-Scaler feeding a Hugo TT 2. Speaker system is an all Linn Exakt setup driven by the latest Klimax DSM. I use an R
  • Create New...