Iphoto export plugin for simpleviewer

hi there!
i have followed the directions here
http://www.hagus.net/taxonomy/term/14
to download and install the iphoto plug for simpleviewer
( http://www.airtightinteractive.com/simpleviewer/ )
The instructions say to copy the package to
~/Library/Application Support/iPhoto/Plugins directory
By 'package' do they mean the whole folder called-
simpleFileExporter.iPhotoExport
or the contents folder inside?
or, is there supposed to be an application with its own little icon that usually happens when you istall something?
Also, my ultimate goal is to use simpleviewer's sister, postcardviewer
http://www.airtightinteractive.com/projects/postcardviewer/
so I also need to confirm that the iphoto plugin will indeed work.

Hi Bernd,
the hagus site is wrong about that... I sent them a message but didn't get any answer and they didn't change it...
*Here's the right way:*
Uncompress the file and get the "simpleFileExporter.iPhotoExporter".
2.Go to your application folder, hit ctrl and click on iPhoto
3.Select Show Package Contents
4.Search the Plugins Folder
5.Drop the "simpleFileExporter.iPhotoExporter" into the Plugins folder
Note: if Safari auto-uncompresses this file, it takes you straight to the "Contents" folder. Go to your downloads folder and get the "simpleFileExporter.iPhotoExporter" package instead
6.Restart iPhoto. You will now have a new option available to export your photos when going to File menu and Export.
For anybody else wondering about SimpleViewer have a look at point 3) of the following page
http://alyeska.altervista.org/en/iWebiWeb_Photos2.html
Regards,
Cédric

Similar Messages

Shutterfly iPhoto Export Assistant - for INTEL Macs

I have twice followed the directions on the shutterfly site -
http://www.shutterfly.com/downloads/features_mac.jsp
. I have uninstalled and reinstalled the plugin. It appears in my list of plugins and is checked when I go through the applications folder and get info on iPhoto. Still, when I select photos and click on export NOTHING happens - no tabs, no nothing. Suggestions?
Machine Name: MacBook Pro 17"
Machine Model: MacBookPro1,2
Processor Name: Intel Core Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per processor): 2 MB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: MBP12.0061.B03
SMC Version: 1.5f10
Serial Number: W86291NTTHY
Sudden Motion Sensor:
State: Enabled

I just got off the phone with Shutterfly tier 2 support and was told that the current Export Assistant for Intel Macs will not work with OS X version 10.4.8.
It seems to me that since 10.4.8 has been out way before the Intel compatible iPhoto Export Assistant for Shutterfly they might have tested it with the latest version of OS X. Also, there is no mention of compatability issues on the Shutterfly "Free Software" page, even though they are aware of the issue.
Additionally, the Shutterfly support pages only suggest uninstalling and reinstalling the plug-in, again with no mention of the fact that it does not work with the current version of OS X. Nice!

Flash Video Exporter plugin for FInal Cut Pro

Does anybody know how to install the Flash Video Exporter
plugin for Final Cut Pro so it shows up as an option in FCP?
I want to create FLVs directly from FCP.
Thanks

http://www.adobe.com/devnet/flash/articles/flv_exporter_03.htm
Scroll Down - its about mid page
This is on the intro page:
Note: You must have Flash MX Professional 2004 installed on
your machine to use the Flash Video Exporter with your video
editing application. The only exception is using the exporter in
Demo Mode.

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)

Exported Interlaced Video by SDK Exporter plugin for premiere pro cs6

Adobe Premiere Pro CS6 for Project Setting Sequence is XDCAM HD422 1080i25(50i)
I tested the Plugin AVI(Uncompress) ,output interlaced video OK no problem.
I use Premiere Pro CS6 r2 SDK
I am trying to build a plugin for interlaced video.
Problem occured when I modified by the program below:-
SDK_Exporter.cpp at subroutine RenderVideoFrame
for interlaced video with PrPixelFormat_BGRA_4444_8u or PrPixelFormat_VUYA_4444_8u
and set
renderParms.inRenderQuality = kPrRenderQuality_High;
fieldType.value.intValue = prFieldsUpperFirst;
mySettings->exportParamSuite->ChangeParam(exID, 0, ADBEVideoFieldType, &fieldType);
renderParms.inDeinterlace = kPrFalse;
renderParms.inDeinterlaceQuality =kPrRenderQuality_High;
SequenceRender_GetFrameReturnRec renderResult;
    resultS = mySettings->sequenceRenderSuite->RenderVideoFrame(mySettings->videoRenderID,
                                                                videoTime,
                                                                &renderParms,
                                                                kRenderCacheType_None,
                                                                &renderResult);
    mySettings->ppixSuite->GetPixels( renderResult.outFrame, PrPPixBufferAccess_ReadOnly, &frameBufferP);
In frameBufferP is only progressive frame not intelaced frame
Please advise what should I do in order to get interlaced frame.
Regards,
Putaporn

Adobe Premiere Pro CS6 for Project Setting Sequence is XDCAM HD422 1080i25(50i)
I tested the Plugin AVI(Uncompress) ,output interlaced video OK no problem.
I use Premiere Pro CS6 r2 SDK
I am trying to build a plugin for interlaced video.
Problem occured when I modified by the program below:-
SDK_Exporter.cpp at subroutine RenderVideoFrame
for interlaced video with PrPixelFormat_BGRA_4444_8u or PrPixelFormat_VUYA_4444_8u
and set
renderParms.inRenderQuality = kPrRenderQuality_High;
fieldType.value.intValue = prFieldsUpperFirst;
mySettings->exportParamSuite->ChangeParam(exID, 0, ADBEVideoFieldType, &fieldType);
renderParms.inDeinterlace = kPrFalse;
renderParms.inDeinterlaceQuality =kPrRenderQuality_High;
SequenceRender_GetFrameReturnRec renderResult;
    resultS = mySettings->sequenceRenderSuite->RenderVideoFrame(mySettings->videoRenderID,
                                                                videoTime,
                                                                &renderParms,
                                                                kRenderCacheType_None,
                                                                &renderResult);
    mySettings->ppixSuite->GetPixels( renderResult.outFrame, PrPPixBufferAccess_ReadOnly, &frameBufferP);
In frameBufferP is only progressive frame not intelaced frame
Please advise what should I do in order to get interlaced frame.
Regards,
Putaporn

NEED TO FIND MP4 IMPORT AND EXPORT PLUGINS FOR PREMIERE 6.0

DOES ANYBODY KNOW WHERE TO GET
SUCH ITEMS FOR THIS DINOSAUR?
ALSO WOULD LIKE TO FIND OPEN SOURCE ITEMS FOR PREMIERE 6.0
DO THEY EXIST?
WOULD LIKE TO FIND MJPEG PLUGINS AND FX OR OTHER EXPORT FORMAT PLUGINS, OR ?
THANKS FOR THE HELP WES

Wes,
I could be wrong, but IIRC, it was not until PrPro 2.0 that H.264 was added. Check me out on this.
Pr/PrPro uses installed CODEC's. There are three popular H.264 CODEC's, Apple's, Lead's and MainConcept's. Some have had issues with Apple's, but mainly with Export. I'd install one of those, and test. Let's hope that my memory is faulty on version numbers, and that Pr 6.0 CAN use the CODEC, when installed properly.
Good luck, and please report. I would be happy to be proved wrong on this one.
Hunt

Confused: Simple Export Plugin for several formats and sizes

Hi all,
I'm a bit confused about the Lightroom SDK structure - and the tiny documentation isn't helpfully at all...
I want to create a plug-in which exports several versions of each selected image (JPEGs in original size, thumbnails, etc.), TIFF-Versions, a copy of the Master-Image, etc to a specific directory.
I don't really know where to start - I explored the ftp sample plugin but but I can't find a hint where to tell Lightroom which different versions it should export.
Could anyone help me getting started? Is there anywhere additional documentation - beside the Manual and the API reference?
Thanks in advance...
Jonas

Hello Jonas;
I had a similar need and as far as I can tell, you can have lightroom export only one version of the image, but you can use that image create other versions. For example, I used imagemagic to create two versions of the original image scaled differently, copied them to a specific directory and then re-directed the exported image to another directory.
You may be able to kick off different export sessions with loading different settings(one for tiff, one for different sizes, but I have not done that, and others may be able to give some insight).
I think the easiest way is to use an external tool to generated the different sizes/formats for you and Lightroom only exports one of them, probably the one that is hardest(or needs more manual tuning) with external tools.

Format of file Exported by SDK Exporter plugin for premiere pro cs4

Hi
I am trying to build a plugin which can use a custom codec to export an imported video to h264 format.
The codec which i have to use converts a YUV420 raw video to h264 format. As given in the Premiere SDK Guide
the SDK Exporter supports uncompressed 8-bit RGB with or without alpha, and packed
10-bit YUV (v410). The initial rendering is performed by the RenderVideoFrame() function call which is called in RenderAndWriteVideoFrame().
This is then converted using various calls like ConvertFrom8uTo32f(), ConvertFromBGRA32fToVUYA32f(), and ConvertFrom32fToV410().
The problem i m facing is that i m not able to verify if the RenderVideoFrame() is working correctly and the format in which it writes.
Is there any way to check using any media player that can play the exported video. Unless i know the exact(correct) exported format
i wont be able to convert it to the required YUV420 format that i need.
Also if i dont use the ConvertFrom functions and use only the video stream written by RenderVideoFrame, can u specify clearly the format
and any media player which can play it, so as to check the working.
Thanks
Agam

Zac do you have any charts on what the pixel formats each filter supports?
If you use quirky filters (Adobe or 3rd party) you know they implemented with the mandated pixel format (BGRA_4444_8u) but probably no others. The result is that no matter what the importer/workflow/compiler combo you think you're working in you are forced to use BGRA_4444_8u from that point on in the workflow. - so much for "native" DV, HDV, MPEG2, MPEG4, CineForm, RED, etc etc etc.
Can you provide a list of what PixelFormats the Adobe filters support?
It would great to see it for CS5|4|3 & Prem Pro 2.0*
Eg:     FILTER      PIXELFORMATS
     MOTION     BGRA_4444_8u   YUVA_4444_8u   V410   DV etc etc
     BLUR          BGRA_4444_8u   YUVA_4444_8u   V410   DV etc etc
     XXXXXX     BGRA_4444_8u   YUVA_4444_8u   V410   DV etc etc
     YYYYYY     BGRA_4444_8u   YUVA_4444_8u   V410   DV etc etc
That would be a fantastic table for the user to have. That way you know when you're forcing the workflow from the native import pixelformat type (and colorspace for that matter) back to 8bit RGBA. (and potentially loosing 10bit quality and screwing up the colorspace of rec601 and rec709).
I mention Premiere Pro 2.0 because it was the last version that processed the Timeline single threaded and thus the last version that single-threaded filters can be used on. 'fortunately plugins intended for later versions of Premiere will work with it because Prem Pro 2.0 understands the version 8 API of CS3 and CS4.
For this reason (legacy plugins) I'm in the process of pulling some plugins from CS3 into the Prem Pro directory to see it they work. I'm willing to do that even though the filter I want to use is BGRA_4444_8u only. - the filter is THAT important to me.
Sidenote: this is why I'm SO disappointed with CS5. Forcing plugins to be 64bit has killed the use of hundreds of 3rd party plug-ins created over the last 20 years - many of which are End Of Life and thus will only ever be 32bit. I would have been a lot happier to have CS5 implement proxy editing (ie OffLine editing) and then on Export click a button to use the Online (ie full res) material instead. That feature would have allowed v fast timeline rendering (with or without CUDA) and much lower requirements on cpu/gpu and storage. In the few instances that you need to edit in native 2k or 4k etc then sure do it but I bet 90% of the time you can work in 1080p or lower to get your movie produced.

I need MP4 export plugin for Premiere 6.5

Hi there, i have Premiere 6.5 DV500 Pinnacle, and Windows XP but when i import something, the quality is ... Damn it!
Is very difficult upload a video in Youtube with good looking. I tried to export with indeo 4.4 ("best quality"), but i have to many problems with the conversion. Somebody help me please?

This is aimed at Premiere Pro, but may help
A link with many ideas about computer setup http://forums.adobe.com/thread/436215?tstart=0
Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

SDK_Exporter_params.cpp in SDK Exporter plugin for premiere pro cs4

This question is regarding the code in
exSDKGenerateDefaultParams(exportStdParms                *stdParms,
                                         exGenerateDefaultParamRec    *generateDefaultParamRec) function
The below function is called in the above function's code
exportInfoSuite->GetExportSourceInfo(    exporterPluginID,
                                                kExportInfo_VideoFrameRate,
                                                &seqFrameRate);
to get info for videoframerate in seqFrameRate
Then seqFrameRate.mFloat64 is compared with different values in the code segment
if(timeSuite)
     timeSuite->GetTicksPerSecond (&ticksPerSecond);
     if (seqFrameRate.mFloat64 > 29.97f &&
            seqFrameRate.mFloat64 < 29.98f ||
            seqFrameRate.mFloat64 < 0.1f ||
            seqFrameRate.mFloat64 > 60.0f) // Strange values fall into this case
            timeSuite->GetTicksPerVideoFrame(kVideoFrameRate_NTSC, &seqFrameRateTicks);
for assigning the appropriate value to seqFrameRateTicks
The problem i m facing is that the value of seqFrameRate.mFloat64
is coming out to be zero(why?).
Also, since the type of ticksPerSecond and seqFrameRateTicks
is PrTime(which is a 64 bit int), i want to know what will be the best way
to convert them into other 32 bit values(int, float etc).
Thank You
Agam

Hi Agam,
This code in the CS4 SDK was written for the initial 4.0 release, where GetExportSourceInfo(kExportInfo_VideoFrameRate) originally returned a float value. In 4.0.1, this was changed (to be simpler for developers) to return a PrTime value. So in the CS5 SDK release, the code now looks like this:
exportInfoSuite->GetExportSourceInfo(
    exporterPluginID,
kExportInfo_VideoFrameRate,
&seqFrameRate);
frameRateValues.value.timeValue = seqFrameRate.mInt64;
So it now uses the mInt64 member of the union, because PrTime is a 64-bit int.
To convert PrTime to a float, the SDK Guide, chapter 3, section on Time, reads: "When a frame rate is represented as a PrTime, the frame rate is the number of ticks in a frame duration. The current number of ticks per second must be retrieved using the callback in the Time Suite." So just divide the PrTime value by the ticks per second returned by GetTicksPerSecond().
Cheers

Export plugin on Macintosh not honoring LrTasks.startAsyncTask ?

Hi -- I need some help again!
I'm writing an export plugin for my own application.
On Windows, everything works as expected -- I can start the export and then go back to doing other tasks in Lightroom while my application does its own thing.
But on Macintosh, Lightroom hangs with the rotating "busy" icon until my application quits.
I am baffled by this behavior because I think I've wrapped everything I'm doing in calls to LrTasks.startAsyncTask.
Apparently I'm missing something about how asynchronous tasks work in Lightroom, or at least in Lightroom on Macintosh.
Do you have any suggestions about how I can get the Mac version to keep Lightroom responsive while my exported-to application does its thing?
Thanks!
--Rik
For further information...
Mac OS X 10.9, Lightroom 4.2
Here is the current structure of my ExportToMA.lua file
local myLogger        = LrLogger("myLogger")
myLogger:enable("logfile")
ExportToMA = {}
ExportToMA.outputToLog = function(param)
myLogger:trace(param)
end
LrTasks.startAsyncTask( function()
    myLogger:trace("Entering outer LrTasks.startAsyncTask function")
    LrTasks.startAsyncTask( function()
        myLogger:trace("Entering inner LrTasks.startAsyncTask function")
        local activeCatalog = LrApplication.activeCatalog()
        local frameSet     = activeCatalog.targetPhotos
        local exportSession = LrExportSession( {
            exportSettings = {
                LR_exportServiceProvider       = "net.mydomain.MAloader",
                LR_exportServiceProviderTitle = "My Application",
                LR_format                      = "TIFF",
                LR_tiff_compressionMethod      = "compressionMethod_None",
                LR_export_bitDepth             = 16,
                LR_export_colorSpace           = "sRGB",
                LR_minimizeEmbeddedMetadata    = false
            photosToExport = frameSet,
        myLogger:trace("Before doExportOnCurrentTask()")
        exportSession:doExportOnCurrentTask()
        myLogger:trace("After doExportOnCurrentTask()")
        myLogger:trace("Exiting inner LrTasks.startAsyncTask function")
    end )
    myLogger:trace("Exiting outer LrTasks.startAsyncTask function")
end )
When run on Windows, the log file contains a sequence of messages like this:
12/30/2013 10:36:48 TRACE    Entering outer LrTasks.startAsyncTask function
12/30/2013 10:36:48 TRACE    Exiting outer LrTasks.startAsyncTask function
12/30/2013 10:36:48 TRACE    Entering inner LrTasks.startAsyncTask function
12/30/2013 10:36:48 TRACE    Before doExportOnCurrentTask()
12/30/2013 10:36:49 TRACE    After doExportOnCurrentTask()
12/30/2013 10:36:49 TRACE    Exiting inner LrTasks.startAsyncTask function
   <meanwhile my application continues to run while Lightroom stays responsive>
But when run on Macintosh, this is what happens:
2013-12-30 19:01:50 +0000, TRACE    Entering outer LrTasks.startAsyncTask function
2013-12-30 19:01:50 +0000, TRACE    Exiting outer LrTasks.startAsyncTask function
2013-12-30 19:01:50 +0000, TRACE    Entering inner LrTasks.startAsyncTask function
2013-12-30 19:01:50 +0000, TRACE    Before doExportOnCurrentTask()
<indefinitely long pause while my application runs>
2013-12-30 19:02:44 +0000, TRACE    After doExportOnCurrentTask()
2013-12-30 19:02:44 +0000, TRACE    Exiting inner LrTasks.startAsyncTask function
Ideas?

> I'm confused by your application: if you already have a renditions loop, then why are you starting another export
I apologize for the confusion.
In each case I've exercised, there is only one export and one renditions loop.
The code I've been showing you is what gets executed to service a menu entry in File > Plug-In Extras. I'm focusing attention on that case because it seems more transparent. Notably, I get to specify which task the export happens on.
The renditions loop in my processRenderedPhotos function is in another script. The renditions loop gets called in two places: 1) from File > Plug-In Extras via the explicit doExportOnCurrentTask (now doExportOnNewTask), and 2) from Lightroom's internal processing of File > Export... and File > Export with Preset.
> did you try doExportOnNewTask?
I tried it just now. It did not change the behavior.
I also added some more diagnostics. Here is what happens on the Mac:
2013-12-31 01:09:31 +0000, TRACE    Entering outer LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    Exiting outer LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    Entering inner LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    Before doExportOnNewTask()
2013-12-31 01:09:31 +0000, TRACE    After doExportOnNewTask()
2013-12-31 01:09:31 +0000, TRACE    Exiting inner LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    MyApplicationUploadTask.processRenderedPhotos prefs.maPath: /Users/myaccount/Desktop/MyApplication.app/Contents/MacOS/JavaApplicationStub
2013-12-31 01:09:31 +0000, TRACE    tempPath: /var/folders/4n/2lxf6v593x5_c3lmx_jghgnw0000gn/T/temp_lre_ma_1230170931
2013-12-31 01:09:31 +0000, TRACE    nPhotos = 2
2013-12-31 01:09:32 +0000, TRACE    source path/Users/myaccount/Desktop/jpeg-8d/testorig.jpg
2013-12-31 01:09:32 +0000, TRACE    destination path: /var/folders/4n/2lxf6v593x5_c3lmx_jghgnw0000gn/T/6F05FC8E-126C-47E0-AD51-C545CE0DA66D/tes torig.tif
2013-12-31 01:09:32 +0000, TRACE    source path/Users/myaccount/Desktop/jpeg-8d/testprog.jpg
2013-12-31 01:09:32 +0000, TRACE    destination path: /var/folders/4n/2lxf6v593x5_c3lmx_jghgnw0000gn/T/6F05FC8E-126C-47E0-AD51-C545CE0DA66D/tes tprog.tif
2013-12-31 01:09:32 +0000, TRACE    just before LrShell.openFilesInApp
   <long pause here, while I let my application run for a while>
2013-12-31 01:10:00 +0000, TRACE    just after LrShell.openFilesInApp
The LrShell.openFilesInApp call happens after my renditions loop, at the very bottom of my processRenderedPhotos function, which is now separated by 3 levels of asynchronous tasks from whatever task initially serviced the menu entry.
Nonetheless, on Macintosh only, as soon as LrShell.openFilesInApp is called, Lightroom comes to a grinding halt heralded by a spinning beach ball.
It's as if, deep under the covers, LrShell.openFilesInApp (on Macintosh only!) is telling the rest of Lightroom to wait until the spawned application terminates.
I know, it sounds crazy to me too, and I've been programming for close to 45 years.
At the moment, the only way I see to work around this problem is to provide a separate "application" that is actually a spawn-and-terminate, so that LrShell.openFilesInApp will see a rapid termination of the thing that it launches. That seems like a lot of trouble for what I've been hoping is a simple misunderstanding on my part.
The one thing I can see different between my app and anybody else's is that mine is written in Java, so the thing that gets launched by LrShell.openFilesInApp is the JavaApplicationStub.
Any other ideas?
--Rik
PS.
> Do you have this problem with hard drive export too?
I doubt it, but I don't know for sure. On my test Mac, at the moment, there are not enough files to keep hard drive export running long enough to notice.

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).

Premiere Export Plugin Migration

A few years back my current company created an export plugin on Premiere Elements 7 that brings up its own complex UI for creating video content for our Simulation Product. We have a need to move forward to the latest version of Premiere Element which is now 11. And it seems that somewhere around 9 the export went away and has been replaced with the Share window. From what I can gather you can create export plugins for the share window, but you provide a set of parameters to Premiere which it then uses to build a UI. This is not going to work for our particular application, is there a way to migrate our existing plugin to the new SDK that we can still launch our own UI?

Zac,
Thanks for the quick response. In looking at the new SDK it looks like the exportcontroller example is closer to what we need, at least in that it provides access to the ecStdParms struct which has a pointer to the piSuitesPtr. We use many of the functions on this object to get infromation about the video. Is it possible to get this piSuitesPtr from the "ex" interface? I haven't been able to find access to that. Are ExportController plugins also accessible thru the Publish+Share menu?

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.

Does anyone know of a JPEG 2000 plugin for importing into iPhoto 6

I was quites surprised when I learned that iPhoto 6 had not been designed with jpg 2000 format in it. With that said, if anyone knows of a method or plugin for importing them into iPhoto I would greatly appreciate it.
Thanx,
-Al-

What do you want to do with your .jp2 files?
They import into iPhoto just fine for me. When choosing export leave the option set for the format as "Original".
If you want to convert a .jpg (or other format) to .jp2 you can do that with Preview.

Iphoto export plugin for simpleviewer

Similar Messages

Maybe you are looking for