Registering and logging in removes this ad.
Registering and logging in removes this ad.
Comparison of Alternative Macro Tools
Submitted by BruceCyr on Wed, 01/16/2008 - 02:42.
There are a lot of ways to write script for Dragon nowadays, including by my count:
1. DNS Pro scripting
2. Vocola
3. Unimacro
4. KnowBrainer scripting
5. Utter Command (http://www.redstartsystems.com/)
Have I overlooked any?
In any case, I wonder if anyone has developed a systematic comparison of the capabilities and, more importantly to me, compatibilities of these various scripting tools. In particular, I am increasingly finding that DNS Pro's native scripting is only sporadically compatible with applications that I try to work in. I'm wondering if any of these other tools are more widely compatible?
I understand that tools based on the Dragon engine sometimes exhibit the same problems as DNS Pro scripting because the problem lies there and not in the scripting module(s).
BTW, an example of the kind of problems I see is here: http://www.speechcomputing.com/node/1714
Note on unimacro and vocola
For what it's worth:
See http://qh.antenna.nl/unimacro/features/vocolaandun...
for a comparison of a vocola and unimacro. In short (my view):
- Unimacro adds lots of macros for common tasks that everyone needs (browsing, working with folders, selecting tasks). It's like a free library of macros, you install it and use it, but I would not write my own macros inside unimacro.
- Vocola makes it easy for you to write application-specific macros (by voice if desired). It's a free, end-user scripting tool, great for quickly creating commands involving a sequence of keystrokes but a lot more powerful.
(Before discovering Unimacro I was spending a lot of time creating/adapting various Vocola scripts for common tasks but with Unimacro installed I've been able to focus on my custom apps.)
KB & VP are covered in other posts, no experience of DNS Pro.
Back to your question: Using Vocola scripting to issue keystrokes and positioning the mouse has worked for all applications that I use.
BruceCyr wrote:There are a
There are a lot of ways to write script for Dragon nowadays, including by my count:
1. DNS Pro scripting
2. Vocola
3. Unimacro
4. KnowBrainer scripting
5. Utter Command (http://www.redstartsystems.com/)
Have I overlooked any?
In any case, I wonder if anyone has developed a systematic comparison of the capabilities and, more importantly to me, compatibilities of these various scripting tools. In particular, I am increasingly finding that DNS Pro's native scripting is only sporadically compatible with applications that I try to work in. I'm wondering if any of these other tools are more widely compatible?
I understand that tools based on the Dragon engine sometimes exhibit the same problems as DNS Pro scripting because the problem lies there and not in the scripting module(s).
First, you forgot VoicePower. If you didn't think that VoicePower was or included Advanced Scripting tools, then you haven't really reviewed or understood it. VoicePower should definitely be included among these.
Second, I don't understand your second paragraph. Doesn't make any sense. The reason for this is simply that everything has to go through the Dragon engine. Scripting compatibility has absolutely nothing to do with what you are referring to. I don't know where you came up with that, but it couldn't be further from the truth. Yes there are various issues related to one thing or another, but of the scripting command doesn't work in a particular application, then it's most likely a problem with MSAA (Microsoft Active Accessibility). That's Microsoft's accessibility link between SAPI and speech recognition applications. Point your finger at Microsoft on this one, not DNS. Remember that all scripting is based on VBA, and VBA has its limits. I have yet to find an application that I cannot create Advanced Scripting macros for in DNS Pro Advanced Scripting, and I use an awful lot of them in my work.
Chuck Runquist
Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS
"Problems cannot be solved by the same level of thinking that created them." – Albert Einstein
Chuck, It seems like the
Chuck,
It seems like the passing of time has been as rough on your sensibilities as mine
My nonsense second paragraph seems to have inspired more of the same! I suppose like begets like
I agree there is no problem at all in writing Advanced Scripting macros in DNS Pro -- the problem is getting them to work consistently and reliably.
I did however manage to pick up a few nuggets amongst the dross in your response:
1. Voice Power has advanced scripting capabilities -- I wasn't certain, which is why I left it open.
2. [This is really the most important finding.] All of these scripting systems work through DNS Pro's VBA (according to you), so they all should have the same compatibility problems, like the one detailed in my companion post:
http://www.speechcomputing.com/node/1714
I was worried after my absence but maybe speechcomputing.com would have gone "civil", but I see now that that was a needless anxiety
Chuck Runquist wrote: I
I don't know where you came up with that, but it couldn't be further from the truth. ...
... Remember that all scripting is based on VBA, and VBA has its limits. I have yet to find an application that I cannot create Advanced Scripting macros for in DNS Pro Advanced Scripting, and I use an awful lot of them in my work.
Chuck, the natlink system (written in python) is definitely very different from the VBA system and probably "enters into DNS" in a different way. Natlink macro's (grammars of macro's) are often more flexible than what can be done with VBA. Or at least a lot easier.
I also use a lot of VBA macro's in my work, but I would not like to miss many unimacro macro's.
Quintijn
PS How about applications that use the SDK? Are there any available?
I thought voicepower
I thought voicepower allowed/facilitated the creation of keystroke macros (I suppose that is advanced scripting, it isn't how I think of it)
-- do voicepower preferred and voicepower professional both offer this?
Judy
I guess I left out the other
I guess I left out the other major alternative, Natlink, although apparently Vocola is based on Natlink:
http://speechwiki.org/NL/HomePage.html
The key question for me then is whether or not Natlink is free of the same kinds of problems that plague the VBA-based scripting systems? And whether or not its own problems are worth the effort for me to look into it again? I say that with a grain of salt because over the years I have repeatedly failed to get any version of Natlink to work with any version of DNS -- no doubt an indicator of my incompetence.
BruceCyr wrote: no doubt an
no doubt an indicator of my incompetence.
I work for many years with natlink now. VoiceCode, Unimacro and Vocola all rely on natlink.
I know installing is not always easy, and currently possibly "out of order" with 9.5 and/or vista and/or python 2.4. I am working on these last bits.
As to "same kinds of problems" as with VBA-based systems: in my experience the natlink based macro's are quite reliable, sometimes better than advancedscript.
On the other hand it is all opensource and volunteer work, and the continuity of the products is not guaranteed, as Joel already pointed out when he released natlink.
Quintijn
If I understand the gist of
If I understand the gist of Chuck's comment in light of Scott W's speechwiki diagrams, the problem arises from conflicts between SAPI 4 and Java/JavaScript, in which case it probably wouldn't matter which scripting system is used -- no form of Dragon scripting is going to work smoothly in Photoshop.
Given that and my lack of finesse with Natlink/Python installation, I probably won't pursue that option UNLESS I learn that it does work compatibly with Photoshop.
Thanks to all for the comments.
BTW, in light of the above, I infer that Vista SR scripting isn't going to work for Photoshop Command and Control either -- which doesn't mean that I intend to look for a M$ compatible photo editor
PS: Oops! I just remembered VSR work via SAPI 5. The results may be the same, but not for the reason I deduced. Guess we'll have to wait and see.