Jump to content

AriMargolis

Members
  • Content Count

    100
  • Joined

  • Last visited

About AriMargolis

  • Rank
    Sophomore Member

Personal Information

  • Location
    Denver, CO

Recent Profile Visitors

608 profile views
  1. For the N10 users who have not been able to "see" the "Use Native DSD" option in advanced settings, there's a Conductor app coming in the next few days to solve that. Sorry for the delay here...we're rolling this out model-by-model.
  2. FYI, any QB-9 users who also use an Aurender, Native DSD input is now confirmed to be working. It will work for all users after the next Aurender firmware update, but if you're hot to trot, you can reach out to us at [email protected] and we'll update your system in advance on a case-by-case basis. Note: Native DSD output is not available yet on some Aurender models, but it is coming soon across the board. Onward & upward. This particular instance did not require Ayre to do anything on their end as it only required an Aurender update, but I'd still like to thank Ryan and Gary for being super helpful with other recent issues. They are super generous, smart and helpful. They have made me personally a big Ayre fan.
  3. So, there’s system software and then the conductor app...they are different and need to be updated separately. If you’re unable to download the latest system software for your Aurender, check that your conductor app is up to date. If it’s still saying software is up to date even though the website reports newer software is avail, send a support request to [email protected]
  4. This is a really good question and I have been meaning to post something here about the Native DSD roll out that Aurender is doing right now. Aurender is enabling Native DSD output model-by-model, because, well, it is just plain tricky. It is now enabled in the latest software updates for W20SE, ACS10, N10, N100H/N100C/N100SC, and X100L, so that’s pretty much everyone (W20 “classic” is coming too at some point soon) A little background on “Native” DSD vs. DoP. What the hell does it all mean? DoP (DSD-over-PCM) remains the industry standard DSD transmission protocol. It involves the player/output software “re-packing” a DSD file into a PCM container along with a special flag or marker that alerts the DoP-compatible DAC to “un-pack” that file and process it as DSD. It is totally lossless and the file is processed by the DAC as true DSD. At no point is the actual digital information converted from DSD to PCM. It just puts on a PCM jacket for a second to get into the club, and takes it off when it’s ready to party. This is NOT to be confused or conflated with DSD to PCM conversion, which is a less desirable transcoding of DSD to PCM, from which there’s no going back. Now, some DACs, for example Chord Electronics’ amazing DAVE from the post quoted above, can actually process DSD input without this clever DoP repacking. However, unmarked or “Native” DSD transmissions nearly always require a custom driver to facilitate communication between the player and DAC. Chord has a custom driver for Windows to enable Native DSD input to the DAC from Windows. So, yes, the DAC technically supports Native DSD, but ONLY ON WINDOWS (for now). This is not to pick on Chord at all...it is true for the vast majority of DACs that claim Native DSD compatibility. Very few work with Linux right out of the box. In many cases, Aurender’s SW team will be able to achieve Native DSD compatibility even if the DAC doesn’t explicitly support this functionality with a Linux source. But, it is not guaranteed. We cannot test every DAC on the market, so we need your help! This is important: if you own a DAC that claims to support Native DSD, but it is not working with your Aurender, we would love to hear from you! Please send a remote support email from the app (Settings>Help>Send Remote Support Request Email) to let us know. Aurender is committed to enabling Native DSD support with as many DACs as possible, and the DAC manufacturers, including and especially Chord, have also been very cooperative. We have reached out to other Linux audio manufacturers to request sharing source codes in case they have added Native DSD support for DACs that we haven’t gotten to yet, and vice-versa. I hope this helps to understand.
  5. @vortecjr @jabbr @The Computer Audiophile I'm not going to continue to hijack this thread, but I do want to clarify my answers from over the weekend. Based on some of the responses, it seemed like there was some concern that Aurender was not playing by the rules according to the Linux GPL. After speaking with Aurender's lead software dev, Eric Shim, I can confirm that that is definitely NOT the case. Any of you readers who have met Eric at a show or otherwise know that he is extremely kind and generous and he firmly believes in the spirit of the GPL. He clarified that, yes, of course he and his team do make updates and changes to the Linux Kernal on a case by case basis to solve problems as they come up. None of the changes he's made are proprietary in any way. Aurender's complete source code is provided on request to anyone who asks. Aurender sends the complete source code to MPD annually, and it has been updated here as well. Back to the original subject of compatibility with the Unison update - @agillis @vortecjr - it sounds like you guys have not encountered this "buzz on 'next' command" issue with the Unison...did you have to apply any patches? or did it "just work?" There may well be something on our side that is "unique" (but not proprietary) to Aurender that needs to change, but in case it's a broader problem requiring a patch to the audio driver, now would be a good time for me to ask if you already have the solution?
  6. @vortecjr yeah I think I misspoke. I will clarify after educating myself and talking to Eric.
  7. @The Computer Audiophile @jabbr The source code is posted at aurender.com Just to clarify - I'm not a software engineer. Maybe I used the wrong terminology about "patches" and caused confusion above? I can get more info from Aurender's SW team on Monday if clarification is needed. All I was trying to say in my comment above is that in cases where compatibility issues arise, most of the time they can be fixed by changing settings on the software side without the DAC manufacturer having to do anything.
  8. @vortecjr Aurender‘s platform is based on the standard USB audio drivers and MPD player software but it’s not just an “off the shelf” / “plug-and-play” implementation. Inevitably, some DACs do things a little differently. As you know, many DACs were not engineered explicitly for use with Linux sources, so Aurender’s SW team installs certain tweaks to achieve full compatibility when necessary. I don’t know how much if any of it is proprietary, but it is custom engineered/bespoke implementation for Aurender.
  9. Aurender uses standard USB Audio Class 2 drivers augmented by many custom “patches” to support a wide variety of DACs that would otherwise not work with 100% smooth compatibility.
  10. I just wanted to let you all know that Schiit has graciously sent us (Aurender) an Yggy/Unison DAC for troubleshooting. I’m cautiously optimistic that Aurender engineers will be able to squash any compatibility issues. “That’s the way that the world goes ‘round.”
  11. @davide256 yes there is the option to add a delay but that seems to only be important when switching sample rates. The problem @Jeff_N is reporting occurs when he hits the "next" button to advance to the next track, even if the next track is the same format, same sample rate.
  12. Hey all, yes, @Jeff_N and I have been in touch about this already and Aurender has been trying (unsuccessfully) to get rid of that nasty buzz on our end. Unfortunately I'm afraid we're not going to be able to solve the problem remotely, BUT i'm going to reach out to Schiit to see if they would be so kind to furnish us with a loaner DAC for testing. The Aurender software wizards in Korea have managed to patch small issues like this with DACs from other manufactures. We'll see if we can achieve full compatibility with the Unison if we can obtain a loaner. Thanks for reaching out. @The Computer Audiophile
  13. @tdimler 2 significant differences: 1. ACS10 ships with 2 8 TB HDDs installed and pre-configured in a RAID configuration. Larger HDD configurations are available via special order. On the other hand, ACS100 ships with no storage pre-installed but there are 2 slots for user-installable HDDs or SSDs. You can use any 2.5" internal drive, max height 7 mm. They are easy to install on your own and there are instructions here: SSD/HDD Installation Guide 2. ACS10 has a very nice/quiet linear power supply and a filtered/isolated USB Audio port. It also has a 2X Isolated LAN port. ACS100 omits all of those audio performance features and it uses an external switch mode power supply. ACS100's best use is as a CD ripping/library management/storage companion piece or an "add-on" to use with another Aurender as the primary player. ACS10 has all the CD ripping/library management/storage features + it has really excellent audio performance thanks to the nice power supply and usb port.
  14. @Justubes the USB recovery stick is basically a booting image. If possible, booting to SSD recovery from USB stick should restore the SSD, but sometimes that is not possible. In case it is not working, I can try to facilitate communication with Aurender Korea for additional assistance if you email me at our support channel. [email protected]
  15. Hi @justubes - you know where to find help if you need it! If the unit is not booting up and it is unable to boot to SSD Recovery or Remote Support modes, then I'm afraid there's nothing that can be done remotely. Your dealer or distributor in your country can assist with the repair. As always, we are here to help at [email protected] It sounds like you have already tried this, but just in case, here are the steps to boot to SSD Recovery Mode or Remote Support Mode (from internal USB stick) Shut down the Aurender and make sure the back panel switch is off. Press the front power button and hold it. While holding the front power button, turn on the back panel power switch. As soon as the display turns on, release the front panel power button. When the display shows the "aurender recovery" message, scroll to the REMOTE SUPPORT option using the skip forward button. Once "Remote support" is highlighted, press the play button to start remote support. Take a picture of the screen and send it to us.
×
×
  • Create New...