Hot folder for import, using Automator/Folder Actions -- pretty quirky
I've followed other's suggestions for setting up a hot folder such that when new images/folders are dropped into it, all images are imported into a selected project in Aperture. This was described in the following thread:
http://discussions.apple.com/thread.jspa?messageID=1288674�
This procedure only *sort of* works for me. It only works if I'm simply moving a folder of images from the same hard drive to the selected 'hot folder'. Why?
Because if I'm copying or *importing images from a digital camera* to this hot folder, there is a significant TIME DIFFERENCE between the instant the first image is copied to the folder and the Automator actions is started, and the instant the final image is copied or imported into that folder. Say, for example, you're copying 100 images from your digital camera to aforementioned 'hot folder'. As soon as image #1 is copied to said 'hot folder', Automator lauches the folder action that begins importing images into Aperture. Say that by the time the action is actually sent over to Aperture to begin importing images, 25 images have been copied to said 'hot folder'. Then, ONLY THOSE 25 IMAGES are imported into Aperture, and then the Automator action quits. Meaninwhile, images 26 - 100 are still being copied into said 'hot folder', but Automator feels like it's already done it's job. So images 26 - 100 are never imported into Aperture, and you're left with a partial import.
The above is just an example scenario. Sometimes Automator will launch the import action again, and again, but there's no guarantee that ALL 100 images will be imported into Aperture (even though all 100 images will be copied into said 'hot folder'). Seems like a huge bug with the 'Import Images' Automator action for Aperture.
On the other hand, if I simply move a folder of images into this 'hot folder', then the move is almost instantaneous (given that the folder you are moving resides on the same hard drive as the 'hot folder'). Since it's INSTANTANEOUS, the time difference between when the move is made and completed, and the point at which the Automator action is launched, is almost null... hence all images are imported into Aperture.
Crazy... yet predictable. Anyone have a workaround for this? Anyone else experienced this?
http://discussions.apple.com/thread.jspa?messageID=1288674�
This procedure only *sort of* works for me. It only works if I'm simply moving a folder of images from the same hard drive to the selected 'hot folder'. Why?
Because if I'm copying or *importing images from a digital camera* to this hot folder, there is a significant TIME DIFFERENCE between the instant the first image is copied to the folder and the Automator actions is started, and the instant the final image is copied or imported into that folder. Say, for example, you're copying 100 images from your digital camera to aforementioned 'hot folder'. As soon as image #1 is copied to said 'hot folder', Automator lauches the folder action that begins importing images into Aperture. Say that by the time the action is actually sent over to Aperture to begin importing images, 25 images have been copied to said 'hot folder'. Then, ONLY THOSE 25 IMAGES are imported into Aperture, and then the Automator action quits. Meaninwhile, images 26 - 100 are still being copied into said 'hot folder', but Automator feels like it's already done it's job. So images 26 - 100 are never imported into Aperture, and you're left with a partial import.
The above is just an example scenario. Sometimes Automator will launch the import action again, and again, but there's no guarantee that ALL 100 images will be imported into Aperture (even though all 100 images will be copied into said 'hot folder'). Seems like a huge bug with the 'Import Images' Automator action for Aperture.
On the other hand, if I simply move a folder of images into this 'hot folder', then the move is almost instantaneous (given that the folder you are moving resides on the same hard drive as the 'hot folder'). Since it's INSTANTANEOUS, the time difference between when the move is made and completed, and the point at which the Automator action is launched, is almost null... hence all images are imported into Aperture.
Crazy... yet predictable. Anyone have a workaround for this? Anyone else experienced this?
MacBook Pro Core 2 Duo, Mac OS X (10.4.8)
