Trying to speed up Macro

[aenae]

Hey all, I've been using ME to automate data entry, the only problem I'm experiencing is the following:

 

I have 3 macros that I have captured.

They each have been modified with a Macro PlayBack speed: x faster than normal macro script

 

No problems yet.

 

It's when I build a macro with all of them together it gets funky.

I grouped all the macros together for process efficiency, and to prevent having 3 different macro hotkeys for just one job.

 

I'd go to quickwiz > macro > next > build from > and then combine all the macros in the order I need.

Then I'd check the macro scrips on the newly built macro, and then run it. It will run at only x1 speed aka human speed aka not acceptable. lol

So I even added another line of the macro playback speed in the script editor of the built macro, and still no change (mind that each Macro Run: has a speed up script within that macro itself as well)

 

Everything was swell up to this point ;P

[rberq]

If you capture a macro directly from your keystrokes, there can be a lot of delays built in because ME will capture all your hesitations and play it back the same way. Look at the macro with the script editor and you can see the delays and delete them. Then, if anything, it might play back too fast.

 

I think there's an option to keep ME from capturing the delays, but I don't have a PC handy with ME installed so I can't look it up now.

 

There are probably good uses for adjusting macro playback speed but I have never found the need to do so.

[aenae]

If you capture a macro directly from your keystrokes, there can be a lot of delays built in because ME will capture all your hesitations and play it back the same way. Look at the macro with the script editor and you can see the delays and delete them. Then, if anything, it might play back too fast.

 

I think there's an option to keep ME from capturing the delays, but I don't have a PC handy with ME installed so I can't look it up now.

 

There are probably good uses for adjusting macro playback speed but I have never found the need to do so.

 

Thank you for your reply =].

 

Removing the delays will probably make the macro run too fast, however you may have made a good point, I can try to edit the delays and reduce them drastically so that instead of running at x1 speed, it'd be running x1 with much fewer delays - though there are a LOT of delay entries I'd have to edit, I'm still quite interested in finding a way where I can 'edit speed for all'.

 

Any suggestions?

[rberq]

I don't know how big your macro is, but I DO know what you mean by "there are a LOT of delay entries I'd have to edit" -- I have done it and it's an awful job. That's why I never bother any longer capturing keystrokes -- too much problem with the timing, and you get halfway through and make a mistake and then you have to start over or remember where the mistake was and go back and fix it anyway with the editor.

 

I just use the scripting error right from the beginning and build the macro that way. Write a few lines, test it up to that point, write a few more, test, and so on. I have yet to find a macro that runs too fast overall, though you may find a few spots like clipboard commands or window changes where you need to add delays or "wait for window", or you may set keystroke speed a little slower in a few spots where you want the user to actually watch what is happening. Setting a slow keystroke speed is also very handy while debugging so you can watch where it goes wrong, then comment out the "keystroke" command once you fix the problem.

[aenae]

I don't know how big your macro is, but I DO know what you mean by "there are a LOT of delay entries I'd have to edit" -- I have done it and it's an awful job. That's why I never bother any longer capturing keystrokes -- too much problem with the timing, and you get halfway through and make a mistake and then you have to start over or remember where the mistake was and go back and fix it anyway with the editor.

 

I just use the scripting error right from the beginning and build the macro that way. Write a few lines, test it up to that point, write a few more, test, and so on. I have yet to find a macro that runs too fast overall, though you may find a few spots like clipboard commands or window changes where you need to add delays or "wait for window", or you may set keystroke speed a little slower in a few spots where you want the user to actually watch what is happening. Setting a slow keystroke speed is also very handy while debugging so you can watch where it goes wrong, then comment out the "keystroke" command once you fix the problem.

 

Looks like I'll be learning to write scripts given the situation! Thanks for the help rberq, though your mentions of the problems with the timing, and having to start all over again with captured macros is bringing me nightmares. hahaha