08-29-2017
12:10 PM
- last edited on
03-05-2024
09:49 PM
by
ROGBot
09-28-2017 05:36 PM
johnaldmcgee wrote:
I have the same problem. There is a workaround that doesn't require reinstalling the drivers. Every time you reboot, go into the SupremeFX manager and recombine the front and back interfaces and check the box to mute the rear sound when something is plugged into the front. Hit OK on the screen, then go back in and change it back to have separate interfaces.
Hopefully whoever is doing the driver development can figure out why the settings aren't persisting through reboot. I went ahead and ordered a little USB sound card to plug in the front of the case for now so I won't have to hassle with it (cheap ones are 5-10 bucks). But I'd much rather use the case ports and tie up one less USB.
09-28-2017 12:01 AM
Toxic Waste wrote:
Hi all,
so I recently build myself a new rig with a rog motherboard, the Asus Maximus IX Formula. Since I use my computer a lot for games, I have both a speaker set and a sennheiser headset connected to my rig, so I can use the speakers for game audio while I use my sennheiser for communication. On my previous computer, it was very easy to do this, I could just split the audiostreams for devices, register the proper device on teamspeak for example and done.
...
On my new motherboard however, this does not seem to work. Or to be more precise, it works the first time, and after I reboot, it is gone. I have tried this with the latest drivers, and an older WHQL version, I installed 6.0.1.8158, and I also tried it with 6.0.1.7997, but the problems are identical....Anyone that can help me with this one?
10-16-2017 08:52 AM
Toxic Waste wrote:
Hi all,
so I recently build myself a new rig with a rog motherboard, the Asus Maximus IX Formula. Since I use my computer a lot for games, I have both a speaker set and a sennheiser headset connected to my rig, so I can use the speakers for game audio while I use my sennheiser for communication. On my previous computer, it was very easy to do this, I could just split the audiostreams for devices, register the proper device on teamspeak for example and done.
On my new motherboard however, this does not seem to work. Or to be more precise, it works the first time, and after I reboot, it is gone. I have tried this with the latest drivers, and an older WHQL version, I installed 6.0.1.8158, and I also tried it with 6.0.1.7997, but the problems are identical.
I set up my speakers, they work fine, I add the headset, I select the corresponding jacks to the correct devices. I can toggle between Windows 10's audio devices and there is no issue. However, the moment I reboot, the SupremeFX seems to do something wrong,because from that moment, the sound is both in my headphones and on my speakers, and when I switch to the other device in windows settings (being my headphones), I hear nothing. Running the 'test' on the devices in windows audio results in the test sounds on my speakers, and hearing nothing for the headset..
I am at a loss here guys, did I miss a critical thing, or is the realtek hd audio manager really that buggy that I cannot seperate my headset and speakers? Another thing is that when I go in teamspeak and try to select any after a reboot, it just fails to play the sound and says 'Error opening playback device: device not registered/known
Anyone that can help me with this one?
10-29-2017 12:34 PM
HERNANBOZZANO wrote:
im having the same problem, and the workaround is pretty annoying.. i hope someone from ASUS will develop a fix for this. I disabled "enable auto popup dialog, when device has been plugged in" but any time i plug a new device, the popup appears. Clearly it doesnt work.
The only workaround i've found usefull is to plug/unplug the device with my hand every time.. but, that is not the way it should work.
Is there any other way to submit a claim to asus?
11-03-2017 06:47 AM
Toxic Waste wrote:
I have no way, maybe we can contact support? Or gives this thread a lot of visibility? It is a shame that for such an expensive motherboard, such basic functionality just doesn't work..