CUE 16.8M Color Statement

[ChuCho]

Originally Posted by Jucko13

Ok, I just found out why (I think) the keyboard is flickering with the new update. What they did to achieve the 16.8m colors is to change the protocol (not that much tho). What they previously did was sending a 64byte packet 5 times with all the RGB codes. When you select the 16.8m color option in the GUI of corsair it will send 12 packets of 64bytes.

They use a bulkmessage to send the 12 packets as fast as posible but the hardware cant really handle that much information at the same time. What i did in my own software is add a really small delay (5 milliseconds) between every 4 packets (so 3x a delay) and that removed the flickering for my software.

maybe someone from corsair is reading this and can fix it by just a little software update ;)

Here is a screenshot of the simple GUI i made (just for programming profiles when im not at home) http://i.imgur.com/BDYba5V.png

Someone give this guy a job at corsair xD hope they hear your wise words...

[ragedberserker]

Originally Posted by ChuCho

Someone give this guy a job at corsair xD hope they hear your wise words...

Corsair James, can you comment on this please?

[ChuCho]

Originally Posted by ragedberserker

Corsair James, can you comment on this please?

i was kidding about the job thingy tho xD just wanted to highlight his post because i saw some knowledge right there

[ragedberserker]

Originally Posted by ChuCho

i was kidding about the job thingy tho xD just wanted to highlight his post because i saw some knowledge right there

I was talking about the initial finding about the delays lol, not so much about the job.

[ChuCho]

Originally Posted by ragedberserker

I was talking about the initial finding about the delays lol, not so much about the job.

then you should have been quoted his post and not mine :/

But yeah, lets see if them powerful people can do something with that info about the delays :D

[delslow]

Originally Posted by ChuCho

then you should have been quoted his post and not mine :/

But yeah, lets see if them powerful people can do something with that info about the delays :D

Corsair James answered this in another thread. Nope, not related. Flickering is not going away.

[remilton]

Originally Posted by ChuCho

then you should have been quoted his post and not mine :/

But yeah, lets see if them powerful people can do something with that info about the delays :D

Unfortunately, this is the final state for this version of the KB.

[Jong]

Unless Corsair actually tried this, I'd say it's worth a go. Doesn't sound it would be hard to patch. Because Jucko clearly thinks it makes a big difference and he's the only one who can see. It could, just could, be that Corsair know that what they are doing is overtaxing the hardware and are just assuming that all of what we see is because of that, when some, even most, could be due to the timing issue Jucko is raising.

[morris8809]

Problem is, corsair isn't going to keep sinking labor into this kB when they are probably making a revision that will work properly. At this point its take the lighting or leave it. If you want good static colors, turn on 16.8m colors. If you want non seizure inducing animations then use 512color mode. If this makes you angry, then speak with your wallet and get your money back.

First the k70 had leds going out, now they can't build a rgb kB with proper hardware to do the job. All this after stringing us along for months to end up in no better spot than where we started is unacceptable. I'll be looking elsewhere for my hardware from now on as this will be my last corsair purchase. /rant

[RusselC]

Originally Posted by Proffo

Terrible spelling and grammar, but if you can make any sense of that ridiculous comment, you'll find that it's ridiculous.

Please stop with this personal vendetta as it's getting very childish.

[Riekopo]

Originally Posted by Jucko13

Ok, I just found out why (I think) the keyboard is flickering with the new update. What they did to achieve the 16.8m colors is to change the protocol (not that much tho). What they previously did was sending a 64byte packet 5 times with all the RGB codes. When you select the 16.8m color option in the GUI of corsair it will send 12 packets of 64bytes.

They use a bulkmessage to send the 12 packets as fast as posible but the hardware cant really handle that much information at the same time. What i did in my own software is add a really small delay (5 milliseconds) between every 4 packets (so 3x a delay) and that removed the flickering for my software.

maybe someone from corsair is reading this and can fix it by just a little software update ;)

Here is a screenshot of the simple GUI i made (just for programming profiles when im not at home) http://i.imgur.com/BDYba5V.png

It sounds to me like you're confirming what Corsair has said. They can eliminate the flickering, but it would affect the performance of the keyboard. That is, introduce 15 miliseconds of delay.

[PrimE11]

Originally Posted by Riekopo

It sounds to me like you're confirming what Corsair has said. They can eliminate the flickering, but it would affect the performance of the keyboard. That is, introduce 15 miliseconds of delay.

But if you are not gaming and just using the keyboard in a casual way... would 15ms be really that bad if it would mean that we get the full spectrum of colors and effects without any downside like flickering.

I personally wouldnt care about a small delay and for gaming I would just use static colors or the 512 color mode, if I want animations.

[Riekopo]

Originally Posted by PrimE11

But if you are not gaming and just using the keyboard in a casual way... would 15ms be really that bad if it would mean that we get the full spectrum of colors and effects without any downside like flickering.

I personally wouldnt care about a small delay and for gaming I would just use static colors or the 512 color mode, if I want animations.

Jucko13 seems to think Corsair can "fix" the keyboard. They can't. We can't have it both ways. Either we get good performance and flickering or bad performance and no flickering. They screwed up when they chose the hardware. There's nothing that can be done about it.

[Proffo]

Originally Posted by RusselC

Please stop with this personal vendetta as it's getting very childish.

There's no personal vendetta. I was simply defending myself against the accusation that I'd posted something ridiculous.

[morris8809]

Not sure if this is possible or not, but is there a way to prioritize the key input over color data? If so, couldn't this keep the input lag down, and help out on the lighting side as well. Just asking as I have no experience on the software side of things.