I think I've resolved this problem.
When recording a macro with Quickkeys its default seems to be to issue
keyboard commands by using a 'Type Text' object set to 'insert text'.
Changing the mode of that object to 'type text' worked better, and
switching the object to 'Type Keystroke' works better still.
After doing that it was necessary to insert some small delays between
commands, as you suggested.
Thanks,
--Michael
On 12-10-26 2:19 AM, trevatpc wrote:
>
> Do you have the letter v later in your script?
>
> I've not used quickkeys on a mac, but I have used butler. This
> required some delay programmed between keystrokes (50ms or so I think)
> to allow avid time to process...
>
> (You could post the script ....)
>
> --- In Avid-L2@yahoogroups.com <mailto:Avid-L2%40yahoogroups.com>,
> Michael Brockington <brocking@...> wrote:
> >
> > Any Quickkeys gurus on the list?
> >
> > I'm using Quickkeys to record a macro to section out a timeline. It
> > works as expected when recording the macro, but has a different effect
> > when the macro is triggered subsequently.
> >
> > Stepping through the macro in debugging mode, it looks like
> Quickkeys is
> > issuing the expected commands, but they are getting interpreted
> wrong by
> > Avid, somehow. For instance, Quickkeys types a 'q' (default keyboard
> > mapping: set in-point), but this causes Avid to splice in a chunk from
> > the source window, as though 'v' had been typed instead.
> >
> > Mac OS is 10.7.4. I'm using a Bella keyboard -- wondering if not having
> > a standard Mac keyboard is causing the problem somehow?
> >
> > Thanks,
> > --Michael
> >
>
>
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (4) |
No comments:
Post a Comment