In article
<d5af919b-b4aa-4e12-9448-7b950d799d44 RemoveThis @s12g2000prg.googlegroups.com>,
builtinbc RemoveThis @gmail.com wrote:
> I have been trying all day to get it to recognize a few
> technical words that I use frequently to no avail,
> because although it has added their SPELLING to its
> vocabulary, it clearly has no idea how they are pronounced,
> and therefore can't recognize them. For now I'm going back
> to ViaVoice, and hoping MacSpeech will come out with their
> free upgrade providing basic functionality SOON.
I feel your pain. I am in the same boat.
In my case, I sorta knew what I was getting into, because I
managed to find some early reviews that _did_ say that
MacSpeech Dictate had no correction features.
I still bought it mainly out of curiosity, just to see
how many of the Dragon "engine" features would run.
Like you, for my day-in/day-out serious dictation work,
I reverted to using another speech application, in my case
Dragon NaturallySpeaking. (DNS)
I still justify buying MacSpeech Dictate to any and all
who will listen to me.
My reasons:
1) Mac platform REALLY NEEDS a good speech app', the
only way we are likely to get one is
to support MacSpeech Dictate.
Even the PC guys would benefit, because competition
from MacSpeech would drive down the price of Dragon.
2) MacSpeech Dictate version 1.0 is kind of usable
right now, despite its many missing much-needed
features, which I could provide a list of such
missing features as long as your arm.
Assuming 96% average raw accuracy, correcting the
remaining 4% of mistakes by keyboard is "tolerable".
(but just barely tolerable)
3) In my case, I can use the wasted time that 'Dictate is
"out of production" to familiarize myself with the app'
and its quirks.
For example, I recently found a workaround for forcing
'Dictate to handle speech like this:
For example, say:
******************************************************
When a user says "Open TextEdit" the application opens.
******************************************************
Normally that will not work. As soon as you
said: OpenQuote Open TextEdit CloseQuote
....the darn TextEdit app' would open.
Here is the workaround for the troublesome part.
Say:
OpenQuote
CapOpen
NoSpace
CapText
CloseQuote
....gives the desired text result: "Open TextEdit"
....without the undesired result of opening
the TextEdit application.
There are literally hundreds of little tricks like that
which will have to be learned, in order to improve
the "raw accuracy" of MacSpeech Dictate to acceptable
"Dragon" standards.
For me right now, the highest priority is for me to "bug"
MacSpeech to post a decent "Help" file in their website
so new users can bypass the incomplete Help file in 'Dictate.
Chuck Rogers, where are you.
Chuck has a lotta influence, he barks and MacSpeech jumps.<g>
The present Help file of 'Dictate sucks, I could not find
the OpenQuote command there, no matter how hard I searched
for it.
Only reason I was aware of commands like that is because
they are part of Dragon NaturallySpeaking.
A new 'Dictate user would be totally unaware
such a command existed in MacSpeech Dictate.
Mark-
>> Stay informed about: Sour Grapes on MacWorld forum about MacSpeech Dictate