Obviously NKRO will need to work for chorded typing. I know NKRO is meant to work, but are there any problems with ergodox regarding this?The stock ErgoDox firmware has 6KRO over USB, because it uses PRJC's USB routines which uses the "boot protocol" which has this limitation.
here's the thing.. is steno would be a huge investment in "learning" in terms of hours..
if it's not your occupation.. I don't see that paying off much at all.
I guess I read your mind as I am considering to do exactly the same thing. The Ergodox keyboard would be nice as then you would be able to use it as a regular keyboard along with plover. But before I make the purchase I too would really like to know how well does the NRKO work. The longest (mis)stroke that I found in the plover dictionary was 14 keypresses long (STKPWHRAOEUPBS: guidelines), so in practice NRKO is needed.
I have already tried plover for some time using Microsoft's sidewinder keyboard, but the problem has been that I have really hard time when I try to hit the middle positions especially for DZ, TS and LG. I have not bothered to buy the keypads that are sold for plover though. Have you given a thought which keypads would be the best considering that you need to press two keys with one finger?
What about the stenosaurus? Have you considered to get it when it will be available?
Obviously NKRO will need to work for chorded typing. I know NKRO is meant to work, but are there any problems with ergodox regarding this?The stock ErgoDox firmware has 6KRO over USB, because it uses PRJC's USB routines which uses the "boot protocol" which has this limitation.
To get full NKRO, you could use Hasu's tmk_keyboard firmware which has support for ErgoDox, but it requires that you build it yourself and some simple C programming to change the layout.
6KRO in this case means that it supports a chord with up to six keys where none is a modifier. The modifiers (Ctrl, Shift, Alt, Windows/Command) will always be recognized because they are separate in this protocol.
not to mention that the muscle memory in a real steno board will be completely different from repurposing an ergodox
here's the thing.. is steno would be a huge investment in "learning" in terms of hours..
if it's not your occupation.. I don't see that paying off much at all.
not to mention that the muscle memory in a real steno board will be completely different from repurposing an ergodox
The keys seem so widely spaced on the Stenosaurus, how would you hold two at once? Do you only need to hold two keys along the columns, maybe?
You could probably dremel and glue up something that works ok for square caps. The ergodox is so customizable that I can't imagine there's many problems that couldn't be adequately solved with a bit of ingenuity.
I should hopefully have my ergodox set up in three weeks time, waiting on parts to arrive atm. I'll try to remember to let you know how it goes. Like I said, I'm a newbie to steno but I'll start on more lessons as soon as it's all set up.
I should be ok getting hasu's firmware to work. I have no problem editing some layout files. I'm sure there'll be ok documentation.
Well yes, you are quite right that the learning curve is quite high for steno, and it can take a while before you master it. It depends quite a loton which theory is used to learn steno.
Still I would not say that only court reporters or captioners benefit from steno. Also programmers and persons that need to write a lot and fast may benefit from steno. Of course you can learn it just for fun.
Yes. If you need to press two adjacent keys on a column you flatten your finger little bit and position it on the gap between the keys. Some theories include also combinations like *R and SZ which require pressing keys on adjacent rows. For this you need widened * and DZ keys which as I have understood will be made available for the stenosaurus additionally to the regural keys.
You could probably dremel and glue up something that works ok for square caps. The ergodox is so customizable that I can't imagine there's many problems that couldn't be adequately solved with a bit of ingenuity.
I should hopefully have my ergodox set up in three weeks time, waiting on parts to arrive atm. I'll try to remember to let you know how it goes. Like I said, I'm a newbie to steno but I'll start on more lessons as soon as it's all set up.
I should be ok getting hasu's firmware to work. I have no problem editing some layout files. I'm sure there'll be ok documentation.
Please, do let us know if you get the NKRO working. Also photo of your ergodox would be nice if you make any mods to it.
KEYMAP( // layer: Plover
// left hand
FN6, NO, NO, NO, NO, NO, NO,
NO, 1, 2, 3, 4, 5, NO,
NO, Q, W, E, R, T,
NO, A, S, D, F, G, NO,
NO, NO, NO, NO, NO,
FN6, NO,
NO,
C, V, NO,
// right hand
NO, NO, NO, NO, NO, NO, TRNS,
NO, 6, 7, 8, 9, 0, TRNS,
Y, U, I, O, P, LBRC,
NO, H, J, K, L, SCLN,QUOT,
TRNS,TRNS,NO, NO, NO,
TRNS,TRNS,
TRNS,
NO, N, M
),
For my setup, here's the extra layer to add to the keymap_x.h file (I started from cub-uanic's layout and went from there).Code: [Select]KEYMAP( // layer: Plover
// left hand
FN6, NO, NO, NO, NO, NO, NO,
NO, 1, 2, 3, 4, 5, NO,
NO, Q, W, E, R, T,
NO, A, S, D, F, G, NO,
NO, NO, NO, NO, NO,
FN6, NO,
NO,
C, V, NO,
// right hand
NO, NO, NO, NO, NO, NO, TRNS,
NO, 6, 7, 8, 9, 0, TRNS,
Y, U, I, O, P, LBRC,
NO, H, J, K, L, SCLN,QUOT,
TRNS,TRNS,NO, NO, NO,
TRNS,TRNS,
TRNS,
NO, N, M
),
I tried to map to the default Plover keys so I wouldn't have to custom-compile my own Plover from source.
More info and links on putting TMK onto Ergodox:MoreThe FN6 button in my layout turns off the Plover layer so I can get back to normalcy.
My full layout is available at https://github.com/simonmelhart/tmk_keyboard/blob/simon_layout/keyboard/ergodox/keymap_simon.h
Official documentation: https://github.com/cub-uanic/tmk_keyboard/blob/master/doc/build.md
TMK on Ergodox thread: http://geekhack.org/index.php?topic=48106.0
NKRO is supposed to work on ergodox when running this firmware.
...and you really do have full NKRO on this thing?
2. Features
Optional. Note that comment out to disable them.
#NKRO_ENABLE = yes # USB Nkey Rollover - not yet supported in LUFA
That is probably right. I'm on the PJRC stack and haven't tried LUFA.
Once you turn on NKRO_ENABLE, you can turn on NKRO with shift+ shift+N. Alternatively, you can edit common/host.c and set keyboard_nkro to true by default, so it starts up in NKRO. I haven't had any compatibility problems.
Is there any documentation that mentions the shortcuts like shift+shift+N? Other than just the mention in the comment for the changelist, that is?
After you make your keymap_simon.h file, how do you tell it to actually use that file?
I would love some of those flat keys; at two bucks a pop, though, that's fifty dollars to outfit all the keys I'm using for Plover. (Group buy, anyone?)
http://www.pimpmykeyboard.com/marketplace.php#
There are some flat square keys near the bottom of the page. They should work okay for pressing adjacent keys. I think the ErgoDox is a good candidate for this.
I've been using Plover with my Ergodox for a few months now, and it works like a charm. I'm currently typing about 40 words a minute, slower than previously, but it is a lot of fun, and I can see upside in my future.
I'm using Hasu's TMK firmware with NKRO on, and a custom layer that maps the default Plover keys onto the home row and bottom row, plus the thumb keys, of course. Diagram attached.
I would love some of those flat keys; at two bucks a pop, though, that's fifty dollars to outfit all the keys I'm using for Plover. (Group buy, anyone?)
I've been using Plover with my Ergodox for a few months now, and it works like a charm. I'm currently typing about 40 words a minute, slower than previously, but it is a lot of fun, and I can see upside in my future.
I'm using Hasu's TMK firmware with NKRO on, and a custom layer that maps the default Plover keys onto the home row and bottom row, plus the thumb keys, of course. Diagram attached.
I would love some of those flat keys; at two bucks a pop, though, that's fifty dollars to outfit all the keys I'm using for Plover. (Group buy, anyone?)
I'd work as a transcriptionist and I've been waiting for somebody to do this. I'm wondering why you didn't just move everything over to the centre and have the asterisks on the four larger vertical keys? It would seem to make more sense to me.
And from a non-tech standpoint, how difficult is it for the average person to program all this?
I mean the average person like myself who finally overcame their fear of programming the Ergodox. Is there an easy way to load Plover
onto the Ergodox that a non-programmer could do?
Okay, I'm getting closer. I had two problems. One, my antivirus wasn't playing nice with the Plover.exe so I fixed that. But I'm not understanding how I get the firmware file. I see them, but how I do I get them?
I have both those files, but I don't understand what I'm supposed to do with them as far as building the firmware.
find . -iname \*hex -or -iname \*eep
lists every file ending in hex or eep below the current directory.git clone https://github.com/shayneholmes/tmk_keyboard.git
to get it to work without some publickey error that I had to look up on stackoverflow, but other than that everything worked and it took about 2 minutes for me to copy and paste all the steps.How do I use it now?
Is it on a different layer from qwerty?
You can toggle the Plover layer on and off by pressing the FN5 key. That's the left-thumb key above the "O" key in the diagram above.