Aperture Color
I'm having an issue with color in Aperture, and after hours of playing around with various options, I'm nowhere close to a solution. This color profile thing is literally something you need a masters degree for.
So, the basics: I shoot all RAW in sRGB workspace (set in my camera, though from what I understand, the color profile in-camera doesn't matter when shooting RAW).
1) I import the RAWs to Aperture, and make adjustments there. This is what the image looks like in Aperture:
It's nice, overall, but lacks the punch of a proper skin tone. What gives me great results is when I go to Edit -> Photoshop CS5. That opens up the document as a 16-bit PSD in Photoshop. Once there, I simply go to Edit -> Assign Profile, where I assign AdobeRGB. Here you can see what the image looks like then:
The greens really pop, and the skin tone has a nice, saturated feel, as opposed to the zombie-like appearance prior.
So I figure, great. Job well done. I click Save, and look at the file in Aperture.
This is where the problem lies. In Aperture, the image looks just as it did in Photoshop, but the green channel appears muted. VERY muted. Compare the two images here: First is in Photoshop, the second is the saved version in Aperture:
If you pay attention to the detail in grass in the low part of the image, you will notice how muted it appears in Aperture. And I cannot figure out why. I need the image in Aperture to look the way it does in Photoshop after I assign AdobeRGB profile to it. Green channel is important to me as I shoot a lot of kids outdoors in grass. If anyone has any ideas I would love to hear them! Thanks!
I will take that as you do not want to know how to make this stuff actually work the right way.
The reason this is happening is one of two reasons with the following supposition:
The PSD being sent to PS is NOT adobe RGB (see export settings) and you then Apply vs Convert to Adobe RGB giving you a profile that does not match the actual color data - hence the shift (not a good practice but if you want even more "enhancements" choose even a narrower gamut and then assign the widest one available - ohhhhh look at the purrrty color)
and -
A) After assigning your profile the copy of the PSD is not being read by Aperture/Saved by PS
or
B) You have found a very very subtle bug in Aperture when dealing with images that have bogus profiles assigned to them because the behavior is strange. On a positive note you can use the bug to enhance your creativity!
RB
Ps. You should probably learn how color works someday being "creative" and all that. Cause you know us people that have figured stuff out - we are not creative at all. I mean look what happened to Shakespeare when he learned how to write - no that's a bad example - ummm, oh yea - I guess creative people really do have to know how stuff works.
Similar Messages
-
Is the 3rd party plug-in 'Synthetic Aperture Color Finesse' which comes with Adobe After Effects, free to use? 'Synthetic Aperture Color Finesse' installs its documentation in the plug-in’s subfolder in the Plug-ins folder.
I cannot locate anywhere on the Adobe site which specifies that this plug-in is free to use for educational institutions.
Can anyone assist please?
Regards
Susan O'Reilly
Staffordshire UniversityYes, it's free and inclusive with every AE install.
Mylenium -
On-screen proofing - please help me get my head around Aperture color!
The context: I recently sent some files for printing to an online lab, and found the prints looking very dull and "muddy" compared with what I'd seen on the screen of my iMac 24".
Looking for what I'd done wrong, I experimented with "on-screen proofing", but I was surprised to find that using a big variety of proofing profiles, the "proof" display looked hardly any different from the "raw" display. I even checked that it was working at all by using a b&w profile!
Next I calibrated my monitor using a Spyder2Express. This isn't the most full-featured tool, and I calibrated the monitor to gamma-2.2, white point "native". Now the screen looks a lot duller.
Going into Aperture I again find the same thing with "soft proofing" - changing the colour profile makes hardly any difference. What also surprised me was that using my original screen profile "iMac", the display doesn't look like it did before I calibrated the monitor (if you see what I mean ..)
Obviously there are some tricks I'm missing here. If someone could set me straight, or mention some resources for this specific question, I'd be very grateful!as a photographer I know the frustration you suffer from , very well.
Once upon a time photographers went to the "darkroom". there they cutted stripes out of photopaper, exposed them in diffrent lengh to the light under the filmp rojektor.Then developed them and compared to decide, how finaly to expose and develope the Image.
To get a good print out of your picture I have some sugestion.
A ) try until it fits :
if you want to go on with the onlinelab, take the picture you got and change the settings in Aperture according to what you think is not right.
f.exemp.: +10% contrast, -50 % Booster, +20% saturation. then "save as" and
name the file xxxxx_v1.jpg . Next version you increase all changes values for another 10 %. then send the pictures to the lab and see what comes close to your expectations.
B ) change the fotolab :
you will get a beter result if you decide your nice pictures are worth some more cent. You choose a recommendet digital fotolab. One benefit willl be, they´ll tell you how to set your color managment so it fits best to their printer.
next you bring one picture file to them to print. next you make the correction you want to come close to what you want. so here we are what Micheal suggestet.
C ) do it yourself :
get your own good printer like Epson 2400....
Please don belive that a cheap printer does the same like the one mentioned above.
here you will spend more money than on way A+B, but in the end you´ll have prints wich look like you want, on the fineart paper you want them and they will last very long time.
D) the professional way wich may include also B+C:
You want or need professional quality and have the money to spend on it.
Sorry, but no Apple Monitor comes close to a hardware calibratet Monitor. Maybe they are semi-professional. I dont say this to insult Apple, ore somebody else, but i say this to sway out the illusion, " if I just spend more money on the calibration tool and software, I´ll have better prints". It´s just not possible, because the monitor cant show what is there. A Apple CRT monitor is far better in this. I you want to have a flatscreen TFT monitor to bring good results you have to choose one that is able to be hardware calibratet and has a higher lookup table (EIZO, LaCie, QuatoGrafics......)
I use use one professional EIZO CG21" and one semi-prof. EIZO FlexScanL985EX(21") and the diffrence is importand betwee the two.
But i need only one to be Print Proof ready.
Before i was always afraid when i gave the picture file to my client, because of what my pictures look like once it is printet. Now the outcome is right or differs only very little from what I saw on the screen.
my calibratiob tool is EYE ONE.
I write in such lenght, because in the beginning I thought I could get arround to by prof. hard-and software. I lost a lot of time and money in that way. so now i know
Cameras I use: D200, D5
G5 dual 2.3/4,5 gigRam/ATI 9600 128MB-PB G4 12" Mac OS X (10.4.2) EIZO CG 21"+EIZO L985ex 21"
G5 dual 2.3/4,5 gigRam/ATI 9600 128MB-PB G4 12" Mac OS X (10.4.8) EIZO CG 21"+EIZO L985ex 21" -
Aperture color space / working space
Something I have been wondering for some time now, and didn't find a real answer so far: what is Aperture's internal color space? Is it ProPhoto RGB? Does Aperture know about the camera's color space (i.e. how does it map my RAW data to its internal color space)?
What I noticed is that images are converted to AdobeRGB before sending them to Photoshop for editing; unless this is Apertures working space (which I hope it is not), it would make sense to change that to the working space. One could work around that by first exporting a TIFF in the appropriate color space, editing that and then reimporting it to Aperture, but this sounds rather unpracticable. And again, one should know what exactly the internal working space is, to avoid conversion losses.
I'm grateful for any suggestions,
BernhardI don't know that there is a background color space. As I said, if someone is working with a point and shoot digital camera vs. a Canon 1Ds Mark II, the range color the chip can capture is likely to be very different. In that case Aperture make work differently for each camera. I don't really know.
I think your question touches on the ongoing debate (it's been years now on Photo Forums) as to whether or not you can really profile a digital camera. Some say yes, some say no. The ones who say yes are the ones selling profiling software and charts. Capture One allows for custom input profiles. The ones saying no are promoting software that doesn't allow for custom input profiles (ACR, Aperture, any camera manufacturer's software). I think the theory on the "no" side is that with a camera the range of color is limitless therefor there is no way to really profile it. This is as opposed to something like a scanner that has a limited amount of color it can see and needs to reproduce.
I know that ACR has two types of general guides within it (one for daylight, one for tungsten) for each camera and then interpolates between the two. I say "guides" because I don't know if they are really termed to be profiles or if another name is more appropriate. -
Aperture, Color Space, Printing, Oh My!
Any help with these is greatly appreciated. I've read countless articles and forums, only to be left with these questions because no one can answer them.
1) In RAW only if I want to print with my B9180 and process in Aperture, does the in-camera color space settings even matter? I do use soft-proofing in Aperture for the HP papers I use. Everything I read about it says Adobe RGB in-camera should be used when making your own prints at home, but they are always referring to printing from within Photoshop, but I don't use PS, so I'm confused about this with Aperture.
2) Now, what if I shot JPGs? Will in-camera color space matter in this same scenario (Aperture, B9180 printing at home)?
3) Using Aperture in a JPG workflow, does the application see the in-camera color space I selected or does Aperture have its own color space? Or is it selected based on the soft-proofing profile I use?Henrik,
That's an awful lot of words but none of it gets at the day to day use of the program or really provides and answer for the original poster of the thread.
Yes, of course a soft proof is a simulation. That's why it's a soft proof. It's also never going to match the output exactly. It can't.
Strip away all the science under the hood as it relates to soft-proofing in Aperture (part of Jerry's question #3) and the questions are:
What is this?
When should I use it?
How do I use it?
What? It's a way of getting a sense of how your image will look when output. It requires that you are working on a calibrated monitor and you need an output profile in order to use it. It will never match your output 100%. It cannot due to screen vs. paper, how the color on each is created, gamut and contrast of each, etc.
When? In Aperture you should work on your image with "Onscreen Proofing" turned off. Why? because you should work your images as best possible without initial regard for the output. It may end up being output for different uses in the future (screen, inkjet print, offset printed, etc.) You can use Aperture's "Onscreen Proofing" if you want get a sense of how your image will look when output. You don't have to, just like you don't have to in Photoshop. If all you are doing is outputting to an in-house inkjet printer you could just make a test print via color managed printing, see how it looks, and then adjust as needed. But if you want to get sense of what's what and whether you need to make any changes before you hit "print" then you can do the soft proof. The soft-proof would also be helpful heading off issues if you are not printing in-house (again, assuming you have a correct output profile.)
How? In Aperture to get a sense of how the output will be you need to select your output profile in View>Proofing Profile and then turn on Onscreen Proofing, View>Onscreen Proofing. Now, you can turn on and off the proofing feature to get a sense of how the image will be reproduced. If your image is not soft-proofing as you expected or want you can create a duplicate of the image file. Then alter that to bring the image as close as possible to the feel of the non-proofed image. This is similar to Photoshop where you can "Proof Setup" and the duplicate your image and/or create additional image layers to bring the image more in line with your intention or expectation.
Jerry - FWIW, I know you posted about an HP printer in another thread. See the comments here,
http://digitalmedia.oreilly.com/2007/02/13/insideaperturepodcast-9.html . There seem to be some HP printer based issues with regard to Onscreen proofing. This link also has a podcast with Joe Schorr, Apple's Senior Product Manager for Aperture, specifically about color management and onscreen proofing in Aperture.
Jon Roemer
site: http://www.jonroemer.com/
blog: http://jonroemer.typepad.com/jon_roemer/ -
I went to Dallas Blooms, a seasonal display of magnificence. Tulips and flowers abound everywhere. Just amazing. Took lots of pictures with two cameras.
I am really disappointed. When I go to view them the first time in Aperture, there is this brief moment they look normal. Normal saturation primarily. Then it blinks quickly and reappears with oversaturations of colors, especially red.
Any idea what is happening? Is it applying some kind of automated color profile? The colors are so dramatic and overblown I'm having to retouch every picture by desaturating colors, especially reds.
Any ideas?
Thanks,
RobertI'm still having this problem. I've scanned in 800 older photos. I have to lower the red in almost every photo. I recently went to Fort Worth botanical gardens. Reds are again way oversaturated. There is this brief moment where I can see the colors all look natural and balanced overall. Then Aperture is overlaying some kind of color profile (maybe?) that causes all the colors to slightly oversaturate, especially reds.
I'm using TIFF files for the scanned pics, combination of RAW and jpegs for the botanical pics. I didn't have this problem until maybe the last 12 months or less. I'm thinking there was some kind of upgrade to Ap3 and I noticed it after that.
I'm still using my 17" MBP and thunderbolt display.
Has anyone else had this problem and any idea how to fix this?
Thanks. -
Looking for iPhoto effect like presets for Aperture.Color Boost/Edge Blur
Hi all,
I am a hobbyist photographer who made the jump from iPhoto to Aperture a little over a year ago. For the most part Aperture is a way more capable editing package than iPhoto. That said, ever now and then, I miss some of the basic effects that were available in iPhoto. In particular, the "Color Boost" and "edge Blur" effects - has anyone seen Aperture presets that mimic these iPhoto effects?
Thanks very much!dsquid:
Welcome to the Apple Discussions. I get the same effect. I don't know if its normal or not. When viewed or printed at anything but very, very large the pixilation is not readily apparent.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file. -
IPhoto/aperture color print problem - want help
I have used my Canon i9900 many times. Suddenly, it will not properly print if I tell it to print on photo paper. If I make it think it is "plain paper," the colors come out ok. but if I set it to print on photo paper, the colors are very off.
Any help appreciated.Questions about your Printer are best taken up with the Manufacturer
Regards
TD -
Color space comparison in PS versus Aperture 3
Photoshop uses ECI-RGB color space in its RAW conversion process. What color space does Aperture 3 employ? Are we comparing Apples to Apples with initial RAW processing with these systems?
ThanksFrom Aperture: Color and gamma settings for print and web
Setting your colorspace in Aperture
In contrast with Adobe Photoshop, you don't have to set your "workspace." Instead, Aperture will always work in a wide gamut, except for when you apply Onscreen Proofing, which shows you how your work should look in final output. When you know your project is bound primarily for one medium, such as RA-4, it's a good idea to leave Onscreen Proofing on all the time while editing, which would give you the equivalent effect of setting your workspace.
Also see this thread: How can I set my work space to sRGB or aRGB & let Aperture handle color mgt -
Aperture crashes when using NIK Plug-In
I have a Mac Pro 2008 8-core 2.8 with 16 GB ram and the ATI HD 5870.
Sometimes in Aperture 3 (newest update) when using NIK plug-in colorefex pro 4 it crashes.
It only crashes when performing certain tasks, like certain recipes. Or more often when I try to edit multiple images at once with the plug-in.
The plug-in works fine with PS, but you can not edit mulitple images at a time.
As per NIK's suggestion, I deleted any duplicate arial fonts but it hasn't helped.
Thanks for any help,
here's my crash report
Process: Aperture [1900]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.2.1 (3.2.1)
Build Info: Aperture-201094000000000~2
Code Type: X86-64 (Native)
Parent Process: launchd [170]
PlugIn Path: /Library/Application Support/Aperture/*/Color Efex Pro 4
PlugIn Identifier: com.niksoftware.cep4.aperture_edit
PlugIn Version: 4.0 (4.0)
Date/Time: 2011-12-08 15:44:48.904 -0500
OS Version: Mac OS X 10.7.2 (11C74)
Report Version: 9
Interval Since Last Report: 788756 sec
Crashes Since Last Report: 20
Per-App Interval Since Last Report: 317967 sec
Per-App Crashes Since Last Report: 10
Anonymous UUID: F7B82CE4-FBF4-44B5-8BD0-52AED3F4B94C
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000004c
VM Regions Near 0x4c:
-->
__TEXT 0000000100000000-000000010078c000 [ 7728K] r-x/rwx SM=COW /Applications/Aperture.app/Contents/MacOS/Aperture
Application Specific Information:
objc[1900]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.ATIRadeonX3000GLDriver 0x000000010d97503f 0x10d91f000 + 352319
1 com.apple.ATIRadeonX3000GLDriver 0x000000010d94e622 0x10d91f000 + 194082
2 com.apple.ATIRadeonX3000GLDriver 0x000000010d95db80 gldUpdateDispatch + 202
3 GLEngine 0x000000010cf02b42 gleDoSelectiveDispatchNoErrorCore + 352
4 GLEngine 0x000000010ce390bc glGetTexLevelParameteriv_Exec + 2387
5 com.niksoftware.cep4.aperture_edit 0x00000001a0df3461 luabridge::rawgetfield(lua_State*, int, char const*) + 5007156
6 com.niksoftware.cep4.aperture_edit 0x00000001a0e138fd luabridge::rawgetfield(lua_State*, int, char const*) + 5139408
7 com.niksoftware.cep4.aperture_edit 0x00000001a0e14798 luabridge::rawgetfield(lua_State*, int, char const*) + 5143147
8 com.niksoftware.cep4.aperture_edit 0x00000001a0dbc40a luabridge::rawgetfield(lua_State*, int, char const*) + 4781789
9 com.niksoftware.cep4.aperture_edit 0x00000001a0dbc6b6 luabridge::rawgetfield(lua_State*, int, char const*) + 4782473
10 com.niksoftware.cep4.aperture_edit 0x00000001a0da3783 luabridge::rawgetfield(lua_State*, int, char const*) + 4680278
11 com.niksoftware.cep4.aperture_edit 0x00000001a0db3432 luabridge::rawgetfield(lua_State*, int, char const*) + 4744965
12 com.niksoftware.cep4.aperture_edit 0x00000001a0f1b0ac luabridge::rawgetfield(lua_State*, int, char const*) + 6218623
13 com.niksoftware.cep4.aperture_edit 0x00000001a0bfb791 luabridge::rawgetfield(lua_State*, int, char const*) + 2943588
14 com.niksoftware.cep4.aperture_edit 0x00000001a0d63bcc luabridge::rawgetfield(lua_State*, int, char const*) + 4419231
15 com.niksoftware.cep4.aperture_edit 0x00000001a0f05b3a luabridge::rawgetfield(lua_State*, int, char const*) + 6131213
16 com.niksoftware.cep4.aperture_edit 0x00000001a0f063e4 luabridge::rawgetfield(lua_State*, int, char const*) + 6133431
17 com.niksoftware.cep4.aperture_edit 0x00000001a12b3bae nbError nbGaussianBlurYoungVanVlietWorkerUInt<unsigned char, nbTileSet, nbTileSet, nbTileSet>(nbTileSet const*, double, nbTileSet*) + 277102
18 com.niksoftware.cep4.aperture_edit 0x00000001a12b4318 nbError nbGaussianBlurYoungVanVlietWorkerUInt<unsigned char, nbTileSet, nbTileSet, nbTileSet>(nbTileSet const*, double, nbTileSet*) + 279000
19 com.niksoftware.cep4.aperture_edit 0x00000001a0a48a68 luabridge::rawgetfield(lua_State*, int, char const*) + 1162555
20 com.niksoftware.cep4.aperture_edit 0x00000001a128c888 nbError nbGaussianBlurYoungVanVlietWorkerUInt<unsigned char, nbTileSet, nbTileSet, nbTileSet>(nbTileSet const*, double, nbTileSet*) + 116552
21 com.niksoftware.cep4.aperture_edit 0x00000001a0bed0a8 luabridge::rawgetfield(lua_State*, int, char const*) + 2884475
22 com.apple.AppKit 0x00007fff8ca950cc -[NSView _drawRect:clip:] + 3995
23 com.apple.AppKit 0x00007fff8ca92d7e -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3020
24 com.apple.AppKit 0x00007fff8ca9386f -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 5821
25 com.apple.AppKit 0x00007fff8ca91ab3 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 270
26 com.apple.AppKit 0x00007fff8ca8cec9 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4755
27 com.apple.AppKit 0x00007fff8ca8593e -[NSView displayIfNeeded] + 1676
28 com.apple.AppKit 0x00007fff8ca8507d _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 648
29 com.apple.CoreFoundation 0x00007fff8fcf1f37 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
30 com.apple.CoreFoundation 0x00007fff8fcf1e96 __CFRunLoopDoObservers + 374
31 com.apple.CoreFoundation 0x00007fff8fcc7159 __CFRunLoopRun + 825
32 com.apple.CoreFoundation 0x00007fff8fcc6ae6 CFRunLoopRunSpecific + 230
33 com.apple.HIToolbox 0x00007fff878113d3 RunCurrentEventLoopInMode + 277
34 com.apple.HIToolbox 0x00007fff8781863d ReceiveNextEventCommon + 355
35 com.apple.HIToolbox 0x00007fff878184ca BlockUntilNextEventMatchingListInMode + 62
36 com.apple.AppKit 0x00007fff8ca493f1 _DPSNextEvent + 659
37 com.apple.AppKit 0x00007fff8ca48cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
38 com.apple.Aperture 0x00000001004b289b 0x100000000 + 4925595
39 com.apple.AppKit 0x00007fff8ccffec5 -[NSApplication _realDoModalLoop:peek:] + 610
40 com.apple.AppKit 0x00007fff8ccffaf9 -[NSApplication runModalForWindow:] + 120
41 com.niksoftware.cep4.aperture_edit 0x00000001a0bba2ec luabridge::rawgetfield(lua_State*, int, char const*) + 2676159
42 com.niksoftware.cep4.aperture_edit 0x00000001a094109b luabridge::rawgetfield(lua_State*, int, char const*) + 82798
43 com.niksoftware.cep4.aperture_edit 0x00000001a023f4f4 nik::plugin_common::BaseImageHandler::setInputImage(nik::util::SharedPtr<nik::i maging::Image> const&) + 2676
44 com.niksoftware.cep4.aperture_edit 0x00000001a024034a nik::plugin_common::BaseImageHandler::BaseImageHandler(nik::util::SharedPtr<nik ::plugin_common::ImageFileAbstraction> const&) + 762
45 com.niksoftware.cep4.aperture_edit 0x00000001a02407e6 nik::plugin_common::BaseImageHandler::create(nik::util::SharedPtr<nik::plugin_c ommon::ImageFileAbstraction> const&) + 54
46 com.niksoftware.cep4.aperture_edit 0x00000001a0212573 nik::plugin_common::BaseApplicationController::createImageHandlerFromImageFile( nik::util::SharedPtr<nik::plugin_common::BaseApplicationController::ImageFile>) + 899
47 com.niksoftware.cep4.aperture_edit 0x00000001a0197b6c 0x1a0152000 + 285548
48 com.niksoftware.cep4.aperture_edit 0x00000001a021c200 nik::plugin_common::BaseApplicationController::loadImage(unsigned long) + 480
49 com.niksoftware.cep4.aperture_edit 0x00000001a0bb13ad luabridge::rawgetfield(lua_State*, int, char const*) + 2639488
50 com.niksoftware.cep4.aperture_edit 0x00000001a0362822 nik::plugin_common::BaseBottomBar::onNextClicked() + 130
51 com.niksoftware.cep4.aperture_edit 0x00000001a0a51ddd luabridge::rawgetfield(lua_State*, int, char const*) + 1200304
52 com.niksoftware.cep4.aperture_edit 0x00000001a0b3dc51 luabridge::rawgetfield(lua_State*, int, char const*) + 2166564
53 com.niksoftware.cep4.aperture_edit 0x00000001a0aed90f luabridge::rawgetfield(lua_State*, int, char const*) + 1838050
54 com.niksoftware.cep4.aperture_edit 0x00000001a0a963dc luabridge::rawgetfield(lua_State*, int, char const*) + 1480367
55 com.niksoftware.cep4.aperture_edit 0x00000001a0bf0a2a luabridge::rawgetfield(lua_State*, int, char const*) + 2899197
56 com.apple.AppKit 0x00007fff8cb171a6 -[NSWindow sendEvent:] + 6504
57 com.apple.AppKit 0x00007fff8caaf68f -[NSApplication sendEvent:] + 5593
58 com.apple.prokit 0x00000001013651b8 -[NSProApplication sendEvent:] + 1829
59 com.apple.Aperture 0x00000001004b282b 0x100000000 + 4925483
60 com.apple.AppKit 0x00007fff8ccfff27 -[NSApplication _realDoModalLoop:peek:] + 708
61 com.apple.AppKit 0x00007fff8ccffaf9 -[NSApplication runModalForWindow:] + 120
62 com.apple.Aperture 0x0000000100271127 0x100000000 + 2560295
63 com.apple.Aperture 0x00000001000378cd 0x100000000 + 227533
64 com.apple.CoreFoundation 0x00007fff8fd21a1d -[NSObject performSelector:withObject:] + 61
65 com.apple.AppKit 0x00007fff8cb4e710 -[NSApplication sendAction:to:from:] + 139
66 com.apple.prokit 0x0000000101366fce -[NSProApplication sendAction:to:from:] + 100
67 com.apple.Aperture 0x00000001004b1a37 0x100000000 + 4921911
68 com.apple.AppKit 0x00007fff8cc3bbd7 -[NSMenuItem _corePerformAction] + 399
69 com.apple.AppKit 0x00007fff8cc3b90e -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 125
70 com.apple.AppKit 0x00007fff8ced8194 -[NSMenu _internalPerformActionForItemAtIndex:] + 38
71 com.apple.AppKit 0x00007fff8cd69ce5 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 138
72 com.apple.AppKit 0x00007fff8cbb551f NSSLMMenuEventHandler + 339
73 com.apple.HIToolbox 0x00007fff87817308 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1263
74 com.apple.HIToolbox 0x00007fff87816914 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 446
75 com.apple.HIToolbox 0x00007fff8782d6c7 SendEventToEventTarget + 76
76 com.apple.HIToolbox 0x00007fff878739f5 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 398
77 com.apple.HIToolbox 0x00007fff8795a645 SendMenuCommandWithContextAndModifiers + 56
78 com.apple.HIToolbox 0x00007fff879a0ef9 SendMenuItemSelectedEvent + 253
79 com.apple.HIToolbox 0x00007fff8786cb07 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 101
80 com.apple.HIToolbox 0x00007fff87999909 _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttjS4_S4_PK10__CFStringPP13 OpaqueMenuRefPt + 1660
81 com.apple.HIToolbox 0x00007fff87999bc8 _HandlePopUpMenuSelection7 + 621
82 com.apple.AppKit 0x00007fff8cd6c9b1 _NSSLMPopUpCarbonMenu3 + 3860
83 com.apple.AppKit 0x00007fff8cd6a9b1 -[NSCarbonMenuImpl _popUpContextMenu:withEvent:forView:withFont:] + 190
84 com.apple.prokit 0x00000001013f8aef -[NSProCarbonMenuImpl _popUpContextMenu:withEvent:forView:withFont:] + 388
85 com.apple.prokit 0x0000000101356204 -[NSMenu(ProAdditions) _popUpContextMenu:withEvent:forView:withFont:] + 529
86 com.apple.AppKit 0x00007fff8d0bec9d -[NSView rightMouseDown:] + 129
87 com.apple.Aperture 0x00000001001bb546 0x100000000 + 1815878
88 com.apple.AppKit 0x00007fff8cb17544 -[NSWindow sendEvent:] + 7430
89 com.apple.prokit 0x0000000101389360 -[NSProWindow sendEvent:] + 242
90 com.apple.AppKit 0x00007fff8caaf68f -[NSApplication sendEvent:] + 5593
91 com.apple.prokit 0x00000001013651b8 -[NSProApplication sendEvent:] + 1829
92 com.apple.Aperture 0x00000001004b282b 0x100000000 + 4925483
93 com.apple.AppKit 0x00007fff8ca45682 -[NSApplication run] + 555
94 com.apple.prokit 0x00000001013673c6 NSProApplicationMain + 387
95 com.apple.Aperture 0x000000010000f4a4 0x100000000 + 62628
96 com.apple.Aperture 0x000000010000f264 0x100000000 + 62052
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff863f87e6 kevent + 10
1 libdispatch.dylib 0x00007fff8ecff5be _dispatch_mgr_invoke + 923
2 libdispatch.dylib 0x00007fff8ecfe14e _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.CoreFoundation 0x00007fff8fcbeb6c __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation 0x00007fff8fcc72d4 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation 0x00007fff8fcc6ae6 CFRunLoopRunSpecific + 230
5 com.apple.Foundation 0x00007fff84b8804f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267
6 com.apple.proxtcore 0x0000000101aec893 -[XTRunLoopThread run:] + 435
7 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
8 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
9 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
10 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.CoreFoundation 0x00007fff8fcbeb6c __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation 0x00007fff8fcc72d4 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation 0x00007fff8fcc6ae6 CFRunLoopRunSpecific + 230
5 com.apple.Foundation 0x00007fff84b8804f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267
6 com.apple.proxtcore 0x0000000101aec893 -[XTRunLoopThread run:] + 435
7 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
8 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
9 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
10 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.CoreFoundation 0x00007fff8fcbeb6c __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation 0x00007fff8fcc72d4 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation 0x00007fff8fcc6ae6 CFRunLoopRunSpecific + 230
5 com.apple.Foundation 0x00007fff84b8804f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267
6 com.apple.proxtcore 0x0000000101aec893 -[XTRunLoopThread run:] + 435
7 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
8 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
9 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
10 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 12:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 13:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 15:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 16:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 17:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 18:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 19:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 20:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 21:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 22:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 23:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 24:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 25:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 26:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 29:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.iLifeSQLAccess 0x0000000101c31b79 -[RALatchTrigger wait] + 57
3 com.apple.iLifeSQLAccess 0x0000000101c31a3c -[RAOperationQueueImpl _workThread] + 204
4 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
5 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
7 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 30:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.iLifeSQLAccess 0x0000000101c31b79 -[RALatchTrigger wait] + 57
3 com.apple.iLifeSQLAccess 0x0000000101c31a3c -[RAOperationQueueImpl _workThread] + 204
4 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
5 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
7 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 31:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.iLifeSQLAccess 0x0000000101c31b79 -[RALatchTrigger wait] + 57
3 com.apple.iLifeSQLAccess 0x0000000101c31a3c -[RAOperationQueueImpl _workThread] + 204
4 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
5 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
7 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 32:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.iLifeSQLAccess 0x0000000101c31b79 -[RALatchTrigger wait] + 57
3 com.apple.iLifeSQLAccess 0x0000000101c31a3c -[RAOperationQueueImpl _workThread] + 204
4 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
5 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
7 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 33:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.iLifeSQLAccess 0x0000000101c31b79 -[RALatchTrigger wait] + 57
3 com.apple.iLifeSQLAccess 0x0000000101c31a3c -[RAOperationQueueImpl _workThread] + 204
4 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
5 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
7 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 34:
0 libsystem_kernel.dylib 0x00007fff863f667a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff863f5d71 mach_msg + 73
2 com.apple.iLifeSQLAccess 0x0000000101c31b79 -[RALatchTrigger wait] + 57
3 com.apple.iLifeSQLAccess 0x0000000101c31a3c -[RAOperationQueueImpl _workThread] + 204
4 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
5 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
7 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 35:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 36:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13
Thread 37:
0 libsystem_kernel.dylib 0x00007fff863f7bca __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff862482a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x00007fff84c05b10 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x00007fff84bcf302 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proxtcore 0x0000000101aeb651 -[XTMsgQueue waitForMessage] + 49
5 com.apple.proxtcore 0x0000000101aea727 -[XTThread run:] + 375
6 com.apple.Foundation 0x00007fff84bd67fe -[NSThread main] + 68
7 com.apple.Foundation 0x00007fff84bd6776 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x00007fff862448bf _pthread_start + 335
9 libsystem_c.dylib 0x00007fff86247b75 thread_start + 13Have you checked with the Font Book Utility if there are still any font families marked with an exclamation mark as duplicates?
If the upgrade to 3.2.2. does not resolve your problem, try if running Aperture in 32bit mode will help.
I am not entirely sure if duplicate fonts might cause the problem - the last crash with nik plug-ins reported in this forum that were related to duplicate Arial fonts (Re: Nik Plugin Crash Issues) was with the viveza plug-in, not with the colorefex plug-in, also the crash occured when selecting the plug-in from the menu "Performing @selector(a_editWithPlugIn:) from sender NSMenuItem", not with a bad access when addressing the graphics card.
0 com.apple.ATIRadeonX3000GLDriver 0x000000010d97503f 0x10d91f000 + 352319
So your problem might be related to the ATIRadeonX3000GLDriver; maybe the plugin is still using an old Snow Leopard version, that may be incompatible with Lion?
Regards
Léonie -
Image cannot be rendered because Aperture does not support image format
Dear all,
I have installed apple Aperture 3.03 and the complete Nick software plug-in selection:
• Dfine 2.0 for Aperture
• Color Efex Pro 3.0 Complete for Aperture
• Silver Efex Pro for Aperture
• Sharpener Pro 3.0 for Aperture
• Viveza 2 for Aperture
History
Until a few days ago the system was running ok / no notable issues on performance. / all pug in seem to run good / no issues. Also
• I Run OSX10.4/ Aperture 3.03 ( 32Bit mode)
• My library contains just over 10000 images / approximately 140GB
• I have recently updated the OSX software update including the security update 2010-005
• as well as the Snow leopard graphic update 1.0
• As far as I am aware all updates where automatically recommended by OSX Software update ( no manual intervention).
• As far as I remember after update the system still was running ok but honestly I can not tell you how many times the Nick Plug in started out of Aperture.
After all, Several times I continued using the system / still no noticeable problem until the following was happening:
Problem:
After creating with "PT gui" a panoramic image File type: "TIF" Pixel size: 5112 × 2556 (13,1 MP) I imputed this file in to Aperture (drag and drop). During the attempt to eddied this file with "Nick Define 2.0" the system was hamming up No response for several minutes from Dfine 2.0 / Aperture" At the end I had to "force quit" the applications.
After the consequential reopening of Aperture I tried again to eddied images with any Nick software Plug-In but each time Aperture prepares any image previously stored in my Library ti open the Pug in the following Error message appears:
*"This image cannot be rendered for editing because Aperture does not support the image format"*
Currently non of my previously in the library safed images can be opened in a Nick software Plug-In this applies to all file types I have tied " Raw, tif, jpg"
• I am still able to eddied normally with Aperture ( so far I do not find any other issue)
• A newly imported Raw image after being taken with my EOS 5D can be edited in the completed Nick software Plug-In selection ( so far I do not find any other issue)
The following actions have been taken to overcome the issue (all not successful):
• I restored my Library out of my back Up ( to previous time of event ( no Time machine back up)
• Uninstallation of all Nick software Plug-In selection
• Uninstallation Aperture Reinstallation Aperture / Nick software Plug-In selection
• Repairing the library ( all three possibilities)
• installation of latest EOS utilitys
Questions
• Can you support me to overcome this issue?
• Have you heard similar issues of Nick user Running the Aperture plug-ins?
For me it is really strange that even after replacing the the library in my normally not connect back up the problem still exists (this should be not affected by the event as the back up was not done any more) / new imported images are editable with the Plug-In.
I would be happy if you could support me in this issue.
Best regards,
Matthias
PS: I have reported this issue to Apple (via Aperture feedback) as well as contacted the Nick software support and currently waiting for feedback.
Harware:
Modellname: MacBook Pro
Modell-Identifizierung: MacBookPro5,1
Prozessortyp: Intel Core 2 Duo
Prozessorgeschwindigkeit: 2,66 GHz
Anzahl der Prozessoren: 1
Gesamtzahl der Kerne: 2
L2-Cache: 6 MB
Speicher: 4 GB
Busgeschwindigkeit: 1,07 GHz
Boot-ROM-Version: MBP51.007E.B05
SMC-Version (System): 1.41f2Dear Ma-Le / All
I have just had the same problem
I use
• Aperture 3.03 with a iMac 2.8 Intel Core 2 Duo with all files on external hard disks (mac extended fomat as apple suggests) with referenced masters.
• Camera Nikon D300, with probably 75,000+ images on 2 hard drives
• Photoshop CS2 with PhotoTools 2.5 plugin
This has been working perfectly until yesterday when the system froze when I was using PhotoTools 2.5 with Photoshop CS2 - as a result of which I resorted to a force quit.
Since then on most of my files it has not been possible to use an external editor.
A message appears saying: *Editing Error - This image cannot be rendered for editing because Aperture does not support image format*.
The problem seems to apply to the attempted use of any external editor (including Noise Ninja)
The following have each been tried, all unsuccessfully:
- Using each of Aperture's library 3 first aid options
- Rebuilding directory using Diskwarrior
- Checking for virus using Virus Barrier X4
- Defragmenting library hard disk using TechTool pro
- Changing permissions settings
- Using Disk Utility first aid to repair permissions and checking main disk
- Removing some plist elements when open 'show package contents' of library
- Setting up a(n almost clean) new system, with newly loaded version of Aperture, with a new library from a vault saved prior to the crash when the problem first occured
Several things seem to me to be totally bizarre:
1 - The problem is the same on the other library hard disk which was not in use at the time
2 - The problem still occurs when a back up vault saved prior to this problem is loaded - using a new hard disk with a new system and a newly reloaded and upgraded Aperture software
3- The problem seems inconsistent. It appears to affect some photos but not all. Even from the same shoot, some photos can be edited using an external editor, whilst others cannot (but as far as i can tell most of the photos in a particular album seem to be consistently affected)
4- The only way around it seems to be if I import a new (copy image) from the original master. Then everything works ok, and I can successfully edit that copy image in photoshop / phototools plug-in.
I am beginning to wonder whether what has been corrupted is Aperture's ability to make copies from the master file which it then uses with the external editor (I have no real idea whether this is correct)
Does anyone have any ideas or solutions - or has anyone else been suffering a similar problem?
Eric
PS: As a professional photographer this problem is a really serious issue for me - and I really don't really want to go to Lightroom or Capture One -
Unwanted color tags showing up on exported jpegs
Aperture has started assigning color tags (in my case, orange) upon export of some JPEGs. Around 10-20 percent of the files get said tags. This happens when exporting versions either original size or 50% (I haven't experimented with any other settings) What's going on here? Aperture 3, Yosemite in use.
ThanksSoftware is stupid that way . Glad your export issues are resolved.
Fwiw, I find the color labels invaluable because they can be so quickly perceived in the Browser. If you have a small series of mutually-exclusive metadata that you want to be instantly knowable while you work in Aperture, color labels are the tool of choice. I use them to indicate each Image's stage of development:
- Red = develop me!
- Orange = some adjustments applied; development not complete
- Yellow = development frozen: used in panorama or replaced by externally-edited Version
- Green = developed.
- Blue = Final Sale Version
- Purple = detail of developed
- Gray = abandon but keep
HTH,
—Kirby, on a TMI spree. -
Since 3.3.1, colors of exported files are terrible
When I exported pictures in previous versions of Aperture, colors were fine. Since updating to 3.3.1 the colors are really terrible. Is there a way to revert to 3.3 or earlier? Have others seen this problem? Pictures look fine on the screen.
RickHi Kirby, thanks for replying.
I right-click the photo and Export Version... then choose one of my presets.
I'm exporting using my lab's printer profile, as I've used for years. They have a Chromira and have provided profiles for Fuji Crystal Archive in glossy and lustre. So no change there. I output TIFF files with black point compensation. Again, all the same as I've done for years.
Here is the good one from a few weeks ago
http://www.rickthurmond.com/HouseOnFire1FujiGloss8x10.tiff
here is the one from today
http://www.rickthurmond.com/HouseOnFire1Today.tiff
Thanks!
Rick -
Prints Managed By Aperture Too Dark/Red; Printer Managed Match Display
I did a Startpage.com search and found this archived discussion: https://discussions.apple.com/thread/1378192?start=0&tstart=0. It has lots of suggestions but before I tried any I did a little experiment: I told Aperture 3 to allow the printer software to manage the color.
The result: the print essentially matches my display. The Aperture-managed print is too red and dark. Go Figure...
I'm trying to understand why Aperture is botching the print job while the HP software gets it spot-on. Theoretically the Aperture color-managed prints should be better than the HP software-managed prints.
My hardware: Mac Mini and 10.8.3. HP Photosmart 8450 printer. NEC 2490WUXi2 display. I am using the stock NEC display profile because it is so darn good. My option is software calibration but nothing I have created has come close to the NEC profile. I have checked the NEC profile against various online display checkers and it looks good, so I see no reason to invest in hardware calibration. sRGB images exported from Aperture for Web use look good too.
When using Aperture 3 "Printer Managed" color management is automatically disabled. I select the proper HP paper profile. The image looks good on the display. The print looks not so good...
When using "Printer Managed" the only automatic setting that I had missed in the HP software was automatic sharpening; I'm going to disable it and see what happens. The only thing I change is the color setting from sRGB to Adobe RGB 1998. Otherwise I stick with the correct paper profile, select "Best" or "Maximum DPI" and hit print.
I would say that my test image is challenging to reproduce: skintones, light blonde hair, deep red/purple color in the clothes.
It's been a while since I printed from Photoshop CS3 but prints managed by that application look fine. I also use Nikon Capture NX2 but I don't recall using it to print. I'm going to test it later.
Any thoughts/feedback? At this point it looks like I should just stick with using the HP printer software. But the question remains: Why are the Aperture prints sub-par? Is it me or is it Aperture?Honestly, it's probably your calibration. Saying it "looks good" with the software profile is completely subjective. If you don't measure the display, it's all guesswork.
Aperture can print fine, with its drivers. You do have to ensure you're not double color correcting (i.e. Aperture AND the printer drivers, which will double down the adjustments and make things look bad), but if you have stuff set up right and colors are bad, then you really can't go to step 2 without doing a hardware calibration. -
What do I need to set my Color Space to? sRGB or Adobe? Also what setting should I have in Aperture 2 to get the best color. I use a D300.
as the other feedbacks mention, your d300 raw files don't have a color profile as such. aperture itself works with a wider color gamut than sRGB or adobe RGB, no need to set anything within aperture. once you leave aperture, color profiles become essential.
as a rule of thumb...
- sRGB jpg for export to web, email, clients
- 16 bit proPhoto for editing in photoshop
- adobe RGB or sRGB for print (ask your printer what he prefers)
also - some people mention CMYK for print. while print documents are prepared in CMYK, i'd always send your images in RGB and let the graphic designer (or printer) convert them to CMYK. they often use specific profiles that match their machines.
Maybe you are looking for
-
Server 9.0.4.2.10 SunOS CWS.log I have a bunch of errors like below. I think it because of blank email addr. I have fixed a few incorrect email addr. Could this be another problem? DATE = Mon Jun 19 14:14:00 2006 PID = 17473; TID = 1; LWPID = 1 SYSTE
-
I want to use both PSE Version 6 and Version 8 on SL 10.6.3. I presently have 8 working fine from disk, but cannot reinstall version 6 from the original disk. Intel Mac. Any ideas? Thanks.
-
Windows client - Linux oracle server SSO through Win2003 DC
Hi, I'm trying to do SSO with the captioned setting, the outline can be simplified as below: windows cleint --> Win2003 DC --> Linux Oracle server Of course, the Linux server would issue kerberos ticket to the Windows client after which successfully
-
ADF Iterator bindings in the page
Hi, I am having the two selectone choice boxes in the same page which are binded to different iterator instances(iterators are binded same View Object). I want show different data list based on parameter from particular selectone choice box. But when
-
Fans acting up after 2010-01 security update
Hi there, My MacPro (2,1) 8-core (16Gb) has it's fans acting up after the 2010-01 security update. This update came together with an update for Java. Being aware of the possibility that problems can rise when updating the two at the same time, I ran