Aperture Set-up vs. Performance

Hello All,
Here's a question regarding performance.
I have about 12,500 images in Aperture 1.5 and the performance is near abysmal given the machine I'm using. I have these images in three projects, one of which has 5,600 images.
Here's the question:
If I start all over again, and import the images organized as "shoots" (a la Lightroom) of say 200 or fewer masters per project, will the overall performance of Aperture improve?
I should state that the reason I purchased Aperture was to be able to have my library of photos (from three cameras) in one location so that I could browse all photos easily and locate a given photo quickly.
Thanks!
G5 Quad / 4.5GB Mac OS X (10.4.8)

I find the library view to be a bit slow, yes. By "a bit slow" I do mean it takes a few seconds to show all the thumbnails.
I have to ask -- does it really make sense for you to view 12,000 photos every time you want to look at some photos? It's going to be slower to do this -- the system will have to load all those thumbnails whenever you access the pane, so when you start scrolling it can show them to you rapidly. In the interest of practicality I'm going to say that yes, you should have a larger number of projects, with fewer photos in them, and rarely go view the entire library at once. Just like I'd say it's a good idea not to punch yourself in the face on a regular basis -- doing either of these hurts

Similar Messages

Leica M9 and Aperture3 not showing camera aperture setting when import DNG files. Shutter speed and ISO are indicated, but not aperture. When I export and open in Adobe Camera Raw aperture setting is displayed.

Does any one have a suggestion as to how to get A3 to show the camera aperture setting on Leica M9 DNG files?

You will want to read this thread in its entirety.
The short story (as I understand it) is that the M9 body receives no information about aperture from attached lenses. It is able to derive an estimate of the aperture, though, and it lists this derived number in the metadata field "Approximate F-stop" (not the exact field name). Aperture (the program) does not report the contents of this proprietary field.

Which aperture setting takes sharper images. f/8 or f/11?

I have t2i (550D) and two lenses i.e. 18-55 mm and 55-250 mm. Any idea how to take sharper images of landscape by selecting a particular aperture setting? I read on a different forum that for sharper images f/8 or f/11 are the ideal settings. Any suggestions?

Seems this topic is having many hits so let me give some more info that might be useful to all:
When you need to know real detail analysis of a lens, there is no better place to check than:
PhotoZone
Specific to your question are the 2 links below. Just scroll down to MTF or Modulation Transfer Function also known as spatial frequency response (Way sharpness is measured objectively) That let you know exactly what you wanted to know about the sharpness.
Link to EF-S 18-55mm IS
Link to EF-S 55-250mm
The site should be very useful for any one eager to know specifically a detail about any lens so enjoy.

Aperture 3 with ridiculous performance

I started using Aperture on version 2 and I loved it. The main reason for that was that it was super fast in handling my 30 thousand photos.
After I upgraded to Aperture 3 though, the performance is pathetic. I can barely scroll through photos. Sometimes creating a simple Smart Album takes more than 60 seconds -- and I'm not exaggerating.
I really don't like Adobe, but I think I'll have to switch to LightRoom if I can get this fixed. I've read some posts about disk fragmentation being the cause for the problem, but I find that very hard to believe. Why wouldn't the same thing happen to Aperture 2?
Turning off Faces didn't help.
Any other ideas on how to fix?

First, are you using "high performance" for the graphics settings on your MacBook Pro? You definitely want to do that.
Second, some here have reported that deleting the Aperture preferences file has helped. I can't say as I had real performance issues so I'm not sure.
Finally, is Aperture 3 doing anything in the background still (updating thumbnails, etc.)? This can slow things down.
I'll note that I find A3 to be faster on Snow Leopard than A2 was. I also think the fragmentation discussion is a red herring. But I also have good performance... it'd be nice if there were a silver bullet for what the difference is between the machines but I'm not sure.

Grey boxes even though set to high performance display

Hi. I am wondering if there is an incompatability issue. Until today, I have been using CS2 with no problems, on Windows XP. I have now installed CS6 on a laptop with Windows 7 operating system and opened my files. Three problems really...
1) about 95% of my many images (all exported images from my Sibelius 4 programme) are displaying in grey boxes even though I set 'View', 'DIsplay performance' to 'high'
(don't understand why as all my tiff drawings done in Photoshop are showing fine).
next problem...
2). A box comes up when I try to open each document saying...
The documents embedded colour profile does not match the current cmyk working space.
…policy is to discard profiles that do not match
Embedded: Europe iso coated FOGRA27
Working: U.S web coated (swop)
Is this anything to worry about? I have been very careful about my colour choices and want nothing going wrong!
Next problem...
3) So annoying, that even though all the links appear fine (i.e.to begin with there were only a few '!' warning in the links folder, but now since i've 'relinked' those, crazily enough to the same file name, there are none), I keep getting a warning box popping up saying: 'Error encountered while reading Tiff image. Image may be damaged or incompatible. Resave the image with different settings and try again' . I keep getting the message box randomly sometimes every few seconds so it's impossible to get work done, not that I can anyway since the vast majority of my work is now in grey boxes and can't be deciphered, as already explained, as if something is wrong with the performance display.
Regarding the display performance, could it be a problem that my machine isn't up to it? I.e. The processing speed. It's quite new though, Dell , Inspiron, 5720.i know nothing about this.
Stuck. Please help!!! Many thanks,
Zylo
P.S> Also worth adding that the 'edit link' feature for my SIbelius images is not working (but is for the Tiff drawings - i.e. I right click, edit link, then it takes me to the original file to edit). Hope this all makes sense!

I would like to inform Adobe staff that it IS most definitely a problem/bug in the CS6 software. It has caused me immense frustration and worry especially as over ten years work was at stake! (a series of books I have written, all using Adobe Indesign CS2 in conjunction with Sibelius 4, importing more than a thousand EPS files!). I find it very disappointing that Adobe have not fixed this problem in CS6 and the new CC2014, despite the fact the bug was reported at least twice previously by people using CS5, both of them using EPS files from Sibelius.
Whilst writing this thread, I have also been corresponding with a very helpful person on the Sibelius help forum. They discovered the problem was not with the EPS files at all: the problem was with the InDesign .indd files themselves, and a bug in InDesign.
Whenever an old version of an .indd file is read into a later version of InDesign, the file format is updated to the latest version. But, if the .indd file contains placed graphics originating from Sibelius (maybe only versions up to 6), the update process results in corruption of the .indd file, which becomes unusable and might even crash InDesign.
The work-around is to export the corrupted .indd file into .idml format, and then re-import the .idml file. (This operation strips out all the TIFF previews of placed graphics, which is where the problems reside). The re-imported file is then happy to re-link to all the EPS graphics from Sibelius, and the InDesign project is recovered.
Here are previous reports of this InDesign bug:
https://forums.adobe.com/thread/966318
https://forums.adobe.com/thread/1146504
https://forums.adobe.com/thread/1188433
An explanation of the work-around:
http://www.creativeprogression.com/idx-idml-troubleshooting/
In summary; the way around this bug is as follows…
- on the new PC, open a troublesome InDesign file into Indesign CS6, and
ignore all the errors;
- In InDesign, choose File -> Export;
- In the drop-down at the bottom of the Export dialogue, choose "InDesign
Markup (IDML)", in the File name box choose a helpful name, and click Save;
- In InDesign, File -> Close the bad document;
- In Indesign, File -> Open the .idml document you just created two steps
above;
- the document will open with all graphics replaced with grey boxes, but
hopefully no error messages;
- you can then re-link all the placed EPS graphics, hopefully in one fell
swoop for the whole file;
- now save the document as an InDesign .indd file: but take care not to
overwrite any of your older InDesign files: you might need them again one
day.
This procedure works because the .IDML export strips out the TIFF previews
of the graphics which are normally embedded in the .INDD file, and it is
those TIFF previews from CS2 which are causing the problem. Re-linking the
EPS files generates new TIFF previews in CS6.
MEANWHILE, Adobe software people, PLEASE fix this long overdue bug!
Hope this thread is helpful for any others who have also experience the same problem.

Locking Aperture Setting in Movie Mode - Canon T4i

I recently bought a T4i to use for shooting short videos, some of which will require me to zoom in during filming. I noticed that if the scene is properly exposed and I zoom in, the image becomes darker. This is not much of a problem sinceonly a short amount of footage will be seen before the zoom starts, so I can just expose the image so that it looks fine after the zoom.
The issue is the when I zoom in, I noticed the camera is automatically adjusting the aperture. I'm using the Manual mode, not Shutter Speed Priority. The ISO doesn't change and the Shutter Speed doesn't change, so why is it compensating by adjusting the aperture? Is there any way to lock the aperture setting in Manual mode? Is there is an auto compensation feature that needs to be turned off? As far as I can tell, Scene Intelligent Auto is off, as is the Auto Lighting Optimizer. What am I missing?

This depends on the f-stop and lens being used.
You didn't mention which lens, but the "kit" lens that comes with the camera (if you buy the camera as a kit) is the EF-S 18-55mm f/3.5-5.6.
A lens normally lists it's WIDEST possible aperture, but notice that the focal ratio for this lens (f/3.5-5.6) is listed as a range.
This means that the widest possible focal ratio is variable and depends on the focal length. At the 18mm end, the lens is able to provide an f/3.5 focal ratio. But as you zoom in, this ratio increases to f/5.6.
If are using a low focal ratio such as f/3.5, then yes... the focal ratio will increase and the image will get darker as you zoom in. That's the physics of the lens. There are better lenses such as the EF-S 17-55mm f/2.8 IS USM. That lens is able to provide an f/2.8 focal ratio (which is even brighter) and can do so at all focal lengths. The f/2.8 focal ratio collects considerably more light (the lens is physically larger).
If you set the aperture on your variable focal length lens to the higher f-stop in the range (e.g. f/5.6) then the lens CAN provide that focal ratio at all focal lengths... hence it will not get darker as you zoom... this assumes you have enough light.
Tim Campbell
5D II, 5D III, 60Da

OWB 10.2.0.4 really bad set-based delete performance

Hi, we recently upgraded to OWB 10.2.0.4, with one of the reasons being the ability to do set-based deletes instead of row-based. However, upon testing this, we're seeing maps that in row based deletes go from 30 - 40 seconds, now taking literally 1.5 to 2 HOURS to run.
I expected the SQL from the set based to take the form of:
delete from my_table
where (col_a, col_b, col_c) in (select a, b, c from ....)
but instead the format is different:
delete from my_table
where exists (select 1 from ....)
I don't quite understand what the SQL is trying to accomplish - and truthfully, it performs horribly compared to the hand-written version (explain plan shows estimated cost of 14,000 for my query, and over 5 million for the OWB query).
Has anyone else seen this - and is there a solution? Part of me wants to say I'm doing something wrong, but the other part says "sure, but it works fine in row-based mode(target only)" - exact same map.
Any ideas?
Thanks!
Scott

Hi everyone, we'll I've figured out what is causing the problem and how to fix it...but still don't understand why it causes the problem.
Here's a high level overview of the ETL - we find deleted record by selecting business key columns from our existing dimension table and doing a MINUS on the matching columns from the source table. If any records come out of this, it means the record was deleted on the source, and we go ahead and do a matching delete on the dimension table.
Here's where the odd thing happens though - there's a column called "source system name" that is part of the dimension business key. This column does NOT exist on the source system - it's just a hard coded constant (put in just in case we ever add an additional system in the future).
Basically, if we do the minus logic on all the columns EXCEPT for this one, and then connect a constant to the delete operator that has this hard coded value in - the delete takes FOREVER... On the other hand, if we actually put this field into the minus operator by simply repointing the existing constant there instead of directly to the delete table...the deletes magically start taking 30 seconds instead of 10 minutes to run.
No idea (at all) why this makes a diff, but it seems to - and it's a day and night different.
Hopefully this can help someone else out who runs into the same issue.
Thanks!
Scott

Imported iPhoto library -- Aperture set time stamp for each picture 5 hours

Very annoying and bizarre -- I imported thousands of pictures, from 3 or 4 different cameras, and all of them have the time stamp 5 hours too early. I'm not worried about time zones, etc. -- even where the camera, computer and file resides in Chicago, and are set to Chicago time, a photo that was taken at 3 PM CST, and says so in iPhoto, says that it was taken at 10 AM CST in Aperture. Is there any easy way to fix this for all of the pictures?

Hi Sharon,
There is a way to make a change to the date of all pictures. Select all the pictures that need adjustment, then go to the "Metadata | Adjust Date and Time" function. Aperture will show the time of the first picture, and you can set that time to something else. Aperture determines the delta from current to new timestamp, and applies that same delta to all of the other pictures.
You are also probably wondering how that happened in the first place. I don't know for sure, but try to import some more pictures, and in the upper right "Import Settings", select "Time Zone" See if the time zones match CST.
nathan

Large Set of Rows - Performance

Hello all.
We do have a report (Apex 3.2), where if no filter is defined, loads about 60.000 lines. Running the same query on sqlplus or Sql Developer, the performance is acceptable, but on Apex, it takes several minutes, causing some users to abort (close the browser and try again, and aborting again). This behaviour is causing extreme CPU and disk workload. Temp tablespace sometimes gets 100% full to (2GB!!!).
It is not an option to tell them to make some selection before submiting the page for 2 reasons: sometimes they forget it and sometimes they just do not want to do it, because they argue that "on Oracle Forms it was really quick".
Are there any suggestions to this situation? It is causing some requests to go back to Oracle Forms 6i...
Thanks in advance.

Query is :
select a.SUP_CHAMADO_ID,
a.SUP_CLIENTE,
a.CONTATO,
a.DDD_TELEFONE,
a.SUP_TECNICO,
a.NOME_TECNICO,
a.SUP_SISTEMA,
a.ABERTURA,
a.SUP_SITUACAO,
a.SITUACAO,
a.NOME_CLIENTE,
a.NOME_SISTEMA,
a.SUP_CLIENTE_ID,
a.Tolerancia_Atendimento,
SubStr(a.Diagnostico, 1, 60) Diagnostico,
SubStr(a.Solucao, 1, 60) Solucao,
case when Tolerancia_Atendimento < 0 then 'red'
when Tolerancia_Atendimento >= 0 then 'black'
end the_color,
case when Tolerancia_Atendimento < 0 then 'bold'
when Tolerancia_Atendimento >= 0 then 'plain'
end the_style
From SUP_CHAMADOS_VW a
WHERE
instr(upper(To_Char(a.SUP_CHAMADO_ID)),upper(nvl(:P2_SEARCH_REPORT, To_Char(a.Sup_Chamado_Id)))) > 0 Or
instr(upper(a.CONTATO),upper(nvl(:P2_SEARCH_REPORT, a.CONTATO))) > 0 Or
instr(upper(a.DDD_TELEFONE),upper(nvl(:P2_SEARCH_REPORT, a.DDD_TELEFONE))) > 0 Or instr(upper(a.FINALIDADE),upper(nvl(:P2_SEARCH_REPORT, a.FINALIDADE))) > 0
Or instr(upper(SubStr(a.DIAGNOSTICO, 1, 4000)),upper(nvl(:P2_SEARCH_REPORT, SubStr(a.DIAGNOSTICO, 1, 4000)))) > 0
Or instr(upper(SubStr(a.DIAGNOSTICO, 1, 4000)),upper(nvl(:P2_SEARCH_REPORT, SubStr(a.DIAGNOSTICO, 1, 4000)))) > 0) And
a.SUP_CLIENTE = DECODE(Nvl(:P2_SUP_CLIENTES, 'ALL'), 'ALL', a.SUP_CLIENTE, :P2_SUP_CLIENTES) And
Nvl(a.SUP_SISTEMA, 'ALL') = DECODE(Nvl(:P2_SUP_SISTEMAS, 'ALL'), 'ALL', Nvl(a.SUP_SISTEMA, 'ALL'), Nvl(:P2_SUP_SISTEMAS, 'ALL')) And
To_Char(a.SUP_SITUACAO) = DECODE(Nvl(To_Char(:P2_SUP_SITUACOES), '0'), '0', To_Char(a.SUP_SITUACAO), To_Char(:P2_SUP_SITUACOES)) And
Nvl(a.SUP_TECNICO, 'ALL') = DECODE(Nvl(:P2_SUP_TECNICOS, 'ALL'), 'ALL', Nvl(a.SUP_TECNICO, 'ALL'), Nvl(:P2_SUP_TECNICOS, 'ALL')) And
a.SUP_DATA >= DECODE(:P2_PERIODO, 'A', TRUNC(SYSDATE) - 10,
'B', TRUNC(SYSDATE) - 30,
'C', TRUNC(SYSDATE) - 180,
'D', TO_DATE('01/01/1900', 'DD/MM/YYYY'))
The main problem is: it does not start to show the results quickly as does in Forms 6i.
Pagination now is set at Row Ranges 1-15 16-30 in select list (with pagination).
Thanks

Aperture 3: poor Export performance

I'm running Aperture 3 on a MacBook Air (not the new model), with OS X 10.6.5. Whilst I welcome the simplicity of editing and keyword tagging in Aperture, I'm finding that it takes forever-and-a-day to export photos from Aperture, whether that's to my desktop or to Flickr or Facebook (and why isn't there a Picasa uploader, as with iPhoto?).
What I'm wondering is whether Aperture 3 is slow to export on any Mac, or is it just the Air? Whilst I realise that you wouldn't expect the best performance on a small lightweight laptop like the Air, nonetheless iPhoto wasn't too sluggish to Export, and the Pixelmator editing software that I also use is positively speedy.

Hi LondonDave,
Welcome to the user-supported discussions forums.
I personally have an older laptop than yours, but it not an Air. I do not feel it takes too long to export, but that's certainly quite a subjective question. Would you feel mine is slow, and would I feel yours is sufficient? I haven't exported from iPhoto in years, but at the time (iPhoto 8), I didn't feel that Aperture was sluggish in exporting.
In fact, just yesterday, someone else commented that he exported 45 RAW photos from Aperture and it took less than 30 seconds. Doesn't seem to bad to him or me. If you agree, then you may be experiencing something with your hardware. Maybe a fairly full drive? Every export (even if to Facebook or Flickr) has to make a temporary copy on your hard drive.
http://discussions.apple.com/thread.jspa?messageID=12868771&#12868771
As for Picasa exporter, Aperture 3 is actually the first Aperture to have built-in specialized exporters. There is an "export plug-in architecture" that allows any developer to write an export plug in. Some 3rd party developers had created Flickr and Facebook exporters for Aperture 2, which are no longer needed in Aperture 3 from the looks of things.
However, on the Aperture plug-in page, there is a Picasa exporter. I don't use Picasa so I don't know anything about it.
http://www.apple.com/aperture/resources/plugins.html#export
nathan

Aperture 1.0 -- your performance experiences?

Hi guys,
how's your feeling for the performance of Aperture?
Here on my Dual G5 2.7GHz PowerMac it's really reeeaallyyy REALLY slow!
For example: I have a 3000x2000 raw image and even the loop tool, when moved over the full screen image on my 2nd display, is not realtime. I move the mouse to move the loop but the loop moves app. 0,5s after I moved the mouse.
I get roughly the same delay in response from the GUI when I move sliders like the Shadow/Highlight or Exposure or Saturation or or or any other GUI element.
Has Apple really meant to be this software so slow on their almost fastest machine? Are we all forced to buy quad-core (dual dualcore) PowerMacs?
disappointed,
Stefan.

For example: I have a 3000x2000 raw image and even
the loop tool, when moved over the full screen image
on my 2nd display, is not realtime. I move the mouse
to move the loop but the loop moves app. 0,5s after I
moved the mouse.
Hi Stefan,
Exactly same machine here (with 6.5GB RAM, but should not make a difference, as according to Activity Monitor not used) also using the GeForce 6800 Ultra DDL and two displays and I do not have this effect. I would not call Aperture a speed demon, but is fast enough on the PM, on the PowerBook it is slightly painful.
Have you run the usual checks (repair permissions, hardware check etc.). Also I had severe trouble using Aperture with a wireless mouse, with the wired mighty one it is much more responsive.
Cheers,
Uwe
PB G4 17 1.5GHz, iMac 20 2GHz, both 1.5GB RAM, PM 2x2.7GHz 6.5GB RAM ,1x23" 1x30" Cinema Displays Mac OS X (10.4.3) FinalCut Studio, LogicPro, Aperture, DVX100A, HVR-Z1, Canon 1DMkII, 5D and 20D

Poor wireless reception when energy saver set to higher performance

When I set my laptop to "higher performance", I get terrible wifi reception. My internet connection slows to a crawl. If I switch to better battery life, the problem is resolved. I have snow leopard 10.6.8.

You're completely right about the graphic cards.
Yes, I've tried unplugging and plugging the cables (mini display port + usb) serveral times. This triggers the normal blue-ish screen for around a second and then goes back to using only the MBP screen.

URL Proxy setting with good performance

Hi All,
I'm looking for URL proxy setting for my project.I have implemented code for that, but it's taking 200-500milliseconds.So I'm looking for any good performance code for proxy settings.If any body are worked on that .Can you please share your sample code?,Then it'll be helpful for me.
Thanks and Regards
Pattanaik

no ,it's depends upon network.but whatever I was tested my application it's taking minimum 200 ms

Scan directly into Aperture - setting dpi and output size?

Am I able to scan an old photo from a flatbed scanner directly into Aperture.
Set the dpi before along with the output/print size I want?
thx
Deb

I've been researching this for my project too. Here's 3 great articles I found on migrating your film scans to Aperture via Automator.
http://www.kremalicious.com/2008/05/scan-images-directly-into-apple-aperture/
http://www.oreillynet.com/pub/a/oreilly/digitalmedia/2007/05/25/digitizing-your- film-archive.html?page=1
http://blogs.oreilly.com/aperture/2008/09/some-tips-on-scanning-film-int.html

Aperture 3.2.3 performance improvement

Hello,
Yesterday I installed the Aperture update 3.2.3.
I noticed a performance improvement.
I'm curious what your experiences are with this update.

I had thought of starting my own post but to ask just how many issues people were experiencing - rather than what if any improved performances people have seen.
Since updating to 3.2.3, I've been completely afraid to use it! Right out of the gate, it completely hung up my Mac and I had to force restart while using it, which then of course required to repiar permissions, and I eventually had to do the more evasive, repair aperture library. I could be having some other kind of issues, but it's funny - I only start having problems after any kind of Aperture update!
Things on Aperture are now VERY slow. I just imported a large project of over 2000 photos that might be affecting my library and Aperture speed, but it shouldn't affect it this much. And now, anything, and I mean ANYTHING that has to do ANY kind of processing - takes forever. And I'm talking about the simpliest of edits will give me the spinning beach ball.
Here's one thing that JUST freaked me out, and why I came to the forums now. I double clicked on a photo I had been working on so that I could get back to the full browser view, showing all the pics I had in a project, and all of Apeture went all weird, and broken up. I can only describe it as looking like Aperture's interface broke up into a puzzle on my display. I'm afaid to try duplicating what happened.
Suffice to say... I've already skimmed the support forums, but enough to know there's something seriously wrong with the recent 3.2.3 update. 3.2.1 was just as horrible, so I was happy, running along fine on 3.2.2, but now 3.2.3 is horrible - crashes, hangs, and takes forever brushing any kind of effects into shots.
I saw that Michael L. was going to try to revert back to 3.2.2 I'm also using a 2009 iMac 27" Core i7 with 10.6.8 with 16gigs RAM. I refuse to upgrade to buggy Lion. I would like to know what process you did to revert back if you did? Just time machine or how? And how has Aperture been running if / since you reverted back?

Aperture Set-up vs. Performance

Similar Messages

Maybe you are looking for