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.

Similar Messages

  • Lightroom 4.4 jpeg export VERY noisy...HELP!

    Hi all,
    I have Googled and quite aware of the noisy jpeg output for v5 onwards.
    But I'm still using 4.4 and all I found on Google is threads for v5.
    Has anyone experienced this noisy jpeg export issue?
    Here's a screengrab comparing the two.

    If you're seeing a reduction of noise in the Export when you increase the Lum NR slider, then it's not a bug preventing the Lum NR from being applied.
    Besides increasing the noise-reduction and not sharpening the remaining noise during Export, the other thing to do is use sharpen masking to prevent non-edges from being sharpened.  You use the Mask slider in the sharpen section to accomplish this. 
    If you hold down the Alt key while moving the Mask slider you can see what areas will have sharpening applied.  Make sure that it is only the edges, not the areas between where noise is the only detail or texture.  The mask slider will probably be close to 100 for optimal results with a noisy image.
    You should expect there to be a little grain left in the image.

  • Aperture vs Adobe Lightroom (Beta 3) JPEG exports

    I've been beta-testing the Adobe Lightroom product and comparing it to Aperture. I'm using Aperture 1.1.1 on a MacBook Pro.
    Lightroom has some intriguing features, but I've noticed a wildly different color when exporting the same image to JPEG format from Lightroom and Aperture.
    I took the same RAW image from a shot I took with my Nikon D70 and exported a JPEG from Aperture using default settings with no color adjustment. In Lightroom I exported the same image to Photoshop, and then exported a JPEG with default settings and no color adjustment.
    Look at the difference:
    https://www.carsonmedia.com/projects/softballphotos/phototests/photocomparison.h tml
    Can anyone explain the difference? Aperture seems to export a JPEG that resembles the original.
    I'm perplexed at the difference.
    --Brandon
    15" MBP 2GB RAM OSX/XP   Mac OS X (10.4.6)  

    Yeah, looks like a colorspace issue -- I'm guessing Pro Photo, but it might not be LR's fault. Last I checked, LR actually exports PSDs, not JPEGs, in Pro Photo space to PS. So 2 possibilities:
    1. LR incorrectly tagged the PSD output, so PS doesn't realize it's Pro Photo.
    2. You didn't do a colorspace coversion in PS before saving the JPEG. Try using 'save to web' in PS -- it usually takes care of the sRGB conversion for you. Does it look correct in PS before the JPEG export?

  • RAW to JPEG export in Aperture 3

    I've imported RAW + JPEG image pairs from my camera, and selected the RAW image as the master. I understand that Aperture uses the JPEG for display purposes. My question is this: when I export (it would be the version rather than the master), as, for example, when I want to send the file to a photo lab for print processing, is Aperture working from the JPEG file it imported, or from the master (RAW)? I've made some adjustments to the white balance and lighting. I noticed that when I export the image after the adjustment, that the JPEG file is the same size as the original JPEG file that was imported as part of the pair (in this case, about 2.5 mb). I bumped up the image quality for the export, which results in a larger JPEG file that is exported (9.3 mb). What I really want to know is, is Aperture just expanding my 2.5 mb JPEG (making a larger file, but still from a lossy format), or is it creating a new JPEG file of larger size from the RAW master (and therefore, less loss)? I hope my question makes sense. I can't find any information on this in the program documentation.

    Richard GORRE wrote:
    Meaning I dont know the utility to import 2 files at the begining, except using more space.
    If somebody can explain the advantage, it will be nice BR Richard
    The main advantage to shoot and import RAW + JPEG is for the processed JPEG from your camera.
    If your camera has the ability to capture say Black & White and you grab some images that look good in camera, then when you import both into Aperture, you will have that B & W JPEG as well as the full color information RAW. If you like the JPEG enough, then the work is done. If not, you can use the full color data in the RAW and create your own B & W image using Aperture's tools.
    The same applies if you like the camera's processing for color, filters, etc. It is a matter of convenience really, not born of necessity.
    Hope that helps.

  • Aperture JPEG export behavior: How does it handle non-versioned JPEGs?

    I routinely export Aperture images as 98% JPEG. I understand what this does for my RAW images and I think I know what Aperture does for JPEG originals that I've edited.
    I wonder, however, what it does for my JPEG originals that I've not edited. I want it to simply export the original, but Aperture might instead decompress the original and recompress at 98% JPEG. This will usually increase the file size and reduce the image quality, it's clearly not a good strategy.
    If I were working in iPhoto it would, in this case, follow the better strategy of exporting the original, untouched.
    So what does Aperture do?

    "Export as 98% JPEG except when there's no version and the original is JPEG. In that case, use the original JPEG".
    Except that it's "when there's been no adjustments at all to the image, no keywords or other metadata changes, no time zone changes, the original JPEG is already in the correct colour space and has the pixel dimensions that I want."
    There's no easy way of making an AppleScript that can find out all that information, particularly whether any image adjustments have been made, or if you have added metadata which isn't in the original file.
    Ian
    P.S. From your talk of 'versioned images' I'm assuming you've got the preferences set to make a new Version if you make any image adjustments? That might make an AppleScript possible, depending on whether you do anything with metadata, and how often you use Stacks.

  • Aperture 3 can't export pictures on Yosemite.

    Aperture 3 can't export picture on Yosemite.
    Anyone can help me to fix this problem?
    Now I don't understand why I updated to Yosemite.
    Thanks

    Jest kot jabolko wrote:
    It's very easy but time consuming: I just open every folder and simply count it.
    Use Finder to search for JPGs. Select the top-most Finder folder, press "{Command}+f". Count of matching files in shown the bottom border of the window (in this example, click "ptgOther" (the name of a folder) instead of "This Mac"):

  • Export Issue - Aperture 3

    Yesterday I finally upgraded to Snow Leopard (I know, it takes me a while to do such things). Once that was complete I upgraded from Aperture 2 to 3. Everything finished processing about 2 hours ago (no more spinning "gear"). I'm attempting to export a photo (as JPEG) to a folder within a folder on my desktop. Aperture's export dialogue sees the main folder but does not see any of the subfolders within it. (by the way, when I hit "cancel" export I get the spinning beach ball - Sometimes I have to "Force Quit" Aperture, sometimes the beach ball disappears in a couple minutes).
    To test things further I chose "create a new folder" from within Aperture's export dialogue window. The folder I was originally attempting to export to is named "Claire", the new one for testing purposes is "ClaireNew". Interestingly enough, while typing the new folder's name I got a little message after typing C-l-a-i-r-e that a folder of that name already existed, yet Aperture still did not show the folder in the export dialogue. Finished typing the new folder's name and was able to successfully export photo as JPEG to the newly named folder (which took about an excruciating 4 minutes). I then attempted to export another photo to the same, newly created folder. THAT newly folder does not show up in Aperture's export dialogue even though I had just a few minutes before & "successfully" but very slowly exported to it.
    I have quit and relaunched Aperture and also restarted my computer to see if this would help. It hasn't. Any ideas as to what may be going on, if anyone else is experiencing the same problem, and/or any possible solutions would be helpful. Also, I'm wondering it perhaps Snow Leopard might still be doing something with Spotlight (being that I just upgraded to it yesterday) that's causing the sub-folders on my Desktop not to show.

    Seems like my system (either Aperture or Snow Leopard) was still processing information somewhere. After typing my above message I went back into Aperture and attempted to export a photo. HA!! Of course all folders on my Desktop as well as their sub-folders showed up. Export of JPEG took only a split second! Seriously, if I had blinked I would have missed it. Tried a couple other photos, everything worked great. Chose a shot to edit & then export. Editing tools are fantastic, but some brushes do unfortunately have a lag (at this time, anyway). Export of edited image to longer than non-edited image, but not anywhere near as long (4 minutes) as it was taking before.
    I think I'll wait a day or two before posting anymore questions if I encounter any Aperture 3 "hiccups".

  • I have imported my pictures into aperture, how do I export into jpeg files so i can share files with friends who dont use aperture ?

    I have imported my pictures into aperture, how do I export into jpeg files so i can share files with friends who dont use aperture ?

    If you want the same export settings on some or all of the images you can select all that have the same export requirements and export them as a group.
    If all the images have the same requirements then you can select them all and run the export command.

  • JPEG Export fails in some way

    Hello guys,
    we have developed a JPEG Export Plugin for InDesign server that worked fine for several years now, never having any problems. Now a strange issue occur and I need some help. When exporting an preview image of one page (containing textframes with text and tables) the preview image is correct if the dpi is smaller than 72 dpi (100% in our application). But when the dpi is equal or greater than 72 the text appears correctly on the image but the tables are missing. This problem occurs on CS4 but not on CS5 server, but there is no difference between the plugin implementation (beside the changes that were obligatory for porting the plugin to CS5). Maybe this is a known issue or someone has solution for it?
    Here is the difference between the exported images (smaller than 72 dpi and greater or equal 72 dpi):

    I do move some photos to OnOne or PS (for editing), then back to Aperture. In Aperture I would select-all (click) the photos I wanted to send to Sam's for printing then drag the selected items (all at the same time) onto the Sam's web site for processing/priniting. Another thought - on occassion I would have to switch-out flash-cards during shooting.
    Ah there you go both pieces of the puzzle solved.
    You're getting the Tiff files in Aperture from the use of the external editor. In the Aperture->Preferences->Export window is the settings for what file type to use with an external editor I'm sure your setting is Tiff.
    And then by dragging the file out of Aperture rather then exporting it you are getting the Tiff.
    IMPORTANT Point:
    By dragging the files out of Aperture you are not really exporting them you are getting the Aperture generated preview (or in the case of the Tiff files the original). The settings in the  Export window have NO effect on the image when you drag it out. In all likelihood you are not getting the size and/or resolution you think you are.
    You should be exporting the versions by using the Export Versions button in the Export window. Once the versions are exported to a folder on your disk you can then drag those to the print web site. This will ensure you are getting the image size and resolution you want.
    regards

  • JPEG Export Looks Saturated in Internet Explorer

    I see this question in many forums and online but without a solution.
    JPEG exports (sRBG) look overly saturated when viewed in Internet Explorer browser, including when uploading/viewing in Facebook, etc, etc.  In other words, the colors looks different between Lightroom and Internet Explorer.  (Colors looks the same between Lightroom and Photoshop though.)
    As point of reference, when you download a sample JPEG image from Canon EOS's website (used to show sample images from their cameras) you see that those images also use sRGB profile.  They also look exactly the same no matter how you view them (Lightroom, Photoshop, Internet Explorer, Safari, etc.).
    What is Lightroom doing to photos upon export to JPEG and you need Lightroom or Photoshop to see the same colors?
    I saw some talk about it had to do with Lightroom presets and that you had to zero those out?  Any ideas from Windows users?

    Have you got Firefox or Safari on your machine?  In which case, how do the images look in either of those browsers?  Or, if you're using Windows 7, how do the images look in Windows photo viewer?
    Also, can you say what monitor you are using please?
    I think it might be a colour management issue.  Internet Explorer is not colour managed (not even IE9), Lightroom and Photoshop are colour managed, so is Windows 7 photo viewer (but not the XP equivalent), so are Firefox and Safari (but not Chrome).  When there's a difference between how something looks in an non-colour-managed program and colour-manged programs then it's worth checking for colour management issues. 
    If your monitor has a wider gamut than sRGB, then you would expect IE9 and other non-managed programs to look over-saturated. 

  • Sharpness APERTURE vs iPHOTO~file exported from Aperture worse than iPhoto

    HEY.
    i'm recently using Aperture for my Photo Editing work.I found that everything Good and Perfect after fine tune and preview in the Window of Aperture...while Export it to the Jpeg (originaly image import from jpeg file) I found it's a bit loose from what i see in the Window Aperture...means,Loose the Sharpness...whole image getting un-sharp or s'ld i say added gausion blur of feel??
    Once i import it(the one exported from Aperture) into iPhoto and Export it (even down size to 800 of diamention) it became Sharp and nice colour tone while compare with the one which Export from Aperture!!!!
    Why?
    In the Export setting of Aperture i do set the Quality to max 12 and 300dpi even...
    Need your hand...thanks!!

    WARNING! The sharpness problem is occurring in iPhoto modifications as well! I'm running Tiger and Leopard at the same time on 2 different computers - SAME EXACT SHARPNESS problems. The problem is NOT the OS - it's in the APPLE Photo Aps!

  • Problem with Aperture 3.6 preset exports.

    I use an export preset that exports at 225dpi. If I export an image with this preset and subsequently import it into Photoshop, the resolution in PS is only 72dpi. When I open the image using Preview and look under Inspector, I notice that the JFIF data shows X and Y density as 72. This has happened since Ver 3.6.
    Images exported with a previous version of Aperture show JFIF X, Y density at 225 (the export preset value) and open in PS with 225 dpi.
    I know that I can adjust the resolution in PS but this is an inconvenience I never had until Ver 3.6. Why has this behaviour changed with Ver 3.6? Is this a bug that can / will be fixed before Aperture closes down for good?

    Frank,
    My export preset limits the dimensions in pixels at a specific dpi, corresponding with an image size in inches. I do this for some images I wish to send to external printing shops to print. I might add text using Photoshop. All worked well before with the set dpi and resulting dimensions in inches. Now, Photoshop resizes the image at 72 dpi giving much larger measurements in inches. As I've said before, this is not a big deal and I can resample under Photoshop back to my dpi of 225. But it is an extra step which I didn't need before 3.6 was released. Also, I do wonder why Aperture allows the dpi to be set to whatever the user wants only to ignore it during the actual export.
    I reckon that Photoshop (and perhaps other software as well), picks up the dpi from the JFIF information for jpeg files. So if a user wishes PS to use a specific dpi, it is a bit frustrating that Aperture only "allows" 72 dpi with this latest version.
    I have found that this only applies to jpeg exports where Aperture 3.6 mashes up the dpi. An export from Aperture in TIFF formats using a particular dpi sticks. Photoshop will retain that dpi when it opens the file.
    I have submitted a report to Aperture. I hope they look at it and consider doing something to rectify the matter. Thanks for your comments.

  • Yosemite/Aperture 3.6 No Support for Nikon D810/ Raw-S Files ?

    I am thoroughly confused.  I only recently began "drinking the Apple Kool-Aid" and am quite disturbed to learn (after upgrading to Yosemite & Aperture 3.6) that Nikon d810 Raw-S files are NOT supported....
    What gives ?  I mean you pay premium dollars for what is allegedly a premium product (MacBook Pro - Retina latest edition) you have the latest/ greatest software (Yosemite & Aperture 3.6) and the latest/greatest camera (Nikon D810) and one of the file formats is simply "Not supported ?"  Seriously ?? 
    I have had more compatibility issues with Apple and its software since being convinced by all the marketing hype to "drink the Kool-Aid" than I ever had with my ancient Dell XP PC laptop.... 
    Getting back to the point.  Why no Raw-S Support for Nikon d810 ? 
    Will there be support for the Nikon d-810 Raw-S files at some point ? If so, when ? 
    If not, WHY ? 
    What should I do with the 400 photos I took of a high school hockey game in Raw-S format given I am now drinking only the "Apple Kool-Aid?"
    Signed....
    Disgruntled Customer

    Apple can't release it until Nikon supplies them with the required information.
    Apple doesn’t routinely monitor the discussions. These are mostly user to user discussions.
    Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
    Feedback

  • JPEG Export Problem

    A few days ago, someone was commenting on funny square boxes in JPEG exports that occurred at places with spot touch up was performed. I have now experienced the same problem with a single touch up.
    D70 RAW file-->single spot touch up-->export to a hi-resolution (best possible) JPEG--> ugly spot at site of touch up.
    image available at www.printroom.com/pro/e2photo in gallery "aperture"
    The previous thread was locked, but I never saw an answer to the problem
    G5 iMac OS 10.4.3
    any help would be greatly appreciated
    steven

    hi. apologies for delay in responding - have been trying to find some time to do some testing
    i removed and re-installed the mogrify plugin and this seemed to do the trick. i couldn't replicate with the standard export, so i assume it was just a mogrify issue

  • Jpeg export output is 'smudgy' vs Lr develop display

    Hello Gang -
    I've been blaming smudged output on facebook & Flickr - but now I've seen the true culprit !
    My Jpeg export output is quite 'smudgy' vs the Develop display - and even when I use export "Email" default it is still smudgy while the Develop module displays great detail...
    what needs to be tweaked please?
    much thanks ~

    Hello -
    Ok - interesting:
    I imported a jpeg into Lr and it looks very good - long story short - Windows Photo Viewer sucks
    Viewed in Paint - looks good, viewed in FastPictureViewer - looks good.
    Viewed in flickr - Bad.  I'm installing Chrome to see if its a firefox issue
    I use firefox browser, I use sRGB as the export color space (although I see no difference among the 3 default kinds.
    I canot find info as to whether WPV makes use of embedded icc profiles, and after googling and reading - I have not found info as to how I would know if I am "even including an embedded profile with the files"
    Flickr and Facebook display my jpegs exactly as I see them in Windows Photo Viewer - which is different from how I see it in Lr's Develop Module - in that dark brown & blacks look smudgy with much reduced detail
    Bob_Peters wrote:
    Does Win7 "Window Photo Viewer" make use of embedded icc profiles?
    What color space are you using for the exported JPEG files?  Are you even including an embedded profile with the files?
    What do Flickr and Facebook do when confronted with an image containing a color profile?
    What browser are you using to view the Flickr and Facebook images?

Maybe you are looking for

  • Problem in the Table view of VC model

    Hi all, We have a created a table view using the BI query as source. the table view has say 4 fields (Serial NO., Plant key, Material and Quantity) initially before submitting the parameters, once we enter some parameters and press submit button some

  • "File Path and Name" field not displaying correctly

    Post Author: DaveWoo CA Forum: General Hello,Here's my situation: I'm currently upgrading from Crystal Reports for Visual Studio .NET 2003 to Crystal Reports for Visual Studio 2005. I have several reports (programmatically generated using VB.NET) tha

  • HT1926 I can't re-install itunes

    My itunes stopped working so I uninstalled it but now when I try and re-install it it comes up with this message saying 'Service 'Apple Mobile Device' (Apple Mobile Device) failed to tsart. Verify that you have sufficient privileges to start system s

  • OData service

    Hi Sir, I am a new SAP Developer and i am able to access record form one table success using OData services but i don't know how access record form more than one table by Parameter using OData service. I a tried last couple of for solved this problem

  • How do I remove flash pop-ups from Safari?

    Hi. Up until now, Safari has been working perfectly. I constantly have flash pop-up ads opening in new windows (e.g. MacKeeper, MediaDownloader etc) or just flashing on Youtube, my email pages and in Google. It is driving me insane. I have researched