Aperture to Smugmug problem

I got a new MacBook Pro with Mountain Lion (10.8) and I have Aperture 3.3.2 installed. Now the Aperture to Smugmug exporters won't work. I have used the AperturetoSmugmug plugin and tried also the Smuginfor Aperture plugin but neither one works. I presume it is about the 64 bits. Any solution to this anybody?

I had the trouble too even after running the installer again
Went to the library (Library/Application Support/Aperture/Plug-Ins/Export) and discovered that the plugin wasnt there
I then manually dragged the plugin into the export folder instead of running the installer
Then restarted Aperture
Worked for me and hope it helps

Similar Messages

Aperture Video Import Problem - from Lumix GH4: Imported clips have their dates changed to the import date. The files show up on the hard drive but many are not showing up in Aperture.

Aperture Video Import Problem - from Lumix GH4: Imported clips have their dates changed to the import date. The files show up on the hard drive with import date not created date, but many of these same files are not showing up in Aperture. Sometimes the clips actually show up with the current import but take on the video information from a previously imported file.

It was suggested I move this question to IPhoto or IMovie which I did.
Well moving to a different discussion group did not provide an answer to this question either. But what I finally did was import one batch of photos and videos into IPhoto for a given day at a time. Working with these I could change the date and times in order to get them in the original sequench taken. Then I would create an album with that batch. These would all be on the same day (IMove was closed for this phase). Then I would open IMovie, generate the thumbnails for that album, and select the album I had created. This was necessary because the importing process in IPhoto was using incorrect dates for my video so it was a real struggle finding them in IMove until I developed this approach.
I believe that this whole process was so screwy because I was importing from an external hard drive not a camera. I had these photos on a PC and did not have the original cameras to use to import directly which I am fairly sure would have made this easier!

HT202020 Using a SDHC card adapter I can import directly on my iPad2 videos (.mov) taken with a Panasonic DMC-ZS3. The same video files (same file format) imported in Aperture 3.3 cannot be synchronized with iPad. Is Aperture causing the problem?

Using a SDHC card adapter I can import directly on my iPad2 videos (.mov) taken with a Panasonic DMC-ZS3. The same video files (same file format) imported in Aperture 3.3 cannot be synchronized with iPad. Is Aperture causing the problem?

Oh, baby! This bad boy flies!! Here's what to expect:
I had 40,000 images in Aperture 3 and it was dog slow at everything. I installed 3.1 update today. It took 5 minutes to update the database and then behaved marginally better than before at ASIC library navigation. I was disappointed.
Then I QUIT the app. It took a couple of hours to "update files for sharing" with a counter that went to 110,000 images. So it must have updated every thumbnail and variation of preview. Turned it back on , and BAM. Came up fully in seconds. Paused for 10 seconds ten everything was lickrty split. For the first time ever, I can use the Projects view with all 791 projects and scroll quickly. I even put it in photos modevand whipped thru all 49,000 images!
Haven't done anybprocessing yet, but i'm liking it!!
Jim

How can I access the iphoto library using windows pc? Upgrading to aperture solves my problem?

How can I access the iphoto library using windows pc? Upgrading to aperture solves my problem?
My home network is used both by my macbook and my wife's windows pc. Considering that, I would like to know if we can share our pictures with each other (specially because I intend to store all of them into a NAS storage - WD My Cloud, probably).

No you can not - neither iPhoto nor Aperture has any cross platform capability
You can share photos with the PC using MyPhotoStream or Shared PhotoStreames
You can not share the iPhoto library
And you can not put the iPHoto library on a NAS - it MUST always be on a volume formatted Mac OS extended (journaled) and mube on a fast wired local connection - it can not be on a Network
There are Digital Asset Managers that can do what you want - iPhoto and Aperture can not
LN

Iphoto and aperture start up problem with Yosemite

Just found out that after installing Yosemite, both my iPhoto and aperture library took very long in order to show up contents after start up. Not sure what causes the delay, does anyone else experience the same problem? For reference, I am using late 2013 15" Macbook pro.

In the case of Aperture you can open the Activity window and check what Aperture is doing.
From Aperture's main menu bar: Window > Show Activity
When Aperture launched the first time, I saw the following activities, that took a noticable amount of time:
Importing iCloud photos
Scanning faces
Rendering previews for iCloud videos.

Aperture Import Date Problem

I'm importing photos and have noticed repeatedly that when I tell it to automatically split projects, it's not breaking them in the right place. It would appear that all photos before 11am are thrown onto the previous date. I have played with (and double-checked) the time zones and they appear to be in sync.
Tonight, I have discovered a new wrinkle to this. I'm rebuilding my database and I knew this problem was happening, so I've been manually (ugh!) choosing each group and putting it in the proper place. Now, I can see that the above is still happening, but now it's doing this:
For example, I have 10 images showing up as January 1st. The first 5 are really January 1st, but the next 5 are January 2nd before 11am. I download the first 5 images to a January 1st folder and when I go back to import, the next 5 are NOW showing up as January 2nd as they should have to start with.
Has anyone else experienced a problem like this? I'm going SO crazy having to manually sort these in the right place. I'm on the first of 3 SD cards I need to import and it's going to be about 7 months of photos and 30gb of data. If anyone knows a solution, I'm all ears!
Oh, and I went to the genius bar last week about this with no luck. I'm hoping there's a solution out there now and that I don't have to just report it and wait for a bug fix...
Thanks!
MorrowClan

To be honest while its something you want to avoid if at all possible its not the end of the world. I've been forced to do it on a number of occasions and haven't had anything really bad happen. Do you have a recent backup? That helps to relieve the anxiety
If you do force quit it make sure the very next thing you do is run a library repair. Hold own the option and command keys while starting Aperture to get the repair window. Once that is done (and it may take a while to run) and Aperture comes up look for a project Recovered Photos (or something like that, its been a while since the last time its happened to me) . If that is there there were images in your library that the repair function found but couldn't figure out where they belonged. You'll need to sort them out yourself.
Again, if you haven;t already, start a good backup routine for your libraries. That will go a long way towards alleviating your stomach distress
good luck

Aperture 2.14 problems make me reluctant to buy 3.0

spinning ball of death on cloning tool, even though my HD is 40% empty and I have 2 gigs of RAM. It doesn't matter if the only program I have open is aperture. 1.) The lag on cloning tool is maddening. 2.) I get freguent lock-ups, unexpected quits all the time. 3) I get a reddish maroon blank screen with an unsupported format message even though I have been working with an image without issue. ( I never have trouble downloading RAW files from Nikon D200) But every once in a while an image will be replaced by a reddish maroon blank. (it comes back after a restart) 4.) I built a vault on a Lacie 1TB external drive. I also export entire projects to the external drive, then delete projects on the internal drive to make room for more images. When I restart, the projects and their albums reappear with no images - even with the external drive disconnected or turned off. Why do these deleted projects reappear with no images? 5) Apple is unresponsive to these problems, if someone could solve these issues I might buy aperture3.

I started with A2 on OSX 10.4.6?? on an iMac with a 2.0 GHz Core 2 Duo. I've gradually upgraded SW and then HW and now I'm running A3 on OS 10.6.3 on an iMAC with a quad core i5. I'm running a couple of Lacie external drives for the vault and really big image files.
I've experienced your problems #1,#2,#3 (but not very often). I don't think your user experience is fundamentally going to change simply by upgrading to A3 on your existing machine.
A3 will not run faster than A2 on your machine. A2 is probably more bug free than A3 at this time.
If I was in your shoes, I would stay with your current Machine and A2. Upgrade your OS to 10.5 or 10.6 (perhaps even reinstall the OS). Make sure you are using Firewire not USB to connect the external drives. One thing that causes Aperture to lock up is resource shortages.
Check the free memory while running A2, see if its running out of RAM when it locking up. If so, add more RAM. (I had 3GB). Are by any chance running Photoshop and A2 simultaneously, or some other resource hungry application? If so I would add RAM for sure.
Check the console logs to see if any process is causing a lot of crashes or other trouble (I discovered I had a Canon twain driver that was launching a new process every 10 seconds)
Your problem #4 may be a bit of a mirage. Aperture keeps thumbnails and editing settings for each version of an image, these are different files and much smaller than the master image file. This additional info is kept in the Aperture library, it doesn't disappear when you delete master image files. That way you won't loose your organisation and your image edits if you ever bring the images back.
The extra info doesn't take up much room, and you are better off keeping it. You can control the size of this info by choosing a smaller thumbnail size, and then forcing the thumbnails to regenerate (BEFORE you delete the masters).
HTH
Eric

Example of Aperture dead pixel problem

A lot of people have been complaining about green pixels in their converted output. I noticed a pixel in the RAW image as rendered within Aperture and went in for a closer look. It's more like a dead pixel. I've put up crops of an image mangnified at 300%:
Aperture:
http://www.pbase.com/chrobb/image/53050269
Photoshop CS2:
http://www.pbase.com/chrobb/image/53050270
Make sure you're looking at the "Original" size of the file (located at the bottom of the webpage)
This is a pretty glaring example of some major processing problems with CoreImage. I'm going to send a bug report to Apple.
G5 1.8G SP, 1.5M RAM Mac OS X (10.4.3)

I think this was one of the biggest concerns that I had with Aperture: the reliance on OSX code to decode the RAW files. If Apple were to re-write their RAW file processor or need to tweak it to fix this bug, it would likely need to come in the form of an update to the operating system. A couple of problems with that:
1) Sometimes, because of other problems with an update, you might not want to update your OS. Say, an update fixes something in Aperture, but breaks Mail. Which is more important?
2) OS updates are likely to be released more slowly than application updates. This may not be the case since Apple may release Aperture product updates even slower, but there are a whole slew of considerations that developers need to take into account when getting something merged into the much larger OSX train.
Maybe Apple can release small RAW updates that only affect the portion of the OS that deals with RAW. I seem to reall them doing that with other apps. It remains to be seen how well and how quickly they respond to these issues. I know a lot of people are probably waiting to see how responsive Apple is before entrusting their library to a proprietary application.
G5 1.8G SP, 1.5M RAM Mac OS X (10.4.3)

Please Help - Screen corruption while in Aperture - graphics card problem?

Over the past few weeks, I have noticed frequent screen corruption within the confines of the image that I am currently editing. The corruption only occurs when in Aperture. The corruption occurs as multiple thin (one pixel?) horizontal lines of random color and random length that occur in random locations within the image. If I force a re-calculation of the image (such as change white balance) the random lines will disappear, only to reappear somewhere else. The actual image (after export) is never corrupted, only the display. Recently Aperture has started to "hang" in random ways, sometimes freezing the whole machine, sometimes crashing, sometimes beach-balling.
This sounds like a hardware problem to me, but the standard Apple hardware test runs without errors, as does an extended memtest. Setup: Mac Pro, 5GB, SW fully updated to 10.4.11 and Aperture 1.5.6. I tried re-seating the graphics board to no avail.
Are there any programs that I can use to test the Radeon X1900 card?
Any other suggestions?
Thanks in advance.

Thanks David,
I did some more research and it appears that quite a few of us (unlucky) users with an early version of the Radeon X1900 graphics card are now seeing failures that appear to be due to poor heat dissipation by the graphics card. There's a huge thread on the subject here:
http://discussions.apple.com/thread.jspa?threadID=1195969
The problem with random display glitches doesn't show up for most people until they upgrade to Leopard, which puts a larger strain on the graphics card than Tiger. I am still running Tiger, but the glitches show up for me when using Aperture, which of course uses the graphics card more aggressively than most other programs. I assume that Aperture increases the heat which causes the glitches.
I tried cleaning the dust out of the Radeon's heat sink, and I added a tool (smcFanControl) that lets me manually override the default fan speed. By keeping the card's temperature lower, the glitches have gone away. If I let the temperature rise, they come back. Looks like I'll be needed a new graphics card.

Aperture Split View Problem

The vertical photos in the split view bar at the bottom have all switched from being displayed normally to being rotated and showing squashed and distorted.
I have tried to close and re-open Aperture, and I have also restarted the computer. The pictures are distorted whther they are in the Grid view or Filmstrip. I also tried to "Update Preview", but it tells me that it is up to date.The horizontal/landscape pictures are showing fine, the problem is only with the vertical/portrait pictures in the Split view.

Select all the ones in one Project and run "Photos→Generate Preview". Does that work?
"Update Preview" changes to "Generate Preview" when "{Alt}" is pressed.

Aperture 3.3 problems RAW+JPG Import

After the update on Aperture 3.3 I have the following problem: Before import everything looks normal (see picture one). Aperture imports none jpg and Raw files as picture pairs and the Raw import looks completely colour-wrong. Moreover, there is no field more than Raw treatment
Any idea for solving this problem?

Also using a Panasonic (.RW2) I have had exactly the same problem, with exactly the same "colour effects". I did some varitions of importing and observed the following. The test shots were RAW only on a newly initialized SDHC card.
In the import dialog, if RAW only was selected, no previews were shown. Same if JPG only. If RAW & JPG selected, a preview was shown (even there were no jpgs on the card).
No presets, Auto Enhance and several others had no effect (i.e. same error).
The photos imported perfectly using iPhoto, and were then perfect in Aperture.
After thinking some, I suspect the preview image is the problem (I wished I'd exported them as tiff to see, but it was yesterday and I deleted the dodgy imports).
I had some pictures (also .RW2) not in the library at all (I'd been using them to try out LR4). I drag/dropped them from a Finder-folder into Aperture, (not import) by droppong them into the Inspector panael of Aperture; they were perfect BUT said they were RAW/JPG pairs which they were not.
Come on Apple. There was a time when your software was bug-free. Nostalga isn't enough.

Aperture and expose problem

I have a wierd problem, when I use aperture now, I can't see the main window. If I use expose to see all windows, I can see the aperture main window, but when I click on it the window goes away.
Its kind of like a reverse expose. Totally wierd.
This started happening soon after I hooked my MBP up to a plasma tv, but who knows if that is the culprit.
anyone have this problem?? I am annoyed

Your Main Window is located outside your Screen just try to conect a second display and move the Main window back to your first display.
You can also try to force Aperture to creata a new Preferences File if you delete
~/Library/Preferences/com.apple.Aperture.plist
or modify the values considering the window position (your presets won't be touched by this because they are saved in another plist.

Aperture 2 Upgrade Problem

I am trying to upgrade to Aperture 2.0 from a fully updated MacBook Pro. On the first attempt Aperture seems to start opening a Library and then reports "Unknown Error 1." This even occurred when trying to open a specific library.
I deleted Aperture and reinstalled 1.1, then I ran the upgrade. I am getting the same error.
Thanks for any assistance.
-William

We're following this problem over here as well:
http://discussions.apple.com/thread.jspa?messageID=6984093
No solution yet.

Aperture flickr delete problem

I keep on encountering this same problem with the flickr section on Aperture 3.2.2, on Lion.
I drag a photo from a project into an existing flickr album. Then I decide I don't want it there, so I delete it from the flickr album.
I then find that the master and all versions are deleted from the original project, all has gone in the trash.
All the documentation says that if you don't want a particular photo in flickr anymore you can just delete it, but it seems that this deletes it from everywhere in aperture.

I work with referenced files in Aperture and just did the same drag and drop operation to get some of my images into an existing flickr album yesterday.
If you browse your flickr album (within Aperture) and right click on one exemplary image, do you see a "Show in Finder" entry?
I do see this (as I work with referenced files which are not imported in the library itself) and I just discovered that the reference is to the same original directory as within the project. Maybe it's a kind of "bug", at least I agree that this is misleading if not dangerous. That way deleting an image in the flickr album section means deleting the file globally!
My recommendation for the moment: Open the flickr gallery (website) and delete the images there. There is a flickr button at the bottom toolbar of Aperture to switch to flickr.

Aperture Image Resolution Problem

I know there have been a lot of posts about image resolution, but I haven't found an answer to my problem.
I use a DLSR and and shoot in RAW and/or maximum resolution JPG. When imported to Aperture, the file size is usually in the 10-15MP range. However, when I try to email photos in their "actual size" or export photos to BookSmart (blurb) to create a photo album, the photos become compressed (to about 1MP). According to blurb support, my 10MP images are only 96 dpi, and not enough for a high resolution image.
I have my image export presets set to highest quality, original size, and 300 dpi, so I don't know what the problem is. Can anyone help me?

Agree.
OP:
A quick review, just so we are on the same page.
Digital image files have two "sizes".
The actual image size is measured in pixels. The digital image comprises a grid of colored dots. Each dot is a pixel, which is short for picture ellement. The dimensions of the image are given as so many pixels in one direction (usually height) by so many pixels in another direction (usually width), e.g.: 600 x 800 pixels, or 4,000 x 6,000 pixels. The overall "size" of the image is calculated by multiplying the height by the width. In the examples given, the first image is (600 x 800 = ) 480,000 pixels. The second image is (4,000 x 6,000 = ) 24,000,000 pixels.
That's a lot of pixels. The size is often given in megapixels, where 1,000,000 pixels = 1 megapixel (abbreviated MP). So the first image is approximately half a megapixel, and the second one is 24 MP.
Pixels themselves have no other unit of measurement. There is no way from the pixel count to know how many inches (or centimeters) an image will be when printed or shown on a screen. In order to determine that, you must have the pixels-per-inch (PPI) of the printer or screen (or projector, or any other display device). A 600 x 800 px. image, at 100 PPI, will be 6 x 8 inches.
Pixels are device independent. PPI tells some programs and devices how big to display (or print) an image.
The other image file size measures how much data is in the file. Data is measured in bytes. One thousand bytes is a megabyte, abbreviated "MB".
Generally, the larger the image size, the larger the file size. But this is not necessarily so, and shouldn't be used as anything but a very general guide.
Your question is about resolution, which is a question of density: how many pixels there are in a given area. This is commonly measured in PPI. Resolution and file size are independent.
Message was edited by: Kirby Krieger

Aperture to Smugmug problem

Similar Messages

Maybe you are looking for