Warning: iOS 8 Resized My Images When Exporting Via Image Capture

I have an iPad Air and I take lots of pictures. I installed iOS 8 last night. I don't like the lack of a Photo Stream and a Camera Roll, but I am willing to try new things, so I decided to clear out all the images from my iPad and start from scratch. Unfortunately, I've run into a pretty bad reproducible bug.
First I copied all the Moments (i.e. Camera Roll) Photos on the iPad to my Mac using the Image Capture app. I've been doing this for years. Everything came out fine with those photos.
I also had several iCloud shared albums so I decided to start over with them as well. Hmm, how to copy them over to my Mac? I tapped one picture and tapped "Share -> Save Image". OK that worked! So to save some time I tapped "Select" and then tapped all the pictures in the folder. Once again I tapped "Share -> Save 20 Images". Worked fine. Deleted the shared album. Did this with five other albums. Now everything is clean and I can start figuring out how this works from scratch.
OR SO I THOUGHT. Once the pictures were on my Mac, I realized the pictures I exported one at a time were fine, but the ones I exported in groups came out at odd low resolutions - 257 x 342, 256 x 384, 268 x 332, instead of the full resolution of the original pictures.
Luckily I had copies of all these pictures backed up, but this is not appropriate behavior. There was no warning that the pictures would be saved at a lower resolution. I'm not even sure the Photos app "meant" to do this. Why weren't the full sized images exported? Has anyone else had this experience? Could someone check and see if this is happening on their iPad?

The photos in this thread are the same exported files that are in the slideshow. As you advance through the slideshow(try looking at the shadows to right of the subject and his sunglasses), you'll see a change in tone/saturation that, however subtle, is quite alarming for a consistent workflow.
I always work with calibrated display profiles, and was told by Aperture Pro support to try the export with a standard, device independent profile to rule out a display profile related issue. I told them on the phone that while I'd try it, that would not be a viable solution long term for me, or any other professional, as different screens need to have independent, calibrated profiles for a consistent working environment.
That said, regardless of the display profile(I tried multiple scenarios - including calibrated profiles), the exported file is always the same on the same machines - and as I said before, distinctly unique to each machine. The display profile should have nothing to do with it anyways, as that is simple a translation of the the 'static' data onto a specific screen. I'm not saying the screens look different to me, I'm saying that the exported files are different when viewed together on any one screen.
These are all fresh installs of the same download; no settings in the software have been changed, except for what I've detailed above. The processing of the color/export should be the same from the same file in the same library with the same adjustments and the same software settings, but it's not.
Can anyone try this same test in another environment? Or does anyone know how Aperture might leverage hardware perhaps in it's processing of color?
-Ricky

Similar Messages

  • ALV Grid Display - Dump when exporting (via right click)

    Hi,
    We have an ALV filled with a dynamic table because we needed dynamic columns. Our ALV has totals and subtotals. When exporting ALV via right click I get the following error:
    OBJECTS_OBJREF_NOT_ASSIGNED
    I observed two facts:
    1.- If I disable subtotals and totals (commentig wa_cat-do_sum = 'X') export works properly, otherwise I get the dump.
    2.- Having totals and subtotals enabled, if I use export icon (top toolbar) the export works properly, but using right-click export gets the same dump.
    Our fieldcat is like this:
        CLEAR wa_cat.
        wa_cat-fieldname = g_cols.
        wa_cat-seltext_s = gi_subdiv-btrtl.
        wa_cat-seltext_l =  gi_subdiv-btrtl.
        wa_cat-datatype = 'INT4'.
        wa_cat-do_sum = 'X'.
        wa_cat-outputlen = '6'.
        APPEND wa_cat TO fs_fldcat.
    and we call ALV:
    * Call ABAP List Viewer (ALV)
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          it_fieldcat            = fs_fldcat
          i_callback_program     = v_repid
          is_layout              = s_layout
          i_callback_user_command  = 'USER_COMMAND'
          it_sort                = t_sort
    *      i_callback_top_of_page = 'F_TOP_OF_PAGE'
          i_save                 = 'X'
        TABLES
          t_outtab               = <t_dyntable>.
    Any help will be appreciated!
    Thanks,
    Josep

    Hi kat_k,
    I tried to do what you say, but I still get the same error!
    More ideas?
    Thanks!
    Josep

  • IOS 10.8.2-image capture and my canon camera

    Is there an update for image capture that will allow me to connect to my canon camera? I get a dialogue box saying this os can't use find the camera.
    Thanks,
    d440

    To see the contents of the iPhoto Library, in the Finder, right-click or control-click on the iPhoto Library and choose "Show Pacage Contents". That will open the iPhoto Library, which is a "bundle" (a folder that looks like a file unless you show contents, then you see the folder). 
    It's hidden because you can really mess iPhoto up if you add or delete something in there (by hand).
    So don't change anything in there unless you are a techie.
    I don't have a "Metadata Backup" folder in my iPhoto Library, so from there you may need more help but hopefully you'll see your file in there..
    Then you could make a new alias.
    But that is a very odd location for an alias, why would you want an alias of  the *backup* of just the Metadata of a photo? How and why did you make the alias in the first place and what is it supposed to be? Your photos are probably somewhere else in the iPhoto Library 's folders, of course the easy way to get to the photos is by using iPhoto and save/export a copy somwhere if you need a copy outside of iPhoto. Is a photo what you want?

  • Premiere CC 2014 crashes when exporting via the Queue

    Having issues exporting from Premiere CC 2014 via the "Queue". 
    My system:
    Dell Precision T5600 Workstation
    Windows 7 Pro 64 bit
    Xeon E5-2680 @ 2.7 GHz processor
    Nvidia Quadro 4000 graphics card, driver ver 347.25
    32 GB RAM
    Creative Cloud 2014
    Premiere Pro CC (2014) Up to date
    Media Encoder CC (2014) Up to date
    Exporting via the Queue has work just fine in the past.  Had this issue awhile back and cleared some cashed files which fixed the problem but don't remember what I did.   I have uninstalled and re-installed Premiere.  This took care of the problem for awhile, but now the same issue has cropped up again.
    Symptoms: When exporting a sequence from Premiere, clicking "Queue" launches Media Encoder but it doesn't completely hand off the sequence to Media Encoder.  Premiere locks up, leaving a small blank window open named "Export Media (Not Responding)".  It never completes the hand over to the Media Encoder queue.  If I reverse the process by launching Media Encoder and import the same Premiere timeline directly into the Media Encoder queue, it loads and renders just fine.  If I do an "Export" from Premiere, it works just fine.  This seems to indicate something is going on with the exchange between Premiere and Media Encoder.  I have this issues on multiple projects.
    Any help would be greatly appreciated.
    Thanks, Dave

    I'm not clear why you couldn't run it in Administrator mode ... right-click the program icon, Properties -> Compatibility, near the bottom, run in administrator mode ...
    Neil

  • Pages resize in browsers when exporting to html

    I love using pages wrap feature to place images in paragraphs exactly where I want them.
    The problem is that when I export to html and then view the page in a browser, the entire layout resizes repositions and reformats itself as you change the size of the browser window.
    Dreamweaver has a function called adding layers that will keep the layout exactly how you organized it even when resizing the browser window.
    Does pages have a feature like this that will actually allow my html pages to look exactly as I intended them to without resizing/repositioning within a browser??
    Please help if you know how to accomplish this. It would be a shame if I could not do this with pages. thank you

    David,
    The HTML export feature in Pages is pretty basic. While there are ways that you can create perfect HTML (and CSS) to simulate a printed document, it's pretty complicated to do, even by hand.
    I think the reason that Pages doesn't have a layers feature is because it's mostly meant to create printed publications. (Although it would be really really cool if Apple added something like Pages to the next iWork specifically for the web)
    It's probably not what you wanted, but you could print the document to a PDF and publish that online instead.

  • Severe anti-aliasing when exporting via compressor

    Hello all, can't seem to find anything to answer this in a search, so any help would be much appreciated.
    I seem to be getting severe anti-aliasing whenever I export anything from FCP to compressor. At first I thought the problem was with compressor, because everything looks and exports directly from FCP perfectly. But if I open compressor and import/open the exact same movie directly, compressor seems to do its job as expected, so I'm pretty sure I've narrowed it down to when I export something 'using compressor'
    I've tried various different codecs and sequence settings including totally 100% uncompressed, I've also tried upping the bit rate and everything still comes out looking exactly the same.
    I have a feeling I've accidentally changed some setting(s) somewhere (although I can't think where or how) because until a few weeks ago, everything worked just fine.
    I think I'm going to have to re-install everything, which I'd obviously like to avoid, so if anyone has any advice or suggestions I'd be very grateful.
    Thanks in advance.

    The anti-aliasing preference setting in both Illustrator and Acrobat is just a preview on screen.
    If you're going to print it preserving the jagged nature you could apply Effect > Rasterize with appropriate settings in Illustrator, for example.

  • CS3 exporting drop outs and red screen flashes when exporting via Media Encoder

    Hi forum
    I have been using Premiere Pro CS3 for a long time on my dual core PC with no issues.  Suddenly, I am now getting a major issue i MUST get sorted asap for a client is waiting for the final video.
    It is a HDV (1080i, 25fps) project/timeline.  An 8 minute video has been put together in this and every time I try to export as either MPEG2 (Blu Ray) or WMV, I am getting pixelation in certain places usually around certain cuts, or horrible red blocky pixels filling up the screen for a second or two. They seem to come always at the same point.  They don't happen when i render the timeline or show up when playing the edit itself in the timeline - just when i playback the exported video in premiere or in Windows Media Player.
    To try a workaround I exported the whole video as high quality MPEG2 (blu ray - 30mbps), which I brought into a new sequence, then I exported small sections where this problem was happening as Uncompressed Microsoft AVI and called them "patch 1", "patch 2" etc. and brought them back in and overlayed over where the problems were occuring.  The short Uncompressed AVI patches seem to have exported with no glitches, so theoretically I thought I had a clean good timeline in my new sequence made up of the MPEG 2 video overlayed in the dodgy places with uncompressed AVI "patches".  However, trying to export a new MPEG 2 master from this has created the same problems, in the same places!!! Still drop outs and still those horrid red flashes filling the screen.  Not always as bad, and some places where there were problems are ok, but I am still left with most of the problems still there.
    I am now trying to export the whole video as an AVI uncompessed but dont know if this will work and will take a very long time.
    I do have Saphire plugins, but they are not being used in this new sequence so therefore could that be a possible problem?  I thought perhaps it was the brightness/contrast filter etc so removed that from some of the problem areas, and it helped on some of them, but not on others, so not sure its anything to do with my plug in or filters.
    Any help would be greatly appreciated.
    thanks, James

    This topic is about a year old, but I thought I would reply because I just experienced this problem very recently and stumbled upon an easy solution.
    Problem: When using Adobe Media Encoder to create an HD or .m2v video file, a bright red screen will flash followed by a mashup of red blocks/pixels somewhere within the file you've just encoded. This phenomenon lasts for exactly 10 frames before clearing up.  Most likely, you won't see this problem until you import the encoded file into Adobe Encore.  It shows up on the timeline, the preview monitor and the DVD itself. It occurs on edits that the system reads as being corrupt or when a flash bulb goes off from a still camera.  Both instances make the encoding process go haywire.
    Solution: Encode your HD or .m2v file with CBR (1-pass) bitrate encoding rather than VBR (2-pass).  Don't worry about losing any quality in your video or creating unnecessarily large file sizes with your new renders. I guarantee you won't see much of a difference, if any.  I can't explain why this solution works.  It just does.
    Hope this helps you as much as it did me.

  • "internal error: assertion failed" when exporting via LR4

    I've never had problems doing this with Lightroom 3, just upgraded to Lightroom 4 and I can't seem to export anything. I also can't publish either.

    Thanks for the suggestions. I tried removing the com.adobe.Lightroom4.plist. This didn't help, still getting the error.
    Then I removed these files as well:
    com.adobe.Lightroom3.plist
    com.adobe.Lightroom2.plist
    com.adobe.Lightroom3.LSSharedFileList.plist
    com.adobe.Lightroom3.plist.lockfile
    None of that helped.
    I tried creating a new library and just importing one picture but I still get the same "internal error" VERY FRUSTRATING.

  • Resizing output when exporting to Flash/SWF

    Does anyone know if there is a way to resize the output when exporting a Keynote presentation to Flash/SWF? When you export to QuickTime, you can adjust the output size. I can't find a way to do that when exporting to Flash.

    I think that's because the Flash output displays at whatever size you want when you embed it into a website. For example, you can't create a Keynote presentation smaller than 200x200. BUT, if you create at 200x200 and then, in your embed statement, change it to 100x100, then that's how it will display on your web page.

  • When exporting an image: Image sizing, resize to fit auto changes measurements eg 22cm becomes 22,000cm. How do I fix this?

    When exporting an image in LR, any measurement entered into "Risize to fit...."automatically changes the measurement from 22cm to 22,000cm. for eg. or 33cm becomes 33,000cm.
    How do I fix this?

    Lr always uses three decimals for dimensions in the export dialog. So 22 cm is exactly the same as 22,000 cm.
    Maybe you're used to a dot as a decimal separator, and a comma as a thousand separator? If so, it probably looks like 22 thousand cm to you.
    Whether to use a dot or a comma for a decimal separator, is set in your computer's operating system.
    On windows, Control panel > Region and language.

  • When exporting files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might do 524 images but not the full 600. I've tried resetting Aperture, it's the latest version etc etc. Help please!

    If anyone can help me with this I would be seriously grateful.
    When exporting mutliple files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might make 524 pages but not the full 600. I've tried resetting Aperture and its persmission and am using the latest version of 3.
    I have 3600 images which I need to upload as sublfolders, each with their own URL and at the moment Aperture is dropping of anything from 1 to 90 images.
    This is critical as people need to see each and every on of these images online. So if a file has 600 photos in it, Aperture should make a URL with 600 full image pages. And this is what it's not doing. On small files, say 30 or so it seems to work well, it's when it gets to more than that the problem starts.
    I've used Aperture in the past under previous versions and not had this problem.
    Any help would be great.
    Thanks.
    Bob.

    Hi Jack,
    Thanks for responding (as it seems as though no one else has been able to provide any insight as of yet)! Not sure if you saw my recent post, but the version of Aperture on the 2008 MacBook has been upgraded to 3.1.2 (not sure how; I bought it in 2009, but only have OS X 10.5.8... which apparently can't house 3.1.2 of Aperture, but hey, like many other anomalies i'm encountering, I'm no longer surprised!). I am unable to upgrade it any further, as it warns me that my OS X does not fit the requirements. I exported the projects as libraries; however, like I posted before, apparently these are from too old of a version for the new Aperture (3.3.1) to handle and import.
    It's getting to the point where I'd almost pay to upgrade the OS X on my previous MacBook (10.5.8) to something newer in order to THEN update Aperture to a newer version; however, my previous MacBook simply cannot handle this (the specs are awful -- hence my decision to save up and upgrade to the newest MBP with Retina).
    I've spent hours upon hours transferring files, libraries as projects, previews, versions, even masters (though, apparently some of them aren't accessible?) with no luck. I've rebuilt the library and reprocessed everything. And this is all after having to return one MBP already since Aperture 3.3.1 is glitch-y as it is, and froze everything for having a "managed library". So, now that I know that I have to deal with a referenced library in Aperture... I just need to actually transfer my previous library to my new one (hopefully WITH adjustments since these are years worth of photos and work).
    Again, any help is appreciated. I've lost enough sleep, time, and vision health over this at this point.
    Also, I know Migration Assistant is an option, I was told that it wouldn't work properly anyway because of the different operating systems, and the potential for problems.

  • When exporting my Indesign Layout with Images, the images disappear ?

    When exporting my indesign layout the images disappear once exporting as a PDF print.
    I have had several information bubbles appear claiming I need to alter my blend space due or colour settings ?
    I have altered the blend space to rgb and still it does not work.
    I have also unlocked all the layers in attempt for this to work.
    My assignment is due in tomorrow and still I cannot get this feature to work
    any help would be great !

    CharlieLDavis1992 wrote:
    When in preview mode they do not appear either.
    If you understood my question and the images also disappear in InDesign when switching the screen to Preview mode, or Overprint Preview, that means they are set to non-printing in some way. Either they are on a layer set to non-printing, or they're set to non-printing on an individual basis in the Attributes panel.
    >I am using the latest OS,
    Not really helpful. OS X? Windows? Probably not relevant, as it turns out, for this problem, but you should be specific.
    >The pdf appears in preview
    Does that mean you are trying to use Mac Preview to view the PDF? If so, it may give you bad results. Mac Preview is not a godd general-purpose PDF viewer and is incapable of rendering complex PDF.
    The first error dialog you show is what you would get when opening a file in ID that has different document color spaces than the default settings in your color settings file. That's not a problem, and to preserve the color appearances you would leave things as they are.
    The second warning dialog indicates you are making an interactive PDF, which is RGB. If you are using CMYK images I don't think you'll avoid color shifts no matter what you do if you have transparency, but I don't do interactive PDF, so I can't give good advice here. If you are using RGB images, by all means your transparency blend space should be set to RGB.
    Can you post a screen shot of the export dialog?

  • Image distortion when exporting

    Hi all,
    I'm experiencing off and on problems when exporting RAW images from LR 3.3 to JPG. (on MacBook Pro Snow leopard 10.6.6)
    I am using Camera Raw 6.3.
    Original RAW images taken with Canon 550D.
    This is what happens:
    Original                                                                                           Result
    It doesn't matter if I resize or not, change quality of the JPG, sharpen or not, whatever.
    11 out of 140 images go wrong, the others are exported ok. Not every 11th image either.
    Exporting 1 by 1 no difference.
    What's wrong here? Has anybody had this before?
    Maybe connected: I have taken a lot of pictures of an ice hockey game some time ago. During import I've seen that some of the images imported had a similar problem. During importing I first saw a normal image, but it was changed to something simular at the end. I thought that was the memory card, as I was shooting multiple shots, low light, high iso.
    Thanks in advance
    gr. Paul

    In addition: I just switched in LR from "library" to "develop" and the image on screen switched from the before and after image in the original post!
    I have edited this picture before in LR, have cut the paiting out of it's environment, no other corrections. Probably I edited this one with an earlier version of LR.
    Changed to original image, only the crop boundaries disappear, same crazy image...
    And now in the library too, of course.
    Is it possible that when you copy pictures from one drive to another that RAW files get damaged?
    As in copy from camera to diskdrive (import LR) or from internal drive to external drive (as I did from Finder)?

  • Bridge Exports Changes Resolution from 300 to 72 dpi, resizing my image

    I like to use Bridge (CS5) to export my photographs for printing, and frequently I will use the Export feature to resize the images (e.g., 5x7 vs full size), but every time I export it recharacterizes the images as 72 dpi, vs the 300 dpi I prefer. 
    Consistent with some of the previous postings (~2 yrs ago) I have seen on this topic the exported images are now "sized" much bigger (29"x20" for what should have been ~5"x7"), and hence expectantly I haven't lost any resolution, but it's aggrevating to have the dpi changed.
    Can anyone tell me how to export without having the dpi changed?
    And while I'm at it, can anyone confirm that I'm not loosing image resolution?
    Thanks so much!!

    Can anyone tell me how to export without having the dpi changed?
    Can't find any other settings to change and just having tested it I can confirm that it sets ppi (it is pixels per inch -ppi- for a digital file which is made from pixels and dots per inch -dpi- from the ink dots of a print ) to 72.
    And while I'm at it, can anyone confirm that I'm not loosing image resolution?
    You already stated yourself that you did not loose pixels, therefor the size of the files stays the same. It is just a mater of figures. 300 ppi means a larger concentration per inch and 72 pixels per inch means a smaller concentration of pixels per inch. Given the same amount of pixels for both settings this means a smaller image dimension for 300 ppi and a larger image dimension for the 72 ppi.
    300 ppi is some 'magic' number from printed press, but it really depends on the need of the job related printing machine. If you have a small image and need to look closely it should have a larger concentration per inch to reflect its sharpness.
    However theoretically you would almost have the same visible quality when printed on 72 at billboard sizes. That's because you always have a large distance between your eyes and the bill board. If you look closely you will see the dots (because the billboard is a product of ink dots…) but of course it is not meant to study at that close range.
    The same is for judging sharpness on your computer. Ideally you do so at 100 % for correct judgement at real size pixels. But in reality there will be almost no situation you will study a print at that same distance
    Any thoughts on why these would be different?   And am I fretting over things unncessarily?
    Only guesses, the use a different algorithm or calculation scheme, in my case I tried a Canon Raw (converted to DNG) without any ACR settings then the basics applied and found that Bridge export jpeg 11 creates larger files then using PS.
    But there are some other concerns I have and that certainly would make me fretting in use of export module:
    First of all I almost never use it, merely in this cases for testing, because using the menu tools give a shortcut to Photoshop / Batch and inhere I have created several dedicated resizing and resaving actions that also places the files in preset folders.
    But with this small test I found out that
    a: it changes ppi to 72 ppi, not a very big deal but I did not asked for it nor did I wanted it.
    b: it converts my Adobe RGB color space to sRGB and I certainly did not want that without my explicit wish for this conversion, so this is more then a bit worrying to my concern.
    c: it seems to apply a sharpness that I certainly did not want to happen without my knowledge, and this rules the use of the export module out completely.
    Since I only tried a DNG file without settings or retouch/developing  in Photoshop the jpeg generated by PS was not very sharp. This makes sense to me because I have set my basic ACR to apply sharpening only to preview. There are a lot of different sharpening theories around but I use one in PS itself. So I was a bit shocked to learn that the export module did all those for me unwanted and not adjustable settings putting me completely out of control…
    So if you want to have full control about things happening under the hood yourself just start creating actions in PS, it is very easy to record an action and even more easier to play it. Instead of every time dragging files to export module and always recheck the image options (it seems to reset itself always to jpeg quality 8 on my system) only select the files you want to resize and choose menu tool / Photoshop Batch and select the wanted action. hit OK and your almost done, PS does the rest.
    The great thing of the latest PS CS6 action pallet is the extension with a so called 'insert conditional' that let's you create an 'if - then else' action for both landscape and portrait resizing actions so you don't need the 'constrain to fit' or 'fit image' option. Just once create an action for both resizing dimensions and then create a new action with insert conditional. choose If image is landscape play action…. / else play action….
    It is really a very productive way. I have a lot of actions (organized in sets for better overview) and even one that creates 4 different sizes in 4 different folders using 1 go in Bridge

  • Photoshop CS5 crashing my Mac when resizing large images

    I don't have much to explain this further but Photoshop CS5 is crashing my Mac when I resize large images.  Small images are fine but large 300dpi images crashes it without warning.  Don't know what to do.  The only other similar thing is After Effects CS5 is crashing my Mac when I trim a clip.  It completely turns off my Mac when I trim a clip. 
    I have 8gigs of Ram and am running 27" iMac Core i5
    Any help would be much appreciated!
    Thanks,
    Hal

    Hi Wendy
    Thank you for your insights. We are having the same problems here.
    It's been a headache as we bought two 27" iMacs in March 2011; and we've had even BOTH iMacs exchanged.
    After exchanging, same thing happened. We then got all 16GB of RAM on each iMac replaced.
    But we noticed that the auto-shutdown problem happens with files on 300dpi. We are contemplating on changing them to 299dpi though haha!
    Unfortunately, here in Singapore, we don't have a physical Apple store. We only have Premium Resellers.
    And the other unfortunate thing is, when RAMs are upgraded these Premium Resellers sell 3rd party RAMs.
    I supposed we'll have to deal with this for now until we have enough funds to replace ALL 32 RAMs to original Apple RAMs (which will cost abt another USD1600!!) ..
    Hope this forum helps others as much as it finally helped me understand the issue we're having.

Maybe you are looking for