iDentify crashing when using Hazel

I use Hazel to help catalog my TV shows and Movies. I have set it up to run any movies or tv shows added to a particular folder through iDentify, which adds all the metadata to the video and then adds it to itunes.

The way it is setup has run perfectly for the last 6 months, up until I recently updated to Mountain Lion. Since this time, every time Hazel runs its shell script to open the file with iDentify, iDentify crashes. The shell script that I use is:

open -a "identify" "$1"

However if I run the file through iDentify manually, without Hazel it works fine, or if I open up iDentify before running Hazel, then Hazel will send the file to iDentify and it will work fine without crashing. It seems to only be crashing when Hazel has to open iDentify itself that it crashes.

Any suggestions?

I've had issues with this too.
I just tell hazel to open identify first before it sends the file. I do this withe an applescript:

Code: Select all: tell "iDentify" activate end tell

So my hazel rules sequence is then

Code: Select all: run applescript open file with iDentify

Seems to work fine for me. No more crashes.

Thanks for the reply, I tried to activate identify first but it would still crash. It seems that it crashes any time hazel tries to open it.

I am still having this issue also...anyone find a fix for this?

I don't know how iDentify works but you may want to contact its author to see why it's crashing. Hazel doesn't do anything special in this case and you are using the "open" command which is a system tool. I'm wondering if iDentify is expecting something in the environment that it won't get when run from a non-interactive shell.

Also, is there a reason why you aren't using the built-in "Open" action for this?

Mr_Noodle wrote:I don't know how iDentify works but you may want to contact its author to see why it's crashing. Hazel doesn't do anything special in this case and you are using the "open" command which is a system tool. I'm wondering if iDentify is expecting something in the environment that it won't get when run from a non-interactive shell.

Also, is there a reason why you aren't using the built-in "Open" action for this?

I've tried it with the built in "Open" action as well as with a shell script. I have also tried using an apple script to simply open iDentify first and then using a second hazel open command to send the file to identify and it still crashes upon Hazel opening iDentify.

However if I run the same apple script outside of Hazel, identify opens fine without crashing.

Hazel and iDentify worked great together up until the upgrade to Mountain Lion. Not sure why I have these issues now

Again, you may want to check in with the author of iDentify. As an additional check, see if Hazel can open other applications. If so, taht would point to an iDentify specific issue. You should send them the crash log if you can and see what they can make of it.

Mr_Noodle wrote:Again, you may want to check in with the author of iDentify. As an additional check, see if Hazel can open other applications. If so, taht would point to an iDentify specific issue. You should send them the crash log if you can and see what they can make of it.

I've tried contacting the author of iDentify, but no response yet. Yes Hazel has no problem opening other apps with the same files. Its weird because if iDentify is already running then Hazel sends the file to iDentify without a problem. However if Hazel has to open iDentify and send it the file, it crashes.

Not sure why, it worked so well until this Mountain Lion update.

Can someone send me an export or a screen shot of how to do this? I have been trying to do this for a while... Any help would be amazing.