Hi Joseph, welcome back! Show us some photos!
Q: I have Lion and the latest aperture 3.3.1. I use a lot the RAW to JPEG script. It was working perfect. I don't know if it was the update but it is not responding (none of the 3). I already lock them. What is the next step???
Thank u…
Hi Carlos,
You’re not the only one having problems since the last update. But I still haven’t been able to reproduce the issues on my machine, so I haven’t been able to fix them.
You could help me by opening the Console.app (use Spotlight to find it), run the scripts on some photos in your library and tell me what errors you get in the console.
Hi Joseph, I ran the Console app..
Pick some pictures and try to run the applescript.
This is the result on console app….
7/23/12 9:26:17.310 AM AppleScript Runner: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
7/23/12 9:26:17.310 AM [0x0-0x155155].com.apple.AppleScriptRunner: AppleScript Runner: OpenScripting.framework - scripting addition “/Library/ScriptingAdditions/Adobe Unit Types.osax” declares no loadable handlers.
7/23/12 9:26:17.311 AM AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.
Carlos,
While waiting for Morten to get back to you, I noticed you said you locked the scripts. However did you do that after a clean install? If you lock a script that already stopped working, that won’t help.
Photos — If you’re on Instagram there are a few there from my friends (I didn’t post any wedding ones, of course). The pro photog’s photos will be with me in a month or so.
-Joseph
@PhotoJoseph
— Have you signed up for the mailing list?
Hi Carlos, thanks for the error logs. I think I’ve found a solution for you.
I don’t know why, but AppleScript relies on technology from Adobe (Adobe Unit Types.osax) to handle image files. Earlier versions of this file was 32-bit only, and it wouldn’t work when called from 64-bit applications. It sounds to me like you need an updated version.
Go to this site, download the file and follow the instructions. I’d like to hear if it solved your problem.
Hi, Still not working, I installed the adobe unit type.osax and ran it again and this is the message i got from the app console.
7/24/12 5:33:14.509 PM AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.
any ideas?
That message isn’t a problem. If you don’t get any error messages, the script should be working. Did you restart your machine after updating the Adobe file?
JOSEPH, still not working, Im getting the same message, any ideas??? I also want to buy the presets, but im afraid to have a similar problem..
Carlos,
Like I said before, the deprecation message isn’t a problem. It simply means that the called method might be removed in the future, so you should stop relying on it. As it happens, it’s Apple’s own AppleScript engine that calls it, so they don’t exactly practice what they preach. But again, it is not a problem.
I need to know some more about your system if I’m going to help you figure this out: Machine, Operating System, Language settings, RAM. Do you have all the latest updates? Did you install or change something right before the script stopped working?
hello all,
same here so i re-installed the script (first removed it then made sure it was gone)
then i used terminal to run the script and it worked like:
$ osascript Convert\ Master\ File\ Format\ v1.0.scpt
the only thing i did different was to make the script executable for everyone.
$chmod +x Convert\ Master\ File\ Format\ v1.0.scpt
but i can’t imagine that was what did it.
carlos: just to let you know, after i upgraded to mountain lion, it worked at least 1 time before it stopped.. not sure what is happening there, just thought i’d let you know.
Hi Tom,
Thanks for the tip! If this is indeed the solution to the problem people are having, I will make sure to chmod a+x on all the scripts we sell.
Carlos, please let us know if this fixed it for you.
Morten.
Hi tom and morten, im afraid a dont really understand how to chmod a+x on the script. Can you please explain me step by step. Thank you, I really like the scripts!
No problem. It’s a command you have to run in the Terminal application (usually it’s in the Applications/Utilities folder).
1. Copy or move the script to your home folder.
2. Run the Terminal application.
3. Type (without quotes) “sudo chmod a+x ./NameOfTheScript.scpt”.
4. Enter your computer’s password if you’re asked.
5. Test if the script works.
This command makes the script executable by all accounts, and it may solve your problem. Please let us know if you need more help.
Morten.
Hi guys, so I moved the scripts from the aperture script folder to my home folder (little house icon) i ran the terminal application an typed this…
Carloss-MacBook-Pro:~ drsotomedina$ sudo chmod a+x ./Convert Master File Format v1.0.scpt
Password:
chmod: ./Convert: No such file or directory
chmod: Master: No such file or directory
chmod: File: No such file or directory
chmod: Format: No such file or directory
chmod: v1.0.scpt: No such file or directory
Carloss-MacBook-Pro:~ drsotomedina$ sudo chmod a+x ./Calculate Storage Space v1.0.scpt
chmod: ./Calculate: No such file or directory
chmod: Storage: No such file or directory
chmod: Space: No such file or directory
Carloss-MacBook-Pro:~ drsotomedina$ sudo chmod a+x ./Open Master in Lightroom v1.0.scpt
chmod: ./Open: No such file or directory
chmod: Master: No such file or directory
chmod: in: No such file or directory
chmod: Lightroom: No such file or directory
chmod: v1.0.scpt: No such file or directory
Carloss-MacBook-Pro:~ drsotomedina$
Then I copied the script files back to the aperture script folder.
I got no changes, in app console the same message than before… mmmfff
Sorry Carlos. My bad. I forgot that there were spaces in the file names.
It’s simple to fix: just add quotation marks like this.
sudo chmod a+x "./Convert Master File Format v1.0.scpt"YES! Guess what! It started working. I found that somehow the folder aperture moved from one place to another in the OSX upgrade. Also the file was corrupted because y installed a new downloaded script and started working.
Thank you guys for all the help….
YOU ROCK
That’s great to hear Carlos!
I just wish I understood why it started working.