Problem Exporting versions ---I get double exposures

To make calendars for Christmas gifts, yesterday I made a file on my Desktop to export images into. As in the past, my choices were: Export -> Versions - Jpeg Original 300. Problem: This time, all of the photos exported as double exposures - the double in all was the same, a photo from another project, appearing in the upper left corner, about 1/2 size. I first noticed this problem with a blog posting of 2 photos I did on Dec 6th. `Didn't think much of it then, and didn't do export any more versions until yesterday.
Background: I use Aperture 3, and it has been updated to 3.1.1 I tried Repairing the database and Rebuilding the database. Neither solved the problem. I considered moving the Album of Calendar photos into a whole new Library, but didn't know how to move them and maintain their size, without the Export Versions step - and hence having the same problem) F.Y.I. When I exported a Master, instead of a version, there was no double exposure.
Not one to give up and anxious to get the calendars ordered, this AM I went at it again ... same problem, but I found one way around it. i.e. When I use Export -> Version -> Original Size* --- there are no double exposures. (*vs Original Size 300) So, I'm back to the calendars adding photos via this route.
All explanations and problem solving suggestions will be appreciated. THANKS.

I didn't intentionally set up that watermark, and don't recall ever playing around to do so. But it was definitely there! Thanks to you, the problem is now solved. THANK YOU! THANK YOU! Happy Holidays!
Noreen
P.S. If I ever want to set up a watermark, I now have a sense of how to do it ... somehow scaling the watermark to be smaller and less invasive!

Similar Messages

Problem exporting versions in original size

hi!
with Aperture 3 when exporting versions in original size, I obtain 400xYYY pixels (images constrained to 400x400) showing impossibility to respect the original size.
attempting to solve the problem I have exported selecting limited wider sizes (like <4000x4000) to allow the program to keep the higher resolution. It doesn't work because then all images are forced to be exported in 4000x4000.
anybody has the solution?
thank you. david

Welcome to the forum.
Go to Aperture>Presets>Image Export, select the export preset you are using and make sure that it's on 'original size' and not on 'fit within'.
Ian

Problem exporting versions

Anyone know why i can't export versions from aperture 2 on a new imac? Exporting masters is no problem; and I'm trying to export the versions in the same way, ie, file/export/version/s but the little dialogue box doesn't even appear for me to choose where to export the versions to. Must be something very simple I've overlooked but grateful for any help.
Ta, lucas

Are you by any chance using export as jpeg to fit in 1024 by 1024? I was and found the same problem but found that other sizes work OK including custom ones I set up (25% of original in my case)

Double image when exporting versions

Hi, I exported a version of a RAW file to PS CS2 for editing with no problems but subsequently all other versions I exported from Aperture will have a double image of the initial file sandwiched together regardless whether I open it with Preview or PS. However, there are no such problem if I drag the thumbnail from Aperture to Desktop before opening it.
What have I done wrong???

Hi Firstlaunch,
what I did was wrong. I should have used "Open with external editor" instead of "Export Versions", which is low res jpegs in my preference setting. Anyway, I then open these jpegs with PS CS2 and got on with my editing. The edited pics are then re-imported to Aperture and that's where the problem began. All exported jpegs from then on will have a double-image/multi exposure of the first pic I exported.
I can't show you screen shot cos I've since trashed all the file on Aperture and re-installed everything. I still don't know what caused the problem but I'm doing it the right way now and everything's fine. Thanks.

I have been exporting lightroom webgaleries to my iweb site without any problem. Suddenly I get the error message "finder can't complete the operation because some data can't be read or written" - error code -36 - thoughts?

i have been exporting lightroom web galleries to my iweb site without any problem. Suddenly I get the error message "finder can't complete the operation because some data can't be read or written" - error code -36 - and the move to the sites folder on my idisk fails..... thoughts?

Try this community: MobileMe on my Mac: MobileMe: Apple Support Communities.
And you can continue to use iWeb for some time to come. The following will explain:
It's now confirmed that iWeb and iDVD have been discontinued by Apple. This is evidenced by the fact that new Macs are shipping with iLife 11 installed but without iWeb and iDVD.
On June 30, 2012 MobileMe will be shutdown. HOWEVER, iWeb will still continue to work but without the following:
Features No Longer Available Once MobileMe is Discontinued:
◼ Password protection
◼ Blog and photo comments
◼ Blog search
◼ Hit counter
◼ MobileMe Gallery
All of these features can be replaced with 3rd party options.
I found that if I published my site to a folder on my hard drive and then uploaded with a 3rd party FTP client subscriptions to slideshows and the RSS feed were broken. If I published directly from iWeb to the FPT server those two features continued to work correctly.
There's another problem and that's with iWeb's popup slideshows. Once the MMe servers are no longer online the popup slideshow buttons will not display their images.
Click to view full size
However, Roddy McKay and I have figured out a way to modify existing sites with those slideshows and iWeb itself so that those images will display as expected once MobileMe servers are gone. How to is described in this tutorial: #26 - How to Modify iWeb So Popup Slideshows Will Work After MobileMe is Discontinued.
In addition the iLife suite of applications offered on disc is now a discontinued product and the remaining supported iApps will only be available thru the App Store from now on.
HOWEVER, the iLife 11 boxed version that is still currently available at the online Apple Store (Store button at the top of the page) and those copies still on the shelves of retailers will include iWeb and iDVD.

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
~/Library/Application Support/Aperture/Plug-Ins/
where ~ is the home location for the current user account. All the other plug-ins however were installed in
Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

When I try to export a photo to my desktop I get the followiing error message "Export Versions Complete with Errors" any ideas why?

when I try to export a photo to my desktop I get the followiing error message "Export Versions Complete with Errors" any ideas why?

Have you tried to export different images as a test to see if it is related to the one you are getting the error on? Also try to export to a different folder other then the Desktop, again to see if the problem is connected to that folder.
Another thing to do is run the Aperture Library First Aid on the library. Hold the option and command keys down while you start Aperture. First run the Permission Repair and see if that helps. If not quit Aperture and restart and run the Library Repair and try.
Post back if you still have problems
regards

Camera shake reduction filter - double exposure blur problem

I am having a problem using the camera shake reduction filter to work on a digital image of an old photo which had a clear cut motion blur which formed a
double exposure when the camera motion stopped... this can be seen when the image is enlarged. Is it possible to sharpen these type of images ?

Can you post a small bit of it?
Usually the Shake Reduction tool will improve an image some, especially if you hunt around with the position, size, and shape of the analysis region until it gets it just about right, but there's really not a magical fix for motion-blurred images. Such an image, with whatever recovery mechanism, will not ever look as an image that's well-exposed to begin with.
-Noel

Apple Please sort out the V 11.1.4 problems as I cant get iTunes to work now. You need to have a new version asap

Please sort out the V 11.1.4 problems as I cant get iTunes to work now. You need to have a new version asap

Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
Remove all of these items in the following order:
iTunes
Apple Software Update
Apple Mobile Device Support (if this won't uninstall move on to the next item)
Bonjour
Apple Application Support
Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
Please note:
Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
tt2

When exporting versions (from DNG-to JPEG org size) they get very smal?

when exporting versions in aperture (from DNG-to JPEG org size) they get very smal? Why cant they stay the same size and kvalety as the DNG?

How are you exporting? If you are dragging the image out of Aperture you get the preview, you are not exporting the version.
If you are exporting then the most likely reason for what you see is the setting on the Quality slider. Remember JPG images are compressed and you will always see a difference between the original and the exported JPG.
regards

Whilst updating itunes software to latest version I get runtime error R6034 and cannot get into itunes. Is there a fix for this problem?

Whilst updating itunes software to latest version I get runtime error R6034 and cannot get into itunes. Is there a fix for this problem?

Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
(99376)

Export version : sizing problems

For sending print files to a lab, I usually click "Export Version" and set the dimensions in cm and at 300dpi. I then have a couple of photoshop actions to create a border & keyline.
Recently, since Aperture 2, these actions havn't been working.
This is because, although the versions are supposed to export at 300 dpi, when opened in Photoshop they actually show 72dpi. (they do have the correct number of pixels).
Similarly, if I open them in Preview, and try to print, it thinks the dimensions are enormous, because it is set to 72dpi.
I've tried creating a new export size, but it still always does 72dpi.
has anyone experienced this problem yet?
It's just a bit of a bore to have to write new photoshop actions because of this glitch.
adrian

I just realized something - The size as to which people are viewing the video is correct (720x480). But when I view the video, it's at 854x457. Why would this be???

I am getting doubles of every incoming email. How do I stop this problem?

I am getting doubles of every incoming email. Is this a virus? How do I stop it?

Well, at this point, since you're using Snow Leopard and I'm using Mountain Lion, I should probably bow out. It does sound like a number of folks saw this kind of thing in Mail under Snow Leopard back in 2009, but I don't know whether that was a bug or just an accumulation of lots of different issues with the same symptoms all in one place. I would refer you here for possible solutions:
https://discussions.apple.com/thread/2133249?threadID=2133249&start=0&tstart=0
Pay particular attention to anything that Ernie Stamper says there, as he is extremely knowledgeable about issues with Mail.

CR4Ev2 problem exporting to PDF containing Turkish characters

I know there are other threads with similar topics but I also know some people get irritated when people jump onto their threads with their own problems.
I am using CR4Ev2 and on my machine which I have installed Eclipse on I have no problems
exporting my reports to PDF, I have Turkish characters which display perfectly (they did not with
CR4Ev1 so thanks so much for that)
I have now exported my project as a WAR file and am trying to run it on another machine with the same
Tomcat and Java versions.
If I view the report via the CrystalReport Viewer the Turkish characters display with no hassel.
But if I try export the report to PDF all the Turksh characters now display as ?, (as they did in CR4Ev1)
Am I missing something, is there something that I am not including in my project that I need
when exporting the PDF.
I have installed Adobe Reader 9 on this new machine incase the Turkish langauge fonts were not in
my version 8, but still get funny ? characters, I even installed the Turksih version of Adobe 9 and still nothing. Is there some other files that I could have installed on my Eclipse machine that I have not installed
on the second machine.
I have tried both the following commands to export to PDF
CRJavaHelper.exportPDF(clientDoc, response, true);
and
CRJavaHelper.exportPDF(clientDoc, response, false);
both dont work.
I have also tried the following (which I used before with CR4Ev1)
ByteArrayInputStream byteArrayInputStream = (ByteArrayInputStream)clientDoc.getPrintOutputController().export(ReportExportFormat.PDF);
writeToFileSystem(byteArrayInputStream, EXPORT_OUTPUT); // EXPORT_OUTPUT = "c:\test.pdf"
private void writeToFileSystem(ByteArrayInputStream byteArrayInputStream, String exportFile) throws Exception {
          //Use the Java I/O libraries to write the exported content to the file system.
          byte byteArray[] = new byte[byteArrayInputStream.available()];
          //Create a new file that will contain the exported result.
          File file = new File(exportFile);
          FileOutputStream fileOutputStream = new FileOutputStream(file);
          ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream(byteArrayInputStream.available());
          int x = byteArrayInputStream.read(byteArray, 0, byteArrayInputStream.available());
          byteArrayOutputStream.write(byteArray, 0, x);
          byteArrayOutputStream.writeTo(fileOutputStream);
          //Close streams.
          byteArrayInputStream.close();
          byteArrayOutputStream.close();
          fileOutputStream.close();
But that also does not work.
Please can someone tell me what they think I am missing.
Oh, another note with the CRJavaHelper.exportPDF(clientDoc, response, false); command
It does work but I do get the following error in my console (both the Eclipse machine and the new one).
org.apache.jasper.JasperException: java.lang.IllegalStateException: getOutputStream() has already been called for this response
06-Feb-2009 15:06:52 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response
     at org.apache.catalina.connector.Response.getWriter(Response.java:610)
     at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
     at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
     at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
     at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:188)
     at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118)
     at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77)
     at org.apache.jsp.Report_002dviewer_jsp._jspService(Report_002dviewer_jsp.java:263)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Thread.java:619)
But as I said it seems to work fine apart from the Turkish character issue on the new machine)
Is this part of the problem or a seperate issue??
Thanks all for looking at this.
Darren

Ted,
I have double checked the Java version and infact reinstalled jdk6u7 (multilanguage version) just to be
100% sure, but that did not help.
ON my Eclipse machine the Fonts are as follows
Verdana(Embedded Subset)
     Type: TrueType
     Encoding: Built-In
but on the other machine it is different
Verdana
    Type: TrueType
    Encoding: Ansi
    Actual Font: Verdana
    Actual Font Type: TrueType
So that does appear to be the problem, but the question is what controls this?
As I said the project is exactly the same (same WAR file) so what I have done differently or what am I
missing in the new enviroment.
I set the "Text file encoding" for the whole project to UTF-8 before I exported the project (in Eclipse)
but that didnt help. I even set the properties of each report to UTF-8.
I am sure I am missing something simple.
The only other difference is Im running XP Pro on Eclipse machine but W2KSP4 on the other, but
surely that is not the issue.
Cheers
Darren

I am having problems exporting my time lapses from quick time pro i need to save my files as photo jpegs but the standard video compression window will not open fully,

i am having problems exporting my time lapses from quick time pro i need to save my files as photo jpegs but the standard video compression window will not open fully, it just keeps my mac (old 1.6Ghz 2.5 GB sdram G5 still good for most stuff i need) spinning for ever but i can see compression type H.264 selected and the other setting but i can not select any other options as it still thinking but never opens! why is this happening how do i get round it?
my work flow is: 300 images shot on a 5d mark II medium jpegs opened in Light Room cropped to 16:9 then exported and opened in quick time i can save a .mov H264 giving me files sizes of 14 mb for a 16 second time lapse, mp4 9 mb. the only way i can get large files is saving as a self contained movie then i get 300mb files.
i need to save my files 1920 x 1080 photo jpeg codec as i want HD quality.
i am sure there is a simple way round this?
thanks guys!

It is very difficult to offer troubleshooting suggestions when the "os version" you are using is unknown as each os has their own troubleshooting solutions.
How large is your hard drive and how much hard drive space do you have left?

Problem Exporting versions ---I get double exposures

Similar Messages

Maybe you are looking for