You are here

16 posts / 0 new
Last post
Convert Master File Format Not Working #1
Flipkal's picture
by Flipkal
February 4, 2012 - 8:09pm

Like Santiago, I can't this script to work. I've re-downloaded and installed it. I've made sure it is locked. It worked when I downloaded it about a month ago. I'm using AP3 v 3.2.2. Any help? Thanks!

Phil in Midland

PhotoJoseph's picture
by PhotoJoseph
February 4, 2012 - 10:10pm

Philip,

Did you lock it after installing before running it the first time?

@PhotoJoseph
— Have you signed up for the mailing list?

Morten Scheel's picture
by Morten Scheel
February 5, 2012 - 10:18am

Hi Philip,

I need to know what happens when you run the script. Any error messages?

Morten.

Santiago Martinez-Caro's picture
by Santiago Martinez-Caro
February 5, 2012 - 2:32pm

No error message, and script is locked. Images simply disappear from my projects and they are not in the trash. Library still says the number of images supposed to be in the project, but it is empty after the conversion. It does this once every 4-5 times I launch the script.

Flipkal's picture
by Flipkal
February 5, 2012 - 3:02pm

Joseph, After I downloaded the script and installed it in the ~Library/Scripts/Aperture folder, I locked it. I then re-started Aperture. When I run the scripts, after selecting the images, I see NO activity or error messages. I’m using AppleScript 2.2.1 (editor version 2.4.2 release 131).
I’ll try anything to get this script working again, since I find it very valuable. Thanks.

Phil in Midland

Flipkal's picture
by Flipkal
February 5, 2012 - 5:36pm

I opened Console immediately after running the script and copied what I found. I don’t know why it is looking inside the ScriptingAdditions directory. The script is in the Scripts/Aperture folder.

2/5/2012 11:40:55.825 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
2/5/2012 11:40:55.825 AM [0x0-0x194194].com.apple.AppleScriptRunner: AppleScript Runner: OpenScripting.framework - scripting addition “/Library/ScriptingAdditions/Adobe Unit Types.osax” declares no loadable handlers.
2/5/2012 11:40:55.826 AM AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.

Phil in Midland

PhotoJoseph's picture
by PhotoJoseph
February 5, 2012 - 7:33pm

Philip, Santiago, Morten,

I’m at a loss but Morten do you know why according to Console it’s looking for Adobe Unit Types? Could a recent installation of some Adobe software be getting in the way? Philip, Santiago, have either you of installed or updated anything from Adobe lately?

Let’s be sure that the DMG you have hasn’t somehow been damaged as well. If you can email me your receipt from the original purchase, I’ll look it up and reactivate the download for you. If you don’t have that, just let me know what email address you used for purchase (your PayPal email) and I can look it up that way.

@PhotoJoseph
— Have you signed up for the mailing list?

Morten Scheel's picture
by Morten Scheel
February 5, 2012 - 8:06pm

Thanks for the feedback to the both of you. I was able to look up a possible solution that I hope will work for the both of you.

You’ll find both a description of the issue and a link to download the updated (64-bit) version of Adobe Unit Types here: http://kb2.adobe.com/cps/516/cpsid_51615.html

The short version is that Photoshop installs a 32-bit version, whereas the scripting environment needs 64-bits. I think Adobe Software Update should take care of it also, at least it seems to have for me.

Anyway, please let me know if it works out for you.

Morten

Flipkal's picture
by Flipkal
February 5, 2012 - 9:03pm

Joseph: I did install a Twain plugin, but have just removed it until I have to use it. (Did not seem to be the problem however). I may have updated Adobe Air or some other components, when I was prompted to do so in CS5. You might want to check this yourself and see if that effects the script. I did install the latest 10.7.3 System update in the past few days.

Morten: I downloaded the Unit types file, installed it, restarted the Mac. Tried to run the script and got the following message in Console:

2/5/2012 3:47:14.655 PM AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.

I no longer get the message referring to ‘ScriptingAdditions’. However, Joseph’s script still doesn’t run. My Mac is pretty ‘clean’, in that I don’t install any utilities that modify the GUI or Finder operations.
Thanks for your efforts with this.
Phil

Phil in Midland

Flipkal's picture
by Flipkal
February 5, 2012 - 9:16pm

Well, I’m really blushing now because I think I know what the problem is. When I go to the AppleScripts menu while in Aperture, I see a script at the bottom (Convert Master File format v1.0) which I have been selecting. Why it is there, I don’t know. I now realize that I need to Select the Aperture pull-out menu and select the script from there. And now the script works as designed. Really sorry for all this hassle, but maybe some other poor soul out there is trying the same thing, and this will help him/her out. Thanks again!
Phil

Phil in Midland

Morten Scheel's picture
by Morten Scheel
February 5, 2012 - 9:21pm

Philip,
No need for blushing. Where to place script files and how to access them isn’t exactly user friendly, especially since Apple decided to hide the ~/Library folder in Lion.

To make sure I understand your situation correctly, please verify that you have two copies of the script in different folders? I would guess that one of them is unlocked and somehow corrupted.

And don’t worry about the CPSGetFrontProcess() line in the console. It’s not an error, just a warning that the method may become unsupported in the future. Besides, it’s Apple’s own AppleScript Runner that calls it, the script doesn’t request anything like that.

Anyway, I’m glad you figured it out.

Morten

Flipkal's picture
by Flipkal
February 6, 2012 - 6:43am

No, I don’t have two scripts. The one that is in the ~Library/Scripts/Aperture folder is the only one. When I’m in Aperture and pull down the AppleScript menu, I see the script name (active, not grayed) under the Heading ‘Aperture Scripts’. This is at the bottom of the menu and is selectable. This one does not work. It appears to be a list of the most recent scripts used, but I can be wrong on this. Only when I select the pullout menu item ‘Aperture’, and select the script, then it performs. Thanks!

Phil in Midland

Santiago Martinez-Caro's picture
by Santiago Martinez-Caro
February 8, 2012 - 3:25pm

To be honest I haven´t had the time to use Aperture in the last 3 days. But I seem to have a similar problem to Philip. The pull down menu has two options for the same script. One works, one does´t and it seems to change from time to time. I will get back to you if problem persists.
Many thanks.

tyeNewton's picture
by tyeNewton
June 28, 2012 - 1:27am

Hey all,

I’m running into a different issue: When I try to run the script, the only thing I notice happening is the Aperture Convert-Master Temp Folder appears on the Desktop with ONLY THE FIRST photo from my selection, as a JPEG. That folder remains there, nothing appears in the Rejected section, and all RAW files remain in place inside my project.

I’m running Aperture 3.3, so I’m wondering if the script just needs an update to work with 3.3 (being a fairly recent update to the software).

Love the idea of the script, but this is my first attempt using it, and it hasn’t worked at all. : /

tyeNewton's picture
by tyeNewton
June 28, 2012 - 1:49am

Shoot! I bet I know exactly what the problem is… Aperture 3.3 allows iPhoto and Aperture to share a library (an amazingly helpful feature), so the library I’m working with is called “iPhoto Library” … I bet the script is looking for the wrong library. Any idea of a way I can safely test/work around this?

Morten Scheel's picture
by Morten Scheel
June 28, 2012 - 6:13am

Hey Tye,

I’m sorry to hear about your problems with the script. I’ve tried to reproduce the issue you describe, but I’ve been unable to do so. The script doesn’t care if you’re working on an Aperture or iPhoto library and I haven’t had problems with either.

I really want to figure this out, but I’ll need some more information. If you feel more comfortable doing this via email, please contact me on monostratos at gmail dot com.

You may login with either your assigned username or your e-mail address.
Passwords are case-sensitive - Forgot your password?