Currently Being ModeratedMay 2, 2011 4:57 AM (in response to msinjin)
Welcome to the user-supported Aperture discussion group.
I assume you are talking about dragging-and-dropping.
The first thing that we should do is make sure you are truly talking about projects here. The behavior of dragging-and-dropping a photo into an album makes it appear to copy the photo. The behavior of dragging and dropping a photo from a project to a project is to move.
Before one truly understands the different types of containers, it may seem that Aperture has some useless idiosyncracies concerning dragging-and-dropping. However, once you examine the source and destination of the drag, you will find the rules are definitely concrete.
So, just to make sure, can you describe the exact types of containers you are dragging from and dropping to, and the relationship of those containers?
Currently Being ModeratedMay 2, 2011 10:00 AM (in response to Mr Endo)
One clarification Nathan....
Just want to make sure the OP understands that the "destination" you are referring to is the actual drop target. Where the drop target to "move" MUST be an actual project NOT an album within another project. Some times new users are confused because they are using a drop target that is an album that happens to be in a different project and the words we all use get translated differently for different people.
So just to be as clear as possible: To move from project to project the drop target MUST be an actual project and NOT an album even if the album is located in a different project.
Currently Being ModeratedMay 3, 2011 5:44 AM (in response to Mr Endo)
Thanks Nathan and RB.
I am indeed trying the drag and drop between 2 projects. After some more playing around I think I've hit on the problem: the photos I am trying to move (but will only copy) are also shared to my Flickr account (using the built in Flickr album facility). So it appears any photo I add to a Flickr set gets marooned in the project it was in at the time I set up the Flickr sharing for it. I have confirmed that if I remove a photo from a Flickr album it is shared with, then I am able to properly drag and drop it between projects.
That seems to explain it, but this is highly annoying behaviour!
Currently Being ModeratedMay 3, 2011 6:09 AM (in response to msinjin)
I recently confirmed this behavior where photos are shared to a Facebook album as well, and also Slideshows you create.
The Master only copies, and does not move when used in the album, even though the drag is from originating Project to another.. Confirmed that the Master was in fact duplicated in the Masters folder of the library package, and file count was incremented.
Currently Being ModeratedMay 5, 2011 2:37 AM (in response to Ernie Stamper)
While I'm glad I understand the reason for the behaviour now, it seems to be a bug. Or at the very least the Aperture guide should warn that the move behaviour changes to copy (with no other option) if the photo is used in an album. Yuk, no. I'm gonna stick with my first thought: it's a bug.
For what it is worth, I've been having enough grief with Aperture's Flickr sync facility that this discovery has prompted me to abandon it and purchase FlickrExport from Connected Flow.
Currently Being ModeratedMay 5, 2011 3:58 AM (in response to msinjin)
I am not defending the behavior, nor do I claim to yet fully understand it without more study.
I use SmugMug Pro galleries to distribute photos, and utilize a plug-in for that Export. Those galleries are not repeated in Aperture, and Aperture does not monitor them. That seems to me the preferred way. Perhaps integration can go too far!
Currently Being ModeratedMay 5, 2011 4:15 AM (in response to Ernie Stamper)
Integration gone too far, I like that. Agreed the export rather than Aperture syncing approach seems to be the winner.
Sorry Ernie, I didn't mean for my previous post to be in reply to yours (i.e., I did not think you were defending the behaviour etc). It was meant to be closure for my original post and the thread but I clicked the first "reply" button I saw. Newbie mistake.
Currently Being ModeratedMay 5, 2011 4:25 AM (in response to Ernie Stamper)
+1 for everything Ernie said, but especially this:
Ernie Stamper wrote:
Those galleries are not repeated in Aperture, and Aperture does not monitor them. That seems to me the preferred way. Perhaps integration can go too far!
I use Zenfolio. I used the plug-in exporter, but eventually found it easier to control and monitor what I was doing by simply exporting as needed to a desktop Finder folder, and then uploading from there. This simple, mechanical-like placement of copies where I want them has the same relationship to full integration as eating breakfast has to dreaming about it: one of them satisfies a need. I don't think the goal of this kind of integration can be singularly specified, let alone programmed. I'd much rather the Aperture team devote its time to other tasks.
Currently Being ModeratedMay 5, 2011 7:35 AM (in response to Ernie Stamper)
I have just done some additional testing, and it is wild! Despite the examination of the Masters folder in the Package of the Library showing that an additional Master was created if you acted to Move a Master from the Project from which the FB album image originated, there remains some sort of linkage between the original Master and the apparent new Master. To give an example: if you totally desaturate the image in the new Project location, that adjustment does not impact the image in the original Project, nor in the FB album -- seems logical. But in the original Project, if you click on Edit the option to Undo the desaturation done in the new Project is presented, and if you choose it, the desaturation will be removed in the new Project. During all this, no visible change occurs either in the original Project, nor the FB album. Yet there are two copies of the Master in the Masters folder. This is very difficult to explain from a design standpoint!
Later today, or tonight, I will try to duplicate these tests in a very simple New Library, where I can clearly and totally follow the activity in the Masters folder of the library package.
Btw, I do not have make a new Version when adjusting selected.
Currently Being ModeratedMay 5, 2011 8:39 AM (in response to Ernie Stamper)
I'm not seeing this behavior with slideshow albums. Tried it both with the slideshow album at the library level and with the slideshow under the original project.
In both cases the images were moved to the new project and the slideshow referenced the images in the new project.
Don't have a Facebook account so can't try it there, but definitely not seeing it with slideshows.
Just tried it with Flickr. The images in a a project that are also in a Flickr album are duplicated when the images are moved from the original project to a new one. I didn't see any adjustment cross over however. If I adjusted images in one project the copied image in the second project didn't react.
Currently Being ModeratedMay 5, 2011 8:49 AM (in response to Frank Caggiano)
So you see this behavior with a Flickr album as well? I had not tested a Slideshow, but did see some evidence of duplication in the Masters folder of images that were in a slideshow, so suspected it was.
I cannot use show location of the Master in the Finder with my Managed Library, and I doubt you can learn anything either, as I suspect the any second Master will be in the Library -- but you can check that.
There is something that may be akin to stacking going on, but that does not explain why the option to Undo in the new Project is also presented in the original Project.
Currently Being ModeratedMay 5, 2011 12:06 PM (in response to Ernie Stamper)
Talking with Ernie ( don't shoot me for draggin this over to here but thought a good idea ! ) in another post and he said this : " I hope that the Facebook/Flickr albums do not open a path to Masters, but only the filename of Versions! "
I just checked out a few things.... if you open the photo in the FaceBook section of the Library Panel and edit ANY of the Metadat on the published photo then it updates it in the Master of the project and the Album !!!
Currently Being ModeratedMay 5, 2011 12:14 PM (in response to josephleebrown)
Isn't it just the one and only Version of the Master? Use the New Version from Master, and check the result. I will test as time allows, as well.
I just tested, and the New Version from Master has the original file and version name -- whew!!! Doesn't have the adjustments, of course.
Message was edited by: Ernie Stamper
Currently Being ModeratedMay 5, 2011 12:17 PM (in response to Ernie Stamper)
I may just go back to iPhoto... I am joking by the way !!