Noodlesoft Forums

So here's a problem I've been running into with Hazel. I have a rule that is designed to open .m4v files in an external application, Identify 2, upon a rule match. For some reason, if Identify is not running when the rule is triggered, Identify crashes upon launch. If Identify is running on rule match, the application does not crash. Unfortunately, in the latter scenario, Hazel closes Identify which leaves me right back in the same situation after one file is processed.

I'm not entirely certain what to do here. Prior to using Hazel, Automator was my tool for this effort and it worked ok. I replaced Automator with Hazel due to a gradual memory leak that would occur over time and ultimately crash the host computer. Any suggestions?

I suggest contacting the author of Identify. Hazel just does a common system mechanism which opens the application. You can test Hazel out with other applications to see if they crash. If they don't then there is a problem with Identify dealing with it.