My PC was always very laggy for a few seconds - especially in sound-intensive applications - which either led to acute inoperability or, in the worse case, to a BSOD/black screen/game crash. This back and forth with the driver so you could somehow cheat Dolby Atmos in caused many more problems for me. PPS: Here again the link to the support page. The headset receives the \"Setup\" state. I also cannot say how the microphone sounds after these changes, but those who use other input devices or no G-Hub at all should not have any problems with this. The downside of the whole story is that the headset can no longer be selected via the Logitech G-Hub and the microphone can no longer be adjusted. Select the second option for "USB Audio Device", then the default driver will be installed successfully and you can select Dolby Atmos for the headphones in the headset settings. Right-click your headset again and select "Update Driver", then "Search for driver software on your computer", and finally "Select from the list of drivers available on your computer".
You will notice that the driver is now named "Logitech " Gaming Headset or similar, depending on the device.
Then look for the section "Sound, video and game controllers". Type "Device Manager" in the Windows search.Well, after much searching, I found the solution to the problem on the Dolby Atmos support page and didn't want to keep it from you! Logitech installs a custom driver for the headphones that disables Windows Surround Sound and to re-enable it, you have to install the default driver. Only in the sample videos in the app was anything audible. Like most people, I heard no sound through the headset when Dolby Atmos was enabled. I've been looking everywhere for a solution to enable Dolby Atmos on my Logitech G Pro X Wireless Lightspeed Gaming Headset. The headset remains inactive in the G-Hub. The standard drivers still have to be installed to use Dolby Atmos. Update (): Everything is further underchanged.
0 kommentar(er)
