Same Here, Blackwidow V4 full. Media Keys not responding properly when Synpase runs. As soon as I close it, media keys are great. I open it or let it run in the background, and media keys become unresponsive. expect for roller scrolling. I can assign stupid macro to media
Got a Huntsman V3 Pro yesterday. All was working perfectly fine until I fired up Baldur’s Gate 3, which is Chroma compatible. It was the game’s first run on this new machine so I guess it set something really wrong inside Synapse.
So, after running BG3 for the first time, volume slider became scroll up & down. All other “media”, actually custom buttons are behaving as per Synapse settings, including 3rd which is set to Play/Stop on press, Next on double press and Prev on triple. This happens no matter the profile, including Factory Default, which is non-adjustable by the user.
Quitting Synapse reverts the behavior back to normal volume adjustments. Fixed after rebooting the machine.
Later edit: can not reproduce it anymore.
Same Here, Blackwidow V4 full. Media Keys not responding properly when Synpase runs. As soon as I close it, media keys are great. I open it or let it run in the background, and media keys become unresponsive. expect for roller scrolling. I can assign stupid macro to media
I opened a ticket with razer about that problem.
they answered very fast, and helped me figure out where the problem was and how to repare it.
Now, no problem…
Help yourselves, and ask directly to razer customer service!
Can confirm. The command dial is virtually useless while using Synapse. Not only that, the Fn key shortcuts, i.e. Home, End, Sleep, etc. don’t work. Exiting Synapse returns the keyboard to normal, although without control over lighting, etc.
Same Here, Blackwidow V4 full. Media Keys not responding properly when Synpase runs. As soon as I close it, media keys are great. I open it or let it run in the background, and media keys become unresponsive. expect for roller scrolling. I can assign stupid macro to media
I opened a ticket with razer about that problem.
they answered very fast, and helped me figure out where the problem was and how to repare it.
Now, no problem…
Help yourselves, and ask directly to razer customer service!
I wish I knew what solved your issue. I contacted Razer support via phone and, after searching for several minutes, he was unable to find a fix. He said Synapse 4 is basically still a beta so the only real option is to wait for developers to fix it.
The only difference I see is that you have a V4 full and I have a V4 Pro 75%.
@Ayana_Amsa
I wish I knew what solved your issue. I contacted Razer support via phone and, after searching for several minutes, he was unable to find a fix. He said Synapse 4 is basically still a beta so the only real option is to wait for developers to fix it.
The only difference I see is that you have a V4 full and I have a V4 Pro 75%.
Update: Well, no dice for me. After the last contact, I used a ticket and was told to use Synapse 3 in the meantime. I pointed out to them that their own support FAQ stated the V4 Pro 75% is not supported by Synapse 3. I was then told the only option is to wait for the developers to fix the issue.
It’s not the end of the world, and I can use the missing functions if I kill Synapse, but I expect better QA for a $300 keyboard.