Jump to content

Deribas

  • Posts

    37
  • Joined

  • Last visited

  • Country

    United States

Retained

  • Member Title
    Freshman Member
  1. Thanks, Kal. Always appreciate your to-the-point guidance. What is the most trustworthy and up-to-date guide for setting up Dirac 1.x in mch with JRiver (i am on version 25)?
  2. BTW, I did try to plough through the long Dirac version 2 thread on this forum, but could not glean the necessary information, other than the fact that a Dirac company representative frequents that discussion and sometimes assists forum readers
  3. Here's another late newcomer to the Dirac integration into the multichannel audio reproduction system. For years, I have been using Jriver MC on a Mac Mini to play back SACD rips and mch downloads (eClassical, etc) via HDMI to the Marantz AV8801 processor. The latter uses the higher-end version of Audyssey for room correction. A few years ago, under the influence of Kal Rubinson's persuasive writing, I had decided to try a dedicated multichannel DAC and Dirac live on Mac Mini for room correction, excluding the Marantz prepro altogether. To this end, I had bought a full mch version of Dirac 1.x and an Exasound e28 DAC. Within the 30 day trial period of the Exasound DAC I could never obtain any sort of satisfactory Dirac room correction doing the multi-point room measurements. Maybe the measuring microphone was a dud (UMIK-1), maybe Dirac software was not configured right, maybe another kind of user error. In Any case, the exasound DAC went back to George in Canada and Dirac software sat unused while I went back to Marantz prepro and Audyssey. Recently, I happened to pick up a used exasound e18 DAC, which does multichannel in PCM only. No problem, I thought. Dirac needs to do its room correction in PCM, do the DAC would never see DSD material anyway, as long as I am using room correction upstream of the DAC, as I believe one should. Things got complicated when I tried to see what updates I should apply to my Dirac software. I discovered that Dirac 1.x was ditched for a completely new product, Dirac Live 2.3, and that the latter was only available for some select AV receivers and processors only. Moreover, standalone Dirac 2.x for MacOS could be had for beta-testing by a few chosen technophiles, but it may or may not be multichannel-capable at this time. Is this correct so far? So, my question is: what is my best approach to using Dirac live, taking mch input from Jriver MC on a MacMini, and outputting the room corrected mch PCM signal via usb to Exasound e18 DAC, which is directly connected to my 5-channel bryston amplifier and a subwoofer in a 5.1 configuration? Should I just go back to Dirac 1.x and try make it work from scratch again, or should I sign up for Dirac 2.x beta testing, or something else? Thanks for reading and any constructive feedback
  4. Ok where in CA? I can help you in you are in the Bay Area and want to drop off and pick up. Lmk
  5. Carl, I'm lucky enough that my solitary PS3 has been holding up for the entire backlog of SACDs that I own and is now used only for the few new ones that I get monthly. Btw, I got it from the guy recommended on this forum a while back. But, like you, I'm considering moving to a new Oppo model from BDP-93. Just to catch up on the latest: does Oppo BDP-105D function as a multichannel asynchronous USB DAC with its newest firmware? I recall that our excitement was limited by its stereo-only performance.
  6. After a recent update to Synology Cloud Sync, the files with the "conflict" suffix are not generated anymore. But... for some reason Synology is uploading everything else all over again to Amazon Cloud! Wish I could understand how this sync process actually works and how to make it do what I need.
  7. A quick correction: As I browsed by Amazon Cloud folders, I found the duplicates there, not in the original folders on the Synology NAS. So, I can imagine the following happens: A folder is uploaded to Amazon Cloud, its files get renamed on the Synology NAS, thus becoming out of sync, and get uploaded again into the same folder on the Amazon Cloud, with the "conflict" name. See for example:
  8. Chris, thank you for your willingness to investigate: according to several participants on the Synology forum, the same behavior has been seen widely over the last few months, or perhaps since Amazon came out with the $59.99 "unlimited" deal. I see these renamings/extensions in all kinds of music and non-music file names. Sometimes, I have seen the same folder hold both the original file, and a renamed one - there's a possibility that a copy of the original file is created with the extended "conflict" name, and then the original gets deleted by some process that Synology runs, some time later. In any event, more commonly I see that only "conflict"-named files are present. see some screen captures below:
  9. There is a nasty problem that started creeping in midway through my rather large (several TB) upload process via Cloud Sync from my 1513+ NAS to Amazon Drive. The process is taking months, and there have been a couple of Synology software update in the meantime - I can't point to the exact system change that started it. Btw, my sync is set to be unidirectional only (upload). My files form a music library which I play using the JRiver media center software. I learned that there was a problem when JRiver would sporadically fail to play a particular album. When I went to check in File Station if that particular albums folder was missing or corrupted, I found that the folder was there alright, but all the files we renamed with _DiscStation_***date****_conlict appended at the end. Now I could reimport all these folders into the JRiver library, but all the tagging info for music that I painstakingly entered would be lost. How can this software (Cloud Sync) be allowed to alter original file names?! I am waiting for the solution to remove all these harmful extensions from file names, so my music library can once again recognize the files. Anyone has any ideas?
  10. Well, after many dozens of smooth rips, the last few ones I tried have become notably slower: instead of 2.64 mb/sec that I always got with mch SACDs, I only get up to 1.64 mb/sec. Is this a sign that the drive is beginning to fail?
  11. Hope I can still join the May 2 event in Berkeley - live just across the Bay but have not met many computer audiophiles on the Peninsula. Max (deribas)
  12. That's a stubborn one. I did read recently that someone succeeded with this SACD using the network ripping method that's enabled in version 0.37. Haven't tried it myself yet (and not sure if I can make it work with a Mac). Have you?
  13. Synfreak, I always rip to .ISO only. and, as you and Paul3000h have pointed out, there is some sort of funky character issue. I now realize that it can be dealt with by setting up network ripping, but have not proceeded to do so. Thanks to both of you for your suggestions.
  14. One more observation since, on advice from Synfreak and ted_b, I switched to version 0.30 to rip previously undoable SACDs from Pentatone, Chandos, BIS and Oehms. 6 out of 8 now worked perfectly. 2 (both from Pentatone: Mendelssohn Piano Trios and Colin Davis Berlioz Requiem) were recognized and proceeded to the ripping progress screen, only to change to error message "An error has occurred. (8002B301)". Did not freeze PS3, though. Does anyone have an idea of what it means and if something else can be attempted?
  15. Ok, an update on stubborn SACDs. Indeed, version 0.30 (kindly supplied by Synfreak) solved the ripping problem with 5/6 discs so far (Pentatone, BIS and Oehms). I was a little worried about using the keys linked in The Guide when installing an old build, but no problems came up. Btw, all the discs that I now succeeded in ripping have some funny characters. Other than not having server mode for ripping, is 0.30 in any way inferior to 0.37?
×
×
  • Create New...