I have two things I'm focusing on with my writing right now: -P and commas. I'm still working on that "stacking SKP" business, but I got it nailed down once classes started. I put SKP in as a conflict - with "and" as both choices - just so it would show up in green every time I stroked it to remind me to stop stroking it.
For some reason it didn't help much when I was mainly doing captioning, but almost the first day I switched to more CART, I got myself doing SKP-P at least 90% of the time. Maybe it's because I don't have much time to think during captioning, and even having just a few times during CART where I got to really think about it before I wrote it allowed it to become reflexive.
I completed my project of entering conflicts for "words that typically have commas after them." I had a list of 35, and I experimented with one a day until I had gone through the whole list. Some worked with two, three, or four options, and some I could tell weren't even going to work with two. Now the problem is that I never remember they're in there, and I just write the comma anyway. They come up in green, though, which reminds me that I'm supposed to be not putting the comma in.
I actually had myself pretty well trained with "so" and "okay," until I came into a bunch of instances where the AI wasn't picking correctly and I had to delete them. I'm doing the best with "well" and "all right"; I'm pretty sure none of the others have stuck at all. I seem to write "therefore," "however," and "in other words" the most, though.
Speaking of conflicts, I have an awesome one that works great: day to day versus day-to-day. The software is really good at knowing which is which, probably since one is just some words and the other is an adjective. I bet there are other things I could do that with (once-in-a-lifetime maybe?), but for now I'm just happy with "day to day."
Another thing I'm working on is waiting until the new sentence starts to put punctuation for the last one, so I can avoid when I think they're done, and I put a period, but then the next thing they say isn't a sentence on its own. It's hard to wait, though. Lots of times I can delete the period that turns out not to belong, but also lots of times I don't have time.
I also had to change my outline for a question mark. I think the S- key is stiff on this IE. It won't matter since I'm getting a new one, but I was almost never hitting the S- in STPH* for my question mark, and it kept coming out as N. I had the probablem occasionally with the LS, but it started to get really bad with the IE. I initially made a conflict, but the software wasn't choosing correctly often enough, and I would erase the N and re-write it three times and still get N, so I had to do something. It was getting bad! I wound up just making my question mark STPH*P, and I was so relieved to have a way to actually get a question mark to come out that I picked it up almost instantly.
The strange thing is that I drag the S in weird places on the IE, too, probably because I have the sensitivity set low since the key is stiff. Maybe it's not so strange, after all. The worst is when I think I've written "he," but it actually came out "she," and I don't notice it until it's too late. I keep getting "snot" for "not," too. I hope it's all better on the new machine!
Showing posts with label Conflicts. Show all posts
Showing posts with label Conflicts. Show all posts
More New Stuff
Another new idea I picked up comes courtesy of Phoenix theory, via Jade King on her FB group. I think Phoenix doesn't use the asterisk for conflicts, and they teach the idea of stroking R-R after something there might be a problem with. So, mat might be MAT, and Matt would be MAT/R-R. I absolutely love it! I've used it for all sorts of things - Mayhew, Wei, Wie, Barr, Busch, Cannes, Pitt, Starr..the list could be endless! I'm fairly good about being able to use the asterisk for things like that, or being creative like KA*UN for Kahn, but there's only so much I can think of. As with all things, now the problem will be remembering which things I used R-R for. But if anything comes up frequently enough that I can actually remember it, it will be an easy stroke to use.
No one ever really said a.k.a. much in CART, but it seems to come up a lot on TV. Not only is it annoying having to fingerspell it every time, it looks weird in all caps when the rest of the sentence is also in all caps, so I came up with AIK/R-R as an outline for it.
I've also made briefs for a couple buzzwords that come up a lot - best practices (BIKTS) and takeaways (TA*EZ).
It took me forever, but a few weeks ago I finally figured out how to do credits properly. They're supposed to pop on in their entirity regardless of the fact that most captioning is roll-up and done in two or three lines. At first I thought I would just have a stroke with the entire caption as the definition, but that was still roll-up. Then I figured out how to read in a block file, but with the stations that do two lines, for example, only two out of three credit lines were showing up. I knew I could probably just ask the captioning company or a FB group, but I was determined to figure it out myself.
I finally happened upon the answer in the sports section of the new NJCaptions (now C2CC) captioner's manual. You can put a "position" tag in your stroke that reads the block file; and you put the pop-on as a script command in that block file, and voila! If you're doing an opening credit, you can put the position tag for the rest of the programming in its own stroke, and stroke that after you do the opening credit to put it back to two lines or however many you need. I feel so much better now that I can do the credits properly!
No one ever really said a.k.a. much in CART, but it seems to come up a lot on TV. Not only is it annoying having to fingerspell it every time, it looks weird in all caps when the rest of the sentence is also in all caps, so I came up with AIK/R-R as an outline for it.
I've also made briefs for a couple buzzwords that come up a lot - best practices (BIKTS) and takeaways (TA*EZ).
It took me forever, but a few weeks ago I finally figured out how to do credits properly. They're supposed to pop on in their entirity regardless of the fact that most captioning is roll-up and done in two or three lines. At first I thought I would just have a stroke with the entire caption as the definition, but that was still roll-up. Then I figured out how to read in a block file, but with the stations that do two lines, for example, only two out of three credit lines were showing up. I knew I could probably just ask the captioning company or a FB group, but I was determined to figure it out myself.
I finally happened upon the answer in the sports section of the new NJCaptions (now C2CC) captioner's manual. You can put a "position" tag in your stroke that reads the block file; and you put the pop-on as a script command in that block file, and voila! If you're doing an opening credit, you can put the position tag for the rest of the programming in its own stroke, and stroke that after you do the opening credit to put it back to two lines or however many you need. I feel so much better now that I can do the credits properly!
New Ideas
A new month already, and I actually have time to update within the first week! I don't have any interesting updates on anything, so I'll just have to write about some things I never have time to get to.
Steve Kosmata started doing a cool thing where he posts a short video once a week about stuff you can do in Eclipse; that's what inspired me to take a look at my most frequently used three-stroke words, although I had seen the suggestion to do that before. Last week he brought up the old "conflicts for not having to write puncutation" idea, which I'd also seen kicked around, but I just didn't want to get into it.
In the video, he mentioned using it for words that typically have a comma when they start a sentence - therefore, so, oh, etc. I didn't want to get *too* into it, but those seemed like they might work, so I sat down for an hour and a half or so and played around with it. It turned out to be a bigger project than I was expecting. There are so many words like that, and they could come at the beginning, middle, or end of the sentence, so you might need a comma before, after, before and after, or no commas at all.
I experimented with it, and if it didn't seem like it was going to pick correctly 99% of the time, I didn't go all the way with it. A couple of them I was able to do all four choices for; some of them I could only do two; and some of them I wound up tossing out the idea altogether. There are a ton of words I didn't experiment with, so I'm going to tackle one of those a day. Now the hard part is going to be remembering what words I don't have to write commas for, and in what situations I don't have to write the commas. I really haven't picked up on that at all yet, but I only put things in a couple days ago.
I also changed the function keys on my IE to act like S, so hopefully that will cut down on untrans from accidentally hitting them when I mean to hit S. I wanted to use them for speaker IDs, but it's just a project I don't want to start right now. On the LS, I used to occasionally reach my pinky too far and hit plastic instead of a key, so maybe having the function keys in the space where that plastic will be, and functioning just like the S, will actually be helpful.
Steve Kosmata started doing a cool thing where he posts a short video once a week about stuff you can do in Eclipse; that's what inspired me to take a look at my most frequently used three-stroke words, although I had seen the suggestion to do that before. Last week he brought up the old "conflicts for not having to write puncutation" idea, which I'd also seen kicked around, but I just didn't want to get into it.
In the video, he mentioned using it for words that typically have a comma when they start a sentence - therefore, so, oh, etc. I didn't want to get *too* into it, but those seemed like they might work, so I sat down for an hour and a half or so and played around with it. It turned out to be a bigger project than I was expecting. There are so many words like that, and they could come at the beginning, middle, or end of the sentence, so you might need a comma before, after, before and after, or no commas at all.
I experimented with it, and if it didn't seem like it was going to pick correctly 99% of the time, I didn't go all the way with it. A couple of them I was able to do all four choices for; some of them I could only do two; and some of them I wound up tossing out the idea altogether. There are a ton of words I didn't experiment with, so I'm going to tackle one of those a day. Now the hard part is going to be remembering what words I don't have to write commas for, and in what situations I don't have to write the commas. I really haven't picked up on that at all yet, but I only put things in a couple days ago.
I also changed the function keys on my IE to act like S, so hopefully that will cut down on untrans from accidentally hitting them when I mean to hit S. I wanted to use them for speaker IDs, but it's just a project I don't want to start right now. On the LS, I used to occasionally reach my pinky too far and hit plastic instead of a key, so maybe having the function keys in the space where that plastic will be, and functioning just like the S, will actually be helpful.
Learn Your Software
I've learned some pretty cool stuff from the Eclipse FB group. I strongly recommend checking it out if you're on Eclipse. I also watched the full 8 hours of Eclipse basic training tutorials (bo-ring!). It was mostly about title pages and auto indexing and stuff I don't use, or stuff I already know how to do, but I did pick up a couple ideas.
I have a stroke that takes me to the bottom of my realtime feed/has me follow it, and it was always bad when I forgot to hit that after I scrolled up to look at something. But I found out about the "follow always" checkbox in the realtime tab, and now that's not a problem anymore.
I learned that you can make conflicts if you want a certain thing to happen after a number. I use P-KT for % and PER/KRENT for percent, but sometimes it's so much easier to hit P-KT, that I just don't get PER/KRENT in there. I think I've got it set up now that I can write "a large P-KT" or something and it will come up "a large percent," so that's cool. I've been trying to see new opportunities for conflicts overall. Sometimes I miss the F in I've (AO*IV) and get "aye," but why not make it a conflict with the first choice being "aye"? Just today I changed YO*U from ewe to \ewe\you're, because I miss that R so often.
The best idea I got from the FB group was about suffixes. I think someone just said something about their suffix rules table, and it reminded me about how I keep getting things like "organizationtion" when I accidentally drag an extra G into ORGS/S, making it ORGS/GS. So I made a rule that when the word ends in -tion, the suffix should delete the -tion and add an -s, and voila! ORGS/GS is organizations now, and I won't get orientationtion or objectiontion or anything like that, either.
I've come up with tons of applications for that now that I've realized I can do it. No more defectiveive if I already tucked the V and forgot about it (DE/F*EFKT/IV), no more passageage if I got confused and did PAJ/AJ, no more strategicically, or longerer if I didn't realize I tucked the R (LORNG/ER). I don't think -tor was in there as a real suffix; it was in my dictionary, but it wasn't in the suffix table, so it didn't have any suffix rules. I kept getting things like compacttor and reacttor because instead of RE/AK/TOR, I'd write RAEKT/TOR.
But I fixed that rule, so it works for -tor and -tors. And I was getting things like "humorral," so I told it if you're going to add -ral and the word already ends in "r," delete the first "r." I feel like someone who does realtime already has all these suffixes in their suffix table and suffix spelling rules, and I must've missed out on them in an update or something. I should ask on depoman or the FB group for someone's tables, but I'm afraid it might mess things up. I don't see how it could, though, really; it would only change the suffixes in English. It wouldn't have anything to do with my steno outlines. I guess I'd just have to make sure all the things I've changed were still in there.
I also changed my background color from white to gray. Someone on the FB group said it's easier on the eyes. I've heard stuff like that before, but I never really thought about actually changing it until I saw it there. I really do like it better.
I have a ton of different settings files I use for different companies, so it's a pain to change suffix tables or whatever in all of them. I asked about it on FB, and Dave Stanley said that I could just have a global.set that all settings would use for certain things. It seemed like a great idea, except that it overwrites your realtime settings if you let it change your translation settings. It also overwrites your job dictionaries no matter what you do, which is a drag.
I learned how to finally get TM to stop messing with my stroke for "a," which is awesome. I told it to stop pulling "an" and "everyone" into other words, too. I actually turned TM up a bit. The new sliders are kind of confusing, but I understand them now. My main problem was that TM wasn't being aggressive enough; there were tons of words it just left alone. So I unchecked "require an untran," and I bumped it up from whatever it was at (it might've been as low as 1%) to 30%, and I think it's doing better now.
I found out there's a dictionary entry you can use to reject the last AB suggestion and get a new one all at once, and I also found a macro for requesting a brief for the last word, which I think will come in handy.
I have a stroke that takes me to the bottom of my realtime feed/has me follow it, and it was always bad when I forgot to hit that after I scrolled up to look at something. But I found out about the "follow always" checkbox in the realtime tab, and now that's not a problem anymore.
I learned that you can make conflicts if you want a certain thing to happen after a number. I use P-KT for % and PER/KRENT for percent, but sometimes it's so much easier to hit P-KT, that I just don't get PER/KRENT in there. I think I've got it set up now that I can write "a large P-KT" or something and it will come up "a large percent," so that's cool. I've been trying to see new opportunities for conflicts overall. Sometimes I miss the F in I've (AO*IV) and get "aye," but why not make it a conflict with the first choice being "aye"? Just today I changed YO*U from ewe to \ewe\you're, because I miss that R so often.
The best idea I got from the FB group was about suffixes. I think someone just said something about their suffix rules table, and it reminded me about how I keep getting things like "organizationtion" when I accidentally drag an extra G into ORGS/S, making it ORGS/GS. So I made a rule that when the word ends in -tion, the suffix should delete the -tion and add an -s, and voila! ORGS/GS is organizations now, and I won't get orientationtion or objectiontion or anything like that, either.
I've come up with tons of applications for that now that I've realized I can do it. No more defectiveive if I already tucked the V and forgot about it (DE/F*EFKT/IV), no more passageage if I got confused and did PAJ/AJ, no more strategicically, or longerer if I didn't realize I tucked the R (LORNG/ER). I don't think -tor was in there as a real suffix; it was in my dictionary, but it wasn't in the suffix table, so it didn't have any suffix rules. I kept getting things like compacttor and reacttor because instead of RE/AK/TOR, I'd write RAEKT/TOR.
But I fixed that rule, so it works for -tor and -tors. And I was getting things like "humorral," so I told it if you're going to add -ral and the word already ends in "r," delete the first "r." I feel like someone who does realtime already has all these suffixes in their suffix table and suffix spelling rules, and I must've missed out on them in an update or something. I should ask on depoman or the FB group for someone's tables, but I'm afraid it might mess things up. I don't see how it could, though, really; it would only change the suffixes in English. It wouldn't have anything to do with my steno outlines. I guess I'd just have to make sure all the things I've changed were still in there.
I also changed my background color from white to gray. Someone on the FB group said it's easier on the eyes. I've heard stuff like that before, but I never really thought about actually changing it until I saw it there. I really do like it better.
I have a ton of different settings files I use for different companies, so it's a pain to change suffix tables or whatever in all of them. I asked about it on FB, and Dave Stanley said that I could just have a global.set that all settings would use for certain things. It seemed like a great idea, except that it overwrites your realtime settings if you let it change your translation settings. It also overwrites your job dictionaries no matter what you do, which is a drag.
I learned how to finally get TM to stop messing with my stroke for "a," which is awesome. I told it to stop pulling "an" and "everyone" into other words, too. I actually turned TM up a bit. The new sliders are kind of confusing, but I understand them now. My main problem was that TM wasn't being aggressive enough; there were tons of words it just left alone. So I unchecked "require an untran," and I bumped it up from whatever it was at (it might've been as low as 1%) to 30%, and I think it's doing better now.
I found out there's a dictionary entry you can use to reject the last AB suggestion and get a new one all at once, and I also found a macro for requesting a brief for the last word, which I think will come in handy.
7.28.13
I struck out at the EMG test, which I guess was a good thing. The neurologist doesn't think it's carpal tunnel or a pinched nerve. He said he'd "think about it" and I should wear the wrist brace at night for three weeks and then come back and see if he came up with any new ideas. I don't think I'm going to pay to make that happen. I scheduled a PT appointment for this week, so we'll see how that goes. The neurologist also wrote me a prescription to try Topamax, but I haven't gotten it filled yet.
I've been having a good streak where I remember things that have given me trouble in the past, like TS and DZ, and remember to write them out in two strokes during realtime practice. I'm doing the same thing with words that are conflicts the "normal" way I would think to write them; nothing as simple as plague/playing, but that's the idea. I just have a general feeling that I shouldn't write it the easy way. I don't remember why right then, but it pays off. Before I would just kind of be stubborn about it and write it the easy way anyway, and then have to scramble to try to fix it.
I've had a small epiphany (can that be a thing?) about numbers, too, and I'm writing them one at a time more instead of garbling them. 12 is *really* difficult for me to write with my hand the way it is, and I realized I can just write it in two strokes, with much less chance of misstroking it.
I got Pyongyang right twice during practice today (without getting it wrong, to boot). I write it out a long way: PAOE/YONG/YANG. It's hard to start. It's almost like I want to bolt whenever I have to write it. But it's not so bad once I actually do it. I also fingerspelled a lot of names in practice today; some I knew right away weren't in there and fingerspelled the whole thing, like Lindy Boggs. Others I tried to do first (Pedro Vargas) and wound up fingerspelling them after they didn't come out right. I always do a thing where I think "I have -da defined, so I can just write Brunda, that'll come out fine."
My writing is really stilted with my hand being messed up, though. I wind up with a lot of dashes in the transcript that aren't preceeded by any mistakes. I just get lost and things start to feel wrong and I might hit one wrong letter and erase it, and then dash. At least I can pull it together and do it without dropping anything. Sometimes I don't catch the mistakes, though, and I wind up just hitting an S before writing SRAR, or hitting an N after writing something with N in it. I've got an average of 98.56% accuracy for my last five practice shows, though, so I'm keeping it together pretty well.
Words that end in -nal weren't coming out right, even though I don't think I've changed anything from theory (I just do NAL), so I re-wrote all 472 of those. I also wanted to start doing -tary with an asterisk to avoid any conflicts with tear, so I fixed 145 of those entries.
I've been having a good streak where I remember things that have given me trouble in the past, like TS and DZ, and remember to write them out in two strokes during realtime practice. I'm doing the same thing with words that are conflicts the "normal" way I would think to write them; nothing as simple as plague/playing, but that's the idea. I just have a general feeling that I shouldn't write it the easy way. I don't remember why right then, but it pays off. Before I would just kind of be stubborn about it and write it the easy way anyway, and then have to scramble to try to fix it.
I've had a small epiphany (can that be a thing?) about numbers, too, and I'm writing them one at a time more instead of garbling them. 12 is *really* difficult for me to write with my hand the way it is, and I realized I can just write it in two strokes, with much less chance of misstroking it.
I got Pyongyang right twice during practice today (without getting it wrong, to boot). I write it out a long way: PAOE/YONG/YANG. It's hard to start. It's almost like I want to bolt whenever I have to write it. But it's not so bad once I actually do it. I also fingerspelled a lot of names in practice today; some I knew right away weren't in there and fingerspelled the whole thing, like Lindy Boggs. Others I tried to do first (Pedro Vargas) and wound up fingerspelling them after they didn't come out right. I always do a thing where I think "I have -da defined, so I can just write Brunda, that'll come out fine."
My writing is really stilted with my hand being messed up, though. I wind up with a lot of dashes in the transcript that aren't preceeded by any mistakes. I just get lost and things start to feel wrong and I might hit one wrong letter and erase it, and then dash. At least I can pull it together and do it without dropping anything. Sometimes I don't catch the mistakes, though, and I wind up just hitting an S before writing SRAR, or hitting an N after writing something with N in it. I've got an average of 98.56% accuracy for my last five practice shows, though, so I'm keeping it together pretty well.
Words that end in -nal weren't coming out right, even though I don't think I've changed anything from theory (I just do NAL), so I re-wrote all 472 of those. I also wanted to start doing -tary with an asterisk to avoid any conflicts with tear, so I fixed 145 of those entries.
Practice and Theory
I'm
still having major problems with my dictionary. So many conflicts are
caused by the StenEd theory. I'm still working to get an asterisk in
every word ending that's also a standalone word - Nate, Kate, date,
nation, etc. It really helps to see my mistakes live as I make them,
though. Previously, after every take I would go through and check my
mistakes, and make note of words I wanted to practice. But it's
different when you're trying to write "live" and you actually see the
mistake come up. It has much more of an effect, and I'm more likely to
remember next time I write it that I need to write it differently,
because I don't want that mistake to happen again.
I'm also writing a larger volume of material now, because I only write a show once and move on. I don't repeat the same show over and over for weeks, or even twice. Seeing just how many words are coming up incorrectly solely because they're not in my dictionary the way I want to write them has made me feel like I need to just go through the whole dictionary and re-write every word to make sure it's going to come out right. I keep a record every show of how many of those "wrote it right but it wasn't in my dictionary that way" words there are, and after 32 shows, I've got an average of .32% right now. It's not horrendous, but it seems like it should be a lot closer to zero.
I've been at the process of re-writing all the words in my dictionary for about 6 weeks now, and I've made it through 7,000 entries. Only a year left to go before it's done at that rate!
I've developed an entirely new theory on defining conflicts. I now define a lot of misstrokes as conflicts. I figure, if it was only going to be defined as "fun" before, what's the harm in having the AI choose between "fun" and "gun" since what I wrote wasn't the correct outline for anything, let alone "fun" or "gun," in the first place?
I am staying away from defining correct outlines as conflicts, though, and trying to come up with different ways of writing things instead. I occasionally stack "N" and "A," like with "taken a," so I'm trying to write "A*N" for "an," but it's not sticking at all. I even write five sentences every day with "an" in them, and most of the time I can remember the asterisk when I write the sentences, but it's been months, and I haven't written it properly once during the news.
Instead of my old practice of going through a take and re-writing each incorrect word five times (that took forever), now I just try to remember as I go through and count errors/make dictionary entries, to also think about whether or not I need to practice that word more. If I do, I add it to a list. I have a list of 58 words I write five times each at the beginning of each practice session. I keep a record of when I added them to that list, and make sure I write them for at least five sessions before I take them off, although I often leave them on for longer. As words get deleted from that list, I add new ones that I found while writing the news.
There are all sorts of words on the list, from names that were hard to write (Ezekiel Emanuel) and new ways of trying to write things (MEN/TO*R, since TOR is a beginning for words like "torment"), to old ways of writing things that I still haven't quite gotten the hang of (EN/M*I so words like it won't conflict with "my"). It seems like an insurmountable task right now to get everything squared away in my dictionary and in my memory, but I guess I'll get there someday if I keep plugging away at it.
I'm still practicing two drills in the Phoenix book at the beginning of every practice session, and my average wpm on all of them is up to 178.5. It's been stuck there for a few weeks for some reason. I think having that cushion to drop words during the news (which I only do when I have to, of course) might be interfering with what little speedbuilding rhythm I had going. Whenever I get discouraged with it, though, I can look back to when I started using the book a year and a half ago, and my average was only 115 wpm. I am improving, whether it seems like it or not.
In support of my theory that I need to re-write all the words in my dictionary, is one particular word: Demetrius. I had it defined 15 different ways, and not one of them was the way I would write it today. I was originally going to identify word groups that I write differently, such as words that end in "cy" or "gy," and re-write only those groups as I identified them. I realized, though, that the problem was much larger than that. Before that, though, I fixed 60 "-cy" entries, 260 for "-gy," and 160 for "-ta," which I now write with an asterisk.
I also had about 1,000 entries ending in "ly" that I had defined with a tucked -L, but that I would never write. Those were causing lots of problems when I misstroked the -L in a word, so I spent some time getting rid of them. And I finally fixed my "di-" so it wasn't the same as my "-dy," but darned if I can remember to write it that way yet.
I'm also writing a larger volume of material now, because I only write a show once and move on. I don't repeat the same show over and over for weeks, or even twice. Seeing just how many words are coming up incorrectly solely because they're not in my dictionary the way I want to write them has made me feel like I need to just go through the whole dictionary and re-write every word to make sure it's going to come out right. I keep a record every show of how many of those "wrote it right but it wasn't in my dictionary that way" words there are, and after 32 shows, I've got an average of .32% right now. It's not horrendous, but it seems like it should be a lot closer to zero.
I've been at the process of re-writing all the words in my dictionary for about 6 weeks now, and I've made it through 7,000 entries. Only a year left to go before it's done at that rate!
I've developed an entirely new theory on defining conflicts. I now define a lot of misstrokes as conflicts. I figure, if it was only going to be defined as "fun" before, what's the harm in having the AI choose between "fun" and "gun" since what I wrote wasn't the correct outline for anything, let alone "fun" or "gun," in the first place?
I am staying away from defining correct outlines as conflicts, though, and trying to come up with different ways of writing things instead. I occasionally stack "N" and "A," like with "taken a," so I'm trying to write "A*N" for "an," but it's not sticking at all. I even write five sentences every day with "an" in them, and most of the time I can remember the asterisk when I write the sentences, but it's been months, and I haven't written it properly once during the news.
Instead of my old practice of going through a take and re-writing each incorrect word five times (that took forever), now I just try to remember as I go through and count errors/make dictionary entries, to also think about whether or not I need to practice that word more. If I do, I add it to a list. I have a list of 58 words I write five times each at the beginning of each practice session. I keep a record of when I added them to that list, and make sure I write them for at least five sessions before I take them off, although I often leave them on for longer. As words get deleted from that list, I add new ones that I found while writing the news.
There are all sorts of words on the list, from names that were hard to write (Ezekiel Emanuel) and new ways of trying to write things (MEN/TO*R, since TOR is a beginning for words like "torment"), to old ways of writing things that I still haven't quite gotten the hang of (EN/M*I so words like it won't conflict with "my"). It seems like an insurmountable task right now to get everything squared away in my dictionary and in my memory, but I guess I'll get there someday if I keep plugging away at it.
I'm still practicing two drills in the Phoenix book at the beginning of every practice session, and my average wpm on all of them is up to 178.5. It's been stuck there for a few weeks for some reason. I think having that cushion to drop words during the news (which I only do when I have to, of course) might be interfering with what little speedbuilding rhythm I had going. Whenever I get discouraged with it, though, I can look back to when I started using the book a year and a half ago, and my average was only 115 wpm. I am improving, whether it seems like it or not.
In support of my theory that I need to re-write all the words in my dictionary, is one particular word: Demetrius. I had it defined 15 different ways, and not one of them was the way I would write it today. I was originally going to identify word groups that I write differently, such as words that end in "cy" or "gy," and re-write only those groups as I identified them. I realized, though, that the problem was much larger than that. Before that, though, I fixed 60 "-cy" entries, 260 for "-gy," and 160 for "-ta," which I now write with an asterisk.
I also had about 1,000 entries ending in "ly" that I had defined with a tucked -L, but that I would never write. Those were causing lots of problems when I misstroked the -L in a word, so I spent some time getting rid of them. And I finally fixed my "di-" so it wasn't the same as my "-dy," but darned if I can remember to write it that way yet.
Finally, another big list of all the word endings
I went through and added asterisks to: –rat, -lator, -seen, -lent, -tor,
-clear, -tha, -sell, -cell, -mist, -gan, -trick, -dance, -phone, ax-, -con, -YOU, -el, -tel,
-tal, -don, -lop, -ger, -yam, -mat, –ture, -tin, -ten, -ron, -ster, -band,
-kate, -nate, -yum, -date, -late, -tize, and -ual (yule).
Back
Long time no post, again. I've still been plugging away with my two hours of practice every day. I kept up with my routine of using the actual live news for my speedbuilding practice until June, when I started doing the Caption Masters Series. I didn't exactly test into it, I just signed up for it, figuring I was probably good enough to do it. That's been true in some senses; I don't have any trouble at all keeping up with the homework, but I have yet to pass a test. You have to get 98.5% accuracy first-pass on live broadcasts, and I'm not quite there yet.
So far I've practiced the news and the weather. I can occasionally get a 5-7-minute weather segment at 98.5% accuracy on the first try, which is pretty cool. The teacher suggested we use "smart writing," which involves dropping adjectives and other things that might not be super important if it keeps us from dropping things that are important. It's been pretty effective. On the one hand, it's easier because you don't have to write things verbatim; on the other hand, it's harder because it adds an extra level of things you're thinking about the whole time. "What phrase wasn't important? What don't I have to write? How could I paraphrase that to make it quicker?" Of course, verbatim is always your ultimate goal. But it's more important to convey everything loosely than to convey half of it verbatim. Unfortunately, it's a strategy that's going to work against me whenever I take the CBC exam.
I don't use the tripod anymore. I felt like I couldn't reach the machine, so I went back to putting it on my lap. I just use a little leather portfolio folder to give it about 3/4 of an inch of extra height and keep it flat. That seems to be working out okay. I still feel like I'm a little shaky 75% of the time in terms of "finding" the keys, but I'm doing a lot better in that area than I was before.
I have a ton of free time to do steno stuff now, but I don't do it. I did spend about an hour working on a list of 30 "to-do" items I had come up with in the past few months, though. Here's what I fixed:
-Defined "out-" as "O*UT," yet I still had ~50 words in my dictionary defined like RAED/O*UT.
-Finally went into my pre/suf table and deleted all the StenoMaster stuff I don't actually use - the integrated -able, -en, -ful, -ive, -ize, -ment, -ness, dis-, and -ly. Hopefully that will result in TM suggesting fewer of those, although I've already got so many defined it's kind of a mess.
-Deleted 300 entries I made using "DZ" for "-ing."
-Fixed problematic word endings with -lick, -rat, -line, -rid, -rig, -man/-men, -woman/-women, -ard, -son, and -gan.
-Updated my "ego-" to AOEG.
-Updated "TAIR" to "TA*IR" in 100 words.
-Decided to do LAM/NAIT, etc. and NA*IT for Nate; COMP/KAIT, etc., and KA*IT for Kate
-Finally got around to changing all 113 of my leftover "nk" words from "*NG" to "FRNG"
I came up with a couple more things to fix after I did that. I also just started defining conflicts. I think I've stayed away from them all this time because I didn't want to take the time to sit down and train the AI. But I defined one, and it picked up on it almost immediately, so I thought, what better time to work out the kinks than when no one can see them?
So far I've practiced the news and the weather. I can occasionally get a 5-7-minute weather segment at 98.5% accuracy on the first try, which is pretty cool. The teacher suggested we use "smart writing," which involves dropping adjectives and other things that might not be super important if it keeps us from dropping things that are important. It's been pretty effective. On the one hand, it's easier because you don't have to write things verbatim; on the other hand, it's harder because it adds an extra level of things you're thinking about the whole time. "What phrase wasn't important? What don't I have to write? How could I paraphrase that to make it quicker?" Of course, verbatim is always your ultimate goal. But it's more important to convey everything loosely than to convey half of it verbatim. Unfortunately, it's a strategy that's going to work against me whenever I take the CBC exam.
I don't use the tripod anymore. I felt like I couldn't reach the machine, so I went back to putting it on my lap. I just use a little leather portfolio folder to give it about 3/4 of an inch of extra height and keep it flat. That seems to be working out okay. I still feel like I'm a little shaky 75% of the time in terms of "finding" the keys, but I'm doing a lot better in that area than I was before.
I have a ton of free time to do steno stuff now, but I don't do it. I did spend about an hour working on a list of 30 "to-do" items I had come up with in the past few months, though. Here's what I fixed:
-Defined "out-" as "O*UT," yet I still had ~50 words in my dictionary defined like RAED/O*UT.
-Finally went into my pre/suf table and deleted all the StenoMaster stuff I don't actually use - the integrated -able, -en, -ful, -ive, -ize, -ment, -ness, dis-, and -ly. Hopefully that will result in TM suggesting fewer of those, although I've already got so many defined it's kind of a mess.
-Deleted 300 entries I made using "DZ" for "-ing."
-Fixed problematic word endings with -lick, -rat, -line, -rid, -rig, -man/-men, -woman/-women, -ard, -son, and -gan.
-Updated my "ego-" to AOEG.
-Updated "TAIR" to "TA*IR" in 100 words.
-Decided to do LAM/NAIT, etc. and NA*IT for Nate; COMP/KAIT, etc., and KA*IT for Kate
-Finally got around to changing all 113 of my leftover "nk" words from "*NG" to "FRNG"
I came up with a couple more things to fix after I did that. I also just started defining conflicts. I think I've stayed away from them all this time because I didn't want to take the time to sit down and train the AI. But I defined one, and it picked up on it almost immediately, so I thought, what better time to work out the kinks than when no one can see them?
1.05.12
It's been a while since I updated. I'm still liking the tripod with my LS. I'd like to move away from it and go to a lapdesk at some point, but that's down the road when I've perfected my positioning. I think I'm making progress on that front, but it's definitely not dialed in yet. I've been working on my sitting posture, starting with getting comfortable in the legs and back, and adjusting everything else from there, on a daily basis. The past couple of days it's worked out pretty well.
I got probably about 3 minutes into my last piece, and then I was ready to try out a new strategy I've been planning to start for a while. I completely abandoned the speed "tapes." The VITAC book suggests recording national news and practicing to that, and that seems like a pretty solid strategy. I really need practice writing spontaneously, and it's great for practicing a variety of names and terms instead of the same ones for two months at a time.
The book suggests breaking the episode up into each individual story. First you listen to it in its entirity, and write down/practice any words you think might trip you up. I always come up with an alarming number of them, way more than I feel like I should have at this point. I've tweaked my theory so much though, I just don't have any of it in my muscle memory at all. Which is why I'm also going back through my theory book. That's something I've been trying to do for a long time, but I let myself get sidetracked with dictionary maintenance.
Speaking of which, I got a lot done there. I finished all of my P and B inflected endings, and did 2-3 other things that I don't remember anymore. I have yet more I need to do, but I'm going to try to do that during non-practice time.
After you run through the story without writing anything, you write the introduction alone until you've got it perfect, then the story, then the follow-up. It's awesome not having people blazing along at a constant 250 wpm anymore! I don't pick it up nearly as fast as I should; sometimes it takes me 2-3 hours just to get a 3 minute segment. But hopefully, you can't go wrong practicing at real speeds.
I'm up to at least 130 wpm on all of my Phoenix drills, with an average speed of 150. I've been using the drill book for 30 weeks so far. Only another 30 to go if I keep up at this rate..
For those of you following along, perhaps in your own dictionaries, here are the rest of the possible word-boundary errors I've fixed.
Final word parts:
light, ground, long, box, fish, hound, fight, shot, saw, bag, book, cuff, cap, string, sick, strong, break, sight, knife, pot, sake, proof, seed, spring, hood, cure, night, week, stop, pick, suit, shop, coat, drop, sack, paper, track, bite, lash, pipe, place, berry, play, lance, piece, field, spread, bug, bird, port, pit, beat, wood, weight, word, guard, bed
Instances that only affected one word:
heartthrob, hedgehog, henpeck, hitchhike, hoodwink, inkblot, ironclad, jackhammer, landlord, livestock, mankind, nightclub, paycheck, pinstripe, shoptalk, skyrocket, smokestack, spendthrift, sunroof, wisecrack, carefree, shipshape, sideswipe, switchblade, bedfellow, bellhop, jailbait, kidnap, netherworld, nosebleed, postpaid, postscript, snowplow, stopgap, teacup, wastebasket, watchdog, waterspout, wiretap, shopworn
I discovered that I was writing "fore-" and "fore" the same way (thanks StenEd), but I don't think I'm going to fix it. I also had a lot of problems with words that start with "up" (uphold, uphill, etc) and "air" (aircraft, airstrike, etc).
11.11
I got my new minute already. I really liked the strategy of starting at a slower speed. I think what worked for me was telling myself I wasn't allowed to move on until I was "comfortable" writing it, as opposed to just shooting for 95% accuracy. The minute was also only at 220 wpm, which is the speed RTC claims the entire piece is, and the speed at which I actually want to practice.
I decided to try getting a tripod for the LS, and today was the first time I used it. It was actually really nice not having to balance anything on my lap. It felt much more sturdy that way, and I think it's going to work out.
I have another list of potential word-boundary conflicts: cast, going, grade, heart, ward, stream, wind, bridge, found, wax, bound, rail, nail, comb, fill, hole, room, pile, mill, fare, house, made, and bulb. And there were a few words that only presented problems in one instance: printwheel, standstill, and handshake. I can't believe anyone would have STAND\STIL defined as one word! There were a lot of instances for "-house" and "-room" especially. I also changed "board" to BAORD a while ago, but I never went back and put asterisks in for "-board" or even fixed all instances of BORD, apparently, so I took care of that.
When I got to "-nk" in the Phoenix drills, I realized I never practiced doing FRNG instead of *NG. I started trying to think of the finger formation as "-nk" instead of thinking of words as, for example, DRAFRNG. That's what you're always supposed to do, but there are a lot of instances where I never quite got there. PB I think of as N, of course, and TK as D, etc., but for a lot of the other stuff, like IFM for "-ism," I'm still thinking "IFM." "-nk" words were dramatically easier to stroke once I started thinking of the position instead of the keys, so hopefully I can apply that to other aspects as well.
I decided to try getting a tripod for the LS, and today was the first time I used it. It was actually really nice not having to balance anything on my lap. It felt much more sturdy that way, and I think it's going to work out.
I have another list of potential word-boundary conflicts: cast, going, grade, heart, ward, stream, wind, bridge, found, wax, bound, rail, nail, comb, fill, hole, room, pile, mill, fare, house, made, and bulb. And there were a few words that only presented problems in one instance: printwheel, standstill, and handshake. I can't believe anyone would have STAND\STIL defined as one word! There were a lot of instances for "-house" and "-room" especially. I also changed "board" to BAORD a while ago, but I never went back and put asterisks in for "-board" or even fixed all instances of BORD, apparently, so I took care of that.
When I got to "-nk" in the Phoenix drills, I realized I never practiced doing FRNG instead of *NG. I started trying to think of the finger formation as "-nk" instead of thinking of words as, for example, DRAFRNG. That's what you're always supposed to do, but there are a lot of instances where I never quite got there. PB I think of as N, of course, and TK as D, etc., but for a lot of the other stuff, like IFM for "-ism," I'm still thinking "IFM." "-nk" words were dramatically easier to stroke once I started thinking of the position instead of the keys, so hopefully I can apply that to other aspects as well.
11.6
I finally got the two minutes together that I was working on. It only took me 7 weeks. Way longer than it should have, but I just can't get the positioning right. It's like when you type on someone else's keyboard. On your keyboard, you can type 100 wpm. On an unfamiliar keyboard, suddenly you're knocked down to 60. I feel like I've been writing on someone else's steno machine for the past 8 months, and it hasn't gotten any more familiar than it was on the very first day.
I decided to go back to my old teacher's strategy of speedbuilding: learn the minute at a slow speed, then bump it up a speed until you're comfortable with that, and then bump it up one last time to your goal speed. I don't know what kind of progress I'll make with that strategy, but for now I'm liking writing at 180 wpm.
I'm down to 8,440 entries with "B" in them that might need inflected endings added. I figured out a lot of ways to weed out things that weren't verbs, like looking at words that end in "y" or "s" or whatnot. I've also continued finding word parts that need to be asterisked: bone, stroke, nose, son, late, lock, hand, time, foot, wear, print, note, step, land, head, walk, and hold.
I ran into particularly tedious problems with "out-" and "sub-". The old StenEd "out-" is O*UT, which is my "-out," so I had to move the asterisks in those outlines from the first stroke to the second one. I don't like the idea of "sub" and "sub-" being the same outline, so I had to add an asterisk to all the strokes that come after "sub-" (or at least the ones that are words on their own), like "submarine" and whatnot.
I decided to go back to my old teacher's strategy of speedbuilding: learn the minute at a slow speed, then bump it up a speed until you're comfortable with that, and then bump it up one last time to your goal speed. I don't know what kind of progress I'll make with that strategy, but for now I'm liking writing at 180 wpm.
I'm down to 8,440 entries with "B" in them that might need inflected endings added. I figured out a lot of ways to weed out things that weren't verbs, like looking at words that end in "y" or "s" or whatnot. I've also continued finding word parts that need to be asterisked: bone, stroke, nose, son, late, lock, hand, time, foot, wear, print, note, step, land, head, walk, and hold.
I ran into particularly tedious problems with "out-" and "sub-". The old StenEd "out-" is O*UT, which is my "-out," so I had to move the asterisks in those outlines from the first stroke to the second one. I don't like the idea of "sub" and "sub-" being the same outline, so I had to add an asterisk to all the strokes that come after "sub-" (or at least the ones that are words on their own), like "submarine" and whatnot.
10.23
Looking through every dictionary with B in it is turning out to be more useful than I thought. I'm discovering a lot of potential word boundary conflicts. So far, I've come up with -log, -list, -lift, -top, -mark, -stick, -plate, -rack, -store, -worm, -dock, and -neck. I also had to figure out a way to distinguish between "ball," -bal, and -ball. I was already doing BA*UL for -ball since I discovered a problem with that a long time ago, but I had never actually changed the dictionary entries to reflect it! I wound up doing BAL for "ball" and B*AL for -bal, so the only part I have to try to remember is B*AL.
I still have 35k entries to go through, but at least I feel like I'm doing a little more than just getting in a few inflected endings a day.
10.16
I'm trying out something new with the Report-It: focusing on my wrists. Trying to make them straight instead of tilted down. So far I can either get into a position where my shoulders/arms are comfortable, or I can get into one where I can actually stroke the keys, but not both at the same time. Someday.
I got all of my drill speeds up to 120, and my average drill speed is now 140. I also spent about two and a half hours going through my dictionary and deleting all the briefs for phrases that I didn't even know were in there, because I never learned them. They just came pre-loaded on the StenEd dictionary. I wound up deleting 2400 (or actually, moving them out of my dictionary into their own dictionary, since I'm trying to remember not to actually "delete" anything anymore).
While I was doing that, I discovered some more things that could have been word boundary problems. I found some phrases like "bill folded" that made me wonder if BIL/FOELD was defined as "billfold," and, in fact, it was. I wound up fixing issues with -fold, -rest, -watch, and -end. I also realized I was using the same stroke for fer- and -fer, and in fixing that I also fixed -vent and -tile. I'm trying to remember to asterisk any word ending that's also a word on its own.
My next big project is to go through all the entries in my dictionary that have B and/or P in them and add inflected endings to the verbs. Eclipse 5 has the awsome feature of automatically translating your integral prefixes and stuffixes, which is great except in the case of N. NG and ND cause way too many conflicts, so I don't want them to be automatically translated, which means I can't have BG/BD or PG/PD in the table, either, and I'll have to manually enter all of those.
I've got 45k entries with B in them, and I only knocked out 4500 in my first go at it today, so I'm not going to be moving on anytime soon.
StenEd: Y U No Be Conflict-Free?
I've hit a major roadblock in my speedbuilding, and it's really starting to become aggravating. I haven't made any progress in a whole year. I'm supposed to have been "graduated" by now! Ugh. All I can do is keep plugging away at it, I guess. I don't know what the big problem is with this 2-minute section, though. It's really starting to lose all meaning at this point.
I did finally accomplish something, though: I made it through the list of conflict-finding sentences! At first I was just going through it and if the sentence didn't produce a conflict, I moved on. But sometimes that was just because of a particular brief I had. So I took a closer look at what the sentence was trying to show me (that you shouldn't have the same outline for PER-, -PER and PER, for example) and made sure I wouldn't have any conflicts in any situation, not just the one presented by the sentence.
I discovered a lot of flaws in my own personal theory, and in StenEd, the above example being one of them. At the end of the exercise, I had a problem with: -con, -ran, -less, -fin, -den, -mine, -lean, -net, -lent, -rise, -set, -let, -size, -sit, -stance, -ate, -wait, -pal, -lay, -nut, -plain, -lies, -man, -jer, -win, est-, -til, -mit, Ron-, and -ster. A lot of them are easy fixes, like adding an asterisk to the word part and leaving the actual words as they are, and I didn't have to change a huge amount of entries. However, there were some word parts that took more work. They were, with number of entries I had to fix: -tic/tic/tick (200), -cal/cal/-cal (345), ter/-ter (277), -rate (113), -ton (115), and -ship (92).
Tick/tic/-tic was particularly problematic. TIK for tick, obviously, and T*IK for tic, but I couldn't do T-K for -tic because that's my "it can." So I went with T*K. The real problem is going to be remembering my resolutions for all of this stuff. Why couldn't StenEd have just actually been a conflict-free realtime theory, instead of being one "most of the time"?
With all the stuff I had to fix, I was beginning to think I should've just left the asterisks in all of my ending word parts, because now I have to try to remember which ones have asterisks and which ones don't. I tried to delete the vowels or do something other than just add an asterisk to make it easier to remember. Hopefully the number of ones I wound up just doing asterisks for is going to be small enough that I can learn them without inducing massive amounts of hesitation.
I also spent about half an hour going through all of my capitalized entries and forcing literal case on names like "De Niro." I already had most of them done, but I wanted to make sure I hadn't missed any and it would all be consistent.
7.24
I made it through three sections of the VITAC book in one day. One was about homephones, which I pretty much had worked out already from StenEd. The next was prefixes and suffixes, and luckily there aren’t that many in the VITAC book. I did skip a few, and there are a few I still need to learn. I spent most of the time in that section on the "medical and technical" ones. The last section was 25 pages of words that might create conflicts. Going through that wasn’t any fun at all.
I think I might have found a good position for the BackJoy and the Report-It and everything. It’s not perfect, so I’m still tweaking it, but maybe someday soon I won’t feel like I’m fighting to hit the right keys anymore. I got my last minute on Wednesday, and I got that one and the one before it together yesterday at 96.5% accuracy. The new minute doesn’t seem too hard, and it’s at 230 wpm.
Subscribe to:
Posts (Atom)