Export issues in Aperture 3

Please help! I'm about to give up on Aperture 3. I've got the trial version and I really want to buy the software but I cannot get decent exported images especially in black and white! I'm going into Aperture -> Presets and exporting in every different preset and every single image exports the exact same when I look at them side by side = lossy and soft, causing me to lose all of my contrast and sharpening effects.
Would someone be willing to give me the preset details I need to export the image so it looks EXACTLY as it does when I view it in Aperture?
Thank you!

Thanks for your feedback.
I'm importing directly from my iPhoto library. I'm not sure how the format ends up coming across when you import that way.
I use a Nikon D60 and import directly to iPhoto because I can go through the duds a lot faster there than I can in Aperture (because it runs really slow on my Macbook for whatever reason).
I do add a watermark but not always and it makes no difference in the photo quality - it always looks the same.
When I export the original imported photo it looks the same as it does in Aperture - which is strange right?! It's like my edits are coming across crappy.
I'm just viewing my images through preview on my computer but I when I upload them to my website they come across looking like crap so I know it's not just preview.
I'd appreciate any insight into why the original imported image will export and look the same as it does in Aperture but why my Aperture edited images export in such poor quality.
Thanks a million!

Similar Messages

  • Yet another export issue with Aperture 3

    Judging by a search of topics, there seem to be a myriad of problems associated with getting files out of Aperture, some of which represent occult setting issues, others which seem to be actual bugs.  I've run into an issue which seems to defy categorization, and I'm not sure if it's me doing something wrong, or if it is actually yet another bug with this software.  I've been an Aperture user since 1.0 and I have to say the current version I'm running (3.4.3) is by far the worst yet.  Anyway, enough whining.  Here are the issues:
    I'm running Aperture on a 6 core Mac Pro with Lion 10.7.5.  There are two thing happening. 
    1.  Exporting JPEGs is INCREDIBLY slow - perhaps as long as 4 or 5 minutes for a 3MB file. 
    2.  This is the one driving me batty right now.  Tried exporting a batch of images as JPEGs at the 50% original size setting.  The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2.  They are 80-100MB in size.  When I export the images to a file on my Desktop, it consistently exports 6- 10 KB thumbnails.  I've checked and rechecked my export settings and can find nothing amiss there.  Has anyone else had a similar experience?  Could the view I'm working in have anything to do with this?  I work 95% of the time in split view.
    Thanks,
    Russ

    I agree that there re a lot of posts about exporting, but a very large number of them refer to the same thing, and it's not a bug, but rather a misunderstanding.
    For instance:
    Tried exporting a batch of images as JPEGs at the 50% original size setting.
    Okay.
    The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2
    Not relevant.
    They are 80-100MB in size. 
    Not relevant either.
    Why?
    Because size refers to the dimensions of the image. So a 1,000 x 1,000 pixel image exported at 50% will turn out as 500 x 500 pixels.
    Were you expecting a jpeg between 40 and 50 MB? That's Jpeg quality or the amount of compression applied to the image. And as you're compressing a lossless format (tiff) to a lossy one, and one with an aggressive compression algorithm, he resulting Jpeg, even at high quality, will be much, much smaller, more likely in the 6 - 8 MB range.
    That's the nature - and indeed the point - of Jpegs.
    So, if you're getting 6 - 10 kb images, you're exporting at a very low Jepg Quality.
    This may also explain why it's taking so long to export. Getting rid on 99.99% of the data and compressing into 10kb is always going to take time.

  • Yosemite/Aperture 3.6 jpeg export issue

    I have recently updated to Yosemite and Aperture 3.6.  Now I cannot upload the exported jpegs to my photo site (shootproof.com).  If I pull the jpeg into iPhoto and re-export, then I can upload that file.  I don't have time to double my work flow.  What can I do to fix this issue.
    Regards,
    rharbour

    I can export the photos to jpeg without any errors.  I have tried a couple of the default jpeg settings, but still no luck uploading.  I typically export at the Aperture default full size jpeg setting, quality at 10, dpi at 72.  When exported, I can view the photos fine, and can send them to other computers/ipad/iphone and view them just fine.  I just cannot upload them to shootproof.com without an error.  Worked fine before upgrade to 3.6.
    I can open the Aperture library in iPhoto and export from there and those upload without any problems.  The difference is that in iPhoto, if I export at max the file size is 24 mb but one step down is 1-2 mb.  In Aperture, it exports full size at 7-12 mb which works for me.  I have even had shootproof.com look on their end and they said it was a Aperture issue because they couldn't upload a photo that I emailed to them for testing purposes.
    I will try the fixes that you recommended, but it will be late tonight because I have a shoot this afternoon.
    Thanks and I'll let you know how/if it worked.

  • I can't export photos from Aperture

    After upgrade to 10.9 and Aperture to 3.5 I can't export photos anymore from Aperture nor iPhoto.
    I repaired the database in the three possible ways without success.
    I would appreciate if someone could tell me what else I can do.
    Thanks

    I have the same issue.  Aperture 3.5 - just upgraded to Mavericks.  Export working fine until yesterday - now I can't get the dialogue box to appear - selecting export has no effect at all.
    Console shows:
    29/10/2013 00:40:47.292 Aperture[383]: *** Assertion failure in -[NSSecureColor initWithColor:], /SourceCache/ViewBridge/ViewBridge-46/NSSecureColor.m:32
    followed by
    29/10/2013 00:40:47.296 Aperture[383]: -[NSRemoteView viewDidMoveToWindow] caught non-fatal NSInternalInconsistencyException 'unable to convert NSNamedColorSpace System controlColor to Device RGB colorspace' with backtrace (
        0   CoreFoundation                      0x00007fff8a71041c __exceptionPreprocess + 172
        1   libobjc.A.dylib                     0x00007fff8a27de75 objc_exception_throw + 43
        2   CoreFoundation                      0x00007fff8a7101f8 +[NSException raise:format:arguments:] + 104
        3   Foundation                          0x00007fff87146c61 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 189
        4   ViewBridge                          0x00007fff9397a65c -[NSSecureColor initWithColor:] + 724
        5   ViewBridge                          0x00007fff9397a36f +[NSSecureColor secureColorWithColor:] + 48
        6   ViewBridge                          0x00007fff9399dcfb -[NSRemoteView sendFontSmoothingBackgroundColorToService:] + 40
        7   ViewBridge                          0x00007fff9399ebf5 -[NSRemoteView viewDidMoveToWindow] + 197
        8   AppKit                              0x00007fff910f71d0 -[NSView _setWindow:] + 2899
        9   AppKit                              0x00007fff910f4804 -[NSView addSubview:] + 364
        10  AppKit                              0x00007fff91108953 -[NSFrameView addSubview:] + 45
        11  AppKit                              0x00007fff91116cb5 -[NSWindow setContentView:] + 511
        12  AppKit                              0x00007fff9197c233 -[NSVBSavePanel init] + 287
        13  AppKit                              0x00007fff916fe5b9 +[NSSavePanel newRemotePanel] + 309
        14  AppKit                              0x00007fff916fe675 +[NSSavePanel _crunchyRawUnbonedPanel] + 120
        15  Aperture                            0x0000000109c119fc Aperture + 666108
        16  Aperture                            0x0000000109bb63ef Aperture + 291823
        17  AppKit                              0x00007fff912fe3d0 -[NSApplication sendAction:to:from:] + 327
        18  ProKit                              0x000000010b3d1626 -[NSProApplication sendAction:to:from:] + 101
        19  Aperture                            0x0000000109fdbe86 Aperture + 4640390
        20  AppKit                              0x00007fff91319348 -[NSMenuItem _corePerformAction] + 394
        21  AppKit                              0x00007fff91319084 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 117
        22  AppKit                              0x00007fff913684dd -[NSMenu _internalPerformActionForItemAtIndex:] + 35
        23  AppKit                              0x00007fff91368359 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 104
        24  AppKit                              0x00007fff9130f176 NSSLMMenuEventHandler + 716
        25  HIToolbox                           0x00007fff8c47b6d4 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 892
        26  HIToolbox                           0x00007fff8c47ac87 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 385
        27  HIToolbox                           0x00007fff8c48ed90 SendEventToEventTarget + 40
        28  HIToolbox                           0x00007fff8c4c4a30 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 420
        29  HIToolbox                           0x00007fff8c4f7618 SendMenuCommandWithContextAndModifiers + 59
        30  HIToolbox                           0x00007fff8c4f75c4 SendMenuItemSelectedEvent + 178
        31  HIToolbox                           0x00007fff8c4f74a5 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 94
        32  HIToolbox                           0x00007fff8c4d556e _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttjS4_S4_PK10__CFStringPP13 OpaqueMenuRefPt + 1726
        33  HIToolbox                           0x00007fff8c4d46c6 _HandlePopUpMenuSelection7 + 596
        34  AppKit                              0x00007fff91367221 _NSSLMPopUpCarbonMenu3 + 4153
        35  AppKit                              0x00007fff914d1a95 -[NSCarbonMenuImpl _popUpContextMenu:withEvent:forView:withFont:] + 192
        36  ProKit                              0x000000010b461fc2 -[NSProCarbonMenuImpl _popUpContextMenu:withEvent:forView:withFont:] + 375
        37  ProKit                              0x000000010b3c3ccc -[NSMenu(ProAdditions) _popUpContextMenu:withEvent:forView:withFont:] + 741
        38  AppKit                              0x00007fff9184506f -[NSView rightMouseDown:] + 127
        39  AppKit                              0x00007fff912e2f71 -[NSWindow sendEvent:] + 3721
        40  ProKit                              0x000000010b3f3e50 -[NSProWindow sendEvent:] + 236
        41  AppKit                              0x00007fff91283744 -[NSApplication sendEvent:] + 2021
        42  ProKit                              0x000000010b3d251e -[NSProApplication sendEvent:] + 129
        43  Aperture                            0x0000000109fdbb35 Aperture + 4639541
        44  AppKit                              0x00007fff910d3a29 -[NSApplication run] + 646
        45  ProKit                              0x000000010b3d2dca NSProApplicationMain + 333
        46  Aperture                            0x0000000109b7ef50 Aperture + 65360
        47  Aperture                            0x0000000109b7e8f4 Aperture + 63732
    timestamp: 00:40:47.296 Tuesday 29 October 2013
    process/thread/queue: Aperture (383) / 0x7fff77698310 / com.apple.main-thread
    code: line 607 of /SourceCache/ViewBridge/ViewBridge-46/ViewBridgeUtilities.m in logCaughtException
    domain: exceptions

  • Printing issues with Aperture 3 - color management

    I just made three prints of the same images, two with Aperture 3 that turned out very dark and off color, almost as it they were printed without color management or double profiles. I then printed the third by exporting the image to CS4 and printing with the same settings (rendering intend, printer settings and custom printer profile) and that print looks fine. Has anyone else run into similar problems with A#? I did not have this issue with Aperture 2.
    Thanks,
    Message was edited by: pcalvin

    I print on an Epson 2880 with Lyson inks and custom profiles. In Aperture 2 it worked perfectly, with exactly the same settings as for printing Photoshop - using the laboratory prescribed settings:perceptual and no black point compensation in Photoshop, and Adobe RGB Gamma 2.2 in the Print settings.
    Using the same profile and settings with Aperture 3, the colours are way, way off - exactly as described.
    I then tried with Aperture 3 turning off the Adobe RGB setting, so there was no colour space adjustment in the Print setting. This gave a slightly better result, but rather dead and slightly blue.
    I ran some tests with the GretagMacbeth colour chart used in preparing the profiles, which confirmed the above but also shows a lack of sharpness when printing from Aperture 3, and a blue border on three sides of the image - even though the border was set to 0.00. I have checked the printer head adjustments and run the test chart through Photoshop again to verify these are Aperture 3 artefacts.
    Unless this is resolved, it renders Aperture completely useless! (I have tried reinstalling printer drivers, to no effect).

  • How can I export photos from Aperture with a new sequence and ignore the embedded JPEG number? Have tried renumbering to no avail.

    How can I export photos from APERTURE with a new sequence and ignore the embedded JPEG number? Have tried renumbering to no avail.
    has anyone resolved this issue?
    This is now the second big Problem with using Apple's Appeture with NO apparent FIX...
    Aperture has NO DIRECT way to Burn to a CD/DVD & apparently NO way to RE-SEQUENCE the numbering system????
    ANYONE... I wish APPLE would address/fix these 2 problems... LIGHTROOM I guess is next?

    Hi David,
    Coming in and whining loudly is rude.  We are all volunteers here, voluntarily sharing our expertise so that users like you can make the most of their time with Aperture.  Speaking just for myself:  although I do care about your success with software (it's why I'm here), I don't care what software you use.  If you want to use Lightroom, do so, and post your questions in an appropriate forum.
    Burning files to a CD is a file operation done at the system level (it is built into OS X).  Aperture lets your create sharable image-format files from your Images.  You then use OS X's tools to burn those files to a CD.  Iirc, you can set up a "Burn Folder" in Finder, into which you can export files created from your Images, and with a single click burn your CD.
    Naming the files you create by exporting your Images can be tricky.  There are _many_ possibilities.  Some things can't be done.  Sequencing can be done in a number of ways (see Léonie's answer above).  What have you tried?  What was the result?  In what way did this differ from what you expected?
    --Kirby.

  • HT4007 How do I export images from Aperture to my iPad Mini?

    How do I export images from aperture to my iPad Mini?
    Berndpeter

    I am going to give it a try.
    Greetings from Mexico!

  • Bizzare export issue

    Here is a very weird export issue. Windows XP.
    Project is set at h264 1920x1080 mono audio 29.97 fps
    I have 30 shots that make up the sequence. Each shot is exactly 90 frames. I exported each sequence at h264 1920x1080 with one channel of audio. The first shot exports just fine and is 5 MB. The second shot exports at 10 MB. The third is 15 MB, the tenth shot is 50MB. But the picture is still 90 frames for each shot. BUT, when I export without audio each exported file is just 5 MB. If I look at the properties of each clip the duration of the video and audio is just 90 frames. If I open one of these clips in QuickTime Pro and re-export it as source then the files size goes back to 5 MB; same video, same audio yet with the correct file size.
    Anyone seen this before?
    Is there a setting that could be incorrect?
    -cablet

    Weird, man. Not sure what might cause that.

  • Full screen mode - Issue with Aperture freezing

    Hi I have an issue with Aperture 3 freezing if I send an image to a plug-in or external editor while in full screen dual display mode. I have to exit full screen mode first and then send to photoshop/external plugin.
    It is not a huge deal and a simple workaround but if I forget to do it Aperture will freeze and I will have to force quit the application.
    Any thoughts or suggestions welcome.
    Thanks!

    Just send a comment to Apple via "Aperture→Provide Aperture Feedback".
    IME, both full-screen mode and dual-display mode have some rough edges. (I don't expect any improvements until OS 10.7, which is widely reported to include a full re-design of full-screen mode.)

  • Why do I loose sharpness when I export out of Aperture?

    My images look almost blurred once exported out of Aperture 3.0.  !  I am finding in my reading that others have been having this problem for years!  Has Apple not fixed this yet?  I may have to go to Photoshop, but really don't want to!!!

    That doesn't sound right at all. My exports looks fine. I wonder if it could be some kind of glitch or something...
    Just out of curiosity, what do your export preferences look like? What quality setting do you have for jpegs, and what dpi for external editor file format? How about the dpi in your export presets you've been using? How about your RAW Fine Tuning sharpness sliders? (although that would affect how your images appear in Aperture, although it is subtle)
    Aperture has limited (but effective) sharpening options, and by default rendering the images are softer than what you might be used to if you used to process your RAW images with ACR (Photoshop, Lightroom). But I was able to match the default ACR rendering (in terms of sharpness, I mean) with Aperture by maxing out the sharpness sliders in RAW Fine Tuning and applying a Sharpen Edges adjustment with only mildly aggressive sharpening.
    Oh, that reminds me, which sharpness adjustment are you using? Sharpen is from the previous versions of Aperture, and is included for legacy/compatibility purposes with images that were processed in Aperture 1 & 2. Sharpen Edges is much more advanced and is generally recommended over the other.
    Doug

  • Is anyone else having issues with Aperture 3 since downloading Lion?

    Hi All,
    Is anyone else having issues with Aperture 3 after downloading the Lion update? Aperture 3 is running so ssssslllloooowwww !!! I am a sports photographer who needs this to run the way it used to with Snow Leopard. Any suggestions?????
    Thanks,
    George

    It was one of the many issues I had when I was running Lion. I watched the beach balls and the very, very slow rendering of image edits and restored back to my SL clone immediately. It was looking like Aperture 2 and my sanity just couldn't take that again.
    I have to assume that Apple must have tested Lion with Aperture 3, but you wouldn't know it from how it behaved on my system.

  • Export my entire aperture 3 library to snow leopard server?

    Hi Folks,
    How do I export my entire aperture 3 library to my snow leopard server (over ethernet).  Im currently running out of space on my mac mini hard drive?  I've had a look on the boards but there seems to be a confusion on the topic  ranging from manually drag & drop then point Aperture to the new location or export masters?
    Many thanks
    Paul

    Thanks for the replies.
    I had been under the impression that I could safely work from the Mac Server.  I want to ensure that I am not in danger of corruption/loss etc as the photo's serve my wooden toy box site.  But having read the linked support article (many thanks for the link) I have purchased a FW 2Tb drive to work from.
    Shuttersp33d - I'll follow your advice in this respect - thanks for the confirmation John.
    Just to confirm Is it best to use the export masters function to free up the space on the Mac Mini.
    Also I have a 2 Tb time capsule looking after the backups - will it back up the FW drive as a simple extension of the Mac Mini?

  • Crystal JRC PDF Export Issue

    We are experiencing a PDF export issue with Crystal JRC version 12.2.202.  The PDF report shows 1 of 3 pages but ONLY the first page is generated.  When this occurs, ALL other users that are exporting to PDF experience the same issue with any multiple page report.  I can't find any errors in the log that would indicate what the problem is.  To resolve the issue, I have to recycle the WebLogic application server that hosts  the JRC, which would indicate something gets "locked" in memory and gets cleared when the app server is bounced.
    Any ideas on how to resolve this ?

    Hi Ted,
    Thanks for the response!
    Though, the mentioned Sun JVM Bug explains the root-cause, the Bug status also state that it is not fixed yet.
    Also, we are reluctant to change the JVM Option to -Xint due to unknown impacts on JVM optimizations.
    Is there a patch released for CrystalReports to deal with this behavior? We are using CRJ runtime 11.5.7.620 and seeking for a patch on this version.
    Thanks.

  • PP CS5.5 FLV To MP4 Export Issues / Problems

    I just upgraded from Production Premium CS5 to CS5.5. I do a fair amount of converting/exporting of imported FLV files (downloaded from internet news sites) to H.264/AAC w/ MP4 wrappers using Premiere Pro (PP) and Adobe Media Encoder (AME). My equipment is a 1+ yr. old HP Win 7 Pro w/ an Intel i970 Quadcore, 12 Gb RAM and MSI nVidia GTX 470 GPU. I have never experienced any queue or export issues w/ CS5 (at least that I noticed), but I am experiencing noticeably degraded queue export and direct export problems with these files in CS5.5.
    Description: (1) The queue export times for the exact same imported FLV clip(s) using the exact same sequence settings and H.264/MP4 export settings are noticeably slower in CS5.5 (sometimes 2x, depending on the export settings, e.g. using maximum render quality) than in CS5; (2) My MSI Afterburner GPU monitoring software indicates 5-10% GPU usage during queue/export in CS5, while indicating 0% GPU usage (flatline) in CS5.5; and (3) When I attempt to direct export these files using CS5.5 I get the following error message: "The source and output audio channels are not compatible or a conversion does not exist."
    I suspect that it may have something to do with "conforming" anomalies when the FLV file is imported into PP, but I would put that squarely in the category of rank speculation on my part.
    Has anyone experienced the same or similar problems or have any insight into what may be the problem(s)? Of course, thanks for any help/insight you can provide.
    Jim

    What do you mean by a better routine?
    A better compression routine than H.264.
    Is the quality better than H.264?
    Yes.
    Does this use an MOV wrapper?
    Yes.
    Also, would it import correctly into PPro?
    Yes.
    we would import files into PPro exported out of FCP and would get a red pixelated glitch during preview and export. Does this codec solve this problem as well if it is an MOV wrapper?
    I don't know anything about FCP.
    Sorry for all the questions, just want to get things right before diving into a new codec.
    It's harmless, and free.
    Download it and run some tests.

  • When I export photos from Aperture, the pixel dimensions are halved thus losing data.  I have set the export preferences to export at original size, to no avail.  This happens even if I just drag to the desktop and then back, or if I export into my iphoto

    When I export photos from Aperture to desktop or iphoto I lose pixels.  The pixel dimensions are halved, despite setting the export preference to export at original size.  Anyone know why or how to correct this?

    Dragging an Image from Aperture exports the Preview.  Preview parameters are set on the Previews tab of Aperture preferences.
    Are you seeing the same results when you export using one of the export commands?
    Is so, confirm that the settings in the selected Image Export Preset ("Aperture➞Presets➞Image Export") truly represent those in the Image Export Preset's name.
    HTH,
    --Kirby.

Maybe you are looking for

  • Changing defaults in Illustrator CS4

    Hey folks... this was easier in CS1 and previous, but I was curious as to how to change defaults in Illustrator CS4? For example, I've customized my brush library and want to replace whatever the default brush file is with my customized brush file (f

  • Load image data into array collection without ever displaying it

    Hi all, I am starting with a String that is a path to a local file. I need to add that image (png) to an array collection without ever displaying it on screen. What would be the most direct process to get it into the type BitmapData. No matter what i

  • Can we start Node server as a windows service?

    Hi, I am starting admin server, managed server as windows service. I've also started node manager as windows service on a node machine. But, now if i want to start the node server, I am starting it from windows console. Instead of this, can i start t

  • File Attachments Temporarily Disabled: Joke? Ha! Ha!

    On Feb 22, 2010, File Attachments were disabled... with the caveat that it was temporary. That 'Temporarily' now seems to be a joke... at whose expense i wonder... Because, today, many moons and even more suns later ( i refuse to count), it still rem

  • Report off Active Directory

    Hi , I want to report off our AD directory. I used Crystal reports for that and created an OLE DB (ADO) connection and the provider was OLE DB Provider for Microsoft Directory Services. This report is able to query and successfully pull the data from