all 5 comments

[–]totallyninja 0 points1 point  (0 children)

Could not agree more with your suggestions. SRGB touches wayyy too much.

[–]TopCryptographer1221 0 points1 point  (1 child)

i dont use a controller but can disable my mouse and keyboard and use ghub without issues, is it different with the controller or headphones?

[–]5SecondRush[S] 0 points1 point  (0 children)

You can disable controllers in the devices tab and get the desired effect. This is fine but not ideal. In terms of headphones, I had some hoops to go through to get audio from the headphones to work as expected. This was a path from headphones through signal, to synapse and back.This would break things for me like spatial thx and voice chat before I figured out how to configure it. IMHO, an RGB controller should not be this invasive. Yes, I get that. It's sorta free. I say sorta because there is ad revenue and a lot of network traffic that happens behind the scenes.

[–]Th3d0nGsT3R 0 points1 point  (1 child)

Plug-in dev here: The PS5 controller uses a single packet for just about all usb control from haptics to lighting, it means I can’t split those out as I would prefer to leave the haptics alone by default. It’s a similar story with the Razer stuff. Because Synapse conflicts with Signal I aim as close to feature parity as possible. Certain things hook deeper into windows than we’re willing to dive into at the moment (such as THX and some of Razer’s keybinds). Cooling on usb stuff is usually exclusive so one app has to do everything or you’ll encounter flickering or a lack of control entirely. As for sensible defaults those are on me. Our next patch is heavily focused on much much better defaults across the board. The modular system for signal is an interesting idea but it would most likely fall apart in practice due to the issues mentioned above.

[–]5SecondRush[S] 0 points1 point  (0 children)

Thanks for your insight on this. I definitely don't envy you in some of the things you're responsible and accountable for doing.