walkintheseshoes wrote

penjojay wroteHere's some new info I received from support after linking them to this thread:

[i][i]1. Navigate to Windows Update and ensure all updates current

2. Visit Gigabyte's website at the following link and download latest drivers and firmware for your BaseBoard Product Z390 AORUS MASTER-CF:
https://www.gigabyte.com/Motherboard/Z3 ... -dl-driver
>>>Check BIOS, ThunderBolt, and chipset

3. Optimize as outlined here:
https://support.presonus.com/hc/en-us/a ... rce=search

4. Perform this full uninstall/reinstall of Universal Control:
> Disconnect the Quantum from your computer.
> Hit the Windows Key
> Now type “View advanced system settings” and press return
> Click Environment Variables button.
> Click the New button for the top section on this window.
> For "Variable Name:" type this exactly.
devmgr_show_nonpresent_devices
> For "Variable Value:" enter a single number " 1 ".
> Click OK a couple times and then open the Device Manger.
> Click the View menu and check "Show Hidden Devices".
> Right click and Uninstall any "Quantum", "PreSonus", and or "Unknown Device" you see listed under any category.
> Restart your computer.
> Install Universal Control again
> Connect and power on the Quantum
> Restart the computer and retest the issue.

Also, we recommend using StarTech brand ThunderBolt 3 cable for proper connection.[/i][/i]

Quite a few steps there, so I won't be getting around to completing it right away. Perhaps this is useful for anyone else who hasn't heard back from support yet or submitted a ticket.

EDIT: Tried it. Did not work.

Re
Surprise surprise! They don't want to admit there is an issue now.....do they!
I put in a ticket too but as soon as they said update to the latest uc (which i had already told.them I had) I gave up.
When I tried to fix my firestudio project they stuffed me around for like a month of "fixes" and wasted much of my time when it was clearly a driver issue...products = good customer service = poop! They are not interested in looking into fixes as it's not their software it's your fault or computer specs it doesn't work.

Yep. Not too surprising, as of course they were just trying to make sure I really fully uninstalled the driver. But I gave it the benefit of the doubt just in case it somehow magically worked. Now I did not try installing all of the Gigabyte mobo drivers, because who has time for that? There are like 40 and I don't want all that unrelated crap. I did ask support if they had a specific on they wanted me to try though, so I am waiting to hear back.

I've just noticed that there's a new version of Universal Control (Nov. 17th). Has anyone updated and noticed a change to this issue?

penjojay wroteI've just noticed that there's a new version of Universal Control (Nov. 17th). Has anyone updated and noticed a change to this issue?

No, didn't fix it unfortunately. I was really hoping it would.
Its just a driver update and no firmware update.

Darn, I tried it too before I saw your post. No luck for me, either.

Hi mates. Exactly same problem here. Quantum 2626 and Windows 10 are not good friends...

Any last minute solution???

All of you should make a ticket so Presonus get their act together

TerjeNorway wroteAll of you should make a ticket so Presonus get their act together

Agreed, though I know a lot of us have. Presonus, please! lol.

As I had already done that I went and messaged Rick naqvi on FB and asked him to pass on and get someone to at least watch the video I placed.
I'm hoping that will gain some traction...??
Only time will tell...

Yes I'm having the EXACT same issue, also, opening the UC software and making sure the ADAT mixer is open fixes the issue, its bizarre, going to open a ticket.

[Edit: Removed signature with obsolete system specs.]

Same problem here. Like others have said, it doesn't interfere with DAW use (Studio One), but sound from other applications, including Chrome and Spotify, disappear when the source is changed.

Changing Quantum 2626 settings in UC will reenable the sound. At first, I was changing the sample rate from 44.1kHz to 48kHz and back. Turns out it's faster to change the block size from my typical 128 to anything and back.

Quantum 2626, 1.3-83 firmware, UC 3.4.0.61835, power plan optimized, Gigabyte Vision D z490 motherboard, Intel TB drivers 1.41.890.0, StarTech 2 meter TB cable.

So here's my $0.02. For the longest time I didn't notice this problem because I very often had Ableton running in the background. Then I began having the aforementioned issue with sound playback stopping every time a new video on u2b would start. After a bit of fiddling around I came to the realization that playback would work fine with Ableton running. This seemed a bit excessive so I tried just playing an mp3 in the background with the volume turned all the way down...works just as well (set to repeat for endless functionality). It's a little more resource friendly than having a DAW running in the background for no reason other than just making your desktop audio function, though far from what I'd call a satisfactory solution. This is obviously a driver related issue but from what I've read in this forum, I can't say I'm feeling optimistic about Presonus addressing the issue.

Windows 10 audio drivers do not support multiple devices playing at the same time.

josephellis1 wroteWindows 10 audio drivers do not support multiple devices playing at the same time.

Don't mean to rain on your parade but:
1: never had an issue using 2 x firestuido projects using win 10
2: works perfectly fine when I have both units on and apply the "fix" I found
3: using just 1 unit has the issue unless you apply the "fix" I found.

End result = driver issue just like everyone else that has posted the same issue

Works fine if you run Universal Control like in the screenshot, in the background. So I wish PreSonus would fix it eventually, but for now this is an okay workaround