Відео

(1) I definitely prefer writing with steno over longer periods of time. It's much easier on the wrists and fingers too. However, when it comes to wrist issues, it's really personal and steno isn't necessarily going to help. I know of people who have benefited greatly from learning steno, but I also know of people who have had their pain flare up when writing with steno. (2) My steno keyboard is the only keyboard at my PC, but I often use my laptop a lot so it's maybe 50/50 steno and QWERTY. Though, if my laptop had a viable steno keyboard, I would absolutely be using that. I work in telecom/construction engineering, and a lot of my job involves data entry of single characters, so steno would get in the way there. It is definitely possible to create a tailored system with dictionaries just for those tasks, but it's more effort than it's really worth, so I haven't bothered. (3) & (4) To me, steno is a hobby that I enjoy and have fun with. Being faster and more comfortable than a QWERTY keyboard is really just a bonus to me. I don't regret learning it in the same way I don't regret learning a musical instrument-even if I don't actively play anymore. If you want to learn steno, I'd recommend learning it as a hobby. If you focus too much on results, you may end up burning out or finding out that it's not for you too late in the journey. Some people don't ever surpass their typing speeds. (5) Learning steno has not affected by QWERTY capability at all. My steno speed and QWERTY speed are not related at all. For a very small fraction of people (I've only heard from one or two), steno has made their speed drop by about 10 to 20%. From what I understand, this is mostly just from being confused with the layout and having to take a few seconds to readjust. (6) Stenographers such as myself are constantly adding entries to their dictionary. In writing this whole piece, I haven't come across anything so far, but tailoring your own dictionary is an essential part of stenography. I definitely add at least one entry everyday. It takes me about 5 seconds to do so. If something is missing from my dictionary, I'll just fingerspell (a technique to write something out letter-by-letter), and then add an entry afterwards. I can't say how long it took me until my dictionary was mostly behaved, especially as I built the Lapwing dictionary from scratch in early 2022 for about 6 months. If you're learning Lapwing, you will already have a working starter dictionary, and for most things (such as what I've written here so far), it will be perfectly adequate. You may occasionally find entries missing, or you may disagree with how a certain word is written, and that is when you'd want to tweak your dictionary. (7) I haven't practised much recently, but last week when I spent about 15 minutes on TypeRacer I averaged about 200 WPM. On a QWERTY keyboard it would have been about 100 WPM. (8) I code with steno, and a lot of people do as well. Steno is very flexible and can write anything that a regular keyboard can output (and even more such as emoji and nonstandard unicode characters). The issue is just learning the systems that allow you to do these things. Replacing your keyboard with steno requires a lot of effort because you need to basically learn several systems: you need separate systems for writing English, symbols, shortcuts, numbers, and more (depending on your needs). That being said, some of these systems are quite simplistic and they can easily mesh together without conflicting with each other. The system I use for numbers is just a numberpad like you'd find on a calculator, so entering in phone numbers, for example, is a breeze. I also have a dictionary for writing math equations with LaTeX quite easily, and I much prefer steno over typing in this scenario. I have a video covering the systems that I use: ua-cam.com/video/pW647nfzXLk/v-deo.html . (9) Same answer to (3) & (4). I don't regret it; it's fun, I've gotten use out of it, and I love contributing to the steno community by creating various resources. (10) My steno speed is definitely faster than my thinking speed. It's taken at least 20 minutes to write all of this out because I've had to stop and think about what I want to say. That said, I do think I would feel quite bottlenecked if I had to write this all out with QWERTY, especially as editing text with a regular keyboard is quite cumbersome. My capacity to formulate new thoughts is definitely increased when I use steno and are not bottlenecked by slower typing speeds. Last thoughts: Getting to 100 WPM or so is definitely going to take at least 100 hours for most people. I got to that speed in about 3 months with 1 to 2 hours of practice everyday, but of course, your mileage may vary. Furthermore, as I've alluded to before, there is no guarantee that your pain is going to go away with steno. I certainly think it's worth a shot, though. Stenoing at 100 WPM requires pressing down about two strokes every second, while typing at the same speed requires about 8 successive key presses in one second. It's much more relaxed and graceful. You can also take a look at some of the 2024 survey responses to see how long it has taken people to reach various speeds: docs.google.com/forms/d/e/1FAIpQLScCVqEkkZUAxtlwjx4ZgxxdFF59piJnh4NlB-JB628tdEoQQA/viewanalytics The survey also has some short answer responses, and I think there are a few responses where people have reported success in mitigating their wrist issues. Of course, these responses are probably plagued by surviveship bias. If you think steno is cool, I'd just recommend learning it on the side and see how it goes. It is very unlikely you will degrade your QWERTY muscle memory.

Almost certainly not for Javelin, you'd really have to make a lot of your own modifications. There is a French system available for Plover (with a dictionary), and it even uses the same layout as English. github.com/Vermoot/Pluvier Sadly, the steno community is just so niche and creating a theory, dictionary, and learning resources for various languages is a lot of work.

@@AerickSteno @AerickSteno Thanks for your fast response . It's a very nice community i join the discord server and its really helpful. I don't know if i have thr strengt to try using plover on my azerty keyboard i will try in the futur. Last year (2nd year of University) i'll discover stenokeyboard it blew my mind i was very thinking about contributing to the stenokeyboard asterisk kickstarter but i miss and the fact that it is a qwerty keyboard probably would confuse me a little. So i think i would try to plover another time and i hope my keyboard will be compatible . Thanks hope you will see me in the community soon

Early on when I created Lapwing, I wanted a linker chord for multisyllable words, and I decided on KWR. The initial y consonant isn't all that common, and phonetically it can represent a glide linker, so at the time it made sense. However, eventually I figured that KWR being used for both a linker and initial y caused issues, so I eventually changed initial y to be KWH. It was a lot easier and less disruptive to keep the linker chord as KWR.

@AerickSteno oh wow, thx for a quick reply. I am just starting to learn steno and it's Def very hard. My very first month was on plover but many places recommend Lapwing to learn so I amtrying the switch now. Also hello fellow Vancouverite

The Z change (S* to STKPW) resolves a few conflicts you find in Plover (sink and zinc, for example). It also makes it consistent with the fingerspelling chord (which is already STKPW). The Y change was made to accommodate the KWR chord's new purpose as a silent linker/glide. It was easier to change the Y chord as it's a pretty uncommon consonant. Originally the Y chord in Lapwing was KWR* and that came with a bunch of difficulties, so I switched it to KWH. Your mileage may vary, of course, but I personally relearned the KWR* -> KWH in a few days.

@@AerickSteno Thanks! This is day one for me, so I'm sure at some point the above explanation will make sense. I've decided to just go with Lapwing and not default Plover because the Lapwing explanation makes more sense to me and takes the way words are spelled into account and not just the way they sound? (Which as a non-native speaker helps). Currently typing 10 wpm on stenojig all rows and vowels, lets see if I can stick with it, but I'm enjoying it so far!

I just read through the differences, and I'm not sure about switching, as I don't like these things about Lapwing: A single "correct" way to write words notion. I sometimes use different multistrokes for some words (when I know the affixes) and I'm happy with the many different ways to split up words in Plover. KWH for y. I'm too used to KWR. *PL for -mp. I use FRP exclusively for -mp, I hate using *PL. KWR as the suffix chord. I would rather use KWH, with my y problem. That syllabic splitting sounds super restricting for me. Yet, I still want to do Lapwing, and I will if I can solve these problems.

You can write anything with steno as long as it is in your dictionary. If you understand your steno theory well enough, you can break down any word into a set of steno strokes. However, any dictionary you use is never going to be 100% complete, and you are expected to always be adding missing entries that you come across. With the theory that I use, I'd write these words as: `TPHU/PHOE/TPHOE/UL/TRA/PHAOEU/KRO/SKO/PEUBG/SEU/HREU/KO/SROL/KA/TPHO/KO/TPHEU/KWROE/SEUS` `HAOE/PHOE/TKPWHROE/PWEUPB` `TE/TRA/PHAOER` Out of these three words, I only have "hemoglobin" defined, however. If I wrote the other outlines, they would just output the raw steno as shown above (since they aren't defined). So, what I could do is either add the terms beforehand, or just come back to the undefined entries later and fix them up. This is what court reporters typically do. When they finish their transcript, they will review all the untranslated strokes, add them to their dictionary, and their software will automatically replace them in the transcript with the actual term. I'm not sure if this is a viable workflow for your uses, but it's just the nature of steno that you are constantly tweaking your dictionary and adding stuff that you need.

@@AerickSteno thanks a lot🔥❤️

Nah it works with other languages. The only issue is that the community is so small no one has put in the effort to add support for other languages. Here is my Vietnamese system: ua-cam.com/video/5LLYKb2uwuo/v-deo.html This is a list of all the languages that Plover supports/may support in the future: plover.wiki/index.php/Steno_Layouts_and_Supported_Languages I really don't know what you're trying to say in the second part though...I'm guessing you're thinking that steno only works for typing/transcription? I've also got a video to disprove that: ua-cam.com/video/pW647nfzXLk/v-deo.html I will agree, though, that it's not for everyone :)

Yes, you do not need to update the firmware if you want to use Javelin with Plover! I show this at 3:14. Javelin can be used by itself (embedded mode), but can also be used with Plover (Gemini PR mode). You can toggle between the two modes by pressing a key combo usually (depends on the board)

@@AerickSteno thank you, can i know what key combinations for switching. Im using Uni v4.

@@AerickSteno Also one of the keys in my Uni v4 suddenly stopped working. it's the Final -L key, do you know any possible way to fix this? maybe like resetting the keyboard? or tweaking some settings , hoping for your reply. I badly need to fix this or it's gonna be difficult for me to continue studying. Thank you!

@@ryanjustinrazon4237 You have to press the two thumber keys, the top S- on the left, and the -D key on the right. The key combo is listed in the Javelin firmware builder page: lim.au/#/software/javelin-steno . You just have to select your board, and then scroll all the way to the bottom (step 5). It's unlikely that it's a firmware issue if a single key just suddenly stopped working. You can try reverting the firmware back to the original one and see if that fixes it. If not, you can join the Plover Discord server, and we might be able to diagnose what's wrong with it. You can also reach out to Peter at StenoKeyboards.com to see if he can repair it.

I tried pressing all 4keys and the embedded steno stopped but Plover is still not working. It says "disconnected" what should I do? thanks

Mostly learning curve and the effort you need to put into finding a system/dictionaries that are compatible with your workflow. In some cases it's just easier to use a regular keyboard. Also, Plover is relatively new (less than 20 years old) and QWERTY keyboards have been around much longer than that. Steno has been around for a long time too, but no one thought of using stenography for general computer usage, not to mention that hardware was prohibitively expensive.

I'm not sure. There are no studies on the topic. This is not the same, but for people suffering from RSI and carpal tunnel, some have reported steno is better than a regular keyboard, some have reported it's worse.

Depends on the format. If it's RTF, you can just import it into Plover pretty easily (some of the syntax of special commands might need to be tweaked, but all the word translations will work). If it's a different format, you'll need to figure out how to convert it to JSON, which, sadly there isn't much info on how to do that online. We'd be happy to help in the Discord server for sure!

Plover theory and the default dictionary? Depends if it clicks with you. For me personally, when I came across a word that didn't make sense in the dictionary, I ended up just memorizing a brief or adding my own entry that was more intuitive (this was quite early on in the process). I know for sure that some people don't like that approach, which is why I made and recommend Lapwing instead. For most people it's probably the better choice, in my opinion.

dotterel is also the app i used before getting a steno board and using a normal keyboard to use for steno by changing the keyboard input

According to Javelin's creator, the licences are incompatible.

@@AerickSteno Interesting, I assumed it would've been distributed under either MIT or GPL, but I've never heard of its Polyform license before.

QMK doesn't provide much of what I need to build a full system. It also supports a lot of things (e.g., 8-bit processors that complicate the code) that I have no intention of ever supporting. Taking full control of everything is what allows tight integration of configuration, firmware and web tools functionality. Boards like MultiSteno aren’t supported because they lack the hardware, not because of any other reason Also, I have no interest in maintaining a separate fork of QMK, or fighting QMK politics for mainlining any work. Plover HID PR from dnaq has sat unmerged for 3 years, so it doesn’t seem there is much priority on stenography. Stenography features such as first up and repeat have not been merged for even longer and have become so far out of sync to be difficult for people to rebuild for new boards too

@@jeffreylim9979 Gotcha, makes sense. Thanks for clarifying.

I'm using the plover retro quotes plugin (or retro surround, I can't remember). It hasn't actually been working recently because of weird technical reasons that I haven't had time to investigate, though.

spkeyboards.com/products/sp-f10-flat-keys

@@AerickSteno Thank You!

Yeah, there are a few that support Javelin. There's some information on the wiki but it's still in progress: plover.wiki/index.php/Choosing_a_hobbyist_steno_writer#Javelin_support

There's a list here: plover.wiki/index.php/Supported_hardware

Have a look at this page: plover.wiki/index.php/Setting_up_a_hobbyist_writer_with_Plover If it's still not working, I'd suggest trying a different cable, making sure it's plugged in correctly, and then if all else fails, maybe try opening a tech support thread in the Plover Discord. We could help troubleshoot your issue.

They're still available to watch in one the playlists I think. If not I'll update it. I just didn't like them and would like to redo them at some point.

I've never; they're too expensive, and I don't know any professionals stenographers in real life. I'd love to at some point.

This video came out when I was in my second year of using steno. I had been practising for an hour or two a day up until this point. I was also still 16, so neuroplasticity and all that.