Razer Huntsman Elite local profiles not saving to keyboard | Razer Insider

Razer Huntsman Elite local profiles not saving to keyboard



Show first post
This topic has been closed for comments

72 Replies

peeveskabrewdoo
Same issue. I'm using the Huntsman Elite at work on a PC, where I can't have Synapse installed or running. The only reason I went ahead and purchased was because the onboard profiles seemed like a workable solution for a really cool feature. But the lack of responsiveness / solutions from official staff members is casting some doubt on my purchase.

I see Razer.RedPanda atleast responded to the thread creator back in August, but this is clearly an unaddressed issue. Is someone from Razer going to get in front of this for the others here or do we need to make more noise?

-Patrick



I should have read this thread earlier.. i bought this keyboard for the exact same reason.. and now i can't get the color profiles saved in the on-board memory..
It happens for Blackwidow Elite too. Disappointing product and software.
should have bought Corsair instead
I got a huntsman yesterday and am very disappointed that the packaging basically promoted a load of lies and that there's literally no way I can just make the thing white when I'm programming on a mac.

I feel utterly ripped off and almost feel like going around Razer and their poor support and contacting the relevant trading standards authority for false advertising.

I am literally so angry that if they gave me the API for it, i'd write a mac version for them, or at least something that can control the colour, because I get the feeling we've all been robbed and that's the end of it.

Shan't be buying another Razer product, which is a shame because I fancied a laptop next year.
Just bought this keyboard today and having same problem. Updated firmware and using Synapse3

Dragged profile to all the onboard slots and doesn’t save the lighting nor key mapping. I remapped the default Mute button to Open Calculator and this doesn’t map when i chose the onboard profile.

Very disappointed but I have 15 days to decide whether to keep it.
Literally the same exact expectations, problem, and disappointment. Really need to keep this going. I can't believe you can't save the lighting to the local on board memory, which is really the first thing you'd expect you'd be able to do. :mad_:
I returned my keyboard. The place where I bought from has 15 days satisfaction guarantee and I was not satisfied
Same issue with my new BlackWidow Elite. I am programming keyboard with Synapse 3.3.1216.12212.

I have a workaround of programming with a VMware VM (Win 7). After setting lighting if I disconnect keyboard from VM (BEFORE quitting Synapse), the lighting stays. That is until real machine goes to sleep or I disconnect the keyboard from the real machine. So this is a temporary work around and is not a solution.

Will there be a fix so that lighting settings are saved to keyboard onboard memory?
Userlevel 1
I have this same issue. I am returning 2 keyboards today (purchased 3 days ago), before I lose my money. I will stay with the deathstalker chroma, until I decide which other company to go with (with a keyboard, mouse, and mousepad that WILL save their lighting).

For now, I am using an older Razer keyboard, Firefly, and Lancehead, all of which are supported in Synapse 2, so I can at least not have to see Spectrum Cycle, when the Windows Lock screen kicks in.
Has anyone heard from Razer about this keyboard onboard profile issue? Anyone contact support directly? Does not seem like they hanging around here.

I am keeping my Black Widow, but am holding off on supplying the rest of office until I can get this light thing under control. The default color scheme is ok, but we like it steady.
my blackwidow elite just wont sync up or anything with synapse 3. I plug it in and it turns on, but the num-lock, and the caps-lock lights wont turn on or off when synapse 3 installs. The lightning effects also don't sync over to the keyboard. any advice or is this just synapse 3 right now? Keyboard can still be used and typed on but I want to use the effects.
I've had the Blackwidow Elite for a month or so, and everything is great except one glaring fault and that is the rainbow show every time I wake my computer from sleep or turn my computer on. Come on Razer, for people like me, and as mentioned by others on this same thread, it's outright embarrassing to have this keyboard in a professional environment. Please fix this issue!!, then I could maybe recommend your products again, but until then I'm telling others to look at alternative manufactures for a great "professional" mechanical keyboard.
Userlevel 1
I have started replacing the Razer gear with ROG gear, which syncs with my motherboard. I will let you all know my findings.
yrilo
And that is great approach. BUT, I think that would be OK to put some other lightning effects on baord, just simple one, so we can switch that default wave. Like reactive (pick background color, front color, and speed), ripple effect, and so on.


The effects are already on the board. What I have seen with my own eyes are wave, chroma cycle, static, starlight, breathing and reactive. Not sure how many more there are.

Its just about adding some way to configure this default/offline mode or whatever you want to call it in Synapse.
Same issue for me 😞
RazerThe_Fiend
That someone would be me.

This was a conscious decision after months of deliberation and debate for several reasons :

1. Older devices would never get updates for lighting effects. For example; BW Chroma (first gen) never got Starlight and Fire effects in Synapse 2 because the firmware didn't support it. Only when Synapse 3 was released, we could bring those effects to older devices. We want to keep bringing new Chroma features to our devices for a longer time, which is feasible when using software-driven effects. For reference, all future lighting effects and other lighting related features, will automatically be available on all Synapse 3 devices.

2. On-board micro-controllers don't have the RAM/storage to run complex effects (on multi-layered effects) well. We didn't want to do half-and-half of effects that could be stored on device or that could be run on Synapse. Plus there's only so many effects that can be stored on the limited amount of memory available on-board.

We decided to use that memory for implementing a macro engine, which allows you to execute macros (including even mouse movements) without Synapse.

3. If we want to add or update any lighting effects, we'd have update the firmware for ALL the Chroma devices. This in-turn would require us to test different permutations and combinations of firmware and software versions, which isn't practical.

4. Synapse 3 has Chroma on the forefront with location-aware effects. Those aren't possible using just firmware as it is.


So you're saying there's adequate on-board resources for just a static lighting, if even for a single color. That would be much preferred over the rainbow show. I'm certain a lot of people including myself would be more then happy with that option, and once the keyboard connects to Synapse it can switch to a more complex lighting effect.

Even gdpr.yeah has apparently found a way set a static color that stays until Synapse is launched changes it back. That in it's self says that Synapse already has the ability to write a default effect, why not give us the ability to choose what that effect is.
RazerThe_Fiend
That someone would be me.

This was a conscious decision after months of deliberation and debate for several reasons :

1. Older devices would never get updates for lighting effects. For example; BW Chroma (first gen) never got Starlight and Fire effects in Synapse 2 because the firmware didn't support it. Only when Synapse 3 was released, we could bring those effects to older devices. We want to keep bringing new Chroma features to our devices for a longer time, which is feasible when using software-driven effects. For reference, all future lighting effects and other lighting related features, will automatically be available on all Synapse 3 devices.

2. On-board micro-controllers don't have the RAM/storage to run complex effects (on multi-layered effects) well. We didn't want to do half-and-half of effects that could be stored on device or that could be run on Synapse. Plus there's only so many effects that can be stored on the limited amount of memory available on-board.

We decided to use that memory for implementing a macro engine, which allows you to execute macros (including even mouse movements) without Synapse.

3. If we want to add or update any lighting effects, we'd have update the firmware for ALL the Chroma devices. This in-turn would require us to test different permutations and combinations of firmware and software versions, which isn't practical.

4. Synapse 3 has Chroma on the forefront with location-aware effects. Those aren't possible using just firmware as it is.


So how do Corporate users use Blackwidow Elite. They cannot install Synapse 3 and we do not want Spectrum Cycling as the only option. Can we have static color? Is it possible?
RazerThe_Fiend
For products exclusively on Synapse 3, the only effect on-board is Spectrum Cycling... we use the saved resources (we actually added a bit more) to implement a macro execution engine on hardware,


So the Huntsman Elite is not a Synapse 3 exclusive product?

Because it DOES have more on-board effects than Spectrum Cycling. For instance I can activate starlight or static (not using Synapse of course) and both continue working across boot cycles and even when I am in boot menu or BIOS. (So no software is running.) The other effects probably work to as they are activated exactly the same way, I just haven't tested them.

My keyboard has firmware v1.3. Please check your sources before stating again that it does not have these effects.
Ty_Crisos
My Razer Huntsman elite just came in today and I was super disappointed with how misleading their description was when talking about on-board memory. I paid $225 (including shipping) for this keyboard only to find out I can change the lightning effect when I plug it into anything else without synapse 3. I’m so bummed out as this was my only Christmas gift and I waited over almost 3 weeks just for it to come in. Had I simply known it wouldn’t store my lightning profiles on the keyboard I would have bought a different keyboard. I’d still buy a Razer but a different keyboard nonetheless. Now I can’t even return it sadly, so upset, I have to wait till my birthday just to pick a different keyboard :slightly_sad:


LOL i know the feeling, got my Blackwidow Elite as a gift for XMAS (from my wife) and dont want to return it for fear of upsetting her.

Couldn't give a damn about the macros!
Userlevel 6
Hello! Can you send us a short video of how you save the profiles to the onboard memory?
Razer.RedPanda
Hello! Can you send us a short video of how you save the profiles to the onboard memory?


Here is a link to the file.

https://nofile.io/f/wDqSXWg5aBr/2018-08-07_13-39-19.mp4
Userlevel 6
Thanks for the video. How many profiles do you have and how many do you store in the onboard memory? Also, do you have Synapse 3 open when you cycle through the profiles?
Razer.RedPanda
Thanks for the video. How many profiles do you have and how many do you store in the onboard memory? Also, do you have Synapse 3 open when you cycle through the profiles?


I've only tried with one profile and no I have synapse 3 closed when I cycle to the profile. Does the profile save lighting settings?

Any update on this?
Userlevel 6
Have you tried with more than 1 profile? I sent you a PM so I can help you out with this.
Pls share the workaround here instead of a pm. Having the same issue as well and probably so for many others. 3 profiles saved to the red, green, and blue local profile slots but keyboard lighting goes back to the default cycling once synapse is completely closed or when plugged into another PC without synapse.

Cycling through the profiles using the fn and menu button only shows the menu button changing between profile colours, but the lighting effect stays at the defaulted cycling mode for all profiles.