There was a post on the Eclipse FB group about being able to search the transcript for times when multiple words had been deleted, in order to help find things that needed to be globalled/worked on. It hadn't ever occurred to me before, but Julie pointed out that you could just search for the steno **. Duh! I started doing it a couple days ago, and it's been absolutely amazing.
It takes me five or six times longer to scan through a transcript now, but I'm also finding (and fixing) five or six times more mistakes than before, so it's worth it. It makes it really easy to see mistakes that you make repeatedly, and it's also easier to pick out patterns with stacking or splitting. I'm getting a *lot* more splitting than I was aware of. When I was writing and something would come out wrong, I wouldn't necessarily know why at the time, but I figured the most likely reason was that I stroked or missed an extra key. It turns out a lot of it is splitting!
I think there are lots of settings I can adjust on the IE to address splitting. One that I know about is minLR. I had tried to adjust it down to fix stacking, but it never worked, and I started getting noticeable splitting. I've been gradually turning it up every time I recognize splitting, but it turns out there were tons of times when I didn't know it was happening. I've been turning it up more over the past few days, and I think it might be causing more stacking.
I'm interested to really look into all the things I can tweak for splitting and stacking, but I'm going to wait until I get the Gen O. Then I'll call support and have them help me out.
Tons of other things are also coming from searching for double-deletes. It reminds me about words I knew I was consistently misstroking, but never seriously thought about changing, like TEPD. It should be "tend," but it translates as "tepid." Whenever I've seen it before, I thought, "well, it's a valid outline for tepid, so I'm going to leave it." But the odds are good that I would write "tepid" as TEP/ID, anyway, and I know it's come out wrong over and over again when I meant to right "tend," so I finally changed TEPD to "tend" and made T*EPD "tepid."
Another one I did it with was APS for "Annapolis." It's a great brief, and I do IPS for Indianapolis, too, but I frequently get "Annapolis" when I was trying to write "answer." When it happens, I just think "that darn Annapolist again" and delete it, so it doesn't show up in the transcript and I don't think about changing it. But when I found it this time, it didn't take long for me to realize that I should make A*PS "Annapolist" so that APS can just be "answer."
That's the real beauty of it. There are so many mistakes that I erase, so the consumer never sees them, but that means I don't see them to fix them in my dictionary, either. And I certainly don't remember any of them by the time I'm done writing. Another "hidden" thing that I can see now is briefs that I tried, but hadn't entered into my dictionary yet. I knew I had a brief for "Boca Raton," and BO*EK/RA*T made perfect sense, so I stroked it, but that wasn't right. I wrote out "Boca Raton" instead, and I would normally have no way of remembering I should go ahead and enter in BO*EK/RA*T, too. But this way I can see things like that and enter them.
And it's not just for briefs - it works for new ways of writing things that haven't been assigned to all the words yet, like SAIRBL for the "-sational" in sensational. I had really stopped trying to write things the short way, because they never came out right. But now at least if I write them and they're not in my dictionary yet, I'll know I can catch them later and put them in.
I'm also finding tons more words to add to my practice list. It's mostly not words that were difficult to stroke, because I often misstroked those and am able to add the misstroke to my dictionary. But what I am getting is reminders about words that I forget how to write, like "upwards." I could write it as *UP/WARDZ, UP/WA*RDZ, or *UP/WA*RDZ, but because it takes more effort to include the asterisk, the last time I wrote it, I just did UP/WARDZ, which is "up wards." So I put it on my practice list, and hopefully the week of reinforcement will be enough that I reflexively include the asterisk next time. Even though I know it needs to be there, the fact that I didn't put it in and had to back up to re-write it means it needs to be reinforced.
I've already recognized some misstrokes that I make a lot, but always erase, so I never fixed them, and I just keep writing them and having to delete and re-write them all the time, like REP/SHIP for relationship. I found that twice in one transcript, and then REG/SHIP in the next one. As soon as I saw it, I knew it was one that I get wrong all the time, but it never stuck with me long enough to define it.
So now when I edit a transcript for my own improvement (which I do with every event that I write), I follow these steps:
-Do separate searches for glued A and E to find most fingerspelled words
-Search for */*
-Search for untrans and unresolved conflicts
-Spellcheck in Eclipse
-Spellcheck in Word
I could also just search for * and I'm sure I would find even more strokes to fix, but I think correcting things that really tripped me up and forced me to delete multiple strokes is a good starting place for now. I've made 404 entries in three days using that technique!
Showing posts with label Eclipse. Show all posts
Showing posts with label Eclipse. Show all posts
Clean Words
Just in time for my captioning work, Jeremy put up the list of dirty words that you could add to your "words that have been deleted from the spelling dictionary" file. If you don't have a word in your spelling dictionary, the Eclipse AI won't guess it for TM, integrated pre/suf, or anything else. All you had to do was paste the list into your file, and voila. I took an extra step, though; I wanted to text global all the words as {NULL} so they couldn't even possibly be on the screen for captioning.
It would've been a laborious process doing it by hand, but thanks to some playing around that I did for the IE (it's a long story involving importing/exporting dictionaries to use special keyboard layouts, and I don't even think I needed to do it in the first place), I realized that you can export a dictionary, edit it in Word, import it, and make changes that way! So all the times that I've wished I could "find and replace" all instances of something in a dictionary, I actually could have!
I used it to put = {NULL} after all the words, and also to change them to all caps since that's how they're going to look when I'm captioning, and I instantly had dictionary entries for the entire list. And there are some really bad words on that list, so I'm glad I'm protected now.
I also realized that for captioning, you want to have a lowercase "s" with your acronyms; like if they say there were multiple DAs, you don't want that coming out as DAS; it doesn't make any sense. So as I was editing and I noticed letters next to "s," I slowly just defined them with a lock case, but eventually I actually had time to write/define them all. I hadn't missed many, and it turned out to not take that long (I probably should've just done that in the first place, but I thought it would be more time-consuming than it was).
I had 1st defined as "first," which was really annoying. I don't know how that happened, but I definitely fixed it. I've also been defining common phrases like "10 or 15," "10 to 15," and "10 and 15" with the 10 as a numeral, because otherwise it comes out as "ten or 15," and I don't think about it fast enough to use my numeral trigger before the "ten."
According to my list of things I wanted to write about, I also spent some time paying attention to getting things like YA*RD and WI*CK in my dictionary as ^yard and ^wick, but I don't remember about that anymore. Probably a good thing to do anytime I'm writing something with an asterisk, expecting it to stick, and it doesn't. Maybe I'm not seeing them anymore because I get the delete space in there instead now.
I got into the suffix spelling rules and fixed it so I can't get things like "creativetivity," "establishmentment," and "streghtenenned" anymore, too. Really you would think the AI would be smart enough not to do those in the first place. I guess I don't have those things defined properly in the pre/suf table.
It would've been a laborious process doing it by hand, but thanks to some playing around that I did for the IE (it's a long story involving importing/exporting dictionaries to use special keyboard layouts, and I don't even think I needed to do it in the first place), I realized that you can export a dictionary, edit it in Word, import it, and make changes that way! So all the times that I've wished I could "find and replace" all instances of something in a dictionary, I actually could have!
I used it to put = {NULL} after all the words, and also to change them to all caps since that's how they're going to look when I'm captioning, and I instantly had dictionary entries for the entire list. And there are some really bad words on that list, so I'm glad I'm protected now.
I also realized that for captioning, you want to have a lowercase "s" with your acronyms; like if they say there were multiple DAs, you don't want that coming out as DAS; it doesn't make any sense. So as I was editing and I noticed letters next to "s," I slowly just defined them with a lock case, but eventually I actually had time to write/define them all. I hadn't missed many, and it turned out to not take that long (I probably should've just done that in the first place, but I thought it would be more time-consuming than it was).
I had 1st defined as "first," which was really annoying. I don't know how that happened, but I definitely fixed it. I've also been defining common phrases like "10 or 15," "10 to 15," and "10 and 15" with the 10 as a numeral, because otherwise it comes out as "ten or 15," and I don't think about it fast enough to use my numeral trigger before the "ten."
According to my list of things I wanted to write about, I also spent some time paying attention to getting things like YA*RD and WI*CK in my dictionary as ^yard and ^wick, but I don't remember about that anymore. Probably a good thing to do anytime I'm writing something with an asterisk, expecting it to stick, and it doesn't. Maybe I'm not seeing them anymore because I get the delete space in there instead now.
I got into the suffix spelling rules and fixed it so I can't get things like "creativetivity," "establishmentment," and "streghtenenned" anymore, too. Really you would think the AI would be smart enough not to do those in the first place. I guess I don't have those things defined properly in the pre/suf table.
Bits and Bobs
I've been covering a lot of techy stuff. People are always talking about Drupal, Java, Linux, servlets, HTML, RSS feeds, you name it. I feel like the fact that I know a tiny bit of HTML and tech-type stuff has helped me out. I'm always proud of myself when I get something like JSON right and think, "I bet some other CART providers wouldn't know what that is." The more teleconferences I listen to, the more wonky words I can get in there like syslog, nav, dev, etc.
Alan Peacock had a great article in the JCR about getting things like @ and # in your dictionary. I have @ in there, so that's not a problem, but I don't have anything for # yet. It never comes up in CART, but when I start captioning, it's going to be important.
I've been doing my speaker IDs as GL-[first initial of name] forever, and it was really becoming a problem when I had to do 5-30 new speaker IDs for every event, because each meeting has different speakers. The main problem was not only did I define all the IDs, I also had to define all the misstrokes for them. I thought there might be something I could do with the speaker ID table, but I wasn't really sure.
Then someone on the Eclipse FB group posted something about inflected endings and slop strokes, which was totally unrelated, but it reminded me: slop strokes! So I put all the misstrokes in as slop strokes, and now they physically *can't* come out wrong. All I have to do is define each misstroke for each initial once, and that's it! They're all set for every meeting I write after that. I'm still adding initials as they come up, but I have 36 so far.
A professor rattled off "Minneapolis, Calgary, Montreal, Toronto, Edmonton, and even Moscow" the other day, and I was pretty relieved when they all came out perfectly. I have a great brief for Minneapolis (MIPS, which goes with IPS for Indianapolis), but the rest were just in there. I stroked out "heteronormative" the way I thought it should be and that came out perfectly, too.
I've been doing a lot of stroking things out the long way and hoping that helps them translate better. Sometimes it works, sometimes it doesn't. Lots of times I think the short way was in there, but whatever crazy way I decided to do the long way didn't work. I did have to put "youse" in my dictionary the other day because it wasn't in there at all.
I turned my TM slider up to about 50%, but it was being too aggressive, so I dialed it back down to 29% based on some things I didn't want it to mess with. It does pretty well. I don't like it when it takes a word like "overly," which is just over + -ly and decides that was an untran because it wasn't in my dictionary. But that's not really a big deal.
As I go through transcripts, I still pick out words that I shouldn't have gotten wrong and add them to my practice list. It only has 12 words on it, but I'm at least that many transcripts behind on editing. I'm working on hitting "logical" with an asterisk for words like methodological and genealogical. It's really tough fingering for me, but there's got to be a distinction between "methodological" and "was the method logical."
I like to do my Phoenix speed drills every day, too. It's not even a "have to" at this point; I just like to do it. It keeps me grounded. And it's a little bit like a game. It's one way I can really see progress, and it helps me work on stuff I have problems with. I've even gotten a couple drills maxed out at 220 wpm, which is as fast as the free metronome program I use goes. I'm up to 185 wpm or higher on all the drills, and my average right now is 191 wpm.
Alan Peacock had a great article in the JCR about getting things like @ and # in your dictionary. I have @ in there, so that's not a problem, but I don't have anything for # yet. It never comes up in CART, but when I start captioning, it's going to be important.
I've been doing my speaker IDs as GL-[first initial of name] forever, and it was really becoming a problem when I had to do 5-30 new speaker IDs for every event, because each meeting has different speakers. The main problem was not only did I define all the IDs, I also had to define all the misstrokes for them. I thought there might be something I could do with the speaker ID table, but I wasn't really sure.
Then someone on the Eclipse FB group posted something about inflected endings and slop strokes, which was totally unrelated, but it reminded me: slop strokes! So I put all the misstrokes in as slop strokes, and now they physically *can't* come out wrong. All I have to do is define each misstroke for each initial once, and that's it! They're all set for every meeting I write after that. I'm still adding initials as they come up, but I have 36 so far.
A professor rattled off "Minneapolis, Calgary, Montreal, Toronto, Edmonton, and even Moscow" the other day, and I was pretty relieved when they all came out perfectly. I have a great brief for Minneapolis (MIPS, which goes with IPS for Indianapolis), but the rest were just in there. I stroked out "heteronormative" the way I thought it should be and that came out perfectly, too.
I've been doing a lot of stroking things out the long way and hoping that helps them translate better. Sometimes it works, sometimes it doesn't. Lots of times I think the short way was in there, but whatever crazy way I decided to do the long way didn't work. I did have to put "youse" in my dictionary the other day because it wasn't in there at all.
I turned my TM slider up to about 50%, but it was being too aggressive, so I dialed it back down to 29% based on some things I didn't want it to mess with. It does pretty well. I don't like it when it takes a word like "overly," which is just over + -ly and decides that was an untran because it wasn't in my dictionary. But that's not really a big deal.
As I go through transcripts, I still pick out words that I shouldn't have gotten wrong and add them to my practice list. It only has 12 words on it, but I'm at least that many transcripts behind on editing. I'm working on hitting "logical" with an asterisk for words like methodological and genealogical. It's really tough fingering for me, but there's got to be a distinction between "methodological" and "was the method logical."
I like to do my Phoenix speed drills every day, too. It's not even a "have to" at this point; I just like to do it. It keeps me grounded. And it's a little bit like a game. It's one way I can really see progress, and it helps me work on stuff I have problems with. I've even gotten a couple drills maxed out at 220 wpm, which is as fast as the free metronome program I use goes. I'm up to 185 wpm or higher on all the drills, and my average right now is 191 wpm.
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.
12.7.13
I was feeling pretty confident about things after the CCP/CBC exam, and I decided I couldn't wait around anymore for my arm to feel better. I applied to about 15 CART companies trying to drum up some real work. I got promising responses from a few. It's three weeks later now, and I've only actually done any work for one, and that's only been a couple of hours. I'm hopeful about getting some classes from another next semester, but I'm not sure it'll be a full schedule.
I'm starting to have serious doubts about my ability to make a career out of CART. I don't like having downtime. I'd rather be working. Like it or not, I'm about to have an entire month off. I may actually have to invest in captioning. The good thing about that is I can start any time; it's not dependent on semester schedules.
I've been having a problem where I keep writng -fy as FAOI, even though that's "fie" and -fy should be FEU. I had SUR as Sur for some reason instead of sur-, which caused a problem somewhere, so I fixed that. I wrote that Frozen was a "prison success movie," which was just weird. I guess it's good that it translated that way, but I certainly didn't remember that I'm supposed to write "princess" as PRIN/S*ES. Maybe I should change prison to PR*IN.
Jill posted a brilliant idea on depoman. Instead of just having "-ville" and "-borough" and whatnot just attach, she has them defined to cap the previous word *and* attach to it! I updated a few pertinent entries of my own to do that, and it's totally awesome.
I also joined the Eclipse group on FB, where I've learned some great tricks. You can use ALT + S/ALT + A to add a single word to your spelling dictionary instead of having to run a spellcheck which pushes you down to the next misspelled word whether you wanted to go anywhere or not, which is a lifesaver. There's a command to bring up your steno notes if they're not showing up on a transcript.
The most important thing I saw was a reminder to upgrade to Version 6.0.0.12. I was on .9, and I don't even think I knew there was another update. If I did, I didn't know it was a stable one. I upgraded, and it turns out they fixed the auto-brief window so it works in keyboard macro output! They fixed it around the start of the semester. I *so* wish I had known that! It would've been amazing. I've got it going now, but there's only one week left in the semester.
I haven't had time for dictionary maintenence for a while, but there was a period where I was making good progress on it. I decided it made more sense for ya'll to be YAL and -ial to be Y*AL, so I changed 961 entries. I was really used to doing -ial as YAL, though, and it's not going over so well in my writing yet. -cade needed to be KA*ID to avoid conflicting with Cade, but there weren't many of those. Similarly, -tate (141 entries) got updated to TA*IT to avoid conflicting with Tate.
-gate (162) had to be GA*ET, for obvious reasons. I was writing -ality as ALT and it wasn't translating, so I did 434 of those. Latin was defined as LANT, which made sense. I'm not sure I actually even write it that way, but I updated 86 -lant entries to be LA*NT. -rate words (465) weren't working as RA*T, although I thought I fixed that already. I went ahead and did 84 -fied words as FAOID and FID, so that should work no matter which way I do it.
BER is ber-, so I updated -ber (208) as B*ER. "-zation" words (273) weren't coming out properly. I think I decided they should be fine as STKAIGS, but I defined them all as STKA*IGS for some reason. I wanted my para- prefix (232) to be PA*R, but it wasn't defined. -cate (238) wasn't working as K*AT. YOR is yore, so -ior (84) had to be Y*OR. I'd probably write yore as YOER, though, so I'm not sure I really needed to do that one.
I'm down to only 13 more problems to fix, so maybe I can get them done over winter break.
I'm starting to have serious doubts about my ability to make a career out of CART. I don't like having downtime. I'd rather be working. Like it or not, I'm about to have an entire month off. I may actually have to invest in captioning. The good thing about that is I can start any time; it's not dependent on semester schedules.
I've been having a problem where I keep writng -fy as FAOI, even though that's "fie" and -fy should be FEU. I had SUR as Sur for some reason instead of sur-, which caused a problem somewhere, so I fixed that. I wrote that Frozen was a "prison success movie," which was just weird. I guess it's good that it translated that way, but I certainly didn't remember that I'm supposed to write "princess" as PRIN/S*ES. Maybe I should change prison to PR*IN.
Jill posted a brilliant idea on depoman. Instead of just having "-ville" and "-borough" and whatnot just attach, she has them defined to cap the previous word *and* attach to it! I updated a few pertinent entries of my own to do that, and it's totally awesome.
I also joined the Eclipse group on FB, where I've learned some great tricks. You can use ALT + S/ALT + A to add a single word to your spelling dictionary instead of having to run a spellcheck which pushes you down to the next misspelled word whether you wanted to go anywhere or not, which is a lifesaver. There's a command to bring up your steno notes if they're not showing up on a transcript.
The most important thing I saw was a reminder to upgrade to Version 6.0.0.12. I was on .9, and I don't even think I knew there was another update. If I did, I didn't know it was a stable one. I upgraded, and it turns out they fixed the auto-brief window so it works in keyboard macro output! They fixed it around the start of the semester. I *so* wish I had known that! It would've been amazing. I've got it going now, but there's only one week left in the semester.
I haven't had time for dictionary maintenence for a while, but there was a period where I was making good progress on it. I decided it made more sense for ya'll to be YAL and -ial to be Y*AL, so I changed 961 entries. I was really used to doing -ial as YAL, though, and it's not going over so well in my writing yet. -cade needed to be KA*ID to avoid conflicting with Cade, but there weren't many of those. Similarly, -tate (141 entries) got updated to TA*IT to avoid conflicting with Tate.
-gate (162) had to be GA*ET, for obvious reasons. I was writing -ality as ALT and it wasn't translating, so I did 434 of those. Latin was defined as LANT, which made sense. I'm not sure I actually even write it that way, but I updated 86 -lant entries to be LA*NT. -rate words (465) weren't working as RA*T, although I thought I fixed that already. I went ahead and did 84 -fied words as FAOID and FID, so that should work no matter which way I do it.
BER is ber-, so I updated -ber (208) as B*ER. "-zation" words (273) weren't coming out properly. I think I decided they should be fine as STKAIGS, but I defined them all as STKA*IGS for some reason. I wanted my para- prefix (232) to be PA*R, but it wasn't defined. -cate (238) wasn't working as K*AT. YOR is yore, so -ior (84) had to be Y*OR. I'd probably write yore as YOER, though, so I'm not sure I really needed to do that one.
I'm down to only 13 more problems to fix, so maybe I can get them done over winter break.
Headway
I'm finally starting to feel good about my realtime. Out of the last three news broadcasts I've practiced, my lowest accuracy was 98.83%. I'm starting to not get freaked out when I make a mistake, and be aware of what's being said while I fix mistakes. I still haven't gotten any work from the company I signed a contract with, though. I'd really like to get my feet wet and see where I stand on some actual CART work.
I'm feeling so confident that I even sent out "applications" to five CART/captioning companies, but I haven't heard anything back. It's frustrating because I've been working so long to be "ready," and now that I've put myself out there, no one seems interested in taking me on.
I'm intimidated by the captioning aspect, too. I live in an apartment, and we don't have a single landline, let alone the three or four I might need for captioning. We only have basic cable, and if I started captioning the traditional way, I'd have to buy a TV, modem, coupler, and amplifier, at least, plus AccuCap, which would be $3k alone. I have enough saved up for all of those things, but I'd much rather not have to get them.
In less stressful news, I finally hit an average of 180 wpm on all of my speed drills! I've been gunning for that goal for a while. I'm also doing a lot better making my corrections make sense when I practice realtime; making sure I have a dash before and after the correction word, if it doesn't come right after the error. I was having a problem with dashing before and using a comma after, but that's only happening rarely now.
I finally finished all my -NAIR corrections, and I've moved on to -ia, which I now write as KWRA*. Nothing in that group of 744 words seems to be defined the way I write it now, so that's my next project.
I made some changes to auto-brief; namely, I learned that you can tell it not to suggest certain letter combinations, which is really helpful. I don't ever write -TD or -SZ (or at least, not on purpose), and now I won't get suggestions with them. I also noticed sometimes it would suggest a brief with -TZ in it, which was just crazy (for me, anyway). For some reason after I did that, I lost my pop-up window. It was really weird, and I couldn't figure out how to get it back, until a few days later, it magically reappeared on its own!
I'm feeling so confident that I even sent out "applications" to five CART/captioning companies, but I haven't heard anything back. It's frustrating because I've been working so long to be "ready," and now that I've put myself out there, no one seems interested in taking me on.
I'm intimidated by the captioning aspect, too. I live in an apartment, and we don't have a single landline, let alone the three or four I might need for captioning. We only have basic cable, and if I started captioning the traditional way, I'd have to buy a TV, modem, coupler, and amplifier, at least, plus AccuCap, which would be $3k alone. I have enough saved up for all of those things, but I'd much rather not have to get them.
In less stressful news, I finally hit an average of 180 wpm on all of my speed drills! I've been gunning for that goal for a while. I'm also doing a lot better making my corrections make sense when I practice realtime; making sure I have a dash before and after the correction word, if it doesn't come right after the error. I was having a problem with dashing before and using a comma after, but that's only happening rarely now.
I finally finished all my -NAIR corrections, and I've moved on to -ia, which I now write as KWRA*. Nothing in that group of 744 words seems to be defined the way I write it now, so that's my next project.
I made some changes to auto-brief; namely, I learned that you can tell it not to suggest certain letter combinations, which is really helpful. I don't ever write -TD or -SZ (or at least, not on purpose), and now I won't get suggestions with them. I also noticed sometimes it would suggest a brief with -TZ in it, which was just crazy (for me, anyway). For some reason after I did that, I lost my pop-up window. It was really weird, and I couldn't figure out how to get it back, until a few days later, it magically reappeared on its own!
Proficient
I tested out my skills on QVC and The Weather Channel, and I did
great. I even got above 99% on the weather. I did those two, plus three
national news broadcasts and four local ones. My lowest rate was 98.1%,
and when I averaged them all together, it came out at 98.55%. So, obviously, I don't always hit 98.5% accuracy, but 98% is the minimum to get hired at some companies, at least. And if I could get a gig captioning something like QVC or the weather, I'd be set.
I decided to start out checking back in with the company I shadowed classes for in November. They said my notes looked good, so I got all set up with them. I bought the professional version of Eclipse, since I'll be using it for profit now. I didn't need to get the AccuCap portion, so that was $3,000 off the price, but I'm sure I'll wind up getting it sooner or later. Since it's the middle of the semester, the only CART work they've got is basically just filling in during emergencies. I was hoping I'd get more experience than that, but I guess it's only logical.
I still hate doing "homework." It's such a drag practicing for two hours every day, first thing in the morning. I would feel bad if I didn't do it, though. Lazy. And it's not like I'm doing anything else all that important or interesting. I was so disappointed the first time I failed the CBC, feeling like "now I have to go back to doing homework." For some reason I thought if I passed, I wouldn't have to do it anymore. I felt the same way to a certain degree when I was getting set up with this company. I had planned to keep up with the reinforcement/speed drills/dictionary maintenance, but at least I'd get paid for the "realtime practice" part, instead of doing the news for no one every day.
But the reality is, I don't think I'm anywhere near "perfect" at this yet (and I suppose no one ever is). As long as there are words that are difficult for me to write (which will probably be forever), I have to carve out time every day to practice them. Until I can do all the drills at at least 225, I have to keep doing them. And until there's nothing in my dictionary that's incongruent with how I'm writing it, I have to keep fixing things. No matter where I get hired, for how many hours, the "homework" isn't going away. That doesn't make it any easier to keep doing, unfortunately.
I decided to start out checking back in with the company I shadowed classes for in November. They said my notes looked good, so I got all set up with them. I bought the professional version of Eclipse, since I'll be using it for profit now. I didn't need to get the AccuCap portion, so that was $3,000 off the price, but I'm sure I'll wind up getting it sooner or later. Since it's the middle of the semester, the only CART work they've got is basically just filling in during emergencies. I was hoping I'd get more experience than that, but I guess it's only logical.
I still hate doing "homework." It's such a drag practicing for two hours every day, first thing in the morning. I would feel bad if I didn't do it, though. Lazy. And it's not like I'm doing anything else all that important or interesting. I was so disappointed the first time I failed the CBC, feeling like "now I have to go back to doing homework." For some reason I thought if I passed, I wouldn't have to do it anymore. I felt the same way to a certain degree when I was getting set up with this company. I had planned to keep up with the reinforcement/speed drills/dictionary maintenance, but at least I'd get paid for the "realtime practice" part, instead of doing the news for no one every day.
But the reality is, I don't think I'm anywhere near "perfect" at this yet (and I suppose no one ever is). As long as there are words that are difficult for me to write (which will probably be forever), I have to carve out time every day to practice them. Until I can do all the drills at at least 225, I have to keep doing them. And until there's nothing in my dictionary that's incongruent with how I'm writing it, I have to keep fixing things. No matter where I get hired, for how many hours, the "homework" isn't going away. That doesn't make it any easier to keep doing, unfortunately.
Wishlist
This is the list of things I need to get done, roughly in the order in which I plan to do them.
- Go back and add inflections for -ty/-fy/-vy/-ny (only 1800 entries left!)
- Change how -rate, -dor, -mon, -lish, -gree, -ple, -thor, -nate, and all words starting with ex- are defined
- Write through the Phoenix website's Conflict Finder Sentences and fix all instances of word boundary issues
- Delete any entries where -d is defined as TD
- Re-write/global all 92k dictionary entries to catch inflections and match my current writing style
- Delete briefs I don't use that came from the StenEd dictionary
- Edit some broadcast transcripts and global words/note errors
- Investigate drag/drop options in Eclipse
Subscribe to:
Posts (Atom)