Maybe bug in Aperture GUI

Hi, I will be very appreciate if anyone can help me with this problem. After i upgraded from Aperture2to3. Some parts GUI were missing. I make screenshot for better understanding of my problem. http://qkpic.com/fce7f
It doesnt matter which type of View I am using..it looks like the whole preview section is outspreaded to the right side, over the screen edge. There is no search field, everything is out of the screen view, and I can't reach the photos behind the screen. When I am using Split View I can not see the selected picture over the whole preview section. It is very anoying..I have to use fullscreen browsing for selecting images..It's not very comfortable.
Thanks for advices:)

AS you know, you appear to be missing the controls on the right side of the Browser. Two suggestions:
1) try selecting the Split view instead of the Browser view to see if this is at least normal and then revert back to the Browser view.
2) the actual Browser window is not seeing your window dimensions correctly so try to hit the standard application Resize button on the screen once or twice to change the window size.
Let me know if neither suggestion worked!

Similar Messages

Bug? Aperture 3 asks me to load S/N on start up

Bug? Aperture 3 asks me to load S/N on start up. I have to load Aperture 1 and then Aperture 3 S/N.
Is this a known bug? Is there a workaround. Jo Daniell

Did this happen all of a sudden or after migrating Aperture to a new machine? The serial number cannot be migrated. If you moved Aperture with Migration Assistant, use the installer media to reinstall it and upgrade immediately to the current version using Software update.
And yes, when you upgraded Aperture from earlier versions and bought upgrade serial numbers and not full version serial numbers, you will need to enter all previous version serial numbers. Do you still have them? If not, try this Pro Application Replacement Serial Numbers
when the support site is up again.
If you did not migrate Aperture recently. look at my post here, how to fix the ProAppSystemID file:
This solved my questionRe: does not remember my serial number
Regards
Léonie

New bug in Aperture 2.1

I had been using Aperture 2.1 for some time with only the usual bugs, most commonly, the Viewer screen going black or blue or red occasionally, but a new bug has appeared that is forcing me to restart Aperture frequently. After making edits, when I move on to the next image in the Browser (the thumbnail highlighting changes, as it should) the image in the Viewer does not change. I have not found a way to get a new image in the Viewer except restarting Aperture. This is greatly slowing down my processing of big projects.
Has anyone else seen this bug? Have you found a workaround beside restarting?

Tony Finnerty wrote:
I had been using Aperture 2.1 for some time with only the usual bugs, most commonly, the Viewer screen going black or blue or red occasionally, but a new bug has appeared that is forcing me to restart Aperture frequently. After making edits, when I move on to the next image in the Browser (the thumbnail highlighting changes, as it should) the image in the Viewer does not change. I have not found a way to get a new image in the Viewer except restarting Aperture. This is greatly slowing down my processing of big projects.
Has anyone else seen this bug? Have you found a workaround beside restarting?
can u guys please give us a little more info? where's the aperture library located? in your main hard drive (os x) or on another drive?
are you sending the crash logs to apple?
thanx,
victor

Bug in Aperture 2.1.1 Trial

Hi all,
I am new to MAC and while I am trying to encourange my wife to enjoy the new iMac Aperture is not helping. I have read the forums and still seem to be stuck. I am having a few issues and some of them simply seem to be basics faults in the app (beyond other complains throughout every forum on the net):
(when I imported, I chose to store the photols in Aperture, rather than use referenced files, as I assumed that this would provide better managment of the photo's over referenced files - maybe this is my first mistake)
1. when I am in an Album, from "file" i see two delete options. first is "delete version" and the other is "delete master and all version". this makes sense to me. But when I click on delete version, the pop-up shows "you are about to delete the master and all referenced versions" ahh. I cant just delete a version.
2. everything tells me that to move a master from one project to another you just click and drag. when I do this it create a new version in the new project. when we have imported the photos we had one folder that was a mess and we want to get tidy up all the photos and get rid of this folder. But it seems that because the masters were originally imported into this folder they are stuck there now.
Do other people have these problems? We have a bigish photo collection, about 15,000 now and growing and I was concerned that iPhoto could not always cope with managing so many photos, which I why I started looking at Aperture..
I generally like the interface, but these little things are killing me.
Any advice would be great.
Thanks,
Cameron

Hmmm.
I don't even want to comment on the other posts here but here are your answers for real:
A) If you delete the one/only/last "version" it will take the master along with it, when this happens it warns you. Think of it this way - you never really "see" the master you only see versions including the first version created. This is by design - don't think of the image that you see even if it is the only one as the master - it's not - it is a version. If you were to duplicate version or do a new version from master and then delete version on the first one you will not get that "I am going to delete the master too" kind of message.
B)To move an image (as in the master) to a new project you MUST drop it on the actual yellow project box NOT any other type of object within a project. If you drop it on anything (like an album) even if it is in a different project you are merely adding a view of it to that object, not moving it.
This may help you get your bearings:
http://www.rwboyer.com/RBDesign/Blog/Entries/2008/7/15_Apple_Aperture_2.1Organization.html
If you have any questions hit this thread again - I hope you can understand what I just wrote.
RB

Photo sync bug with Aperture albums?

Hi, I think I have found a bug with how iTunes syncs photos across to my new (and until my number ports across, useless) iPhone.
If you set it up that only selected Aperture albums are synced, like this;
[ ] album1
[tick] album2
[ ] album3
[tick] album4
then albums 2 and 4 are optimized and copied across.
However, if in Aperture you create a new album (by importing new photos, say) that appears in the list, e.g., between album2 and album3, then the ticks retain their spacial position, not their position relative to the album they are meant to sync;
[ ] album1
[tick] album2
[ ] album_new
[tick] album3
[ ] album4
So now, when you sync, album4 is deleted and album3 is placed on the phone - not what you would expect.
Has anyone else noticed this?
Tristan

Tweekme wrote:
It is fixed now though. If you upgrade to iTunes 7.5, and iPhone software Update 1.1.2
Hi Scott,
Thanks for the reply.
That's strange... I am using leopard, with iTunes 7.5 and a brand new UK iPhone (so it has 1.1.2 already on it). It was essentially in 'virgin' state too; I had to return my 1st phone due to a tiny but annoying problem with it. I noticed the this after only a couple of syncs - when the sync was taking a while due to the photo optimizing step.
I will take another look tonight.
Thanks,
Tristan

Full Screen - Main Viewer Bug in Aperture 2.0

When I enter full screen mode the "Main Viewer" button on the toolbar that allows one to view either multiple and a single image is grayed out UNLESS I have the viewer panel displayed before entering full screen mode.
Anyone else noticed this?
dbk123

Tony Finnerty wrote:
I had been using Aperture 2.1 for some time with only the usual bugs, most commonly, the Viewer screen going black or blue or red occasionally, but a new bug has appeared that is forcing me to restart Aperture frequently. After making edits, when I move on to the next image in the Browser (the thumbnail highlighting changes, as it should) the image in the Viewer does not change. I have not found a way to get a new image in the Viewer except restarting Aperture. This is greatly slowing down my processing of big projects.
Has anyone else seen this bug? Have you found a workaround beside restarting?
can u guys please give us a little more info? where's the aperture library located? in your main hard drive (os x) or on another drive?
are you sending the crash logs to apple?
thanx,
victor

Bug in Aperture's Color labels?

When I select an image and use the main menu to change the color label to nothing, viewing in the list view shows the label as "--" (without the quotes). When I use the sidebar to perform the same operation, the list view shows the label to be "No Label" (with the quotes). This seems inconsistent. Is this a bug?

Yes, its been around since at least version 3. While it doesn't cause a lot of problems in Aperture itself if you try to use Applescript to script the labels it causes all sorts of problems.
I reported it numerous times, keep hoping that one day it will be fixed. You can send feedback to Apple reporting this, see Aperture->Provide Aperture Feedback
regards

PDF file Display Bug in Aperture

I'm currently using the trial version of Aperture 2.1 for my small architecture practice. Most of my assets are photos or renderings, but some are PDF files of vector drawings. Maybe I'm asking too much from Aperture, but I am having a very strange problem with the PDf files. The background color for both the preview thumbnail and the large view of the PDF files are being inverted: white backgrounds are displayed as black. When you have a black line drawing and the background becomes black, it is impossible to see the drawing! None of the content of the PDF changes (black and colored lines keep their color), only the background turns black.
I've tried updating the preview but this doesn't do anything. Does Aperture not support PDF files?
Thanks

What do you see when you open the same files in Preview? As far as I know, both use the same OS-level PDF rendering engine.
Ian

Annoying bug in aperture (Or is it just me)

I have like my dump zone project for importing all images then I start to sort them out by dragging them into the right places.
I use the apple key to select specific images, but once I have to scroll down a bit using the mouse or wheel aperture throws a fit it will scroll to where you want to go but when you goto select an image it bounces you back to your last area of selection, meaning that with the mouse held down you land up selecting things you didn't want.
Is this a bug or a 'feature?'

I can select multiple items, scroll down using my scroll pimple (apple mouse) and select future images without any problems. I'm not sure what could be causing your problem.
Mike

Maybe bug : ListCollectionView.addAll with a filter function

Hi,
I think I found a bug in the flex SDK. I've checked in JIRA and it seems that it is not yet reported.
This simple code raise a "out of bouds exception" (flex SDK 4.1) :
var list:ArrayCollection = new ArrayCollection();
list.filterFunction = filter;
list.refresh();
var items:ArrayList = new ArrayList([1,2,3,4,5]);
list.addAll(items);
function filter(obj:Object) : Boolean {
     var n:Number = obj as Number;
     return n<2;
I've checked the code in mx.collections.ListCollectionView and it's obvious : addAll is calling addAllAt. "addAllAt" is calling by looping over the list to add and calling addItemAt for each item, but it increments the index arguments even if the previous item was not really added (due to a filter restriction), and the "out of bounds exception occurs". In my opinion, addAllAt has to be changed as folowing :
current version :
public function addAllAt(addList:IList, index:int):void {
     var length:int = addList.length;
     for (var i:int=0; i < length; i++)
          this.addItemAt(addList.getItemAt(i), i+index);
proposed version :
public function addAllAt(addList:IList, index:int):void {
     var length:int = addList.length;
     for (var i:int=0; i < length; i++)
          var at:int = i+index;
          if(at>length) {
               at = length;
          this.addItemAt(addList.getItemAt(i), at);
Should I open a bug? Or am I missing something?
M1kal

Hi,
I've filled this bug about 2 months ago but nothing seems to happening, is it something I have to do to push it in the process?
reagrds,

UTF8, Media and nacional chars - Maybe bug, not sure

I create Media object using XML like this:
if (event.type == PullParser.TEXT) {
   if(event.qname.name == "url" and event.level == 2) {
      if("{event.text.trim()}" != "")
         parserHelper.url = event.text;
if(event.qname.name == "song" and event.level == 1) {
   parserHelper.media = Media{
     source: parserHelper.url
   insert parserHelper into songs;
}i get exception:
FX Media Object caught Exception com.sun.media.jmc.MediaUnsupportedException: Unsupported media: file:///F:/Żywiołak/epopeja_wandalska.mp3
    source ='file:///F:/Żywiołak/epopeja_wandalska.mp3'
com.sun.media.jmc.MediaUnsupportedException: Unsupported media: file:///F:/Żywiołak/epopeja_wandalska.mp3
        at com.sun.media.jmcimpl.PeerManager$1.run(PeerManager.java:58)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sun.media.jmcimpl.PeerManager.throwMediaException(PeerManager.java:51)
        at com.sun.media.jmcimpl.PeerManager.getMediaPeer(PeerManager.java:211)
        at com.sun.media.jmc.Media.<init>(Media.java:50)
        at javafx.scene.media.Media$1.onChange(Media.fx:88)
        at javafx.scene.media.Media$1.onChange(Media.fx:81)
        at com.sun.javafx.runtime.location.ObjectVariable$2.action(ObjectVariable.java:165)
        at com.sun.javafx.runtime.location.ObjectVariable$2.action(ObjectVariable.java:162)
        at com.sun.javafx.runtime.util.AbstractLinkable.iterate(AbstractLinkable.java:78)
        at com.sun.javafx.runtime.location.ObjectVariable.notifyListeners(ObjectVariable.java:162)
        at com.sun.javafx.runtime.location.ObjectVariable.replaceValue(ObjectVariable.java:117)
        at com.sun.javafx.runtime.location.ObjectVariable.set(ObjectVariable.java:128)
        at com.sun.javafx.runtime.location.AbstractVariable$5.apply(AbstractVariable.java:140)
        at com.sun.javafx.runtime.location.AbstractVariable.needDefault(AbstractVariable.java:158)
        at javafx.scene.media.Media.initialize$(Media.fx:81)
        at pl.koziolekweb.fxmusicplayer.Main$1.lambda(Main.fx:67)
        at pl.koziolekweb.fxmusicplayer.Main$1.lambda(Main.fx:67)
        at pl.koziolekweb.fxmusicplayer.Main$1.invoke(Main.fx:41)
        at pl.koziolekweb.fxmusicplayer.Main$1.invoke(Main.fx:41)
        at pl.koziolekweb.fxmusicplayer.Main$1.invoke(Main.fx:41)
        at pl.koziolekweb.fxmusicplayer.Main$1.invoke(Main.fx:41)
        at javafx.data.pull.PullParser.setEvent$impl(PullParser.fx:444)
        at javafx.data.pull.PullParser.setEvent(PullParser.fx:112)
        at javafx.data.pull.PullParser.next$impl(PullParser.fx:275)
        at javafx.data.pull.PullParser.next(PullParser.fx:112)
        at javafx.data.pull.PullParser.parse$impl(PullParser.fx:211)
        at javafx.data.pull.PullParser.parse(PullParser.fx:112)
        at pl.koziolekweb.fxmusicplayer.Main$2.lambda(Main.fx:94)In my opinion problem is a 'Ż' and 'ł' chars in filenames. I tried with other characters like ą,ę,ś,ź,ć etc. and results were the same.
My question is:
Is any restrictions in JavaFX on the use nacional characters or this is a bug?

Sorry guysy iPhone says unable to download application at this time and I try all day and it still won't let me download no matter how hard I try.

Maybe moving to Aperture and PB G4 15"

I know this is sort of long in the tooth, but I need to use this for a bit longer.
So far, i find the performance to be pretty marginal on this computer (PB G4 1.5Ghz, 1GB of memory). If I quit everything else, I can get it to run ok - not great, just ok. I presume this can be helped by adding some more memory (question: How much?).
I have previews turned off, so that is not slowing this down.
When I got to edit in CS2, I might as well go run around the block a couple of times before it comes up with the file in question. Any other hints here?
I'm coming from iView Media Pro - which seems to have much more control over the metadata - creating custom fields etc... For example, iView has "People" annotation fields. These are not picked up by Aperture so I had to write a script that moves the list of people names into keywords. Is this what has to be done? I had to do the same thing with a custom "Lens" field so I could sort on the lens in Aperture.
The applescript support looks mostly like it is for reading things - it doesn't look like I can set metadata or do other tasks external with an applescript. Do I have this right?
Any hints on improving the performance of this would be greatly appreciated.
Thx.
J.

-I spoke with apple tech support and they said it
would run just fine on my PB G4 as configured.
The Aperture config checker software says it will
work.
he website says it will work.
Am I to presume I am to some how divine that all this
information is incorrect?
And Allen, after using Aperture since preorder days on a PB G4 - an obviously limiting piece of hardware - also says it works. Adequately for such underpowered hardware.
With all due respect, a laptop is a necessary piece
of pro photo gear. So that is not an acceptable
criticism either.
More than a decade of lousy Photoshop performance on laptops has conditioned me not to expect laptops to perform like desktops for heavy graphics apps.
They need to upscale the
'adequate' box recommendations.
You and I agree... but surprisingly there are lots of folks who simply accept what you and I call lame performance. They recognize it as lame, but accept it as a consequence of the hardware. Ergo Apple is disinclined to make the minimum configuration bar as high as you and I might like.
-Allen

Cannot renew code signing certificate - maybe bug with german Umlaut?

Hello!
Since one month I expierence a message that I should renew my code signing certificate and today I thought it is time to stop this message.
Because I could not find anything about renewing the certificate in Mountain Lion I used the KB-article that discribes the process for Lion.
http://support.apple.com/kb/HT5358
after that I get this in at my terminal:
sudo /Applications/Server.app/Contents/ServerRoot/usr/sbin/certadmin --recreate-CA-signed-certificate 'myserver.domain.de Signierungszertifikate für Code' 'IntermediateCA_MYSERVER.DOMAIN.DE_1' 7D3E2458
when I press return I get this:
/Applications/Server.app/Contents/ServerRoot/usr/sbin/certadmin Cannot find the certificate: myserver.domain.de Signierungszertifikate für Code
I checked it again and again - I cannot find any typo or something like that - so maybe Mountain Lion wants to renew the certificate in a different way or certadmin cannot cope with german "Umlaute" - "für" - in english for - but I did not gave this name it was given by the system when I setup the server one year ago.
Every hint is welcome, bye
Christoph

I am stupid - I read the KB article again and there it says
"When entering the hexadecimal serial number, ensure that all letters are entered in lower case."
I retyped the command with lower case hex numbers and everything was fine
Bye,
Christoph

HT2371 Language Issues(Maybe Bug??)

Hello, my iPad was changed to what I presume was Japanese, I managed to change it back, however second of the iPad are still in another language (weather, calendar, dates on the lock screen) is this a bug? Or is there anyway to fix this manually. Thanks!

Settings>General>International>Language
Also check Region Format.

Ah not the printer maybe something in Aperture ?

I found out it is not the printer....it is printing everything from my Aperture Library that I migrated over just fine...the printing problem lines occurs when I try to print things I have recently added to the library...sooo what do you all think

AS you know, you appear to be missing the controls on the right side of the Browser. Two suggestions:
1) try selecting the Split view instead of the Browser view to see if this is at least normal and then revert back to the Browser view.
2) the actual Browser window is not seeing your window dimensions correctly so try to hit the standard application Resize button on the screen once or twice to change the window size.
Let me know if neither suggestion worked!

Maybe bug in Aperture GUI

Similar Messages

Maybe you are looking for