My playback seems to play slower/faster than the original speed. Why isn't Tasker consistent?
Tasker has a significant amount of code dedicated to duplicating the playback speed as closely as possible. Since no two processes take exactly the same amount of time on a computer, it accommodates the operating system's timing surpluses and deficits. Playback speed should be independent of your computer's hardware. Other factors, such as background Windows processes, could potentially affect the speed. If you are technically curious, turn Log Settings in Advanced Options on to maximum and you will see (in the logfile) Tasker's attempts to keep the playback accurate. Be sure to turn the log off in the Advanced Options screen afterwards, or your computer's performance will suffer.
The only things that you can do to increase Tasker's playback accuracy are: 1) (IMPORTANT) Turn off the Tasker Log in Advanced Options; 2) Make sure the playback speed is set to Normal; 3) Modify the playback speed factors in Advanced Options; 4) Look in your system tray for lots of tiny icons. These could be running processes that are taking too much time from the CPU. NOTE: The Keyboard Service for Mappings and ShortType do not affect playback accuracy, since they are disabled during a playback.
One design decision that was made was to keep the overall playback duration as consistent as possible, rather than the timing between individual events. This means if Windows takes a fraction of a second too long to play a key press, the next event in sequence is played sooner to keep the entire playback duration the same. If all the tiny delays were ignored, a long playback would eventually be many seconds longer (or shorter). Again, if you are certain that it is running too long or too quickly, turn logging on and it will tell you what Tasker is trying to do. If there is an error in Tasker interval processing, it will appear in the calculations listed in the log. Vista Software cannot fix any errors that are reported as "it plays too slowly on my PC" without additional information.
Press the "Control + Escape" keys at the same time (press and hold Control, then press the Escape key while still holding the Control key). You can do this key combination at any time.
Another key combination that always stops a Tasker playback is "Control + Alt + Delete", but "Control + Escape" is more common since it doesn't bring up the Task List window.
Unfortunately this is not allowed. The Keyboard Mapping Service (among other things) makes this a bad idea. The different Taskers could interfere with each other.
How can I run programs other than Notepad when using the START script command?
You may have to use the entire path for the program. For example, Microsoft Word might be located at "C:\Program Files\Microsoft Office\Office10\WINWORD.EXE" (for Office XP).
To get these paths, right mouse click on the icon that you want to run and choose "Properties". Then copy the "Target" field where the program location is listed. Use that text for the START command.
Some old 16-bit MS-DOS programs can run programmatically, and others can't. Compatibility with DOS programs was not a priority for Tasker, and our testing has shown it to be somewhat unreliable. The best way to run a DOS program is to use Tasker script: "START CMD.EXE /C C:\DOS\Program.exe" where "Program.exe" is the name of your DOS program. DOS commands can be run with the syntax: "START CMD.EXE /C dir c:\*.* /s" (which does a recursive directory listing for the C: drive). Windows 95/ME uses "C:\WINDOWS\COMMAND.COM" as its command processor.
Here is an example of a Tasker Script file to run DOS commands:
; TASKER SAMPLE SCRIPT
; PURPOSE: Demonstrates how to run MS-DOS commands or programs
; In Windows 95/ME this next line will be something like "C:\Windows\COMMAND.COM"
START cmd.exe
WAIT 2 seconds
; This is what the DOS shell window title is in Windows 2000
; In Windows 2000/XP it will be something like "C:\Windows\System32\cmd.exe"
; In Windows 95/ME it will be something like "MS-DOS Prompt"
GOTO c:\WINNT\System32\cmd.exe
WAIT 1 second
; Type something in the DOS window and press Enter to run it
type dir{return}
WAIT 1 second
; Do something else
type dir /w{return}
WAIT 1 second
We will continue to work on DOS compatibility for future versions of Tasker. Let us know if you have specific problems running one of your programs or if it is more unreliable on certain versions of Windows.
How do I use the TYPE script command to simulate a Ctrl+S for "Save"?
You must use a lower case letter "s". The reason for this is that Tasker will include a SHIFT key if you tell it to type a capital "S", and the SHIFT negates the Control key combination (also called "Accelerators"). The following code works:
TYPE {ctrldown}
; Use "s", not "S"!!
TYPE s
TYPE {ctrlup}
When using a script file, how do I program it to loop or run at a certain speed?
There is no script command to do this, but identical functionality can be accomplished by using Command Line Parameters. To do this, create and save your script file, then run it with switches included on the execution line. This is normally done in the "Shortcut - Target" field in the Properties box.
The possible command line parameters are /SPEED, /REPEATS, and /CONTINUOUS. The Tasker User's Guide has detailed instructions on how to accomplish this, and includes sample screen shots.
How can I use the WAIT script command to pause a fraction of a second, instead of whole seconds?
The design of Tasker Script was only intended have the capacity to wait whole seconds, not fractions. In the future, millisecond timing might be available (that's what is used internally), but it was decided that pauses would be more useful and better understood if managed in whole seconds. Still, there is a way to do it if you really want to.
To WAIT less than one second (fractions of a second), you can use the Fast Factor when combined with the Fast Speed playback. For example, to do a delay of half of a second, you can set the Fast Factor to 2x speed (in Advanced Options - Value Ranges), and then play back at the Fast playback speed in the Playback Tab. WAIT 1 SECOND will become 1/2 of a second. If the factor is set to 4x, WAIT 1 SECOND becomes a quarter of a second.
Of course, the whole script will play at the Fast Speed, so you would have to increase your other delays accordingly.
Do you have a version of Tasker in (espa±ol/deutsch/etc.)?
At some point in the future, we will probably release international (localized) versions of Tasker. At the current time, we are completely occupied with releasing Tasker with new features.
Please let us know what language you would like to use Tasker, and we will make a note of it. Also let us know if you would like to volunteer for translation duties!!
I would like to request a new feature for Tasker. Will you add it to the next version?
Nearly all of the features that are in Tasker are the result of excellent suggestions that we have received from users. (The first version of Tasker only had Record, Stop, and Play!) We welcome all suggestions. If it is a recommendation that will appeal to many people, we will work to include it. It is difficult to predict what version it will be in, however.
Can I modify the .TSK file to correct a mistake that I made while recording?
The TSK file format is binary and should not be modified. The TSX format is text and can be modified. Be sure to save in the "Tasker Editable Text Files Format (*.tsx)" if you will want to edit your recordings. Better yet, write Tasker Script code to perform your jobs.
Each format has its advantages: The TSX format is editable, but it will create a file that is much larger than the TSK binary format. Also, the TSK format is a native Windows specification and thus less prone to any unforeseen errors.
I want to report a problem with Tasker. What should I do?
Before Vista Software can help you with any complex problems with Tasker, we will need to see your Log file. We request that you perform the following steps:
Go to the "Tools" menu, and choose "Advanced Options"
Go to tab #3: "Log Settings"
Set the log to HIGH
Select "Erase old log when Tasker starts" (make it checked)
When it asks you "Do you want to erase the log right now?" answer "Yes"
Duplicate the problem that you are having, then immediately close Tasker
Send the log file (probably "C:\Tasker.log") and a description of your problem to support@vista-software.com
When you start Tasker again, be sure to set the Log level back to OFF or your PC's performance will suffer
These steps help us to provide the best possible service for you.
Tasker is really cool - I was wondering if Vista Software is available for consulting projects or customizing Tasker for my corporation?
Vista Software has done many custom systems for companies, and we welcome any opportunity to show you how we can provide value to your corporation. Customizing Tasker is certainly an option that we can do. We would charge an economical hourly rate for the modifications.