Aperture Picasa Export Plugin

I'm looking for a Picasa plug in for aperture, the one that I have does not work with the most recent update to 3.3.2. Any recommendations would be greatly appreciated.

Which one do you have?

Similar Messages

Any Flickr Export plugin available for Aperture 3?

I was happy to see Flickr included in Aperture 3, but to say the least, it really *****.
The worst thing is that it applies my own keywords to all the uploaded images. I don't want the (full) names of peoples in my pictures to display at Flickr and having my local-language keywords on my images probably doesn't help Flickr where most users are speaking english (compared to my local language).
Basically I wish the Flickr export feature would allow me to either "not sync keywords" or modify my keywords to determine if I want them exported or not - like Lightroom does.

Thanks for the warning Martin. I already know from iPhoto's flickr export that you gotta be careful. I guess the iPhoto/Aperture flickr export is great for those wanting REAL simplicity, but if you want to adjust just one or two settings, it's a no-go and it kinda *****
I hope there's an AP3 flickr export plugin out there? I would be willing to spend $10 on it.

Pixelpost export plugin for Aperture

I found an export plugin for Aperture to send photos to Pixelpost blogs. I'm posting this here in case someone searches the discussion forums looking for one. The link is:
http://www.pixelpost.org/extend/addons/aperture-pixelpost-plugin/
or from the developer's site:
http://www.macroni.be/index.php?x=plugin
His comments:
"APP (Aperture Pixelpost Plugin) uploads the selected picture from your Aperture library to you pixelpost blog without having to export the picture first, and then uploading it manually."
I've tested it with APP v 1.3, Aperture v 2.1.4, OS X 10.6.1, Pixelpost v 1.7.3. The plugin does work, but when you export more than one photo, they all have identical metadata information. You'll have to rename and retag in the Pixelpost control panel. The plugin also does not remember your Pixelpost login information between sessions. In spite of these problems, it is a useful plugin for us Pixelpost users.

Hey - I downloaded it and sent $ the day he put up the note EXCELLENT implementation, flawless installation and FAST uploading. Do yourself a favor if you're a Smugger. As said above, a marriage of two great products!!
david
MP, PB12 Mac OS X (10.4.8)

How can I remove the Facebook Exporter Plugin (32-bit) designed for AP2?

Now that I have A3 which has native ability to export to Facebook, I wanted to delete this plugin I have used and downloaded from the plugin page.
This plugin does not create/provide a plugin that is supposed to reside in the Library/Application Support/Aperture/Plug-ins instead there is a package file and an installer; the developer who created this (and who according to post on his site) no longer is actively developing it.
So it isn't an easy case of just removing the plugin from that directory.
For those who use this plugin does anyone know how to remove it?

Yes, it's stil in the export menu. I also had the flickr exporter that was developed by another developer and initially that was in the export menu as well in Aperture 3. I went to the plugins folder and removed the plugin then when I restarted Aperture the flickr plugin was removed (as expected).
But this Facebook plugin never created a "plugin" per se (a spotlight search indicated some files with the extension ".h" in the Library/Frameworks folder but I'm not sure what that means...).
Consequently there never was a plugin in the Plugin folder to delete, hence my dilemma.

IPhoto 7.0.1 update destroyed Picasa Uploader plugin

I accepted the iPhoto 7.0.1 update this afternoon. After doing so, I could no longer export my photos to Picasa Web albums, which I have been doing flawlessly up until this update.
When I click on iPhoto and do File > Get Info, the Picasa Uploader plugin is active in the list, but the feature does not appear in the Export wizard.
I removed the old plugin and reinstalled it. Still no luck with the Picasa Web album export. It will not show up in the Export wizard even after reinstalling. Please don't cancel my ability to use this feature!!

check with Google to see if (or when) there is a new Picasa uploader plugin that works with iPhoto 7 - until they relase their updated plugin you wll have to export photos to your desktop and upload them the old way
Larry Nebel
Message was edited by: LarryHN

Export plugins

I've been playing with various online photo albums, flickr, picasa and gallery, and it's really nice that there are export plugins available for all three of them. However, I have some problems with two of them: the picasa and gallery plugins from Übermind (0 problems with the flickr plugin from Connected Flow).
What happens is that the upload hangs or that the plugin doesn't seem to want to export at all.
I've tried to contact Übermind to get some help in tracking down the problem but haven't received any answer. Does anyone have a suggestion for what the problem could be? (I'm using the latest versions of the plugins etc)

No answer

Watch me write an export plugin

I have started blogging my experience writing an export plugin for Aperture:
http://homepage.mac.com/bagelturf/cocoa/rwok/rwok.html
It's actually pretty straightforward, but then I'm not very far along yet. The idea behind the plugin is that it exports images and gives them random names. Later I will add other randomness. I am calling it Random Wok.

The only way to do that would be with a script or automation plugin.
An export plugin assumes that you are going to be doing the file format writing (without calling back to Photoshop file IO).

Delete Export Plugin?

I have some old Export Plugins in Aperture. How do I delete them so that they do not show up under my export command in Aperture?
Kevin

Delete them via Finder. They are in either
/Library/Application Support/Aperture/Plug-Ins
or
~/Library/Application Support/Aperture-Plug-Ins

How to get the destination path in an photoshop sdk export plugin when using a batch action?

Hello,
I've written an exporter plugin (not save-as) that exports a given file to a custom format.
I was able to open a file selector dialog and choose a path that is then transported to the saving location.
Now my problem is: Another intended use is batch exporting many files. The user records an action with the export step and then applies a batch on it.
The PS batch window allows you to select the destination to be a directory where the exporter should write the data. Fine.
Now how do I get this path? When running in batch mode the silent flag is set for my plugin so I do not spawn a file selector dialog to annoy the user.
But I am also unable to obtain the path which was selected by the user in the batch window.
The SDK automation plugin Getter has some code to retrieve the path of the file and even that fails as it cannot obtain anything.
PropertyUtils.h has some PIGetWorkPathIndex and PIGetPathName functions but I always get 0 when asking PIGetNumberPaths, and get -1 with PIGetWorkPathIndex.
I would be thankful if somebody could hint me how I can retrieve directories.
It even seems impossible for me to get the path where the file is actually saved. The filter plugin called Propertizer utilizes a function called PIGetDocumentName but this only outputs the file name, not the full path.
(Just to be sure: The file on which the tests run is already saved to disk, if that matters)
Another fun part is: When I record an export step, what is the directory I am exporting into?

Ok, after lots of reading the sdk sample outbound I've realized that or plugin is broken.
When recording an action the outbound plugin stores the current path to gAliasHandle which is then recorded as a scripting parameter. Now when I execute the action I get the alias handle.
However how is this supposed to work with an export plugin and batch processing with a "destination" set to a target? Is this even possible or do I need to double click the export step in the action and "reset" the location even if that causes the entire exporter to run again?

Play from an Export plugin?

Hi,
From a complete novice at Photoshop plugins...
I am wondering if there is any underlying reason why I can't call sPSActionControl->Play() from an Import or Export plugin.
I have a very simple import and export plugin pair to port from Windows to Mac, and both call a third Listener plugin to keep track of open images. The Windows code creates a hidden window (HWND) in the Listener and messages that from Import and Export. I was thinking that I could replace this by calling Play to send a custom event to the Listener, but can't get it to work.
In fact any call to sPSActionControl fails. [The actual failure is sSPBasic->AcquireSuite in PIUSuites.h returns error 'Parm' when called for the sPSActionControl suite. sSPBasic has been set up, looks ok and sSPBasic->AcquireSuite works when called for sPSActionDescriptor suite].
As a test (to remove other sources of error), I pasted the following lines into the PluginMain function of the History plugin in the SDK sample code and this fails in the same way:
// TEMP code to test use of SPActionControl.
SPErr error = kSPNoError;
DescriptorTypeID typeID;
error = sPSActionControl->StringIDToTypeID("Save Prestige Image dictionary", &typeID);
So I'm wondering (a) is there some underlying reason why this doesn't work, or (b) is there some extra bit of initialisation or setup I need to do before calling sPSActionControl functions?
Tearing out what little hair I have left!! Any help or suggestions most welcome.
Thanks
Terry Smyth
PS Is there another way (apart from Play) to communicate from one plugin to another?

Yes, there are many reasons.
But the biggest reason is that it's an export plugin, and not an automation plugin.

CS6 Exporter Plugin doesn't open in Premiere Elements 11 (Windows)

I want to make my (Windows) exporter-plugin compatible with Premeire Elements 11.
So far, I have been gotten my exporter-plugin to appear in Adobe Premiere Pro CS6 and Media Encoder CS6, and the plugin runs there correctly.
I then followed the directions for running Premeire CS6 to create an export a preset file (*.epr). I copied copied that exported *.epr file to "OTHERS/MyCompany/MyPreset.epr" in my Premere 11 [App installation folder]. (As well as copying the plugin-binary *.prm to Plug-ins/common
In the <Publish:Share> tab, when I use the mouse to highlight 'OTHERS', I receive an error-dialog-box :
"Premiere Elements has encountered an error.
[..\..\Src\Exporter_Accessors.cpp-213]"   [Continue]
After I click continue, I don't get the dialog-box for my exporter-plugin. In the <Publish:Share> tab, I now see the warning-triangle and some text next to it: "Export Settings Invalid"

Hmm, I forgot about using Visual Studio's debugger. After some debugging, the error was triggered the first time the SDK_Exporter plugin called anything involving the <exportParamSuite>.
After a little more digging, I found that Adobe Premiere Elements 11 doesn't support the latest version of the exportParamSuite (kPrSDKExportParamSuiteVersion4).
In the CS6 SDK sample project SDK_Exporter, the function exSDKBeginInstance() grabs all of the suiteAPIs. The following call fails:
     spError = spBasic->AcquireSuite(
         kPrSDKExportParamSuite,
         kPrSDKExportParamSuiteVersion, // CS6 supports v4, but crashes in Premiere Elements 11
         const_cast<const void**>(reinterpret_cast<void**>(&(mySettings->exportParamSuite))));
The original-call returns an spError code of <kSPSuiteNotFoundError>, which is actually misleading. I changed the version-argument to v3, and the error-call went away.
     spError = spBasic->AcquireSuite(
         kPrSDKExportParamSuite,
         kPrSDKMemoryManagerSuiteVersion3, // compatible with Premiere Elements 11
         const_cast<const void**>(reinterpret_cast<void**>(&(mySettings->exportParamSuite))));
so it looks like Premiere Pro CS6 SDK's sample SDK_Exporter project requires a few tweaks to run with Premiere elements 11.

Hello! I'm using Aperture with Efex plugins and notice, what when I saving result in plugin and go back to aperture, preview mode is going to grey color and not working until I reboot Aperture. Did you saw this problem?

Hello! I'm using Aperture with Efex plugins and notice, what when I saving result in plugin and go back to aperture, preview mode is going to grey color and not working until I reboot Aperture. What is intresting - in full screen mode everything works fine. Did you saw this problem?

It seems there's a workaround here:
https://discussions.apple.com/thread/5566037?tstart=0

Iphoto and picasa exporter get stuck exporting

I am using iphoto 11 on a macbook pro running OSX 10.7.5. I have uploaded photos from iphoto to Picasa many times before, but three weeks ago, iphoto got stuck every time it tried to export photos to picasa. It simply says that my photos are uploading, but stops and gets stuck when it reaches 288k on the first photo. When I try to upload photos one at a time, it will get to the end of a photo, and then say it is "finishing upload" and never finishes. I have tried exporting directly with Iphoto to Picasa and then using my picasa uploader application, and both have the same problem. I have plenty of space on my picasa account, and it allows me to log in without any problems. Any ideas of what is wrong and how to fix the problem? Thank you.

That Picasa exporter is made by Google - though it hasn't been updated in years. But they're the folks who can help with that.
have tried exporting directly with Iphoto to Picasa and then using my picasa uploader application, and both have the same problem.
I'm not sure what that means.

Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

Raws, even if not compressed, Sould be smaller than a 24-bit Tiff, since they have only one bitplane. My T3i shoots 14 bit 18MP raws and has a raw file size of 24.5 MB*. An uncompressed Tiff should have a size of 18 MP x 3 bytes per pixel or 54 MB.
*There must be some lossless compression going on since 18 MP times 1.75 bytes per pixel is 31.5MB for uncompressed raw.

Aperture to export photos either TIFF or JPEG files, highlight and shadow transition has obvious faults, this problem solved!?

Aperture to export photos either TIFF or JPEG files, highlight and shadow transition has obvious faults, this problem solved!?

What problem?
You will have to be _a lot_ more specific if you'd like responsible feedback.
I export thousands of TIFF and JPG files a week with no obvious faults.
(Sent from my magic glass.)

Aperture Picasa Export Plugin

Similar Messages

Maybe you are looking for