So This Whole AMD/Ryzen Thing Really Kind Of Sucks So Far...

[v1o]

First time I've heard of RME driver issues. Their drivers would even work with non TI firewire chipsets.

[robotmonkey]

Ugh...now my Roli Seaboard 25 isn't being registered via USB either. Let's call that Issue #6?

This is a joke right? This can't be normal. Maybe the mobo was damaged in shipping? There's no way I have a PCI Firewire card that previously worked, a USB Behringer X-Touch One that previously worked, and a Roli Seaboard Rise that previously worked, all of which no longer work with this new PC on top of all the other issues I'm having. This is insane! I've never had this many problems with ANY system.

That's gotta be an issue with the board itself right? There's no way this much sh*t doesn't work.

First thing to check is if there's an option to enable legacy USB support in BIOS. This usually fixes most issues with MIDI controllers and such.

[Funkybot's Evil Twin]

First time I've heard of RME driver issues. Their drivers would even work with non TI firewire chipsets.

RME themselves will tell you where they have driver problems. There are definitely incompatibility issues out there but they're still the best driver authors in audio.

[Funkybot's Evil Twin]

Ugh...now my Roli Seaboard 25 isn't being registered via USB either. Let's call that Issue #6?

This is a joke right? This can't be normal. Maybe the mobo was damaged in shipping? There's no way I have a PCI Firewire card that previously worked, a USB Behringer X-Touch One that previously worked, and a Roli Seaboard Rise that previously worked, all of which no longer work with this new PC on top of all the other issues I'm having. This is insane! I've never had this many problems with ANY system.

That's gotta be an issue with the board itself right? There's no way this much sh*t doesn't work.

First thing to check is if there's an option to enable legacy USB support in BIOS. This usually fixes most issues with MIDI controllers and such.

Will check. I shot ASRock a support email on the USB issues. Will see if they write back. May just get a USB card. Very frustrating.

[Unaspected]

Ugh...now my Roli Seaboard 25 isn't being registered via USB either. Let's call that Issue #6?

This is a joke right? This can't be normal. Maybe the mobo was damaged in shipping? There's no way I have a PCI Firewire card that previously worked, a USB Behringer X-Touch One that previously worked, and a Roli Seaboard Rise that previously worked, all of which no longer work with this new PC on top of all the other issues I'm having. This is insane! I've never had this many problems with ANY system.

That's gotta be an issue with the board itself right? There's no way this much sh*t doesn't work.

First thing to check is if there's an option to enable legacy USB support in BIOS. This usually fixes most issues with MIDI controllers and such.

I suggested that the other night - previous page. Not specifically pointing where to do it, though it might equally have been mangled by W10 - which is why I suggested starting from scratch with a clean off-line install. Then lock that bastard up so it doesn't start making decisions and downloading things you don't need.

But indeed, always start with the BIOS. Work through it as you would with any system, methodically checking which features are required - researching where necessary. Though I've always found motherboard manuals to be very useful.

One thing I don't like about W10 and the modern OS in general is the dumbing down and automatic features. So W10 will decide "what is best" for the user - meaning you have to disable that before you can properly install the drivers that you actually want to use.

Still surprised about USB issues. And I agree with alec.tron - this is an issue for the peripheral manufacturers to resolve with up to date firmware and drivers.

Or get the device manufacturers to get their act together... i.e.

Might be a good excuse to get a Platform M+. I was contemplating one of those for myself. Sold my Behringer BCF 2000 a little while ago and am missing the tactile interaction.

Had the same issue as the X-Touch mentioned here with the Platform M+ (but, all other USB device do play fine with the AMD/x570 ccombo so far, among them a RME Babyface Pro. No UAD or Roli though..).
Been in contact with support for 2 months now.... first round, not usable at all.
Icon blamed ASRock (X570-Phantom-Gaming-ITX-TB3 in my case) for 'underpowered' USB ports, pointing to issues with x570 boards generally (another angle could be that manufacturers have/had soso drivers/firmware, and never needed to run on anything other than intel for the last 5+ years...) and suggested the only fix to get the Platform to run again would be to get an additional PCI USB card...
Low and behold though, after a few more emails, I then got a beta driver / firmware, which at least made the Platform M+ recognized as a USB device again on the x570 system; but then started to act erratic (buttons were not staying lit, etc,) so Icon released another firmware (2.11 beta) which has also fixed the button light issue (and is now available through iMap...), and after 2 months+ the Platform M+ now also works on an x570 based system as intended.
Just some anecdotal bits that it's not necessarily the x570/AMD combo's fault...

c.

Thanks for that. So it should be okay now but no guarantees. I usually research well before buying anything so I'll be sure to do more before investing in a Platform M+. Really, what I ideally want to see is a YouTube video proving such will play nicely with my setup at the time. Then it's not so much USB connection and firmware or drivers, as you suggest.


I hope FET is less stressed today.

[Funkybot's Evil Twin]

I suggested that the other night - previous page. Not specifically pointing where to do it, though it might equally have been mangled by W10 - which is why I suggested starting from scratch with a clean off-line install. Then lock that bastard up so it doesn't start making decisions and downloading things you don't need.

But indeed, always start with the BIOS. Work through it as you would with any system, methodically checking which features are required - researching where necessary. Though I've always found motherboard manuals to be very useful.

I hope FET is less stressed today.

Appreciate the advice. I did look for any kind of USB settings int he BIOS and I didn't find anything like a legacy USB setting. I found something that might have had to do with USB power management, but really didn't want to go screwing around blindly with settings. With my luck, I'd have disabled the USB keyboard and mouse and bricked my machine if I messed with that.

Anyway, I'm hoping ASRock support gets back to me Monday on the USB issues. I really think there's some dodgy stuff happening with the USB chipset in use here. Disappointing to say the least.

Since Friday I completely reinstalled Windows 10 from scratch, actually twice after some Windows updates were crashing. Think that was due to installing chipset drivers before installing Windows updates and probably not enough restarts in between. Did things one step at a time with lots of restarts and now the system seems mostly stable except for the aforementioned and still currently unresolved USB issues. Then again, I haven't used the PC much other than to install software.

[alec.tron]

Yea, it's still bonkers how much legwork one has to do to get computers to play nice with audio & devices as well as vice versa...

Little suggestion for the Behringer X-Touch issues - open a ticket with them and mention that Icon, their direct competitor on motorized fader boxes, had the very same issues (as I've seen reported on the x-touch - i.e device recognition problems) and they've sorted out the issues within just a few weeks...

Good lucks.
c.

[Funkybot's Evil Twin]

Yea, it's still bonkers how much legwork one has to do to get computers to play nice with audio & devices as well as vice versa...

Little suggestion for the Behringer X-Touch issues - open a ticket with them and mention that Icon, their direct competitor on motorized fader boxes, had the very same issues (as I've seen reported on the x-touch - i.e device recognition problems) and they've sorted out the issues within just a few weeks...

Good lucks.
c.

Just submitted a support request to Behringer. I'm not terribly optimistic but I'll follow the process. Maybe they'll surprise me! No word back from ASRock either.

I should note: now that I'm thinking about it, the last time I tried using the Rise 25 on my old PC, it wasn't showing up either. At the time I thought it wasn't plugged in but in hindsight, there's a chance that issue pre-dates the new PC. Going to try on my laptop later today and/or some other ports.

Fun fun fun....

At least nothing has crashed so far today!

[Funkybot's Evil Twin]

Tried the Roli Seaboard Rise 25 on the laptop...same result. Turns out it's just not working with anything anymore. Completely unrelated to the USB issues with the Behringer.

[Scotty]

Multiple variables... coincidental temporally related failures and intermittent glitches make troubleshooting less than straightforward.

[Funkybot's Evil Twin]

Multiple variables... coincidental temporally related failures and intermittent glitches make troubleshooting less than straightforward.

Yeah, talk about bad luck! Seems like the only remaining issue at the moment is the X-Touch.

[Scotty]

I got to research a 3950x build for a pal and had it here for two weeks to optimze and test it while the parts were under full return no questions asked warranty.

My big concerns were UAD-2 compatibility and getting good low latency support. I don't use a thunderbolt interface so after reading anything and everything I could find on the builds I got something that worked out of the box.

I didn't dare budge on this build until that last ScanAudio article came out. Between Pictus and Scan and some brave soles who took the plunge I think I got it right. Some luck of course.

I am building 2 more near identical systems. This one was for a friend who had a more basic needs.. he is an audio guy though so he allowed me to suggests the specs and to optimize it once delivered. Good learning.

[Funkybot's Evil Twin]

Scotty, let us know how you make out. Did you say you were using ASUS boards? I've heard of USB issues with Gigabyte, ASRock, anything using the ASMedia chipset. Maybe ASUS has it figured out.

As to my own issues: I just ordered a StarTech USB PCIe interface with SATA power (someone posted on the Behringer forums that when they didn't attach the optional power cable to their USB PCIe card it still didn't work but adding power did the trick - hence why I went with a powered option). That one uses the NEC chipset that should work.

Hopefully that'll be the last of these issues and I can just move on to enjoying this PC.

[Scotty]

Yes I used the Asus X50 Prime Pro Board - it doesn't have thunderbolt on board as the person who needed this rig uses USB based interfaces. Because I had it here for 2 weeks I tested it with everything I have. PCIe audio cards (RME Raydats), early UAD-2 cards (Quads, Duos and Solo), Native Instruments Komplete S2 and Maschine MK III + Arturia controllers, 3 midi USB interfaces, + 20 approx other synths , groove boxes through the midi interfaces or through the USB midi connections... no issues. I passed SYSEX through one of the interfaces without issue and updated the firmware on my Ndlr with it though USB. Also tested three USB audio interfaces that I have here ... Tascam , Behringer and Steinberg and they all worked. I didn't try to performance test them I just wanted to be sure that playing a project file they passed audio and weren't glitching.

I installed both the bundled USB drivers and the stock MS USB drivers in turn and it looked to me the the Microsoft drivers were giving better DPC latency performance which I was closely monitoring so I went with those. I had read some reports that MS USB drivers are better in some cases so that is why i tested those otherwise I would likely have just gone with the drivers on the motherboard CD and updated them.

I read through every related gearslutz post and comment that had Pictus or Scan Audio attached to it.


There is a need for a dedicated Youtube channel that deals only with DAW performance and related builds.

[Unaspected]

Usually ASUS are pretty good but it took them a little while to get up to speed when Ryzen first hit. Back then, ASRock was the more sensible choice - so that's what I went with. Fatal1ty X370 Gaming K4. I didn't need anything crazy as I don't use additional hardware acceleration but also didn't want to go cheap. Mostly I followed information on Tom's Hardware, which I have usually found to be good.

Back to your issue: It might have something to do with USB power or timings. That was certainly an issue with running both a Focusrite Saffire and Liquid mix on an older rig. Then I had to purchase an additional firewire card and they both lived happily ever after. Of course, USB has the issue of bandwidth sharing - but I'm guessing you've already tested with all other USB devices unplugged. I wouldn't expect anything. I'd be more annoyed if that did fix the problem.

The good thing is the popularity of Ryzen. Other manufacturers are paying attention much more than with older AMDs. So I expect compatibility to improve. Might even be worth risking Thunderbolt - though I think USB 3 really is more than enough bandwidth. Well, certainly for my small home studio with a current max of 10 mic in and a live room which is probably too small to record a drum kit.

But for my next build - maybe a 3800 or 900x next year - I'll be looking at ASUS again. Definitely switched back to AMD for the foreseeable though. Very impressive performance for the cost.