[Carl Varney]

Well, I upgraded to Compressor 4 and apparently you cannot launch an Applescript at the conclusion of a setting anymore. You CAN do post conversion actions on jobs submitted through Compressor, but not within a setting and therefore, apparently, not within a droplet. Unless I’m missing something, I don’t see a way to run an Applescript or Automator workflow at the conclusion of a droplet’s work.

I hope I’m wrong…anyone?

[Carl Varney]

Same problem here. I just migrated to a new iMac with Mountain Lion. Using Compressor 3.0.5. Applescript fires off just fine on my old Mac Pro running Snow Leopard, but not on the iMac running Mt Lion. Everything else works as expected. And, like the original poster, my applescript works fine when I drag the file onto it.

This is literally the only post I’ve found on this issue. I suppose the best thing to do would be to upgrade to Compressor 4 and hope the scripts work with that.

[Carl Varney]

Thanks Jay. At $50, it seems like a no-brainer.

Does anyone out there have experience running Motion 5 on an older MacPro like my 1,1 Dual Core 2.66 GHz Xeon? We’re trying to hold off on cpu upgrades until Apple’s rumored rack mount MacPros come out.

I’m interested in hearing anyone’s experience whether the performance benefits of Motion 5 over 4 would still be noticeable on the older MacPro.

Thanks again.