Author Topic: CODE keyboard dissapointment  (Read 9417 times)

0 Members and 1 Guest are viewing this topic.

Offline cauffe

  • Thread Starter
  • Posts: 7
CODE keyboard dissapointment
« on: Sat, 17 October 2015, 16:11:39 »
Hey all,

I am wondering if there is anyone else out there who has run into any disappointments with the CODE keyboard from WASD keyboards.
The keys feel a little wobbly, not the most stable down stroke path down.

I got one with blues, and these blues just feel way weak. I mean weaker than any other keyboard with blues i've used. They click nice and loudly but the about of pressure needed seems to be really weak. I know blues are not greens and i've used greens and blues before, but there is just something not right about these. They feel weaker than my browns.

Also one of the LED's on my keyboard is starting to flicker out.


I obviously am going to return it because of the dying LED light, but should I get another one with blues? Is it possible I just got a bad board?

If this is kind of a common thing can anyone recommend a good alternative to the CODE KeyBoard with a nice stable downstroke and a stronger blue or maybe  full green? I do need it to be backlit and I would prefer a super-key on the right hand side.

Offline jdcarpe

  • * Curator
  • Posts: 8852
  • Location: Odessa, TX
  • Live long, and prosper.
Re: CODE keyboard dissapointment
« Reply #1 on: Sat, 17 October 2015, 16:14:46 »
I had a 104 with clears, and it pinged so bad that I returned it after a week.
KMAC :: LZ-GH :: WASD CODE :: WASD v2 :: GH60 :: Alps64 :: JD45 :: IBM Model M :: IBM 4704 "Pingmaster"

http://jd40.info :: http://jd45.info


in memoriam

"When I was a kid, I used to take things apart and never put them back together."

Offline tararais

  • Posts: 125
  • Location: East Texas
  • Forum Justice Warrior
Re: CODE keyboard dissapointment
« Reply #2 on: Sat, 17 October 2015, 16:17:39 »
Blues are usually the same, but caps can make them feel wildly different. Tried blues on a board with thick PBT, felt heavy and not very good, and tried blues on thin ABS and then felt light and clicky.

Offline daerid

  • Posts: 4276
  • Location: Denver, CO
    • Rossipedia
Re: CODE keyboard dissapointment
« Reply #3 on: Sat, 17 October 2015, 17:12:44 »
I have two CODEs with Clears (one 87 and one 104), and the 104 pings quite a bit. But overall I'm very happy with them and would recommend WASD to anybody. Sorry to hear you got a bad batch of blues :(

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: CODE keyboard dissapointment
« Reply #4 on: Sun, 18 October 2015, 02:34:44 »
I have a TKL CODE with clears.

It pings a bit, but lightly and consistently across the board.

At home, where it is generally quieter, it almost sounds like wind chimes as I'm typing.  Not unpleasant.  Not loud enough to be a distraction, and once I get into the rhythm of typing something I didn't notice it.

At work it is a bit noisier, and even less noticable.

No LED flicker - all are stable white which I have on the second or third setting.

I haven't noticed any key wobble, but all MX keyboards do wobble a little bit - it's the design and nature of the switch.

CODE with blues and greens have O-rings installed, right?  CODE with clears does not.  Maybe it is the dampening effect of the O-rings that is making the difference.
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline Belfong

  • * Exalted Elder
  • Posts: 5228
  • Location: Malaysia
Re: CODE keyboard dissapointment
« Reply #5 on: Sun, 18 October 2015, 02:40:04 »
Yeah, I have a Code Clear as well and it is a good keyboard. I still use it once a while, well, it's now being replaced by a SSK but I do rotate it out. Still like Clears a lot.
 

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: CODE keyboard dissapointment
« Reply #6 on: Sun, 18 October 2015, 03:42:49 »
Yeah, I have a Code Clear as well and it is a good keyboard. I still use it once a while, well, it's now being replaced by a SSK but I do rotate it out. Still like Clears a lot.

Conversely I'd still be using my SSK at work if someone hadn't complained about it, so I switched to the CODE instead.
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline fuzzybaffy

  • Posts: 553
Re: CODE keyboard dissapointment
« Reply #7 on: Mon, 19 October 2015, 08:10:34 »
Blues are usually the same, but caps can make them feel wildly different. Tried blues on a board with thick PBT, felt heavy and not very good, and tried blues on thin ABS and then felt light and clicky.

This. If you have a specific cluster of keys feeling weak, you might have a case for the MX Blues being bad, but if it's the entire keyboard... yea, I'd suspect it's just the difference in keycaps you're feeling.

Offline saturnotaku

  • Posts: 680
  • Location: The 'burbs, IL USA
Re: CODE keyboard dissapointment
« Reply #8 on: Mon, 19 October 2015, 08:59:26 »
CODE with blues and greens have O-rings installed, right?  CODE with clears does not.  Maybe it is the dampening effect of the O-rings that is making the difference.

Only the MX green CODE has o-rings pre-installed on it.

Offline Phillip_J_Fry

  • Posts: 98
  • Location: Belarus
Re: CODE keyboard dissapointment
« Reply #9 on: Mon, 19 October 2015, 17:04:06 »
I have one (TKL with Clears) and don't like it :(
noise and it's TOOOOOO heavy for me. I have filco with browns at work =(

Offline kinetic

  • Posts: 71
Re: CODE keyboard dissapointment
« Reply #10 on: Mon, 19 October 2015, 18:39:52 »
I have a TKL CODE with Browns and find that it pings quite a bit (more so around the arrow keys).  Besides this, I find the keyboard to be built well, have decent caps and has nice uniform lighting.

Offline MajorMajor

  • Posts: 88
  • Mechanical Keyboard Enthusiast
    • Coding Supply
Re: CODE keyboard dissapointment
« Reply #11 on: Mon, 19 October 2015, 19:17:19 »
I use a WASD 87 with Clears and blue O-rings, never any real issues like others are describing.

The only strangeness is I run my keyboard through a KVM-switch and the media function keys don't work unless plugged directly into the computer. Other keyboards I've tried work just fine through the KVM, it's specific to this WASD keyboard.
TKL / Clears / Dvorak / Flipped Space for Life / Best Programming Keyboards

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: CODE keyboard dissapointment
« Reply #12 on: Wed, 21 October 2015, 04:58:48 »
CODE with blues and greens have O-rings installed, right?  CODE with clears does not.  Maybe it is the dampening effect of the O-rings that is making the difference.

Only the MX green CODE has o-rings pre-installed on it.

Ah, ok, thanks.  I thought it was all the clicky switch keyboards.

I get some O-rings in preparation to install on my CODE with MX clears, but it turned out not as loud as I thought it might be, so I didn't bother using them.
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline SpAmRaY

  • NOT a Moderator
  • * Certified Spammer
  • Posts: 14667
  • Location: ¯\(°_o)/¯
  • because reasons.......
Re: CODE keyboard dissapointment
« Reply #13 on: Wed, 21 October 2015, 06:45:09 »
I have one (TKL with Clears) and don't like it :(
noise and it's TOOOOOO heavy for me. I have filco with browns at work =(
Clears aren't heavy if you don't bottom out. :D

Offline saturnotaku

  • Posts: 680
  • Location: The 'burbs, IL USA
Re: CODE keyboard dissapointment
« Reply #14 on: Wed, 21 October 2015, 08:52:42 »
Ah, ok, thanks.  I thought it was all the clicky switch keyboards.

I get some O-rings in preparation to install on my CODE with MX clears, but it turned out not as loud as I thought it might be, so I didn't bother using them.

I was just checking WASD's site, and you can get o-rings installed on any CODE keyboard, but it will cost you extra. The MX green version is the only one where it comes that way out of the box.

Offline Tuha0jin

  • Posts: 9
Re: CODE keyboard dissapointment
« Reply #15 on: Wed, 21 October 2015, 09:15:26 »
I have a WASD Code Clear 87. It's a good KB. But the standard caps are just not decent. U may need a vortex pbt backlight keycaps

Offline Puddsy

  • nice
  • * Elated Elder
  • Posts: 12281
  • Location: RSTLN E
  • "Do you shovel to survive, or survive to shovel?"
Re: CODE keyboard dissapointment
« Reply #16 on: Wed, 21 October 2015, 10:24:31 »
my KUL doesn't ping

just sayin
QFR | MJ2 TKL | "Bulgogiboard" (Keycon 104) | ctrl.alt x GON 60% | TGR Alice | Mira SE #29 | Mira SE #34 | Revo One | z | Keycult No. 1 | First CW87 prototype | Mech27v1 | Camp C225 | Duck Orion V1 | LZ CLS sxh | Geon Frog TKL | Hiney TKL One | Geon Glare TKL



"Everything is worse, but in a barely perceptible and indefinable way" -dollartacos, after I came back from a break | "Is Linkshine our Nixon?" -NAV | "Puddsy is the Puddsy of keebs" -ns90

Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #17 on: Wed, 21 October 2015, 11:38:09 »
my KUL doesn't ping

just sayin

Must be miracle keyboard. For me everything I have pings, from PCB mounted ergodoxes (vintage blacks with red springs, and mx blue), through Topres (45g HHKB, RF variable fullsize, RF 55g 87u), through GON NerD 60 (stock vintage blacks PCB mounted) up to Filcos with gateron blacks (TKL modded) and mx blue (Fullsize stock) and of course BS boards (the older, the pingier, the pingiest being F122). Basically, if there is a spring, there must be a pings :) such is the physics.
I'm now awaiting code with blues, expect it to ping, but I doubt it will ever bother me.
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline daerid

  • Posts: 4276
  • Location: Denver, CO
    • Rossipedia
Re: CODE keyboard dissapointment
« Reply #18 on: Wed, 21 October 2015, 12:05:35 »
spring = ping

Offline SamFlynn

  • Posts: 20
  • Location: From inside the hive, behind your eyes, and off the grid...into the Black.
  • Type until there is no need...
    • Firefly Online Forum
Re: CODE keyboard dissapointment
« Reply #19 on: Wed, 21 October 2015, 22:19:16 »
spring = ping

too true; tight fitting plates cause it big time. PCB mount all the way baby! Pretty sure there aren't any PCB mounted keyboards (plateless to all the plebs out there) that ping. Just saying  :cool:

I wonder, does WASD even make keyboards without plates?
<Press Any Key>

Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #20 on: Thu, 22 October 2015, 08:00:31 »
spring = ping

too true; tight fitting plates cause it big time. PCB mount all the way baby! Pretty sure there aren't any PCB mounted keyboards (plateless to all the plebs out there) that ping. Just saying  :cool:

I wonder, does WASD even make keyboards without plates?

True, everything with spring pings. Don't tell me RF 55G is poor quality fit, or Model F being poor quality. Or any Filco I tried (3 mine, and numerous I had in service). Everything pings, more or less, but it pings. Even bloody HHKB with plastic plate. There is a spring and it pings.

Also I just got the code and I'm stunned. It has the plate, it's nicely built (although not as tightly as Filco but I somehow like wasd more, even if it's a bit looser construction, I like the looks of the case better than filco).
But the MX Blues they used are nothing like MX Blues! And it's untrue that the newer blues are worse as in FalbaTech we regularly buy batches of brand new MX Blues and they don't have this problem
The ones they use are weird. All of them are mushy and muffled, they don't spring up as nicely as normal switches, some of them lock up, some of them are much heavier than the others (all of them actually feel heavier than my Filco and ErgoDox), and only half of them clicks semi-normally. The other half either clicks but the clicks are very silent, or doesn't click at all! I even made a video that I already sent to WASD that shows it:
https://drive.google.com/open?id=0B4-2eGc1w94mbG9DUGdBa1FjRHc
But apart from switches which are unusable (seriously, rubber dome Logitech feels better than those blues) the whole keyboard is awesome. I love the looks, white plate, consistent and amazing looking backlighting, very clever stabilisers (which were lubed in factory to my surprise as I've read reports that they weren't), not bad keycaps (I don't mind ABS), detachable cable and routing channels underneath (which I really appreciate in Realforce and miss in Filco). I hope I won't need to return it and we will agree on something else with WASD. I have a feeling that this keyboard will be perfect when I replace those crappy switches with my recent favourite - Gateron Black :) It could also be good with MX Clears but I don't like Clears so I pass :)
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline SpAmRaY

  • NOT a Moderator
  • * Certified Spammer
  • Posts: 14667
  • Location: ¯\(°_o)/¯
  • because reasons.......
Re: CODE keyboard dissapointment
« Reply #21 on: Thu, 22 October 2015, 08:10:00 »



I wonder, does WASD even make keyboards without plates?

Almost every oem manufactured keyboard has a plate. More so if it's been released in the last couple years.


Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #22 on: Thu, 22 October 2015, 09:35:31 »
You know what? After using those pseudo blues for a while I think they actually remind me dampened cream Alps switch from old Apple keyboard (which I wasn't sure was clicky or not) which I really dislike. With those blues I'm also not sure if they're clicky switches or not since some of them kind of click, some of them click, and some of them don't click at all :D
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline Kad

  • Posts: 44
  • Location: San Francisco, CA
  • Δ E S T H E T I C S
Re: CODE keyboard dissapointment
« Reply #23 on: Thu, 22 October 2015, 17:05:21 »
I have a WASD v2, not a CODE but I figured I'd chime in to say that my board pings very minimally and it's almost unnoticable unless the room is dead silent when I'm typing.

[WASD v2 w/ MX Blues]

Offline FoxWolf1

  • Posts: 850
  • 154
Re: CODE keyboard dissapointment
« Reply #24 on: Thu, 22 October 2015, 18:22:14 »
I had an experience similar to your "quasi-blues" with MX Blue switches on a Deck recently. Returned it and bought a Keycool with blue Kailh switches instead.

Also, is ping real? I've watched various videos "demonstrating" the effect, and while I can reproduce it by pressing keys in a very weird way, I have not observed it to occur at noticeable volume with any switch type in normal usage. Kind of makes me wonder if noticeable ping in normal usage isn't one of those things that only seems to exist so long as you believe in it.
Oberhofer Model 1101 | PadTech Hall Effect (Prototype) | RK RC930-104 v2 | IBM Model M | Noppoo TANK | Keycool Hero 104

Offline Hypersphere

  • Posts: 1886
  • Location: USA
Re: CODE keyboard dissapointment
« Reply #25 on: Thu, 22 October 2015, 18:33:08 »
I don't have a CODE, but I have a V2 87 with mx browns from WASD. In general, Cherry mx is my least favorite type of switch, but the WASD is one of the best keyboards of this type that I have owned, and their customer service is excellent.

Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #26 on: Fri, 23 October 2015, 00:58:11 »
Yes the keyboard itself is great, I really like it, and don't want to return it. I'd rather fix it with a switches that are actually good.
It's just very sad that the only modern Cherry switch I like is no longer any good. This means that for any new keyboard I get I will have to replace cherries with gaterons, unless manufacturers figure out that genuine cherry is no longer selling point and using a good cherry clone is actually better (although it would be tricky to market clone as better than genuine switch).
As for this keyboard I'm not 100% sure yet whether I will put blue or black gaterons in it. I already have one Filco modified with black gaterons and I love it, I'm accurate and fast on this keyboard (pretty much the same speeds and accuracy as on 55G topre which was so far my best), but I actually wanted this Code to be clicky so why not put a good clicky switch instead? I'm slightly scared of higher force required by gateron blues. The whole reason why I'm using MX now is because of RSI appearing when using my RF 55G, for the same reason I went with MX blue Code instead of MX Clear (which I regret now).
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #27 on: Fri, 23 October 2015, 03:56:28 »
Update on those blues. I already started unsoldering switches from code and did a little analysis of the worst switches. I think it's the problem of actual stem, since when I put normal MX Blue stem in this switch, it works fine, clicks nice and loud. Same goes with gateron blue step, it actually feels almost like genuine (older) MX Blue. Then I tried new MX Blue stem in old MX Blue housing and in gateron housing (with gateron spring), and guess what, no clicks. I also tried with several other springs I had here (55G, 62G, 68G, 120G) and well, it didn't help. I was trying to spot what's going on when looking at open switch clicking and it's not obvious really. I think it's the clicker not fitting the rest of the stem as nicely as in other blue switches, or maybe there is something to do with the lube being different? That's a mistery to me at this point.
I just can't decide if I want this code with Gateron blue or Gateron black :D Both are awesome, but I already have one board with Gateron black - lovely Filco ninja with blank PBT keycaps, this is absolutely one of the best keyboards I've ever typed on, currently with my fingers hurting from RSI, I like it more than Topre 55G. I dare to say I like it more than my so far favourite MX switch being vintage MX Black with 45G spring from brand new MX Reds.
I know I want this keyboard to become my daily driver though, which means it will be used for coding about 12 hours a day + some gaming in between or after that + on gaming on weekends. I was using this gateron black keyboard for about 2 weeks and it was gorgeous. So far I only tried blue gaterons on GON Nerd V60 and there was something I didn't quite like about it (possibly it was inconsistency or switches being too heavy... So I don't know :) I don't want to open and mod this keyboard in near future since it's real pain.
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #28 on: Sat, 24 October 2015, 06:40:40 »
Last update :)
I fixed the keyboard. I really wanted it to become my endgame and it might be true now. It took me quite a while to achieve: desolder LEDs, desolder broken blues, desolder vintage blacks from old G80, open each of blacks, remove diode, replace spring with 62G Korean gold, add lube, solder everything together and here we are. Super light (but not too light), super smooth board to help my RSI. I think WASD should include some linear switches in lineup for Code keyboards. I know linears are perceived as gamers switch, but I know many developers using MX Reds at work and are really happy with them.
So... story over. Code is awesome keyboard, it only needs good switches :)
Cherry on a cake is a MX Grey with 68G spring under the space bar. I'm really happy with how this keyboard came out. I just need to adjust to ligher springs (been typing on black gaterons for last 2 weeks) but even now I can type almost as fast as I ever did on a topre 55g!
« Last Edit: Sat, 24 October 2015, 06:52:41 by czarek »
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: CODE keyboard dissapointment
« Reply #29 on: Sat, 24 October 2015, 22:48:17 »
spring = ping

Ah, so the trick is to get a spring-less keyboard!
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline Elrick

  • Hype Master
  • Posts: 4895
  • Location: CrapTown, Convict Settlement
  • Keyboard Orgasmist
Re: CODE keyboard dissapointment
« Reply #30 on: Sun, 25 October 2015, 02:12:34 »
spring = ping

Ah, so the trick is to get a spring-less keyboard!

Now where would the fun be without "SPRINGS"  >:( .

Might as well go and buy a plain, membrane keyboard and at the same time close down your account here because Geekhack is no longer a place for you.  Instead go visit all the lame "Gamer Forums" and post your trivia and junk keyboard details there, for all to 'fake' praise you.

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: CODE keyboard dissapointment
« Reply #31 on: Sun, 25 October 2015, 02:21:22 »
spring = ping

Ah, so the trick is to get a spring-less keyboard!

Now where would the fun be without "SPRINGS"  >:( .

Might as well go and buy a plain, membrane keyboard and at the same time close down your account here because Geekhack is no longer a place for you.  Instead go visit all the lame "Gamer Forums" and post your trivia and junk keyboard details there, for all to 'fake' praise you.

I like my noisy spring-filled keyboards :p
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline czarek

  • Posts: 627
  • Location: Poland
  • Keep the momentum going!
    • FalbaTech
Re: CODE keyboard dissapointment
« Reply #32 on: Sun, 25 October 2015, 04:04:38 »
spring = ping

Ah, so the trick is to get a spring-less keyboard!

Now where would the fun be without "SPRINGS"  >:( .

Might as well go and buy a plain, membrane keyboard and at the same time close down your account here because Geekhack is no longer a place for you.  Instead go visit all the lame "Gamer Forums" and post your trivia and junk keyboard details there, for all to 'fake' praise you.

That's what I'm saying :) Ping is just a part of mechanical keyboards experience and you have to live with it. Some keyboards are more pingy, some are a bit less so, but they all have some ping, and surprisingly the most valued ones are the pingiest! Ok,j with Realforce you have to try really hard to make it ping but making spring under rubber dome ping is great :D
My little ErgoDox / GH60 factory: http://falbatech.pl

Offline Elrick

  • Hype Master
  • Posts: 4895
  • Location: CrapTown, Convict Settlement
  • Keyboard Orgasmist
Re: CODE keyboard dissapointment
« Reply #33 on: Sun, 25 October 2015, 19:12:24 »
I like my noisy spring-filled keyboards :p

Exactly, here on Geekhack - the PING is KING  8) .

Offline SploogeFactory

  • Posts: 343
  • Location: NSW, Australia
  • Vitamin D deficient
Re: CODE keyboard dissapointment
« Reply #34 on: Mon, 26 October 2015, 07:09:41 »
My CODE hasn't had any of the troubles that I've heard other WASD boards having (there was an issue with earlier versions backspace keys), there is the most minimal amount of audible ping that I can imagine can be produced and I only notice it if I try really hard to listen on the larger modifier keys. Might be a different story on a lighter switch though...

Also, no issues with LED's, the only gripe I have with this board is that the cable routing is fine on the underside but right where the cable comes out from the back of the case routing, it can come loose if played with.

Design is nice and simple, overall really happy with it.
Methylated Spirits, not even once.

Offline Bucake

  • Posts: 945
  • Location: The Netherlands
Re: CODE keyboard dissapointment
« Reply #35 on: Mon, 26 October 2015, 08:45:00 »
ehhh the ping of my ALPS board is actually annoying me a bit.
however, i actually like the ping of my XT F..

i am so confused!
IBM Model F XT // Realforce 87U 55g Type-S // HHKBP2 45g Type-S // KBT Pure Pro Cherry MX Red

Offline sean

  • Posts: 304
  • Location: United States
  • Mechanical newb
Re: CODE keyboard dissapointment
« Reply #36 on: Mon, 26 October 2015, 14:20:53 »
I have absolutely no idea why people keep buying CODE's when everybody that's bought one has had nothing but problems. Also, the fact that WASD hasn't addressed the pinging issue after all this time to me means they don't care about their userbase.

Offline daerid

  • Posts: 4276
  • Location: Denver, CO
    • Rossipedia
Re: CODE keyboard dissapointment
« Reply #37 on: Mon, 26 October 2015, 18:03:25 »
Also, the fact that WASD hasn't addressed the pinging issue after all this time to me means they don't care about their userbase.

Wow... that's quite the leap of faith there

Offline Herothereu

  • Posts: 95
Re: CODE keyboard dissapointment
« Reply #38 on: Mon, 26 October 2015, 18:44:18 »
I thought Filcos had ping too?  Do all Costar keyboards have it?

Offline fuzzybaffy

  • Posts: 553
Re: CODE keyboard dissapointment
« Reply #39 on: Mon, 26 October 2015, 23:32:19 »
If someone casts "pinging" as a problem, that person is seriously retarded. There's this thing called the "Laws of Physics". You smash two things together, it will create a sound. That is what pinging is.

Complaining about mechanical keyboards pinging is the same thing as complaining about your car door making a "slam!" noise when you close it.

Offline sean

  • Posts: 304
  • Location: United States
  • Mechanical newb
Re: CODE keyboard dissapointment
« Reply #40 on: Tue, 27 October 2015, 00:42:40 »
If someone casts "pinging" as a problem, that person is seriously retarded. There's this thing called the "Laws of Physics". You smash two things together, it will create a sound. That is what pinging is.

Complaining about mechanical keyboards pinging is the same thing as complaining about your car door making a "slam!" noise when you close it.

So you're saying this is a totally acceptable noise for a keyboard that is intended to be a daily driver?
I own several keyboards but none make any kind of pinging noise. If I had a keyboard that made an an audible pinging noise it would distract me and I would never want to use it. If it wasn't a problem like you claim then a bunch of CODE owners wouldn't be complaining about it.

But no call me retarded.

Offline fuzzybaffy

  • Posts: 553
Re: CODE keyboard dissapointment
« Reply #41 on: Tue, 27 October 2015, 00:55:10 »
It's a keyboard with a metal plate underneath... What do you expect?

Offline sean

  • Posts: 304
  • Location: United States
  • Mechanical newb
Re: CODE keyboard dissapointment
« Reply #42 on: Tue, 27 October 2015, 01:17:46 »
I have seven keyboards with metal plates. No pinging. Anyway this is pointless. If you like the sound of pinging then you do you.

Offline SploogeFactory

  • Posts: 343
  • Location: NSW, Australia
  • Vitamin D deficient
Re: CODE keyboard dissapointment
« Reply #43 on: Tue, 27 October 2015, 01:33:40 »
If someone casts "pinging" as a problem, that person is seriously retarded. There's this thing called the "Laws of Physics". You smash two things together, it will create a sound. That is what pinging is.

Complaining about mechanical keyboards pinging is the same thing as complaining about your car door making a "slam!" noise when you close it.

So you're saying this is a totally acceptable noise for a keyboard that is intended to be a daily driver?
I own several keyboards but none make any kind of pinging noise. If I had a keyboard that made an an audible pinging noise it would distract me and I would never want to use it. If it wasn't a problem like you claim then a bunch of CODE owners wouldn't be complaining about it.

But no call me retarded.

That's pretty extreme pinging, is that on a linear switch? Honestly never had pinging like that with my CODE.
Methylated Spirits, not even once.

Offline 1swt2gs

  • Posts: 622
  • Location: CA
  • DOGE
Re: CODE keyboard dissapointment
« Reply #44 on: Tue, 27 October 2015, 02:41:54 »
Another Code user here, there is pinging on my clears TKL but not enough to really bug me. I definitely see how it can bug others though!
Such artisan, many caps, very keyboard.

Always searching for Bro caps! 

1swt2gs classifieds!


Offline SploogeFactory

  • Posts: 343
  • Location: NSW, Australia
  • Vitamin D deficient
Re: CODE keyboard dissapointment
« Reply #45 on: Tue, 27 October 2015, 04:05:37 »
Another Code user here, there is pinging on my clears TKL but not enough to really bug me. I definitely see how it can bug others though!

Clears seem to be the common theme here, would explain why I don't get it.
Methylated Spirits, not even once.

Offline drewba

  • Posts: 242
  • Location: IL
Re: CODE keyboard dissapointment
« Reply #46 on: Tue, 27 October 2015, 10:49:14 »
For work I have a WASD V2 with clears which doesn't ping at all  :thumb:

On the other hand I don't like the tiny bezel and sharp edges. I wish I purchased a second KUL but didn't have the patience to wait for a retailer to get them back in stock.

Offline Herothereu

  • Posts: 95
Re: CODE keyboard dissapointment
« Reply #47 on: Tue, 27 October 2015, 10:52:48 »
If you are ping sensitive get a Novatouch!

Offline daerid

  • Posts: 4276
  • Location: Denver, CO
    • Rossipedia
Re: CODE keyboard dissapointment
« Reply #48 on: Tue, 27 October 2015, 13:54:14 »
So you're saying this is a totally acceptable noise for a keyboard that is intended to be a daily driver?

Yes, actually. I am. The sounds coming out of that keyboard seem perfectly fine. To me.

Quote
I own several keyboards but none make any kind of pinging noise. If I had a keyboard that made an an audible pinging noise it would distract me and I would never want to use it.

I'm always constantly amazed how readily most people are to espouse their own personal view of things/the world as empirical truth. Supplying a personal opinion or preference does actually nothing to help your argument, it actually hurts it.

Quote
If it wasn't a problem like you claim then a bunch of CODE owners wouldn't be complaining about it.

It's a problem for those people (and yourself, apparently). Far greater in number are the perfectly happy/satisfied CODE/WASD owners who don't make a peep about their boards because they're busy using them and living their lives.

Quote
But no call me retarded.

That's definitely a bit uncalled for, I'll agree.


I have noticed that Clears tend to ping quite a bit more frequently than other types, I'm almost positive it has to do with the stiffness of the spring. The force curve on stock Clear springs is quite unique among Cherry switches, which probably explains why it doesn't happen to other switches (which usually share springs across more than one switch type).
« Last Edit: Tue, 27 October 2015, 13:55:49 by daerid »

Offline sean

  • Posts: 304
  • Location: United States
  • Mechanical newb
Re: CODE keyboard dissapointment
« Reply #49 on: Tue, 27 October 2015, 18:55:29 »

I have noticed that Clears tend to ping quite a bit more frequently than other types, I'm almost positive it has to do with the stiffness of the spring. The force curve on stock Clear springs is quite unique among Cherry switches, which probably explains why it doesn't happen to other switches (which usually share springs across more than one switch type).

I figured the pinging would have been from a thinner than usual aluminum plate that could cause vibrations, echoes and therefore, "pinging". But it makes more sense if only the keyboards with clear switches are pinging since it seems the majority of people are buying them with clears.

Also thanks for stating your opinion in a civil manner rather than flaming at the moment you see someone that has a different view than you.