SOTM tX-USBexp Question with Mytek Brooklyn DAC+

[seeteeyou]

Sometimes Device Manager might contain too many inactive USB devices and then things could get quite tricky, usually I would simply clean things up and then it's good to go.

 

Unplug everything from all USB ports except for keyboard / mouse, then launch Device Manager and do this

 

 

Go through every single category and find all "grayed out" or "dimmed" items that are related to USB, just highlight each and every item (yes, only one item at a time and it's a PITA) and delete those USB-related items one by one. Make sure that you'll untick / uncheck the box whenever you're prompted to "Delete the driver software for this device"

 

 

Finally you should be left with no more "grayed out" or "dimmed" stuff like USB audio / drives / peripherals etc. after verifying the entire list of items, then remember to reboot before you plug Mytek Brooklyn back into your SOtM card.

 

If that were no dice, your "Event 442" should look pretty much like this one and therefore you might have to give this a shot

 

https://www.tenforums.com/drivers-hardware/138801-winows-10-updated-my-usb-dac-no-longer-recognized.html

https://www.psaudio.com/ps_how/how-to-fix-usb-connectivity-issues-with-dacs/

 

Could this do the trick or what? 

 

 

BTW, perhaps you could also check this out and see if either / both tools were able to show you a better picture

 

WWShowUsbDeviceTree

https://sourceforge.net/projects/playpcmwin/files/others/WWShowUsbDeviceTree109.zip

https://sourceforge.net/p/playpcmwin/wiki/WWShowUsbDeviceTree/

 

USBDeview

https://www.nirsoft.net/utils/usb_devices_view.html

 

I guess that maybe trying another cable with USB-IF cable certification might make a difference but not sure about that one, or even trying a different PCIe slot?

[seeteeyou]

Now that I've read your own post on Head-Fi in addition to another older one on this site, most likely it's more about the initial handshaking between SOtM (as well as Matrix) and Mytek

 

https://www.head-fi.org/threads/audiophile-usb-pcie-cards.944897/

https://audiophilestyle.com/forums/topic/25353-mytek-new-dac-brooklyn/page/62/?tab=comments#comment-556254

On 7/8/2016 at 11:31 PM, BigGuy said:

Unless Mytek has changed the USB configuration implemented with the Brooklyn vs the Manhattan, it may not be the Brooklyn that "doesn't eat it". I have used the VBus and VBus2 successfully with the Manhattan. A friend who has the Brooklyn cannot use the VBus Isolator. Others with DACs other than those made by Mytek also cannot use the VBus (or USB cables with 5V defeated). The one commonality is that all these other owners are running iOS-based music servers. (NOTE: I have never tried connecting the Manhattan to an iOS source to see if too is affected.)

 

The systems in question apparently need to see a 5V "handshake" between source and DAC which may or may not be related to iOS.

 

While Elfidelity might look similar to those PCIe cards, it's actually going through the onboard USB header (does it sound more like a direct path of some sort?) and perhaps the handshake could be more consistent or something like that.

 

Audioquest DragonFly itself might be less picky about the handshake part, and then it's constantly drawing power via the USB port and not sure if that were making a difference in terms of consistency.

 

---

 

If you're trying everything I suggested in my previous reply while nothing is able to help at all, potential issues related to handshake might seem to be closer to what's happening to Innuos before

 

https://audiophilestyle.com/forums/topic/38110-innuos-zenith-se-mkii/page/14/?tab=comments#comment-838015

On 6/26/2018 at 6:45 AM, JFThibault said:

So I just want to pass the information for those frustrated to have to buy an IFi IPurifier2 (over 100$...) to make the connection work, instead just use the really cheap Monoprice Aquamini USB Hub (3.26 $ !) plugged in the Innuos and then plug your USB Cable in it to the Mutec. Perfect solution at a cheap price. Probably other USB hub are working fine. Hope it helps!

 

---

 

Other than that, just wondering if you're powering either Matrix / SOtM (internally) via the same PCIe slot or an external power source is provided. Of course there's also the 3rd option to disable USB bus-power altogether and I hope that at least one of them could help with the handshake.

[seeteeyou]

On 10/22/2020 at 9:06 PM, ID_Guy said:

The mytek works on every USB port on my PC except through the SOTM card.

 

It's a tough nut to crack since we're having such an important point regarding the handshake. Audioquest DragonFly was working on all USB ports and therefore the operating system itself should be OK. It's hard to tell what actually went wrong between TI inside your SOtM and XMOS inside your Mytek.

 

I certainly hope that someone from Mytek could figure out if the handshake issues / incompatibility were having anything to do with Thesycon v4.45 driver, or maybe it's somehow related to their Brooklyn DAC+ firmware v1.28 / v1.11 etc.

 

Regarding your SOtM / Matrix cards, I verified their device drivers and confirmed that both of them were sharing the same (ancient) Texas Instruments TUSB7340 SuperSpeed USB 3.0 4–port xHCI host controller

 

https://www.ti.com/product/TUSB7340

https://www.matrix-digi.com/drivers/element_H_USB_Interface_Driver.rar

http://www.sotm-audio.com/files/Accessories/tX-USBexp/tX-USBexp_Driver_CD_v.1.16.3.zip

Quote

[TI]
%TI_Product_1%=TI_Product1_Install,PCI\VEN_104C&DEV_8241

 

[TI.ntamd64]
%TI_Product_1%=TI_Product1_Install,PCI\VEN_104C&DEV_8241

 

Basically if there were any kinda software / hardware incompatibility between XMOS (on Mytek's side) and TI (on SOtM's / Matrix's side) in this specific case, it's hard to tell if Mytek were willing to do much about such problem since it's working just fine with other "non-audiophile" USB ports on your motherboard / your Elfidelity.

 

TI also wouldn't offer support for legacy products while the device drivers provided by SOtM / Matrix also turned out to be really old. Here's TI's official filter driver for Windows 10 x64

 

https://www.ti.com/lit/zip/sllc448

https://e2e.ti.com/support/interface/f/138/t/684041?TUSB7340-TUSB7340-low-speed-Device-Driver-issue

 

No need to jump through all the hoops over there, we could find the same stuff somewhere else but unfortunately they're pretty much the same old driver release version 1.0.0.5

 

http://adnacom.com/doc/sllc448a.zip

https://ftp.hp.com/pub/softpaq/sp60501-61000/sp60962.exe

https://ftp.hp.com/pub/softpaq/sp64001-64500/sp64176.exe

https://dl.dell.com/FOLDER02581350M/1/2350_Output_Driver_0KG7M_WN_1.0.0.5_A00.EXE

 

Texas Instruments driver update for Texas Instruments USB 3.0 xHCI Host Controller

https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=97dad69c-84de-4e20-b416-584f7bddec7f

http://download.windowsupdate.com/c/msdownload/update/driver/drvs/2016/08/200028650_ab57a59f14734785299c78b380a677ce8ebdbd7f.cab

 

Adnaco = Dell = HP = Microsoft = pci\ven_104c&dev_8241&rev_02

 

Obviously trying different device drivers for TI wouldn't make a difference if you're having hardware-related issues in the first place, that's why I was hoping that you could actually give USB hub and / or another cable with USB-IF cable certification a shot.

 

My Dela D10 ripper didn't work very well with Vertere Pulse-HB USB cable and the ripping software reported all kinda errors, though a generic cable turned out to be perfectly fine.

 

Some Innuos users were having issues with their USB DACs and ZENith SE Mk.II but somehow adding a USB hub saved the day.