Installed 10.5 last week and now when I try to record video and save as a QT movie, it saves it with extension, .mo, and therefore it won't open. Also my hot keys won't work.
Any thoughts?

First, do you have the latest version 2.1.2?

Hello thewoventhread,
Like halprinp suggested, make sure you're running version 2.1.2 as that's our Leopard compatible version. As for the shortcuts, make sure they are still enabled in your Keyboard and Mouse System Preference. They've been disable for some users after the update. Hope this helps

No problems here using Snapz Pro with Mac OS X 10.5 and now 10.5.1. I am using Snapz Pro 2.1.2. Image and movies seems to be saved fine, and my keyboard shortcuts are working fine as well. I noticed that the 10.5.1 update did mess up some of my custom keyboard shortcuts for other apps, so I second checking those.

I do have a problem with 2.1.2 on OS 10.5.1 (PPC G4 Cube 1.3GHz, 1GB RAM).

I recently purchased Snapz Pro as a part of the MacHeist Bundle 2008.

I installed Snapz Pro and it worked just fine (being invoked with SHFT-CMD-3) until I restarted. Now when I press SHFT-CMD-3, the Snapz Pro interface doesn't appear. Instead, a screen snap file simple is saved to my Desktop. Each time I press SHFT-CMD-3, another SS file is saved to my Desktop. Before I restarted though, pressing SHFT-CMD-3 would call up the Snapz Pro interface each time, allowing me to take screen shots or video as I please -- which is what is supposed to happen.

Please note that Snapz Pro is loading just fine when I restart. I know this because after the blue screen and I see the SnapzProX splash screen appear. I also clicked on Accounts in the System Prefs and I see that Snapz Pro X appears in my Login Items.

I read through the Snapz Pro documentation. It didn't talk about my specific problem, but I did confirm I have version 2.1.2 of Snapz Pro.

I decided to use the Uninstaller app to "Uninstall Both." After that, I trashed the preferences, located here: Hard Drive/Users/your_username/Library/Preferences/ com.ambrosiasw.snapz.plist. I then reinstalled Snapz Pro.

After reinstalling, Snapz Pro worked great again. Pressing SHFT-CMD-3 would bring up Snapz Pro every single time. Perfect! But alas, I then restarted my Mac and was back to square one (pressing SHFT-CMD-3 now creates a SS file on my Desktop without calling up Snapz Pro).

I then double-clicked the Snapz Pro X app in the Applications folder. Snapz Pro then opened. I clicked the Preferences tab. I then changed the hot key several times, with many different modified combinations. Every single time I invoked the new modifier it worked to create a SS file on my desktop, but it won't invoke the Snapz Pro interface first.

So this is a very odd problem. Snapz Pro is clearly making the screen shots and saving them to my desktop, but the Snapz Pro interface no longer appears when I restart my computer after a fresh install.

Also, I opted to register during my first installation of Snapz Pro, but it told me that it couldn't connect and it would retry when I restarted. I don't know if that has anything to do with the problem or not. I don't see how it could. Regardless, when I double-click the Snapz Pro app and then click the About tab, I see "Licensed to: 2xxxxx" which confirms the software is unlocked on my Mac.

I look forward to your advice on resolving this problem.

when you startup does anything get logged to Console.app with respect to Snapz Pro failing to launch? and the same question for when you invoke snapz?

-rudy

Thank you for the reply.

You're going to have to guide me when it comes to the Console. I don't even know where to look. With the Console open, I see the following in the Log List:

LOG DATABASE QUERIES
LOG FILES

Both have triangles to the left of them and when clicked, they open up to reveal a various bits of info. The LOG FILES section is by far the most complex, with so many logs here and there it boggles my mind. I filtered for "ambrosia" and "snapz" in the system.log but found nothing. So again, you need to tell me WHERE to search and WHAT to search for.

I also pressed CMD-SHFT-3 with Console open. I didn't see anything pop out at me, so if something is being written to a log somewhere, I have no idea where it is.

Please guide me.


UPDATE:

Since App Zapper 1.8 came in my MacHeist 2008 Bundle, I decided to give that a try, hoping a complete Uninstall and then Fresh install might help. In my original post above, I mentioned that I did use the Ambrosia uninstaller, but that doesn't uninstall everything, as evidenced by the fact that when I install it again, I don't need to register. So I dragged Snapz Pro on App Zapper. App Zapper zapped 19.21MB in the following files:

Snapz Pro X (app in /Applications/Snapz Pro X)
com.ambrosiasw.snapz.plist (/Library/Preferences)
Snapz Pro X License (/Library/Preferences)
Snapz Pro X Application.pkg (receipt)
Snapz Pro X (folder in /Applications)
Snapz Pro X (folder in /Library)

I confirmed all those files were in my Trash, then logged out, then back in, then emptied trash, and finally I restarted. I reinstalled Snapz Pro and invoked it with Shift-Command-3. It brought up the Snaps Pro Interface (as it should), but then I noticed that my Registration information was already in Snapz Pro. This is showing that even App Zapper cannot zap all the files Snapz Pro installs. I am guessing there are hidden files that Ambrosia has strewn around my hard drive somewhere. I am not very happy about that. I truly cannot have a complete uninstall if those hidden files are not also deleted.

Anyway, I restarted. Upon booting to the desktop I saw the Snapz Pro splash. I then waited 30 seconds and pressed CMD-SHFT-3. Nope. Dead. I get a SS saved to my Desktop in the exact same manner as I would had I not installed Snapz Pro. No Snapz Pro interface appears.

So if someone can tell me where all these hidden files are, I can try deleting those and trying another fresh install. But honestly, I have my doubts if even that would work. Ambrosia, is Snapz Pro 2.1.2 truly OS 10.5.1 compatible? I bought the MacHeist Bundle 2008 primarily for Snapz Pro. Please help me solve this problem in short order.

And no, nothing is special about my OS 10.5 install either. I am using it on a PPC G4 running at 1.3GHz with 1GB RAM. When I installed Leopard, I did a clean install. I didn't even use Migration Assistant afterward, instead opting to pull over my prefs one by one, by hand to ensure I have a bullet proof OS 10.5 install. And until I installed Snapz Pro, none of the other Leopard compatible apps have given me any trouble.

I look forward to your reply.

Thank you.

PROBLEM SOLVED!

Being totally dissatisfied with this wicked problem, and not having received any help in this thread, I spent the afternoon today (mostly in vain) trying different things and Googling for Snapz Pro problems similar to mine. I happenstanced across an excellent tip on how to PROPERLY uninstall Snapz Pro (something Ambrosia's uninstaller doesn't do, for reasons unknown to mortal man):

COPY THE FOLLOWING AND PASTE INTO TERMINAL IN OS X

#START
rm -rf ~/Library/Snapz\ Pro\ X/
rm -rf ~/Library/Logs/CrashReporter/Snapz\ Pro\ X.crash.log
rm -rf ~/Library/Preferences/.DS_Store\
rm -rf ~/Library/Preferences/ByHost/.GlobalPreferences.*.plist
rm -rf ~/Library/Preferences/com.ambrosiasw.snapz.plist
rm -rf ~/Library/Preferences/Snapz\ Pro\ X\ License
rm -rf /Library/Receipts/AmbrosiaAudioSupport.pkg
rm -rf /Library/Receipts/Snapz\ Pro\ X\ Application.pkg
rm -rf /Library/Receipts/Snapz\ Pro\ X\ *\ Installer.pkg
exit
#END

1. Next, go to your Applications folder and trash the Snapz ProX folder. Empty trash.
2. Restart.
3. Reinstall Snapz Pro.
4. Restart.
5. It now works!

I'm now satisfied. But not knowing WHY this problem occurred in the first place still bothers me, because who knows if it could happen again. I certainly hope not!

For what it's worth, I also found then even after this PROPER uninstall, when I reinstalled Snapz Pro I found that my ID code was already entered. So there is either yet another deceptive, hidden file stored somewhere on my drive with this information or my DMG was altered when I installed. Either way, it's not something that makes my mind rest easy.

Anyway, I've confirmed Snapz Pro 2.1.2 does indeed work in OS 10.5.1 -- albeit with a few hurdles in my case.

Hello-
Sorry for your troubles, and nice work on finding the solution on your own, but to be frank, I don't know how uninstalling, and then installing those items would address the issue.

In doing some research on this, I've found people are having lots of problems with global hotkeys on Leopard.

Some threads I found indicate that World of Warcraft in full screen mode is to blame, but Blizzard has looked into it and filed the problem as a bug with Apple.

Others indicate that the ScreenSaverEngine can get hung causing the problem.

And still others indicate that unplugging and then replugging the USB keyboard can solve the problem.

Let me know if the problem comes up again.

You would need to remove the "Snapz Pro X License" file sitting in your preferences folder. If you opted to install Snapz for all users on the computer, check for the same file in the Macintosh HD/Library/Preferences folder. Nothing was hidden or deceptive. Glad your problem is now resolved

I just installed the latest version of Snap on my Leopard 10.5.1 Mac, and I have the same problems that JDW had. I've tried all the fixed listed above, but no luck. What to do?

Hello 63strat,
Sorry for your frustration. Just to avoid confusion, can you please state what problem you are having? Can you verify if Snapz is running by looking in the Activity Monitor in your Utilities folder? Snapz should be listed as a process. If you open Console in your Utilities folder, do you see any errors?

63strat, I don't know if this will help you, but I actually did what Evan suggested (prior to his suggesting it) -- I definitely did delete the License file. But that didn't help me. The only thing that did help me is using those terminal commands to wipe out everything, including hidden files. Now if you copied those commands and then pasted into Terminal properly (and didn't get any errors), then go through and confirm if those files were in fact deleted by Terminal. If you did that, then go to System Preferences > Accounts > Login Items. Click once on Snapz Pro in that list and then press the "-" button to delete it. RESTART. Now go through the steps I gave above, including the Terminal commands. The reason for this is because Snapz Pro loads different things in memory. Killing the login item means it won't load in memory, allowing you to delete everything without hassle. Finally, follow Evan's advice and check that the License file is gone. Then RESTART again for good measure, and THEN reinstall Snapz Pro. I just did this again on an external firewire drive running Tiger and what tripped me up was the fact I forgot to delete out that login item. Do that first and all should be well.

With all this said, my problem has been solved. But it was solved only by using the Terminal to delete EVERYTHING, including "hidden files in disguise." And my appeal was and continues to be that Ambrosia do the polite thing and update its Snapz Pro uninstaller to delete EVERYTHING, as does the set of Terminal commands present above. That is the proper and honest thing to do. Don't misread me. I like Ambrosia and its products, especially Snapz Pro. I simply feel the uninstaller should uninstall everything, leaving nothing behind.

Thanks for the reply. Exactly as JDW described: I installed Snapz Pro and it worked just fine (being invoked with SHFT-CMD-3) until I restarted. Now when I press SHFT-CMD-3, the Snapz Pro interface doesn't appear. Instead, a screen snap file simple is saved to my Desktop. Each time I press SHFT-CMD-3, another SS file is saved to my Desktop.

It's most definitely running in the activity monitor. I've uninstalled it with the uninstaller and the script, then reinstalled. Same problem. The script didn't seem to work though. I pasted it in Terminal, but wasn't offered the opportunity to hit the Enter button to run the script (or is pasting it enough?). Did not check for error in the Console, right now the program remains uninstalled; I've already wasted enough time (2 hours) trying to get it to work.

Hello 63start,
What happens when you double-click the application itself? If you could reply to me via e-mail (help@ambrosiasw.com), I can send you a debug version of Snapz which may help us pinpoint your problem. We'd also appreciate any errors listed in your console.log (open Console in your Utilities folder) and your system profile.

The screenshots left on your Desktop are from the built-in function of the OS, not Snapz. If Snapz is running, it should be invoked by the same key command where you would see our capture options. As we are unable to replicate this problem so far, your help would be appreciated. Thanks!

In my case, when the problem exists (i.e., a restart results in Snapz Pro not working), double-clicking the app always brings up Snapz Pro. I reported that in my earlier discussions in this thread. Of course, 63strat needs to confirm this on his machine. But I am guessing his situation parallels my own. In other words, the app works fine. But something is preventing the CMD-SHIFT-3 keyboard combination from pulling up the Snapz Pro interface after restarting -- resulting in a screen snap made by OS X.

While reflecting on this problem in an effort to further help fellow users (like 63strat) who are having the same problem as I, I did further testing. I was shocked to find the problem still occurring on my Tiger external drive today! And I had followed my own advice and restarted several times without problem. The problem was gone when I last booted into my external drive. But today, it's broken again. (It still works fine on my internal drive though).

You see I put Snapz Pro on my internal drive, which runs Leopard. But I also installed Snapz Pro on my external Firewire drive which runs Tiger (because I sometimes need to boot into Tiger to solve my Leopard incompatibility woes). Anyway, when I tried CMD-SHIFT-3 today on my external Tiger drive, Snapz Pro did not appear and OS X vomited up a screen shot on my Desktop. How wicked this problem is! But oddly enough, Snapz Pro still works fine on my internal drive.

So I am guessing that there is some kind of "session recording" or "installation instances" recoding going on here? Does Snapz Pro not like the fact I have it installed on more than one drive attached to my computer? I cannot find any logical explanation for why this is happening. Because when I tested my external drive a couple weeks ago, Snapz Pro was working fine. I would then reboot into my internal drive and I then rebooted again into my external drive. It worked fine. But again, today when I tested SHIFT-CMD-3 on my external Tiger drive, Snapz Pro did not appear. But yes, the splash screen did appear, and yes, double-clicking the app launches Snapz Pro just fine, and yes, I confirmed that it's registered.

This is a very strange and bizarre problem! I eagerly look forward to an official solution from Ambrosia, as I am sure 63strat does.

Hello JDW,
What happens if you create a new user account on your system and test in there? The best I can suggest is that you contact us via e-mail and we can send you a debug build and request for more info. The log file produced may help us figure out what is happening on your systems. The issue is isolated and can not be reproduced here yet.

I've been using the debug build of Snapz Pro since early February this year (since the time of my last post in this thread). Funny, but I've never had a single problem with the debug build! I've not posted back here since then because, like I just said, I've not had any problems. In fact, the only reason I am posting here today is simply to report good things about the debug build. But going back to the normal build gives me problems, as I've reported before.

Interesting. Well, at least I have a version of Snapz Pro that gives me no trouble!

Thanks!

Hey JDW,
Thanks for the update!

I'd been battling a problem where Snapz prefs were persisting despite repeated Snapz Uninstaller & AppZapper efforts. Once I trashed the license file, as Evan explained, my problem finally went away.

The problem, btw, had been that the object selection action wasn't working properly. Snapz couldn't figure out what object was being selected, making it useless. I assume it was a corrupted pref but it took deleting the license for Snapz to stop defaulting to the corrupted behavior. A little weird fer sure.