unable to set or use inter-device profile switching | Razer Insider

unable to set or use inter-device profile switching

  • 16 November 2020
  • 1 reply
  • 22 views

so im having an issue as of the last few days where i can no longer get inter-device profile switching to function using my Huntsman quartz. HOWEVER, it DOES work using my Huntsman mini. it wont register any attempt to remap a key (regular or hypershift) as an inter-device profile switch. clicking on save causes the "save, cancel" buttons to be grayed out but the key change itself doesnt save. ive tried wiping synapse from the computer and reinstalling it, doing manual HID update checks in device manager, "repairing" the synapse install. nothing seems to be making any difference. the only modules i have installed are chroma connect, studio, and visualizer, (all others were uninstalled after a prior issue i had with synapse.)

is there a solution for this? and why would it work on the huntsman mini but not the regular huntsman?

This topic has been closed for comments

1 Reply

Sorry to be replying without a solution, but I'm having a similar problem. I have a Tartarus V2 and Blackwidow Elite. I only have 1 profile for the Blackwidow, but for the Tartarus I have 7 profiles. I have 7 chroma studio profiles as well, one for each Tartarus profile. Each Tartarus profile and its corresponding Chroma effect are linked to the same game, except for the "Desktop" profile/effect, which I purposefully left unlinked so Synapse would treat it as the default. In theory, when I launch a linked game, let's say Skyrim for this example, Synapse should automatically switch my Tartarus to its Skyrim mappings while simultaneously changing the lighting of both of my devices to my custom Skyrim lighting effect. And when I exit Skyrim, everything should return to the default profile/effect because there are no games linked to it.

But Synapse doesn't do that, or at least it doesn't do it reliably. Sometimes it switches exactly like it's supposed to. Other times it doesn't switch at all or only switches the profile and not the effect (or visa versa). It's extremely annoying, so I decided to use the inter-device profile switching to allow me to change things manually if Synapse messes up. My BlackWidow only uses one profile, so it *should* remain constant while my Tartarus and the effects change. Under Hypershift, I mapped my 1-7 number row keys to each switch to a specific profile, and to my surprise Synapse gave me the option to also change the lighting as it switches profiles, which was exactly what I needed. I also mapped my numpad keys to only switch lighting effects in case the mapping was correct but the lighting needed to change.

So does that work? Sometimes it works perfectly, but the problem I've been having is that at random times all of the above mappings just suddenly stop working, and don't work until I exit and relaunch synapse. And when I say "at random times," I mean it. It might do it 30 minutes after Synapse first launches when I turn on my laptop. It might do it 5 seconds after. It might do it while I'm doing school work, or when I'm gaming, or when I'm doing absolutely nothing. There's no pattern or common circumstances as far as I've been able to tell. It just does it whenever it wants. And I know immediately when it does. Whenever it happens, the lighting on both my devices cuts out for a second then fades back to normal like it does when Synapse first starts up. And then 2 seconds later it does the exact same thing. Before this happens, inter-device functions work; after, they don't work.

It seems like Synapse is momentarily losing track of my devices then immediately recognizing them, but still thinks that they're still disconnected at the same time. So when I send an inter-device command, the command can't reach the other device.

So far, I've tried switching to different USB ports, switching to a USB C hub, reinstalling all my USB drivers, and turning off Window's ability to selectively disable ports to reduce power usage. I have not yet tried reinstalled synapse itself or the actual drivers for the devices (which btw, there are at least 6 for each) because I've read that doing that has actually made some people's problems worse. But I will do that if I can't find a solution.

And if by chance I do figure it out, I'll post it here so that maybe it can be of help.