AutoTaleMute v1.2

by John Pane


AutoTaleMute eliminates the need to configure your software each time you insert or remove your TaleDevice. You can simply leave AutoTaleMute turned on. When the TaleDevice is plugged in, AutoTaleMute will activate it and mute the sound, just like TaleMute does; but when the TaleDevice is not plugged in, AutoTaleMute steps aside and allows the sounds to play as normal.

Note: Not all TaleDevices support auto-detect!

TaleDevices (TaleLight, TaleVibes, etc) are available from Tech Center Labs. Before purchasing AutoTaleMute, please confirm that your TaleDevice supports auto-detect. All new TaleVibes support auto-detect but earlier TaleVibes did not include this feature. Also, the Sportster TaleLight and Palm V TaleLight/Flashlight support auto-detect, but Classic TaleLights do not.

Just like TaleMute, AutoTaleMute will intercept the alarms generated by the Datebook application as well as the alarms generated by the Pager Card.

You can find more information on using AutoTaleMute with the Pager Card at: Using the Synapse Pager Card & TaleVibes by John "FuzzFace" McMahon.

AutoTaleMute is $5.

Requirements

AutoTaleMute requires HackMaster, or a compatible system patch manager. I encourage you to register your shareware copy of HackMaster if you use it with AutoTaleMute.

AutoTaleMute will not function correctly unless your TaleDevice supports auto-detect. If yours doesn't, you can use the freeware TaleMute instead.

To test whether your TaleDevice supports auto-detect, you can use the free program TD Detector. TD Detector is a very simple program that uses the same logic as AutoTaleMute for detecting the presence of a TaleDevice. While TD Detector is running, it checks for a TaleDevice once each second. A message on the screen, as well as an audible click or beep, will indicate whether one is detected.

AutoTaleMute is compatible with all versions of the OS through 3.2, and all devices including the new Palm IIIx, Palm V and Palm VII.

Details of Operation

AutoTaleMute is a HackMaster hack. After installing AutoTaleMute, you control its operation by turning it on or off inside HackMaster. AutoTaleMute has no configurable options.

When it is active, AutoTaleMute patches two operating system calls that applications might use to play sounds: SndDoCmd and SndPlaySmf. When either of these routines is called, AutoTaleMute intercepts the call, and if a TaleDevice is detected it mutes the audio and activates the TaleDevice for the duration of the sound.

TaleDevices are activated by opening the serial port. If the serial port is already open, AutoTaleMute will not interfere with the current serial operation, and the sound will play audibly.

AutoTaleMute attempts to match the duration of the sound. Thus, you can adjust the amount of time that the TaleDevice is active by selecting a sound that has a shorter or longer duration. However, some TaleDevices do not respond well to extremely short activation durations. So, AutoTaleMute activates the TaleDevice for a minimum of 30 ms. Unfortunately, if an application plays a series of very short sounds (< 30ms) in rapid succession, AutoTaleMute will cause the series of sounds to last longer than it should.

The auto-detect feature is accomplished by connecting two lines on the serial port: the RTS and CTS lines on pins 4 and 6 respectively. Looking at the back of the PalmPilot, the pins are counted from 1 to 10 starting at the right. The auto-detect logic manipulates the RTS signal and checks for corresponding changes in the CTS signal. While it is possible that some other devices could cause this method to falsely detect a TaleDevice, I have not found any yet. It has been tested with the HotSync cradle (plugged into a computer's serial port), as well as the modem and the GoType keyboard. If there were a device attached that causes a false-positive, AutoTaleMute would mute the sound, but would not cause any harm. You can test whether the auto-detect logic works correctly with your devices by using the free TD Detector mentioned above.

If you are skilled with working with electronics, you might be able to modify your TaleDevice to support auto-detect. I was able to do this with my old TaleVibes. However, it was not easy, and for a while there I thought I was going to have to throw the whole thing into the trash. Also, if you do this modification incorrectly, you could damage your PalmPilot and/or TaleDevice. Therefore, I do not recommend this.

Disclaimer

AutoTaleMute and TD Detector are distributed "as is," in the hope that they will be useful, but without any warranty; not even the implied warranties of merchantability or fitness for a particular purpose.

Purchase AutoTaleMute

Please do not purchase AutoTaleMute until you have confirmed that your TaleDevices and other devices work correctly with the auto-detect logic. Use the free TD Detector mentioned above.

AutoTaleMute can be purchased for $5 from PalmGear.

Phone orders: 800.741.9070
Fax orders: 817.640.6614

Contact Information

The author can be reached at: JPSoftware@pane.net.

The latest information about AutoTaleMute can be found at: http://www.cs.cmu.edu/~pane/atm/

Version History

v1.2: Work around a problem on the Palm IIIx where the sound did not mute properly.

v1.1: Updated to support Palm IIIx and Palm V.

v1.0: Initial public release.

Copyright

Copyright (C) 1999 John Pane
All rights reserved.


PalmPilot Software by John Pane

  • AutoTaleMute
    Redirects alarms to TaleDevices, with auto-detect.

  • TaleMute
    Redirects alarms to TaleDevices.

  • FlashLight
    Activates a TaleDevice while the Palm V hardware contrast button is depressed.

  • BackMute
    Redirects alarms to Backlight.

  • SilentRadio
    Disables Palm VII wireless chirp or another selected midi sound.

  • John Pane's Home Page

    JPSoftware@pane.net (last modified on 990629)