Bug- Aperture is doubling projects

This has been going on for a while. Sometimes when I launch Aperture some of the Projects will be doubled? If I try deleting them the program hangs. I can, however, drag the offending project to the trash folder.
Today its really weird. My current working project (7911 images) was doubled when I launched. When I drag it into a folder the duplicate disappears. When I drag it back out to the "Projects & Albums" level a duplicate reappears.
This is kinda scary. I don't dare trying to drag one of them to the trash in fear they both might disappear.

Thats weird because up to now it was only the smaller projects that were getting doubled. I should clarify this. They were not actually getting doubled - it just looked like they were. For instance it would show two "TA10-11"s but it was actually the same files. If you changed something in one it would change in the other.
In this case if I drag one of the files into a folder the other disappears. When I drag it out the double reappears.
I like to keep each year as a project and separate out things using albums. We are producing to much to have a Project for each job.

Similar Messages

I just updated to the latest aperture, i have projects previously saved on a drive (in the old version) that now won't load... how do i update them?

Hi,
i just updated to the latest aperture, i have projects previously saved on a drive (in the old version) that now won't load... how do i update them?

But, unless I missed something, you are doing the repair with Aperture 3.5 so if 3.5 can't open an earlier library before doing the upgrade then unless I'm missing something the library will be upgraded before the repair is run, no?
OT:
You got me there, Frank - I wondered about the same thing, but Aperture is behaving differently, when upgrading a library, depending on if you are launching into the First Aid Tools or not.
I repeated my experiments, to explore this difference:
I restored an Aperture 3.4.3 library and launched the First Aid Tools:
Apertur went directly into First Aid Mode without first asking to upgrade.
Then "Repair" asked to be allowed to upgrade the library as you predicted.
During the upgrade "Aperture"showed "Rebuilding", not "Repairing" or "upgrading".
Second experiment: When I only double-click the 3.4.3 library instead of repairing, the upgrade alert is very different:
It takes a shorter time and does not show "rebuilding".
I am quite certain, that Aperture will use a different upgrade prodecure, when launched into the First Aid panel for repairing or rebuilding.

[svn:osmf:] 10751: Fix a bug with the ReferenceSample project.

Revision: 10751
Author:   [email protected]
Date:     2009-09-30 10:57:34 -0700 (Wed, 30 Sep 2009)
Log Message:
Fix a bug with the ReferenceSample project.
Modified Paths:
    osmf/trunk/apps/samples/framework/ReferenceSample/org/openvideoplayer/model/ReferenceSWFE lement.as
    osmf/trunk/apps/samples/framework/ReferenceSample/org/openvideoplayer/view/MainWindow.as

(Removed)

Problems importing Aperture 2 archived projects into Aperture 3

Any suggestions please I want to import some archived projects from aperture 2 back into Aperture 3 from an external dive the projects are in folders named xxxx.approject. Aperture 3 sees the folders but the images are contained in separate folders within so for a project that has 600 images in it imports them all in individual folders which is a complete nightmare to sort out. Am I doing something wrong here or is this the way Aperture 2 exported projects? Any help would be appreciated.

It should work. Just try it.
-Allen

Help me to decide the final double project

this semester i am doing my final double project.
i want to use the java advance technology to programming
my coding. especial J2ME.
please suggest me a title that i can do.
now my title is "studing mobile wireless system
to implement SAMSUNG mobile phone remote picture message
transaction using java advance technology"
please help me to choose the title.
thanks very much

i change my topic already my first supervisor said are you sure this samsung A200 model will be suing during 10 years later, your project is useful???
then i have no words.
now my topic is "using TCL/TK to implement the windows and linux doing cross platform sharing and file tranfering"
please give me some advise.

I merge projects in aperture, it works fine until aperture restarts. After aperture restarts, the projects are no longer merged, and are back the way they were. Can anyone suugest how to make the merge permanent?

I merge projects in aperture, it works fine until aperture restarts. After aperture restarts, the projects are no longer merged, and are back the way they were. Can anyone suugest how to make the merge permanent?

I tried the first aid tasks but the issue is still there. I have more info now though. It's not a problem with merging.
The problem is that new projects are being generated everytime aperture starts (with the same name, ie 01, 02.... and 01 (1), 02 (1) .....)
When aperture start, it shows "importing". When I click on importing, it goes into the activity box. In the activity box, has many lines as below. The added projcts are all empty. It's annoying because i have many useless projects being generated.

Creating a Bug after Launching the Project into Production Environment

Hello My Friends;
As I'm New in Implementing TFS 2013, would U advise me How to open a new Bug - after Launching The Project in to Production Environment which has already conducted more than a year ago before implementing TFS. So, a Bug has come from the Business Colleagues.
I'd like to open a new Bug on TFS ?!
What Repro Steps Mean ?!
Thanks for your supportRegards;
EB

Hi EB,
Thanks for your post.
After you connected to team project using your VS, you can open a new Bug work item in VS, please refer to the steps in this document:
https://msdn.microsoft.com/en-us/library/dd293538.aspx.
The Repro Steps mean: provide the detailed reproduce steps there, then developer can follow the detailed steps to reproduce this bug and try fix it.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Importing Aperture 2.1 projects into Aperture 3

I have several Aperture 2.1 projects on my MacBook Air that have already been exported from 2.1. Is it possible to import these directly into Aperture 3 on my desktop or do I have to upgrade the Aperture 2.1 on the MacBook Air first and then re-export the projects?
Joel

It should work. Just try it.
-Allen

I can no longer drag photos in Aperture (within a project, between projects

I find that suddenly I cannot drag photos in Aperture. In other words, I cannot MOVE a photo at all, whether within a project or between projects and albums, &c. Not only this, but I cannot copy & paste either. I can still export photos, though.
I noticed this first a couple of hours ago when attempting to attach a photo into an email using the Mail application. It wouldn't budge. I thought it might have been a problem with the Mail program but no, it appears to be in Aperture because I then tried to drag the photo directly from Aperture into the email (which I've been doing for years).
I've done a rebuild and all that, yet the problem remains.
Any suggestions as to what I might do other than export the whole library to Lightroom and start learning all over again?

Can you confirm:
- that this is true for many Images? Try different Images in several Projects. If possible, try with an Image you had been able to drag-and-drop into Mail in the past.
- that you can't drag from a Project to an Album.
- that the Image you can't drag-and-drop has a Preview? ("Photos➞Update Preview")
What do you mean us to understand with the "and all that" part of "I've done a rebuild and all that, yet the problem remains"?

Possible bug in NetBeans JavaFX project type

Found the following issue when trying to run a JavaFX app as a jar:
1) Create a JavaFX app project.
2) Create a Java class library project, with at least one class.
3) Add the Java class library to your JavaFX app libraries
4) In your JavaFX app, invoke a class from class library.
Now build the app, and try to run it directly using "java -jar". You will get a ClassNotFound exception when it tries to invoke the class from the included library. The library jar file will be copied to the dist/lib directory, but if you open up the manifest in the application's jar file, you'll see that no Class-Path parameter is created for it.
This isn't an issue for web start, because the path to the library jar file is included in the application's jnlp file, but if you're planning to build a regular application that will be launched locally, this would appear to constitute a bug, unless I'm missing something.

:groan:
JavaaFX 2.0 Netbeans external JARS 0 bytes
db

BUG-JDev 11G 5407-Project level resource bundle usage messes the page

When you define a resource bundle on the project properties and if you are using templates the page is not properly rendered in the design view but it runs fine.
What happens is , JDev adds a JSTL set tag just before the *<af:pageTemplate>* tag and this confuses the designer. To workaround I defined the bundle variable in faces-config, it worked fine for the existing texts but when you add a new text to the page JDev keeps adding this set tag at the beginning of the page and you need delete it each time.
It looks like a bug to me ..
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:dvt="http://xmlns.oracle.com/dss/adf/faces"
          xmlns:mcc="http://com.micros.adf.controls"
          xmlns:c="http://java.sun.com/jsp/jstl/core">
<c:set var="abcdmainBundle"
         value="#{adfBundle['com.abcd.view.zzzz.messages.AbcdMain']}"/>
<af:pageTemplate viewId="/tmpl/abcdMainFgTmpl.jspx" id="pt1">
    <f:facet name="main">

Hi,
we have the same issue and therefore do not use the feature of the property inspector.
Instead we open the *.properties file in jdev and edit it manually.
There is bug 7537379 around this c:set tag which MAY BE fixed in the next release (11.1.1.2.0) but I don't know if this bug also covers exactly your problem.
regards
Peter

Import Aperture 3.1 project into 3.2 library

I use a Macbook Air 1.86 Ghz Core 2 with Mac OsX 10.5.8 with Aperture 3.1 to stock and edit my travel libraries.
I export the travel projecs to an external harddrive, to import the projects into Aperture 3.2 on my Macbook Pro 17"..
But the older 3.1 projects can not be imported into the 3.2 version...
Last time i used a work around, .. installed an old 3.1 version on my macbook Pro, imported the project in a new library, updated to 3.2 and copied the library to my master library.. Quite tedious if you have to repeat this for every trip..
The 3.1 version on the macbook air can not be upgraded to 3.2 since it does not run on Mac Osx 10.5..
Is there a faster way to get my 3.1 project intot Aperture 3.2...
it seems logic to me that an update of the project is offered as soon as you try to open it in a newer version.. of aperture ?
Thanks,
Danny Stevens

I export the travel projecs to an external harddrive, to import the projects into Aperture 3.2 on my Macbook Pro 17"..
Hi Danny,
Does it not work, to upgrade your exported 3.1. project to AP 3.2 by opening it in Aperture 3.2?
I'd try the following wotkflow:
export the travel projects to an external harddrive,
connect the drive to your Macbook Pro 17"
open the 3.1 projects with Aperture 3.2 and upgrade them to AP 3.2
then import the upgraded projects into the 3.2. library on your MBP 17"
Regards
Léonie

Aperture thinks a project has offline referenced masters - but it doesn't!

I've just been consolidating two Aperture libraries by exporting projects from one library and importing them into another. For the most part this has gone smoothly, but in one project all the images have the little badge with the red slash through it, to indicate that the referenced masters are offline.
But they're not! The project itself is 2.2 GB - so all the photos are actually in it - and when I click 'consolidate masters' for that project, Aperture tells me there are no referenced masters for this project. For every image that's missing a master (if that makes sense) there's a version that's NOT missing a master. So the data's there and I can work with the image - I'm just a bit worried about making radical moves without knowing exactly what's going on
I've tried deleting the project and reimporting it, but to no avail - also, when I delete the project, it tells me referenced masters are offline and can't be moved to the trash.

There is a special subforum for the Android version of Reader:
http://forums.adobe.com/community/adobe_reader_forums/android?view=discussions

Aperture 2 - imported project in macbook from imac - no images!

Hi - I am very new to Aperture and have hunted high and low in all the forums to find an answer to this question but so far have not found one, so here goes:
I have Aperture installed on both my new imac and year-old macbook (both Leopard and fully updated). I have imported photos from my iphoto library (which Set Up Assistant migrated over from my MB) into Aperture on my imac successfully, choosing to move the masters to my Aperture library there because it has a much bigger hard drive. I have neatly filed them into projects (and into blue albums within those projects) and adjusted them to my satisfaction.
I then exported each project to the Desktop and then, being careful to close Aperture on the imac, brought the project onto the Desktop on my MB via my network. I then opened Aperture on the MB and imported the project from the Desktop. I could see that the project obviously had contents because of its size and it took a few minutes for it to be imported. But the project has no images in it!
I have checked that the images in the imac Aperture are not referenced images so this can't be the problem and I have no problem exporting and importing images themselves - just the whole projects.
I expect there is an obvious answer to this but I have tried in vain for several hours to find it so I hope someone here will be able to help.

Does Aperture 2 have a "Repair Database" when you launch it while holding down alt&command - that solves a lot of problems in version 3.

Bug: Menu option "Build project" is disabled

I have "Build automatically" disabled due to the poor compiling performance of FB (my project has hundreds of classes), and have instead attached a key binding to "Build project" to trigger a build manually.
Unfortunately this option is very often not available, although I have made changes in the project (and saved them).
Yet right-clicking the project, and selecting "Build project" does a build then.
Obviously there is a bug detecting when a build is required or not.

Build project is disabled if you have no project selected in the package explorer/navigator.
Unfortunately, the logic for detecting the project associated with what objecthas focus is not implemented well in Eclipse (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=201650)
That means that if you go to Problems view or switch between editors in a certain way, Build Project gets disabled.
The short of it, it is an Eclipse bug and has been fixed for 3.6 (which is what the next version of Builder ships with).
Thanks,
Anirudh

Bug- Aperture is doubling projects

Similar Messages

Maybe you are looking for