Usher’s App Store hiatus is over

January 23rd, 2014 by Rob Griffiths

After much back-and-forth with Apple, we’re thrilled to announce that Usher 1.1.8 has been approved for sale in the App Store! Version 1.1.8 is basically the same as the recently-released 1.1.7, with a few additional bug fixes. Both the direct and App Store versions of Usher are now at 1.1.8, and both are available at the lower $25 ($24.99 App Store) price.

Direct buyers can get the update via in-app updating; App Store buyers should see the update in the App Store application shortly, if not already. (If you’re having trouble finding Usher in the App Store, it seems that Usher’s hiatus has caused some difficulty with search. Try this direct link instead.)

We’re sorry we had to (briefly) take Usher out of the App Store, but we didn’t feel right selling it with usability issues in OS X 10.9. But now, it’s back, and at feature parity with the direct sales version.

Ushering in some changes in Usher

December 2nd, 2013 by Rob Griffiths

Today we’re releasing Usher 1.1.7, but before upgrading, you should read this entire blog post, so you understand what’s happening with Usher going forward.

IMPORTANT NOTE: The minimum system requirement for Usher 1.1.7 is OS X 10.7 or newer; if you’re still running 10.6, DO NOT INSTALL THESE UPDATES. You can download older versions on our support page.

Why 10.7 or newer? Apple recently declared an old security-related API dead (i.e. deprecated), and recommended that all developers switch to the newer API, which we did. But that new API requires 10.7 or newer.

First up, in case you missed it, Usher is not presently available on the App Store. This change may be temporary (if we can resolve some issues with Apple), or it may be permanent (at least for this major version of Usher).

Second, Usher’s new price is $25 (on our site only, for now), down from $35. Why drop the price? Partly because we’d like more people to give Usher a look. But primarily because this version removes the ability to download videos from YouTube and Vimeo. Why did we remove this feature?

Both YouTube and Vimeo technically allow video downloading, but only for videos that are explicitly marked as downloadable. Unfortunately, there’s no easy way for Usher to tell the downloadable status of a given video, so it tries to download every video. As this is a violation of those sites’ terms of service, we don’t feel it’s right to leave the feature in Usher.

In addition, this feature is support intensive, because it breaks when either site makes even trivial changes to their pages—and both sites seem to make such changes regularly. So instead of spending time coding new features, we were spending our time trying to figure out how to make downloading work again. In the long run, this isn’t good for us, and it’s not good for our users.

Please note that Usher still includes two ways of downloading videos from many sites: The File > Open URLs menu item, and the Usher > Integrate With Browser bookmarklet. You can read more about both of these features in Usher’s help file.

There are also many web sites that exist solely to help you download videos from the web. Many of them work more reliably than does Usher, so you’re not out of solutions if you’re interested in downloading web videos. Finding such sites, however, is left as an exercise to the reader…but if you can use a search engine, you won’t have too much trouble with that exercise.

Usher has gone on an App Store hiatus

November 28th, 2013 by Rob Griffiths

As of today, the App Store version of Usher is no longer available for purchase. It may reappear in the future, if we can resolve some issues with the App Store. For now, though, we have removed it from sale.

Why did we do this, and what does this mean for App Store buyers?

Why did we do this?

We’ve been trying for a few weeks now—without any luck—to get a minor update approved for Usher. The App Store version of Usher has been in limbo for a long time, as they asked us to make some changes we weren’t willing to make at that point in time.

As a result, the App Store version of Usher is 1.1.3, while the direct version is 1.1.6. This wasn’t much of an issue until Mavericks came out. There are a couple of Mavericks-related issues that affect usability, so we agreed to make the changes Apple requested, and submitted a 1.1.7 update.

Unfortunately, the update has been rejected twice, and looks like it won’t ever be approved without us undertaking what is, in essence, an Usher 2.0 total makeover project. While we intend to do this in the future, it’s not a simple fix we can push out quickly to resolve the Mavericks issues.

Due to the App Store rejections and the Mavericks-related issues, we have decided to remove Usher from the App Store, effective immediately. It may reaappear in the future, if we can resolve our differences with Apple. But for now, the only way to buy Usher is directly from us, via the Usher web page.

What does this mean for App Store buyers?

With Usher no longer available in the App Store, App Store buyers can’t download Usher—for use on a new computer, or after a total system reinstall, for instance. If and when Usher returns to the App Store, this problem goes away. But for now, it’s a problem.

To solve the problem, we’ve created a way for App Store buyers to get a full direct sales license for Usher. This process will only be available during Usher’s hiatus from the App Store, because it becomes irrelevant once the app is available again.

To convert your App Store license to a full direct license, please follow these steps:

  1. Forward the iTunes receipt that shows your Usher purchase to usher_conversion at manytricks dot com. Make sure the email shows your first+last name somewhere, as we need that for the license file.
  2. Take your existing App Store Usher and archive it somewhere—if Usher never makes it back to the App Store, this will be your only copy of that version. We recommend you create a zip of the application, and keep it somewhere safe.
  3. Download the latest version of direct Usher from our site. [Direct download link]
  4. When you receive your license email, double-click the attached license file, and you should be a full licensed user of the direct version of Usher.

That’s really all there is to the conversion process. All of your existing library and metadata will be retained, as you’re not modifying any of your settings, just which version of the application you’re using.

How-to: Start and stop Leech on a schedule

November 26th, 2013 by Rob Griffiths

One feature that Leech, our simple download assistant, doesn’t offer is scheduling. For many users, this isn’t an issue, as they can use their internet connection whenever they wish. There is a subset of users, though, who have internet connections that may offer more speed at night, or not have capacity limits at night, or may allow unlimited downloading only at night.

A future version of Leech may offer scheduling, but until that comes to be, you can use AppleScript and a scheduling application to handle the task. It’s not overly complicated, but does require a bit of work in Leech and AppleScript.

The first step is to have Leech queue up all download requests, so you can just copy and paste URLs into it during the day, then let it run at night. To put Leech in queued mode, just make sure there’s not a checkmark by the Queue > Start Downloads Automatically menu item, as seen in the image at right.

Once that’s done, you can add URLs to Leech throughout the day, but they won’t start downloading. Next, you’ll need to create two AppleScripts, one to start those queued downloads, and the other to pause them again.

The scripts

Open AppleScript Editor, in Applications > Utilities, then copy and paste this code:

tell application "System Events"
    if (exists (processes where name is "Leech")) then
        tell application "Leech" to activate
        key code 125 using {command down}
    end if
end tell

This is the “start” script, which will tell Leech to start downloading your queued URLs. Note that if you don’t have any queued downloads, the script won’t do anything (as it can’t start a queue that doesn’t exist.)

Save this script somewhere (such as your user’s Documents folder), with a reasonable filename (Start Leech). Do not close this window, though, as we’ll be revisiting it.

Next, open a new AppleScript Editor window (via Command-N, or File > New). In the new window, paste the following code:

tell application "System Events"
    if (exists (processes where name is "Leech")) then
        tell application "Leech" to activate
        keystroke "P" using {shift down,command down}
    end if
end tell

This is the “stop” script, which will put Leech back into pause mode. Save this script (Stop Leech) into the same location as your other script—and as before, leave the window open.

Scheduling the scripts

Now that you’ve got two scripts, all that’s left to do is to have them run on your schedule. I’ll explain how to do this via OS X’s Calendar application; the directions will differ if you choose to use cron or launchd or some other solution.

In order to use Calendar, the first thing you need to do is convert your scripts to applications, because Calendar can’t run raw AppleScripts (iCal could, but it no longer exists).

In one open editor window, hold down the Option key, then select File > Save As. In the window that appears, change the File Format pop-up to Application, choose a name for your app (it can be the same as the raw script, if you want, as they have different extensions), and save the program.

Do the same for the other window, so that you’ve now saved two application versions of your scripts. Here’s how my setup looks, with the applications (left) and original scripts (right):

Once the application versions have been saved, launch Calendar and add a new event; the basics don’t matter, as you’ll be editing it. Might as well name it Start Leech, though, to help you visually see each task on your schedule.

When the editing window pops up, set the event start time at or after the time when your internet goes to unlimited mode. You don’t need a long-duration event, so set it for five minutes or similar. Then click on the date to open the scheduling details for the event. Set the “repeat” to whatever matches your schedule—daily, weekends only, whatever.

Next, click on None next to “alert” to set the alert for this event. Pick Custom from the pop-up menu; this will open another window (this is progress, really). In that new window, set the first pop-up to “Open file,” then pick “Other” in the second pop-up.

This will then show the standard Open File dialog; navigate to the folder where you saved the Start Leech (or whatever you named it) application. Select the application (not the script), then click the Select button to close the Open File dialog.

Finally, change the third pop-up menu (the one to set the time of the alert) to “At time of event,” then click OK. The screenshot at right shows how my window looked, correctly configured, just before I clicked the OK button.

You’ve now created a recurring event to start Leech’s downloads queue at your preferred time on your preferred schedule. Repeat the process with a new event called Stop Leech. Set this one to be triggered sometime before your unlimited internet usage ends, and point it at the Stop Leech application.

Wrapping it all up

With the scripts, application, and scheduled events created, you’re basically done. Go ahead and launch Leech and start queueing your downloads. When your defined start time arrives, Leech should automatically start your downloads, and then pause again near the end of your free usage period. (You may want to test things first by changing the start/stop times on your scheduled events to a time when you’ll be at the computer, just so you can see that they do work.)

We realize this is somewhat of a stopgap measure for true scheduling in Leech. However, in testing, it works well, and we hope those of you with time-based internet connectivity find it useful.

Toggle Witch off and on via AppleScript

November 15th, 2013 by Rob Griffiths

Recently, a few users have asked about disabling Witch when certain programs are in the foreground. Typically this comes up because of conflicts between Command-Tab or Option-Tab (the two most-common Witch activation keys) and the foreground app. For example, you can’t use Option-Tab in a Remote Desktop Client Windows window, because Witch will grab it. Or when using Fusion to run OS X in a virtual machine, you may find that Command-Tab is trapped by OS X before it gets to your virtual machine.

In those cases, it’d be nice to easily disable Witch, then quickly enable it again when you’re done with the app in question. As of today, you can’t do this within Witch, although we have plans to change that. For now, though, the best solution is to create an AppleScript that will toggle Witch off and on as needed. You can then use any program that can run AppleScripts via hot keys (such as our own Butler) to give yourself a keyboard combo that toggles Witch off and on.

Setting up the AppleScript isn’t overly complicated, though it does differ slightly depending on whether you’re using the App Store or direct version of Witch. If you’re interested in creating your own Witch toggle, read on for the how-to…

To start, launch AppleScript Editor, which you’ll find in the Applications > Utilities folder. It should open to a blank editing window; click anywhere in that window, then paste this code:

on ApplicationIsRunning(appName)
    tell application "System Events" to set appNameIsRunning to exists (processes where name is appName)
    return appNameIsRunning
end ApplicationIsRunning

if ApplicationIsRunning("witchdaemon") then
    do shell script "killall witchdaemon"
    do shell script "open 'REPLACE THIS BIT'"
end if

When pasting, hopefully you noticed the REPLACE THIS BIT portion of the code. That’s what you’ll do next, and it’s where the instructions differ for the direct and App Store versions of Witch.

App Store Witch

Assuming you have Witch installed in the Applications folder, highlight REPLACE THIS BIT in the AppleScript Editor, and replace it with this code:


Make sure you leave both sets of quotations marks (double and single) in place. Also, if you keep Witch somewhere other than in the /Applications folder, you’ll need to replace /Applications/ with the full path to the folder that holds the Witch application.

Direct Witch

The direct version of Witch is a System Preferences panel; this means it could be installed in one of two places: either in your user’s Library/PreferncePanes folder (if you installed for just your use), or in the top-level Library/PreferencePanes folder (if you installed for all users). You can check this in Finder by using the Go > Go to Folder menu item. Activate that, then enter /Library/PreferencePanes. If you see Witch.prefPane listed here, then use the following for the REPLACE THIS BIT section:


If you don’t see Witch listed there, that means it’s installed in your user’s Library/PreferencePanes folder. In that case, use the following for the REPLACE THIS BIT section:


Note that you’ll also need to replace your_user with the short name of your user, i.e. the name of your home folder.

Testing the code

Once you have all the code in, click the Compile button, and hopefully, you won’t see any error messages. If you do, compare your code to what you see above, and see if you can spot the problem area.

Assuming it compiles, the next step is to test it. Make sure that Witch is running, then click the Run button in the AppleScript Editor. You won’t see any output, but in a second, you should find that Witch no longer works. Click the Run button again, wait a second (it takes just a bit to start Witch), then hit your Witch activation keys. You should see the Witch switcher appear onscreen.

If you do, great—keep reading. If you don’t, go back and compare the code above to your code, and make sure it’s identical and that you’ve replaced the important bit to make it work.

Next steps

Now that you’ve got your toggle code working, save it somewhere (your user’s Documents folder, for instance) as a script. You can then use your favorite macro tool to execute that saved AppleScript. Or you could put it into your Dock.

If you’re a Butler user, you can create the AppleScript directly inside of Butler. Create a new AppleScript smart item, paste in your code as above, and assign it a keyboard shortcut.

Regardless of how you set it up, just run the script (via Dock or keyboard shortcut or whatever) to disable Witch, and run it again to enable Witch. (Remember it takes about a second for Witch to become active.)

As noted, this tip may be superseded by a future release of Witch…but for now, it’s the quickest way to disable and enable Witch on the fly.

How-to: Enable Moom in Mavericks

October 23rd, 2013 by Rob Griffiths

Moom is fully compatible with Mavericks, but Apple has changed how users enable the OS X feature (access for assistive devices) that Moom (and some of our other apps) uses to get things done. Enabling this feature isn’t much harder than it was before, but it is different.

Here’s the expert version: After installing Moom 3.1, visit the Privacy tab of the Security & Privacy System Preferences panel, and place a check in the box next to Moom’s entry in the window. Once you’ve done that, Moom should work fine. (If, for some reason, it doesn’t work, please check the end of this blog entry for some troubleshooting tips.)

If you’d like a more-detailed walkthrough on getting Moom to work in Mavericks, keep reading…

First, make sure you’ve downloaded Moom 3.1 from either our site or the App Store. (Older versions are compatible with Mavericks, but display misleading messages on launch.)

Upon first launch of Moom in Mavericks, you’ll see this dialog:

Click the Open System Preferences button; note that this is not the default, so you can’t just press Return/Enter. After clicking the button, Mavericks will launch System Preferences, switch to the Security & Privacy pane, and then activate the Privacy tab. At this point, you should see this on your screen (click for full-size view):

The new Privacy panel

Make sure you see Moom listed in the right side of the window; it will probably be grayed out and won’t have a checkmark in the box next to its name. To make Moom work, you need to click the lock icon at the bottom of the window, and then enter your administrator’s password when prompted:

After entering your password, the Privacy panel will be unlocked, and you can check the box next to Moom; once the Moom entry looks like this, you’re done:

Once this is set, Moom’s pop-up panel should appear when you hover over the green button, and all functions should work as usual.

What if Moom still isn’t working?

We’ve not had any issues with Moom not working in our testing. However, if you’ve enabled it as described above, and it’s still not working for you (or if you can’t enable the Accessibility flag), please try these fixes, in this order:

  1. Quit Moom, open Terminal, paste this command, then press Return:

    tccutil reset Accessibility

    You won’t see any output, but relaunch Moom and see if you can now enable and use Moom.

  2. Delete Moom completely (just the app), then reboot (not just logout/login, but reboot) your Mac. Then reinstall Moom from our site or the App Store, based on where you bought it originally. Note: Make sure you delete all copies of the Moom application before reinstalling. (You will not lose your custom settings.)

    Launch Moom and follow the instructions to authorize it; it should work.

  3. If Moom still doesn’t work, the next step is to try this tiny free app called AppCleaner. Install it, launch it, then drag the actual Moom application onto it. You’ll see a list of Moom-related files; do not click Delete yet! Instead, uncheck the box next to the Moom.plist file, as shown here:

    This way, you’ll save all your custom settings, and delete only the app and related support files. Once that’s set, click Delete to remove all traces of Moom (and its caches, which may be where the problem resides). Then reinstall Moom and authorize it again, and hopefully it’ll be working—we’ve had three users report success with this app so far.

    If you’d rather not use AppCleaner, you can manually delete the files shown in the above screenshot, using Finder or Terminal.

If none of the above solutions work, the final step is individualized support: Email us, and we’ll proceed to troubleshooting your particular situation.

Desktop Curtain and Time Sink updated

October 23rd, 2013 by Rob Griffiths

Today we’re releasing Desktop Curtain 3.0.1 and Time Sink 1.2.2. Neither of these are Mavericks-specific releases; they’re mainly bug fix releases with a couple small new features here and there. As with our Mavericks-specific updates, the following warning applies to these updates:

IMPORTANT NOTE: The following updates will bump the minimum system requirement to 10.7 or newer; if you’re still running 10.6, DO NOT INSTALL THESE UPDATES.

Why 10.7 or newer? Apple recently declared an old security-related API dead (i.e. deprecated), and recommended that all developers switch to the newer API, which we did. But that new API requires 10.7 or newer.

App Store buyers should see the updates shortly; direct buyers can get them through in-app updating, or by downloading directly from our site. If you care about the nitty-gritty details, make sure you check out the release notes pages for each app (Desktop CurtainTime Sink) to see what’s up.

Oh when the updates come marching in…

October 18th, 2013 by Rob Griffiths

We’ve been quiet here lately, but that’s not because we haven’t been busy. Far from it; we’ve been testing our apps with Mavericks, and making changes where necessary (mostly cosmetic in nature). We’ve also addressed a number of minor bugs that have been reported (thanks!) since our last updates. So be prepared, we’re updating nearly the entire lineup today—everything here is Mavericks-ready, for whenever Apple ships the system.

As always, direct purchasers can update within the app, or by downloading a new version from our servers. App Store buyers should see the updates (soon, if not already) in the Updates tab of the App Store application.

IMPORTANT NOTE: The following updates will bump the minimum system requirement to 10.7 or newer; if you’re still running 10.6, DO NOT INSTALL THESE UPDATES.

Why 10.7 or newer? Apple recently declared an old security-related API dead (i.e. deprecated), and recommended that all developers switch to the newer API, which we did. But that new API requires 10.7 or newer.

So what’s new and improved today? It’s quite a list…

  • Butler 4.1.16: A number of behind-the-scenes updates for improved Mavericks compatibility, and a couple minor bug fixes.
  • Leech 2.2: We’ve fixed a fuzzy date bug, improved the ‘resume download,’ and squashed a couple of bugs.
  • Moom 3.1: Lots of goodness here, but the biggie is that you can now specify resize dimensions as a percentage of available space. We’ve also changed how custom names work for saved window layouts, added a new AppleScript command, and made a number of other little changes. Check out the Moom release notes page for all the details.
  • Name Mangler 3.3: The big news here is that Mavericks users can use Tags in renaming operations. We also fixed a couple of minor bugs, and added a checkbox to the Terms List dialog that will make Name Mangler check the source file for updates. Full details on the Name Mangler release notes page.
  • Witch 3.9.3: We’ve updated the “how to enable” text for Mavericks users, and worked around a glitch for those using XtraFinder.
  • If you’re scoring at home, that’s five apps updated; the missing suspects (Desktop Curtain, Keymo, Time Sink, and Usher) all have updates in the works, and we hope to have those out shortly as well. Even without updates, those apps will work fine on Mavericks—so if you’re upgrading your OS, you should be in good shape with all of our apps, assuming you apply the updates we have released.

Saying Goodbye to ‘Buy with Google’

June 24th, 2013 by Rob Griffiths

If you didn’t see the news, Google recently announced that they would be shutting down Google Checkout come November, 2013. Here at Many Tricks, we presently offer Google Checkout as one of our three payment options (direct credit card and PayPal are the other two).

When we relaunched Many Tricks in 2010, having Google Checkout was important, as it was the only alternative to PayPal available to our customers. As such, Checkout accounted for over 20% of our sales in that first year.

But over time, this 20% figure began to drop—even before we added support for direct credit card transactions as a third buying option, it seemed people were moving away from Checkout. Then, when we did add direct credit card purchases, Checkout fell even further. How far? So far in 2013, Checkout accounts for less than 5% of Many Tricks’ buyers.

Given that Google is walking away from Checkout this fall, and looking at Checkout’s greatly-diminished importance to our customers, we’ve made the decision to turn off Checkout at the end of June. So on June 30th, no earlier than 6PM Pacific time, Google Checkout will no longer be available as an option on our site.

If, in the future, we find a decent alternative to Google Checkout that works with our transaction processing house, we’ll see about adding them to our site as a third purchase option. For the short term, though, you’ll be able to choose between using PayPal or paying directly via credit card.

Name Mangler and Butler updates released

June 11th, 2013 by Rob Griffiths

We held these off for a day, so as to not steal the thunder from Apple’s WWDC keynote. But now that that’s over with, we’re releasing Name Mangler 3.2 and Butler 4.1.15 into the wild.

Name Mangler 3.2 adds support for Notification Center, and the ability to highlight spaces (including special emphasis on leading, trailing, and double spaces) in your filenames. We added/fixed some other stuff, too—for more details, check out the release notes. Direct buyers can get the update via in-app updating, or by downloading the new version from our site. App Store buyers should see the update in the App Store application (if not now, then shortly).

Note: If you’re running OS X 10.6 or 10.7 and downloaded or updated to Name Mangler 3.2 earlier today, please check again for updates. We just pushed out Name Mangler 3.2.1, which fixes a post-rename crashing bug.

We’re sorry we didn’t catch this one in our testing prior to release. We’ve given ourselves a good talking to, and we’ll do our best to make sure it doesn’t happen again.

Butler 4.1.15 fixes a couple of minor bugs and updates how Butler handles clipboard content. The Butler release notes page contains the details on these thrilling changes. Update within the app, or by downloading the new version from our site.