Aperture aliasing issue?

Hi all,
I'm experiencing some aliasing/jaggies artifacts with certain images displayed at less than 50% zoom in Aperture 3. It's very noticeable in split-view and viewer only mode, and is still quite noticeable in full-screen mode. There is no aliasing apparent when the image is zoomed in to 100%. Wasn't 3.1 update supposed to fix this exact issue?
From the update notes: "Rendering of images scaled to below 100% in Viewer"
Here are some screen grabs (focus on the rail):
*Split view*
*Viewer only*
*50% zoom*
Is anyone else experiencing this?
Thanks in advance!

Would love to know if there is a fix/workaround for this issue.
Thanks!

Similar Messages

Arabic Language aliases issue in Web Analysis reports

Dears,
I'm using Web Analysis to build reports with aliases in Arabic language. Aliases appear as small squares. Is there any configuration or workarounds should I do to solve this issue?
Thanks.
Regards,
Ahmad.

Hi,
Make sure that you have the right version of JRE in the system. Please try this steps in one client machine
1. Uninstall all the version f JREs from a client computer
2. launch Web Analysis Studio from that client computer
3. It will prompt you to download & install the compatible JRE from the Web Analysis server into your client computer
4. Install the JRE
Hope this helps
Regards,
Nowshad.

Aperture viewer issues after full screen view - in Browser, Split View and Viewer modes

2012 MacBook Air, Mac OS 10.8.2, Aperture 3.4.3. Everything is up to date and, as usual, has been working just fine since the last update a few weeks ago. Full screen view never caused any issues... until today.
I tried quitting and restarting Aperture. Using another Aperture library. Quitting everything and restarting my MBA... same behavior.
I went into the full screen view, edited a photo and got out of the full screen view to export it.
All of the sudden, only one line of thumbnails was showing up in my Broswer view (out of 380 pictures in that project). Looking closely at it, it seems like the Aperture now thinks that the desktop area it has to work with (the dark gray area where the thumbnails are) is larger than the aperture window because a part of photo is showing up cut off at the right edge and no slider at the bottom:
(note: at the bottom it says 380 items displayed)
Going back to full screen view, everything looks and works as nothing has happened:
In Broswer view, if I scroll down such that the first row is out of the view, the second row of thumbnails shows up:
Now, if I scroll back up, two rows of thumbnails are shown in the viewer:
To get the third row to show up, I need to scroll down to get the top two rows out of the way and so on.
At some point I saw this weirdo but have not been able to replicate it:
Split View also has its issues - the photo itself is no longer centered and the slider at the bottom gets out of the way past the right edge of the Aperture window before reaching the end of the row of thumbnails:
Finally, when double clicking the photo in the Split View to view it by itself, once again it is not centered and cut off on the right side but there is no slider...
Any ideas? I tried looking through the Viewer-related threads on here and did not see anything close to this. Is there a way to contact Apple support? I found some form somewhere on the website, but it had a dropdown for operating system and nothing past 10.7.2 so I am guessing it is not being maintained...
edit: added the note under the first image

When the graphical user interface is misbehaving, it frequently helps to remove the Aperture preferences apple.com.Aperture.plist from your user library, see the Aperture 3: Troubleshooting Basics on how to do this.
Regards
Léonie

Aperture Library Issues on NAS - Advice Needed

List-
Need some practical advice here. I've got a 90GB Aperture library that resides on a NAS (QNAP 419P II) that is experiencing major issues. Understood that having the library live on a non-HFS+, non-local drive is not advised by Apple, but it's been there for two years with no issues to speak of.
I had a power failure occur that seems to have done some damage to the library in some way. Upon opening the library, I got an error that said that there were inconsistencies with the file and that it needed to be repaired. I repaired it, and noticed something strange. In almost all files, the picture resolution was poor and both the camera and lens information was gone--in addition to the fact that the Adjustments capability was disabled.
I ran the Aperture first aid and ran all three processes--concluding with the full library rebuild. It looked to be successful and resolution, previews, and picture info returned--but halfway through the preview reprocessing the process just stopped and the beach ball of death ensued. I let it run overnight and it never recovered. I had to force quit and now if I reopen the file it say that there are inconsistencies and that the library needs to be repaired, which won't help.
I also tried to move the library off of the NAS an onto the local drive, but encountered an Error - 50 message--something that apparently is well known in the NAS world where Mac permissions get screwy when dealing with non HFS+ drives.
I have a backup of the original library, but it is sitting in a cloud repository (CrashPlan) that will take time and money to restore.
All of the masters are intact in the Aperture directory, and I have very few major adjustments made to any photos. Aperture is really just a repository for me.
So any practical advice would be appreciated as to how I can create a new local Aperture library and get all of the existing photo files there. I am pretty much giving up on the idea of getting the existing NAS-based library to work properly, so this is more of a real-world question on how to create a new library and eliminate whatever issues there are with the other Aperture files. It looks like everything in the Aperture package is in place, but the library itself is just malfunctioning.
I am also considering moving everything into iPhoto as well, as Aperture may simply be more than I need for my usage. If is is faster and a but simpler to manage, that could be the right answer as well.
Thanks in advance for any ideas or guidance.

The problem is most likely with the library itself being located on the NAS.
But you can have a hybrid solution where the library is located on your internal drive while the actual image files are located externally, eg on your NAS. Image files stored within the Apeture library are called "managed" while image files stored externally are called "referenced". Whichever approach you take, the process is the same:
If you try to make a new Library from your masters, you will lose your project structure. The resulting mess will be in accordance to how you created your projects. Basically, if you look at your Masters folder, that's what you'll end up with when you import your masters. If that isn't a problem, the process is simple
Step 1: Prep.
Move or copy your masters out of the library bundle to a folder (to make them more accesible in finder).
Step 2: Create new library.
Within Aperture, from the File menu "Switch to Library -> Other/New..." to create a new Library on your internal drive.
Set the preferences to indicate previews/faces etc. I'd turn these off for now as they will slow you down.
Step 3: Import your images.
Within your new library, File -> Import - Folders as Projects. This gives you a dialog where you specifiy what and where to import.
If you choose "Import folders as: Folders and Projects" you will get a folder structure that matches the Masters folder, with projects at the end of the chain with names like 20120213-200100.
If you choose "Import folders as: Projects and Albums" you will get a single Project called "Masters" with a folder and Album structure that matches the Masters folder.
Neither of these will look particularly great. If you want to avoid this mess, here's what I'd try.
Fix your library again like you did before. After the rebuild, go to the Aperture activity window (SHIFT + CMD + 0) and cancel the preview generation process before it has chance to hang. This should give you a sem-functional library, hopefully functional enough for the next step:
Select all images and use File -> Relocate Original to move your original files out of the library. During this process you can specify that the originals are stored in sub-folders that match the project name, within a parent folder if required.
This gives you a much neater structure for importing into your new library where the projects will get the folder names (which will be your existing project names). It may not be perfect, for example if you have the same project name in different folders and don't/can't segregate them, but it's a lot cleaner than just importing your masters folder.
Andy

Aperture/iPhoto issue

some of my images in Aperture/iPhoto are appearing pixelated. any idea on how to get the issue fixed

Now my console is producing the following message when I try to import a iPhoto Library:
2/1/11 10:04:59 PM Aperture[4066] POST /WSComments.woa/xmlrpc (FAILED), httpStatusCode:500, errorType:100, transactionState:5, txnId:0DAEAB4A-6DB3-4870-BC3D-08F4A32CDCBD, auto-retries=0, manual-retries=0
2/1/11 10:05:04 PM Aperture[4066] Cannot load Interface Builder file 'NSAlertPanel'

Aperture performance issues.

Dear members:
After some disappointments with the latest version of Bridge (CS3) I decided to start working with Aperture as I found it offered some interesting tools for viewing and selecting images.
First I worked on some test images and everything went well. However, last night I did my first import of "real world" images and experienced severe performance issues.
I imported one folder containing 163 photos to two different locations - the folder and the images were the same but imported into two separate locations in Aperture as I was trying to create the ideal file structure for me.
These are the questions and/or problems I have.
1. This IS NOT a major problem. As much as I tried to import photos into an album or folder I couldn't do it. I don't like the project concept and prefer to have my images placed into folders or albums. My iPhoto library was imported by Aperture using this structure. The iPhoto library is a folder with albums as subdivisions as they were set up in iPhoto originally. However, this doesn't seem to be working as I import photos from other locations.
Q: How can I import photos into folders or albums and completely avoid the projects concept and icons ?
2. This IS major problem. Performance was very poor. I imported the folders last night and waited for approximately 30 min until I decided to turn my computer off. Aperture gave me a message stating that it was still generating previews and asking me if I wanted to quit. I pressed the OK button and turned the computer off. This morning I launced Aperture again and it went back to the spinning wheel on both projects. It must have taken approximately 45 min until the spinning wheels were no longer turning.
This is a problem for me as I have a library with approximately 15,000 - 20,000 images. The ones I imported last night were CR2 generated by a Canon 1Ds MK II (17 MB each). I can only imagine how long it would have taken had I chosen to import the 120+ MB TIFF images I also have in my library from slide scans.
My Aperture preferences have been set for Preview Quality = 12 and Limit Preview Size = Don't Limit. I have it set this way as I don't with to have reduced size previews so that (1) they can display with the highest possible quality as I mostly use the full screen mode for viewing and selecting images, and (2) in case I upgrade to a larger monitor in the near future (I have a 23" cinema display but am planning to upgrade to a 30") the previews will still work with that monitor.
Is this performace typical of Aperture ? I understand my camera is a professional camera that generates large images but isn't Aperture supposed to be a professional application aimed at professional photographers ? And what about those who work with 39 MB images from a Hasselblad or with scanned 120+ MB slide images ?
Is there something obvious I have forgotten to look at or set up in Aperture ?
Thank you in advance,
Joseph Chamberlain

Steve:
Thank you very much for your reply to my post and for your suggestions. Some comments about my experience appear below. I am grateful for your help and don't wish in any way to discuss what you recommend below. I just wish to share my view of this issue and also to try to find the best answers for my problem.
For 1, use File > Import > Folders Into A Project. That will retain your folder
structure using brown folders and albums.
See:
http://www.bagelturf.com/aparticles/library/fivesimple/index.html and
http://www.bagelturf.com/aparticles/library/brown/index.html and
http://www.bagelturf.com/aparticles/library/libinadv/index.html
A. You can't. Projects are the container for everything in Aperture. No
projects, no images. So just live with them and subnvert them any way you
like. I don't have "projects" so I just use months, vacations, events, or
whatever keeps my image collections a reasonable size.
As an user I would like to have control over my own filing structure. This works quite well in iPhoto and I don't understand why Aperture chose to adopt this less flexible file structure. Also I noticed that the imported iPhoto library appears in Aperture inside a folder with multiple albums. Since Aperture can do this for iPhoto I find it hard to understand why it can't do for other imported images.
2. Turn off previews and delete the ones you have. When you find you need > them, use them selectively:
http://www.bagelturf.com/aparticles/previews/pwho/index.html
As stated in my previous post I always (no exception) use the full screen mode for viewing my images which is similar to a slide show. So according to the web page you reference above I would fall under the category of users that need previews.
You don't need high res previews. Aperture already generates thumbnails
for you.
General speed tips:
* Get the best video card with the most RAM you can afford
I can't. My computer is fairly new as it was purchased a little more than 2 years ago. Although it is a fairly new computer Apple no longer offers parts for it. My video card is an ATI Radeon 9600 Pro with 64 MB of VRAM installed. I have contacted Apple about this issue and they tell me there is nothing they can do. I have also contacted both ATI Radeon and nVidia and both have discontinued the only two cards they would work in my system (X800 XT Mac Edition and GeForce 6800, respectively).
* Smaller screens are faster than larger screens
My screen is 23" which I would consider to be a medium size screen by today's standards. However, isn't the purpose of working with Aperture to be able to develop a professional workflow ? And don't most professionals like to use large screens to view their work ?
* Avoid H&S adjustments until all the others are done
* Make sure you have sufficient RAM (2G minimum, 3G on a Mac Pro)
My system has 2.5 GB RAM installed. It has been suggested to me that I should add another 1 or 2 GB RAM as it would improve performance significantly. I have no problem doing that and would welcome that solution if I knew for a fact it was going to address my issues. However, I have already invested too much on hardware and software while still finding myself struggling with the issues I have described. Do you think the additional RAM would solve the problem ?
* Don't use previews unless you need them
Based on what I have read on the pages you referenced it seems to me I am one of those users who needs previews.
* Keep projects small. Use blue folders to group projects
My current filing structure is simple - I four folders each with subfolders containing in average 200 to 1000 images each. Some have as little as 1 image and some have 1000. But the majority would fall in the 300 to 400 images range.
* Rebuild the database once in a while
* Quit other apps if memory is restrictive
It seems in this case that the RAM upgrade I mention above would be helpful. Would it allow me to run other applications while also running Aperture without any noticeable performance alteration ?
To a great extent you have to rethink your workflow once you use Aperture.
Many people do a lot of unnecessary things because they are coming from
an environment that forced them to. Start from scratch and ask yourself
why you do everything you do. Much of the effort you will find is wasted
because Aperture either does it for you or make it unnecessary.
I am trying to simply my workflow as much as I can but not at the expense of quality. Bridge CS2 did a very good job for me. In many ways it was the perfect application althout it didn't have many of the great features I find in Aperture for reviewing and selecting images. First it was simple - all you had to do was to create your own file structure and then point Bridge to the folders as it would create its own previews. Second it was fast - this process happened a lot faster compared to Aperture and Bridge CS3. Third it was high quality - the previews generated were high quality and could be seen with amazing resolution while in slide show viewing mode on my 23" screen. My upgrade to Bridge CS3 was disastrous as (1) it has many bugs Adobe hasn't taken the time to fix, (2) it is slow on average machines requiring the latest hardware to run efficiently which is unrealistic for most consumers and (3) the previews generated are soft and appear pixilated and in poor quality while in slide show view.
I am going back to Aperture after a very disappointing start as I was one of the very first to purchase the software as soon as it was introduced only to be frustrated with all of its bugs and design flaws. Aperture has one of the best interfaces I have seen on any imaging application and I would really like to use but after this new attempt to use and the barriers I have encountered I am not sure I can.
Joseph Chamberlain

Font Anti-Aliasing Issues in HTML/Ajax based Air Applications

It seems that the font-renderer in HTML/Ajax based Air Applications is using some kind of sub-pixel font renderer that is overriding and vastly inferior to the standard Windows ClearType, or any Apple based option as well. This problem is particularly noticable with light text on a dark background, and made worse the smaller the text is. I've put together an example image explaining exactly what I mean at: http://regator.com/fontRendering.png (it's a large image 1126 x 1500 px)
My example shows two fonts at four different sizes rendered in an HTML Air App vs the default Windows Cleartype, as well as using Safari to show the Font style anti-aliasing. In all cases the HTML Air App rendering is far more difficult to read, and in many cases severely distorts the color of the text in a way that other subpixel algorithms do not. As far as I can find after literally hours of googling and searching there's no way to override this in HTML based applications. Is there any solution to this, or a planned fix for the renderer? Other than this rendering issue, the HTML interface for creating Air apps is absolutely brilliant, this is just making my finished product look significantly less polished than it otherwise would if the text were more readable.
Thanks.

Dear caturner81, dear Adobe,
is there a solution to this problem? I'd really love to fix the aliasing thing in Air/HTML!

Aperture file issue

Dear Kirby, reading some of your threads, I am very impressed by your knowledge about special issues concerning "Aperture", and would be most obliged to you, if you could possibly help me with a suggestion with regard to the below issue:
I just returned from a trip to Vietnam bringing along home 2000 photos, approx. 50 GB, and having started my editing them, I discover an unacceptably, and so far not observed, slow rendering, f.inst. when dodging and burning. Therefore I would appreciate any hint given to me about what to do to change this unbearable situation - thus, it may take up to 5 seconds to render f. inst a burning process.
Operating System: Mac OS X 10.7.2 Lion
My hardware:
Macbook Pro Intel, 8GB, HD: 500GB, Free: 142GB, 28%, 142GB pictures contained on the hard drive - and a great deal of relocated masterfiles to external disks.
5 Nik software plugins installed, but they are NOT in use all of them at the same time.
Have tried to shift from 32 to 64 bit, but without a remarkable effect.
Very best regards
Per
[COMPLAIN]
[IGNORE USER] [BOOKMARK] [REPLY THIS MESSAGE] [QUOTE]
< Title Edited By Host >

Our Host was nice enough to start a new thread with this post, which had been mistakenly posted as a reply in another thread. The OP, however, has already started his/her own thread. Please reply there.
Replies to this are better put in this other thread.
Thanks.

Aperture 3 issue

When i start my aperature application i will not open. I paid 200 dollars for the program and i would like for it to work. When i open the program it says "There was an error opening the database for the library “~/Pictures/Aperture Library.aplibrary”." I am not sure what this means and what the issue is i just want the program to work.

I suggest starting with the troubleshooting basics listed at the link below:
http://support.apple.com/kb/HT3805
Note - you can try creating a test library by holding down the 'Option / Alt' key while launching Aperture > Create New button > create a 'Test' library on the desktop to see if the issue is with the library or application.
Successfully creating a library tells you the issue is with the library the error message is referring to. If unsuccessful, then the issue probably lies in the application and a re-install might be called for.

Aperture Upgrade Issues (since Snow Leopard Install)

I upgraded the OS on my 2007 iMAC7,1 Intel Core 2 Duo 2.4 GHz to Snow Leopard a couple of months ago. Afterwards, when I tried to start Aperture, I got a message that my version of Aperture (1.5.6) was not supported under the new OS.
So today, I went to the Apple store and bought an upgrade to Aperture 2. The upgrade version is 2.1.1. I installed this and when I start Aperture, the app appears to start, the "intro" white screen comes up with the version / serial number, etc, and then the Welcome Screen starts up.
No matter what I choose from the Welcome Screen (Usually I pick Start Using Aperture), the SW appears to be stuck. The welcome screen disappears as expected, and the command bar across the top of the screen appears, but that's it - the normal aperture screen that shows your projects, etc. never comes up. Most of the commands in the sub-menus on the command bar are grayed out.
To make matters worse, when I try to quit, nothing happens. No message, no nothing, it just sits there. I have to do the Option-Cmd-Esc sequence and kill Aperture.
I checked for SW update and updated everything that was available (OS and Aperture to 2.1.4), rebooted, etc. However, there was no change in behavior.
Everything else on this machine works fine, no other issues or even behavior changes in my machine. The only problem is with Aperture.
To summarize: Aperture 1.5.6 quit working after I installed Snow Leopard. I bought the Aperture upgrade and installed, which allows me to start Aperture but doesn't let me do anything further.
Has anyone else seen an issue like this? Any suggestions for what may be wrong?
Thanks.

You may want to try rebuilding the library or doing a consistency check. Hold command-option when you launch Aperture and choose the relevant options.
Note that Aperture 2.x will have to upgrade the library from 1.x to run. You should get a dialog box to kick this off (and it does take some time), but it sounds like you haven't even gotten that far.
You do need to be running Aperture 2.1.4 on Snow Leopard, but from your description it sounds like you're already on that version.

FCPX and Aperture Library Issues

Does anyone else have issues with FCPX being unbearably slow when loading an Aperture library when accessing the Photos window on the lower right? I have all the most current versions of both Aperture and FCPX. I have a Macbook Pro Retina with i7 2.6gig processor. 16 gigs of RAM. My Aperture library is very large, about 300,000+ images. The Aperture is located on an external Thunderbolt drive. It can take as much as an hour for the still images to show up in the photo window. Any suggestions our there for speeding this process up. It's one of the main reasons I use Aperture, the supposed terrific integration between all Apple programs. I this speed it's much faster to just export the images and forget about going through FCPX. Any suggestions are greatly appreciated.

If you don't need all 300,000+ images in FCP, I would export what you need and import it into the event library.

Aperture Installation Issues

I have a 20" iMAC G5. Trouble installing 1.5.2 and earlier versions. Have downloaded 1.5.2 and received a 1.5.2 disk from Apple. When I insert the Aperture DVD and click on the "Install Aperture" box I get this message:
"CheckToolAlertEnhancedTitle" with buttons to cancel or continue. When I choose continue, nothing happens.
My system has more than the minimum requirements for running Aperture. And I use it on my Powerbook 17" with no issues.
Thanks for your help!
Bill

Here's the Aperture crash log... guess I tried more than a few times!
Should I delete everything I can find with "Aperture" in the tile and try to reinstall?
Bill
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 16:32:58.647 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 178
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 16:33:45.225 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 182
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 16:51:16.130 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 240
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 16:54:14.224 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 243
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 16:57:14.720 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 255
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 16:57:38.607 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 257
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 17:00:14.290 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 260
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 17:00:25.878 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 262
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 17:00:31.373 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 264
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-03 17:06:21.425 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 269
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 09:27:11.761 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [56]
Version: 1.5.2 (1.5.2)
PID: 271
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 09:27:35.745 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [56]
Version: 1.5.2 (1.5.2)
PID: 273
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 09:27:41.433 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [56]
Version: 1.5.2 (1.5.2)
PID: 275
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 09:28:03.943 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [56]
Version: 1.5.2 (1.5.2)
PID: 277
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 10:02:20.132 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [91]
Version: 1.5.2 (1.5.2)
PID: 266
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 10:07:22.743 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [54]
Version: 1.5.2 (1.5.2)
PID: 174
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 10:36:59.513 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [58]
Version: 1.5.2 (1.5.2)
PID: 183
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 10:55:26.002 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 176
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-04 10:56:34.661 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 182
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-14 19:28:24.212 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 630
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-14 19:28:32.093 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 632
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-14 19:28:45.768 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 634
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-14 19:29:29.114 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 637
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found
Host Name: William-K-Guegold-iMAC
Date/Time: 2007-02-14 19:29:33.987 -0500
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [59]
Version: 1.5.2 (1.5.2)
PID: 639
Thread: Unknown
Link (dyld) error:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found

Smart Object Anti-Aliasing issues in PS CS5

I am having a heck of a time working with smart objects that contain transparency in CS5. Here is an example of what I'm experiencing:
1,700px smart object scaled down to 156px. No transparency in SO. Good anti-aliasing.
Same smart object, but with a layer mask or transparency in the smart object. But alas: horrible anti-aliasing, throughout the entire image.
I frequently embed my transparency within the SOs I work with, due to the limitations of linking embedded SOs with layer masks etc. I experienced no problems in CS3. I'm thinking this is a bug? Does anyone have any insight? Thanks!
UPDATE: after performing many tests, and noticing that having transparency in a smart object does not necessarily lead to poor anti-aliasing in the parent image, I have narrowed-down the issue. The issue will occur only if at least an antire column or row of pixels (of any height/width) along the border of the image are transparent. It does not matter if the transparency is at the top, bottom, sides, or surrounding the image, but it must take up some amount of an entire side. This is looking more and more like a bug... Is anyone able to replicate the issue? (Adobe engineers?) Thanks.

Here is the file I'm seeing this in. Incidentally, if I drag the problematic smart object to another open image, the appearance is the same (Photoshop is, after all, the epitome of wysiwyg software). But this works both ways: I can also re-create the smart object in another document without the poor anti-aliasing, then drag it into the original image and it will still look fine. (in this file there are two side-by-side, so that you can compare the two. you can also play with the smart object on the left to see the anti-aliasing go from good to bad; just go into the SO and delete a row or column of pixels from the border and re-save).
http://dl.dropbox.com/u/8162462/SO-aa-issue%3F.tif
(i used Dropbox; lmk if there's a better way to post a file in this forum)
Since I just started using CS5 (from CS3), I have suspicions that it may be a version translation issue (either in the TIFF or smart object). Either way, I'm glad that this is not a common or easily-reproduced issue. Let me know if you learn anything from the file
Thanks,
Cory

Aliasing issues in ACR 6.4 output, jagged edges

In images with high frequency detail, aliasing occurs that is most visible in diagonal directions. These jagged edges are noticable in the output, and obviously get worse in enlargements which is also the main reason I post this.
To date, I've found 2 workarounds:
process in ACR, duplicate layer in Photoshop, apply gaussian blur around 0,5px, and manually paint on the offending jagged edges
use another raw converter
For demonstration purposes, I've taken an old and unspectacular D3X NEF from imaging-resource.com. It's a picture of a house and some trees etc. I've used:
Camera Raw 6.4 with default settings (first row): aliased edges
Capture One Pro 6.2 with default settings (middle row): anti-aliased edges but introduction of false (green) colour
Raw Developer 1.9.1 with default settings (bottom row): anti-aliased edges free from artifacts
Some (100%) area's where the aliasing shows:
At first I thought the difference was due to the sharpening in these 3 convertors. Forgive me if I omit showing a comparison and just assert that turning of sharpening and replacing it with Photoshop remove lens blur, didn't help. It just showed the defects apparantly already present in the (ACR and C1 processed) file.
The result however from a properly sharpened, denoised, and upsampled TIFF that originates from Raw Developer is impressive. However, given the fact that Raw Developer is Apple OSX only, and I do post-processing on Windows, it introduces a bit of an unpracticality.
Is there any possibility to eliminate this unpleasant aliasing in ACR, so I can keep a high quality Adobe-only workflow?

The "blocky" details are easily reproduced in that image. Looks like something that needs to be tuned up to me.
Note that you have the option of choosing the 2003 process in Camera Raw, which appears to avoid that issue.
I just want to add one thing: There's no upsampled resolution available for this particular camera. 6048 x 4032 is the largest size available. I for one prefer to convert my raw files directly to upsampled resolutions on the theory that it might improve this kind of thing (and it does seem to deliever more accurate detail with my now out-of-date Canon cameras). At some point in the past I requested that Camera Raw make several upsampled resolutions available beyond the "native" camera size for any/all cameras. I hereby renew that request.
-Noel

Aperture 3 Issues: "Apple" Raw Preset Override, Viewing, + Flickr

I have created a RAW preset for my Canon camera and asked Aperture to save it as my default. However, each time I load aperture, the "Apple" preset overrides my specific RAW camera preset. For some reason, the default "Apple" preset maxes out the boost.
Also, hitting the "v" key to change views is behaving erratically. The Inspector/Image view will simply not be in the cycle sometimes. I have also experienced my RAW files flickering when changing views, resulting in CPU overload.
And just some final comments: I'm glad to see Flickr integration, but more options would be nice. I'd like to be able to delete the aperture/flickr project without it actually deleting my flickr set.
Thanks for any help...
Jacob

i have the same issue..the raw preset does not stick....

Aperture aliasing issue?

Similar Messages

Maybe you are looking for