Audiowise Opto-USB, SRC-DX and early experiments with the Chord Qutest before moving to TT2

[creativepart]

10 hours ago, Middy said:

I pulled the trigger and see if it works out ok..Please dont tell my wife.. 

Please report back - you have a Qutest user watching for more feedback. I'd feed the SRC-DX with USB from a SoTM SMS200 Ultra. I've always had doubts about feeding the Qutest with USB.

[creativepart]

I have a SRC-DX on the way and it is expected Friday or Monday. I used to run a Schiit Etr device to take USB from my SoTM SMS200 Ultra and run S/PDIF to my Chord Qutest. After about a year of use I removed it and went back to running USB between the network streamer and the DAC.

 

Now I run HQPlayer via Roon and thought I should give the approach a try one more time. I'll report back once I receive the device. I've been trying to decide if I want to get an M-Scaler or not so I'm testing HQP + SRC-DX + Dual BNC as a poor man's M-Scaler.

[creativepart]

I received my SRC-DX today... but all is not well. I'm getting very low output from the SRC-DX.

 

When using USB into my Qutest I normally have my amplifier volume about 1/4 or less turned up. To get equal volume with the SRC-DX dual BNC I need to have the amp volume at 3/4 max. Honest, USB = vol at 8 pm on the "clock dial" and with the DBNC I have to have the vol = 2 to 3 at the clock dial. In fact, full MAX volume on the amp is just slightly too loud. At 1/4 volume you can't hear any output at all.

 

There is a STD and HIGH output switch - the instructions say to keep it at on HIGH (out) for Chord products. Which I have done. But switching that output button between STD and High does nothing other than change the STD/HIGH led light.

 

I have a "chat" in with the guy at Audiowise but haven't heard a response yet.

[creativepart]

Turns out there is an issue with Linux volume and since I run through a SoTM SMS200 Ultra I am using Linux, though I certainly never thought of it that way. I'm running an iMac, the SMS200 may be running a form of Linux... but I'm not. At least that's how I look at it.

 

Seems Sonore and others that run SonicOrbitor have a simple fix - but none yet for the SMS200. One user was able to get a SSH password from SoTM, install some software, make some changes and get it to work.

 

Dan is being very helpful and is trying to get with SoTM to find a work around. So, I'll just cool it a bit while he works on this. It's not usable in it's current state. Since Dan has run into this previously, I would hope he'll add this to his webpage on the device.

[creativepart]

I'm not able to get the volume issue fixed. The only fix for SoTM users is to get a SSH login from SoTM, use it to install the "AlsaMixer" application to the OS and then configure AlsaMixer to correct the volume issue with the SRC-DX.

 

I know for many with Linux command line and SSH experience that wouldn't be daunting, but I don't want to tinker with the internal systems of my SMS200 Ultra. As I said, I used the SoTM as an appliance to deliver network streaming to my DAC. This device may use Linux to operate, but them so might the IoT function on our LG Clothes dryer. I'm not comfortable diving into it at that level.

 

Dan has been helpful and is taking the device back. I did contact him within 30 mins of receiving it. And, when I contacted him he was aware of the issue and specifically the issue with the SMS200 device.

 

I did suggest that he add more specific cautions about how his product can be an issue with specific devices like the SoTM streamer.

[creativepart]

3 hours ago, BlueDL said:

Yes, this should be made more clear.

I got lucky with my Sonore OpticalRendu as there is a simple fix in the Sonicorbiter OS settings where you just set the ‘DAC’ to max volume.

Yes, you did. I appears you simply have to check a max volume option.

[creativepart]

On 11/9/2022 at 2:28 PM, frieddr said:

Hi did this work for you.  I have Qutest and sms200 ultra neo and I've read with arc-dx there's a volume setting glitch.  Did you solve that?  Was it difficult?

No. I ended up returning it on the day it arrived. The developer wanted me to contact SoTM to request Linux SSH Log in credentials and then install an audio volume module to make the output listenable. I declined taking that step. I was charged both return postage and a 10% restocking fee.

[creativepart]

I tend to keep upto date on firmware - I'm currently at Version Number : V0.5.2 which is latest. Not always, but it wasn't a SoTM firmware issue it was a Linux Kernel issue. The fix was to install a new audio mod in the Linux Kernel. But as I said, SoTM doesn't provide the SSH login except on special request and they are wary of installing new modules.

[creativepart]

On 3/25/2023 at 10:23 PM, deathdisco said:

@frieddr —

I deleted my response. Sorry, I didn't notice that this was addressed to another user.

[creativepart]

SOtM has just posted in their sponsored forum about beta testing a new firmware version that looks promising for using the SRC-DX with SOtM devices. Here is a list of updates in the new firmware:

Quote

• •  

Version: V0.5.5
- Date: 11-24-2023
- Added 'CPU frequency' selector.
- Added 'Set Max volume' button.
- Updated eunhasu, smb avahi services.
-Disabled unused avahi service(nfs).
- Changed a few GUI texts.
- Fixed up 'Start with Logitech Media Server' bug.

I'm checking for full details, but that "- Added 'Set Max volume' button." looks like exactly what is needed to use the SRC-DX.

[creativepart]

I have confirmed with SOtM that the new 0.5.5 firmware in Alpha testing right now does indeed have a Set Max Volume button that sets ALSAmixer to 100% volume and "Should" solve the volume issue with SRC-DX working properly with SOtM gear.

 

The following quote is from May at SOtM:

 

Quote

you are right, the set max volume button makes the volume to be max. you don't need to go to ALSAmixer settings. Just try to use this button.

 

[creativepart]

I've purchased a new SRC-DX to test out this new Set Max Volume feature in SOtM's new 0.5.5 firmware. But just to be safe, I've also tested loading and running ASLAmixer in Linux on the SMS200 Ultra Neo just in case the new feature doesn't work as expected.

 

Maybe two years ago or more now, but I bought the SRC-DX to use with my then DAC (Qutest) and was very disappointed with the volume issue. I didn't want to mess with Linux command line changes back then, and returned the SRC-DX because of that.

 

I used to know Linux CL years ago, and didn't want to get back into it. But I figured before buying the SRC-DX again to test the new Set Max Volume fix from SOtM  I'd better be prepared to intervene manually if necessary so I dusted off my CL chops before ordering.

[creativepart]

I'm back with real world testing of the SRC-DX with a SOtM SMS-200 Ultra Neo.

 

As expected, when I first installed the SRC-DX the volume was reduced almost but not quite to silence.

 

I installed the new ALPHA version of the v0.5.5 firmware for the SOtM devices and sure enough there is now a "Set Max Volume" button located far bottom left of the Configuration menu. Clicking this button immediately sets the SRC-DX to 100% volume in AlsaMixer in the Linux firmware.

 

Once set the SRC-DX works normally with the SOtM network streamer devices.

 

Here are some screen grabs:

 

[creativepart]

As I recently posted, I purchased a new SRC-DX for my streaming setup. I'm running a SOtM SMS-200 Ultra Neo streamer with a Chord Hugo TT2. Until now, I've always used USB output from the SOtM into the Chord DAC.

 

Now with the SRC-DX acting as a DDC to convert that USB output from the streamer into BNC S/PDIF outputs to feed the Hugo TT2. I've had a week or so of back and forth listening to compare the two configurations.

 

My initial impressions were that not much changed... but with more careful listening and comparisons I do find a fairly noticeable difference between the Hugo TT2 on USB and the Hugo TT2 on BNC S/PDIF. The thing I haven't been totally successful with is deciding if these differences matter to me or not.

 

Fed USB out of the streamer the TT2 sounds great. Very smooth, lots of separation between instruments and all the typical descriptions you've heard about the Chord sound. But when fed S/PDIF out of the SRC-DX that doesn't really change but there is an increase in high frequencies, most noticeable in cymbals - high hat especially. There may be a slight change in bass as well. I can't tell if its as clean as the USB fed sound but it is a bit more prominent.

 

Mind you, I'm not talking day or night differences. Very slight changes - except with High Hat cymbals - you really notice these from the TT2 with the SRC-DX.

 

Every day I switch back and forth and each day I think "OK, this is the better of the two" but that's a problem because one day that's feeding the DAC with S/PDIF and the next day with USB.

 

I need more time that this week to decide which is better or perhaps preferred is the better terminology.

 

If you're thinking the dual BNC output from the SRC-DX is going to be the best part of adding this device, think again. I'm not noticing any meaningful change between 768hz, and two BNC output and 384hz and one BNC connection. The same differences I pointed out above exist regardless of using one BNC connection or two BNC Connections. Evidently, there is a basic difference between the Chord's USB input and the DAC's S/PDIF input.

[creativepart]

I'm using the SRC-DX, with dual BNC cables into my Chord Hugo TT2's dual BNC inputs and enjoying 768hz via HQ Player and Roon from Qobuz.

 

I started wondering - since this device is USB powered - in my case from my SoTM SMS200 Ultra Neo streamer - has anyone experimented with modding the device with an outside power supply?

 

Isn't the SRC-DX basically a DDS and wouldn't a separate, better power supply improve the SQ? I mean the power supply quality does matter for any other DDS. YES?