Aperture 2 - Possible UI bug?

G'day all,
I've been just being enjoying my first couple of days of Aperture 2. Fantastic, really enjoy using this version (keep it up Joe & team!)
I think I may have stumbled into a UI bug though. When I cycle through the viewer mode until the filmstrip disapears and the selected image is displayed at it's largest, I can't use the cursor keys or the arrows under the view to move to the next image.
Do you think it's a bug or is this intentional?
Cheers,
Dean
p.s. I'm looking for the Aperture feedbank link to send as feedback.

Is it a matter of what "window" has focus? (...which can be hard to tell) Try clicking the cursor once in the viewer then using the arrows? Does that work?
One way you can get into what you are seeing: If you click in a field in the metadata tab, then try and use the arrow key, its the metadata tab that is getting the keystroke, not the viewer, so the image doesn't change. You can see how it can happen, if you click there, the switch with a click to the adjustments tab, then adjust, then use the arrow key, you get nothing. If this is what you are seeing, then no need to quit the app, just click the window first with the cursor.

Similar Messages

Possible Keyword Bug

Okay,
I think I have found a possible bug with keywords, or maybe just an incositancy. It's kind of a messy situation so I'm hoping someone can help me out or maybe point me in the right direction to send this feedback to Apple.
I had a bunch of jpeg files from my older cameras that had already been tagged with keywords (in the IPTC keyword field I believe). Once I imported all of these into Aperture I stripped the keywords from all the images. That worked fine.
Before I get into the actual issue let me give a little bit of information on my Aperture library layout: I have folders created by year, then 1 project per month. So I have something like this:
2002
01 Janurary
02 Feburary
2003
01 Janurary
What's weird is if I create a new smart album at the folder level, the keywords listed in the search box are appropriate (only those actually added to images). However if I click on Library and create a new smart album (so that it searches the whole library) it lists all of my current keywords, plus all of those that I had removed (from the original files).
Anyone else run across this? Anyone know how to fix it? It's just a minor inconvience, but it does make it a bit of a pain to have a whole ton of keywords to select from in the search box (most of them no longer having any images associated with them).
Also I have searched for images that match the old keywords and it doesn't find any.
Thanks,
Mark

She suggests..
"Go to Window > Show Keywords HUD, and see if they are there. If so, you should be able to delete them from there."
Hopefully, they will then disappear from the Library list.
if not, it does seem like a bug.
Message was edited by: notorious

Aperture 3 Display Bug and Export to Flickr Bug

Has anyone else experienced this issue, and if so what systems do you have and what graphics card are you using?
The issue is the way images are displayed in Aperture. There seems to have been a change in the anti-aliasing between 2 and 3 so than now images with strong highlights display nasty aliasing artefacts and black ringing around highlight edges. It's as if Images are being over-sharpened. Also, when you first move to an Image it displays perfectly fine while it’s loading then when it’s finished it pops into the over sharp aliased version.
I'm having this issue on my iMac 24" running a ATI RadeonHD2600. It seems to only show when the onscreen display is zoomed out to 25% or less. If you go to fullscreen the artefacts disappear on landscape oriented images but remain on portrait. If you zoom in, once you pass a certain zoom factor they disappear.
I have posted some samples of the artefacts here - as well as what they should look like.
http://www.thomas-fitzgerald.net/2010/04/28/aperture-3-is-really-ticking-me-off/
and here
http://theapertureblog.com/2010/03/29/aperture-display-bug/
The bigger issue is that when exporting using the built in fickr tool it uses the same antialiasing and so over sharpens and degrades images the same way.
The problem is not always apparent and it really only shows with images containing high contrast areas, particularly if they clip to white. I would really like to know if this is limited to certain graphics cards as I've talked to someone who has this issue when using the faster gfx card on their macbook pro but not when they turn on the slower one.
If I need to upgrade my mac to make this issue go away then so be it but I'd really like to hear form others who may have seen it?

I have had issues with Aperture's anti-aliasing performance in the Viewer since version 1.5.
To summarize, Aperture's Viewer produces quite jagged edges from Canon RAW files compared to Preview's and Lightroom's renderings of the exact same files. There doesn't seem to be any radical improvements with the 3.x upgrades, and aliasing performance didn't seem to be affected by the updates to Apple's Canon RAW converter (I reprocessed). Images that I had a problem with are still problematic.
I thought that [this thread|http://discussions.apple.com/thread.jspa?threadID=669881&tstart=0] referring to Aperture 1.5 laid out the issues pretty clearly and I was surprised at how little other users were affected by it (or so I infer from the number of responses.)
Until your post I had not looked specifically at Aperture 3.x. I haven't been able to exactly reproduce the issues I had (so many versions ago...) in Aperture 1.5 and it seems the situation has improved a bit.
Aperture still produces a much sharper rendering than Preview, though the aliased edges are not as prominent. To recap from Aperture 1.5:
!http://homepage.mac.com/steve_hoge/.Pictures/AliasedApertureRender.tiff!
And here's what I see in Aperture 3 on the same image:
!http://homepage.mac.com/steve_hoge/.Pictures/aliasedA3.tiff!
Which looks about the same to me on near-horizontal lines, but much better on the high-contrast vertical lines (check upper left corner of the frame).
And today's Preview 5.0.2 rendering of the RAW image is even softer and less contrast-y than back in the day:
!http://homepage.mac.com/steve_hoge/.Pictures/antialiasedPrev.tiff!
-Steve
http://web.mac.com/steve_hoge
http://www.flickr.com/steve_hoge

Thinkpad S540 possible BIOS bug concerning WOL

I have had a Thinkpad S540 for a few months, and have it installed as dual boot Windows 8.1 and arch linux. After completely shutting the machine down from linux I found that the battery would be down to around 70% charge after three days unused, and decided to investigate this problem since it was not reasonable for a new battery to lose charge at anything like this rate.
By chance I came across a piece of information concerning the issue of disabling WOL (Wake on LAN) on the network interface, since I had seen one report that by default WOL is enabled and this requires power to be going to the network interface even when shut down in order to be able to respond to magic packets to start the machine up when it is shut down.
First I checked the BIOS WOL setting and found it was set to "AC only" by default. So I changed it to disabled. This machine has the latest available BIOS version 1.54.
However on investigating this after rebooting in linux I found that
# cat /sys/class/net/enp3s0/device/power/wakeup
enabled
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: g
So WOL was still enabled despite it being set to disabled in the BIOS!
I learned that I can make sure that in arch linux the WOL setting can be changed to set to disabled after bootup by using a udev rule:
# cat 70-disable_wol.rules
ACTION=="add", SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ethtool -s enp3s0 wol d"
Then rebooting the machine I checked the WOL setting and it really is disabled now:
# ethtool enp3s0 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
# cat /sys/class/net/enp3s0/device/power/wakeup
disabled
So I then ensured that the battery was 100% charged and shut down the machine and left it two and a half days - rebooting this morning the battery was still at 100% charge and no longer discharges unnecessarily when the machine is switched off, so this is a clear indication of a bug in the BIOS for the WOL setting - it is still enabled despite the BIOS saying it is disabled!
How do I report this to Lenovo so that they can fix the BIOS and release a new one that is working?
I am aware of other users with different Thinkpads who seem to have the same problem, so this may be more widespread an issue than just on the S540.
It is also not just an issue with the battery running down when fully shut down but will likely also be a problem for a machine in suspend mode since the network interface may be consuming a watt or so of power when in suspend, which will again run the battery down at an unacceptable rate.
I cannot imagine any use case where it would be necessary to have WOL enabled on a laptop that is mostly going to be used mobile - so having the default setting to AC only enabled, and having a BIOS bug enabling it when it is explicitely disabled is a serious problem.

Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network card, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
In my laptop these were all set to enabled by default.

Aperture 3.3 bug? Unable to apply filters to images in book

This seems to be a new problem that cropped up on my dual core iMac only (my workhorse) with 8Gb RAM.
Not on my laptop.
I simply cannot initiate a wash or b&w/sepia filter on an image in a book layout. Nothing even drops down.
Also- on same iMac, images in a book layout do not always update when I apply edits (reminds me of the squashed viewer bug) and crops also do not update appropriately. Again- doesnt seem to happen on laptop (Macbook Pro 15").
Has anyone else noticed this behavior? I filled out a possible bug report for Apple. . . .

One more thing:
iMac also giving occas. Beach balls and pauses since 3.3 upgrade (was smooth before).... Sometimes to 20-30 sec.
I tried repairing permissions and rebuilding library: no change.

Possible code bug causing crash on Wine/Linux

As I am running Linux, I don't expect support as such but thought I would offer a possible contribution to the beta program as follows:
When starting Safari under Wine (an implementation of the Win32 API) on Linux, I get the following debug message:
DIB_GetBitmapInfo (44): unknown/wrong size for header
What I understand this to mean is that the Windows function GetBitmapInfo is being passed a dodgy parameter.
This is followed by a crash for me, but I guess on Windows, is quietly ignored.
I have seen a report on CodeProject regarding an identical crash caused by a coder setting the biSize member of the bmiHeader (BITMAPHEADERINFO) element of a BITMAPINFO structure to the incorrect size. In the example given, it had been set to sizeof(BITMAPINFO) rather than sizeof(BITMAPINFOHEADER)
e.g.
bmpInfo.bmiHeader.biSize = sizeof (BITMAPINFO);
instead of
bmpInfo.bmiHeader.biSize = sizeof (BITMAPINFOHEADER);
For any devs. interested as to whether there may be a bug, the call stack generated by Wine, showing the offsets from the base address of coregraphics.dll (loaded at 0x6b000000) is as follows, with the crash actaully occurring at '=> 1'
Backtrace:
=>1 0x6b262e97 in coregraphics (+0x262e97) (0x0033ed38)
2 0x6b0f9da4 in coregraphics (+0xf9da4) (0x0033f31c)
3 0x6b1e0fff in coregraphics (+0x1e0fff) (0x0033f4bc)
4 0x6b1d19ee in coregraphics (+0x1d19ee) (0x0033f578)
As I say, I'm not expecting any feedback on this - I'm just being neighbourly I also fully accept that I may be completely wrong in my assessment of the issue.
Dell Inspiron Other OS

There was an even earlier build than the two mentioned.
Talk about "early revisions" I guess so, and it doesn't look like there will be a unified version tomorrow.
I recall AYM had a note about video performance and in that instance, the build on the DVD was never than what was on the hard drive and within a week or so disk drives carried the "new, improved" video on disk as well.
There may be other changes that go hand-in-hand other than build, too. Did they look at the Boot ROM and SMC Version of the systems?
Boot ROM Version: MP11.005C.B00
SMC Version: 1.7f6

Aperture 3.3 Bug: Syncing Stacks Syncs All Versions, Not Just Pick

Aperture 3.3 has a pretty significant bug. Syncing to iOS devices results in all versions in a Stack to be synced to the device, not just the Picks. This is a HUGE problem as two things happen:
1) The amount of space consumed by the versions can be increased several fold.
2) There can be incredible redundancy when viewing photos on iOS devices because of all the extra versions, in many cases the versions may be indistinguishable.
Does anybody have a work around for this, or know if Apple has acknowledged this bug?

I've run into the same problem, and it also affects the Apple TV -- my screensaver slideshow started to look pretty strange when all of the extra versions in my various stacks began appearing
Anyway, I have found what may be an acceptable workaround. Since iTunes is only using the previews in Aperture, it will exclude any images for which previews do not exist. So, if you choose the non-pick images in each of your stacks and delete their previews (right-click and choose "Delete Previews") they will be removed from any albums that are syncing to your iOS devices or Apple TV.

Possible Tab Bug?

The current bug: Adding an additional tab below another will cause the tab to looked messed up. The work around suggested was to create a page (with new tabs), publish it as a portlet underneath a main tab. Then you will visually see tabs underneath tabs.
The new problem you get with this work around is your content underneath the sub-tab will not show up the first load. You have to click on another tab, then back to the previous tab to show the content.
Another weird thing I ran across having to do with regions and published folders. I found that you cannot set a corrent percentage within regions when folders are added to regions.
For instance; Under a tab, divid a region into two regions. The first region make 5% and the second 95%; now when you add your (folder) portlets underneath both regions you will see when viewing it, that it will show up 50% and 50%. If you take out the folder portlet on region 1, and add a application portlet; everything shows up fine.
I have come across varies things like this, but I will start posting the errors and possible work arounds.

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>The new problem you get with this work around is your content underneath the sub-tab will not show up the first load. You have to click on another tab, then back to the previous tab to show the content.<HR></BLOCKQUOTE>
I noticed this also. (in 3.0.6.7.2 on NT).
What's funny about this is that this is exactly the same as a bug with sub-tabs in the EA release. Maybe the data structure of a sub-tab and a page in a tab is very similar...
null

Adding EXIF Fields to Aperture - possible?

Hello all,
I would like to add to the EXIF fields that aperture displays. I know that you edit the Metadata views, and check the various Metadate Fields on and off, but I would like to add Metadata that my camera records in EXIF that aren't listed. Is that possible?
As an example, one of the EXIF fields that I see when looking at the RAW picture using exiftool is "Drive Mode" (with a value of "Continuous Shooting" in this particular image). However, I don't see a selectable "Drive Mode" field in the Metadata Fields list, so is it possible to edit the EXIF fields that Aperture displays somewhere?
Thanks,
Brian

To see, which of the EXIF fields of your images Aperture recognizes, try a simple Apple Script:
Launch AppleScript Editor and paste this in:
tell application "Aperture"
          set imageSel to (get selection)
          repeat with i from 1 to count of imageSel
                    tell item i of imageSel
                              get name of every EXIF tag
                    end tell
          end repeat
end tell
Then select an image in Aperture and press the "Run" button in AppleScript's toolbar.
This script will simply list all names of the EXIF tags, that are available to be used in AppleScript messages to Aperture.
For example for my Canon Photos I see this list:
{"ApertureValue", "CameraSerialNumber", "CaptureDayOfWeek", "CaptureHourOfDay", "CaptureMinuteOfHour", "CaptureMonthOfYear", "CaptureSecondOfMinute", "CaptureYear", "ColorModel", "ColorSpace", "Copyright", "Depth", "ExifVersion", "ExposureBiasValue", "ExposureMode", "ExposureProgram", "Firmware", "Flash", "FlashExposureComp", "FlashPixVersion", "FocalLength", "FocusMode", "ISOSpeedRating", "ImageDate", "LensMaxMM", "LensMinMM", "LensModel", "Make", "MaxApertureValue", "MeteringMode", "Model", "PixelHeight", "PixelWidth", "ProfileName", "SceneCaptureType", "ShutterSpeed", "WhiteBalance", "WhiteBalanceIndex"}
To use all tags that exiftool sees, you can embed calls to exiftool into an AppleScript and write them to a Custom Metadata field.
Regards
Léonie

Foreach syntax + generics, Possible compiler bug?

I'm encountering an odd problem trying to use generics and the foreach (colon) syntax. The code in question:
for (Iterator<String> it = col.getParameterNames().iterator(); it.hasNext();) {}
for (String paramName : col.getParameterNames()) {}col is an instance of an inner class of the class whose method this code snippet is from, getParameterNames has the signature:
public Set<String> getParameterNames();
The first line, using the Iterator<String> explicitly, compiles fine. The second line, when present, raises the compiler error:
found : java.lang.Object
required: java.lang.String
for (String paramName : col.getParameterNames()) {
I cannot seem to reliably reproduce this situation in other (simpler) classes I write, but this one in particular seems to trigger it. Is it possible this is a compiler bug, or might there be something I'm doing incorrectly that I'm missing? Are my expectations about how the second line should work incorrect? It seems to in other circumstances...
javac is 1.6.0_01. Any ideas?

Here is a quick update, I'm more inclined to think of this as bad behavior now.
This code compiles:
public class Test {
Vector<InnerTest> inners = new Vector<InnerTest>();
    public class InnerTest {
       public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
    public Test() {
        for (InnerTest it : inners) {
            for (String s : it.someSet()) {
}however, the following does not:
public class Test {
Vector<InnerTest> inners = new Vector<InnerTest>();
    public class InnerTest<P> {
       public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
    public Test() {
        for (InnerTest it : inners) {
            for (String s : it.someSet()) {
}Again, the problem might be with my expectations (I haven't gone through the specifications yet with this in mind), but I can't fathom how or why the unused parameter would make a difference in that method's tpye matching.

Serious Aperture 2.1 | BUG

Hi,
today I was consolidating various projects into a on project consisting of Albums.
In order to do so I selected the project which I wanted to consolidate and dragged all the pictures into the new project. After doing so with various projects I noticed that previews now started to just miss on several picture. There was just this dotted line with gray BC indicating that the browser was seeing a picture with no preview. Clicking the gray space would display the pic in the viewer - so it was still intact. So I decided to update the preview. Aperture told me that the preview was already up to date and that I could re-generate it buy option clicking when choosing the command. So I did that. But no luck the "preview" remained gray with a dotted line around it...
I found ONE work around. since I am using RAW pictures - under RAW fine adjust - I toggled the state from version 1.1 to 2.0 and back to 1.1 - this brought back the preview to the file. Unfortunately this wont work when selecting multiple files. So I had to manually do it on 200 some files.
There seem to be a pretty serious bug from preventing certain previews to be displayed after having moved them from one project into another. The preview were displaying perfectly in the "old" project before moving it to the new project. Also - the preview were lost what appears to be on a random basis and did NOT happen to all previews during the consolidation.
Has anybody experienced this ?

Thanks guys - that did the trick...
To all you reading....
This aint a BUG - merely my NON KNOW HOW...
Thanks again

How It Was Fixed (Possible Software Bug Not Hardware): Getting the iMac Screen/Menus Garbled and/or Yellow Circle Before Getting Into Finder Issues?

Hi. Possible fix done to my late- 2009 iMac's screen/graphics issue that may work God willing, hopefully for most [In my case it sometimes had that yellow circle that appears before it goes to the Finder but mostly it was a messed up desktop and menus (unreadable mostly) after months, prayers and weeks of fixing it; recommended to be read entirely first coz' it's a bit complicated (like a lot of subplots). If uncomfortable to try coz' it involved a GPU stress test, contact your authorized Apple service center for their advice]. I had an iMac (late 2009) screen garbling a few hours ago (was weeks ago when it resurfaced until it got worse that it's at every boot on Mavericks):
† I booted to Snow Leopard USB external (my back-up OS) drive then run the first person shooter at redeclipse.net. I set everything to max, including the display, resolution and graphics setting with fullscreen and v-sync on. I then refreshed it which brought it back to normal (I then tested it's stability with GPUTest 0.7 with Furmark for 15 minutes). * if the display options have been set to max before, bring it back to the default then refresh and then max it again Possibly any games that's has the graphic settings (or more advanced) of Red Eclipse could work (other free ones are Xonotic and Open Arena which are based on Quake 1 or 3s engine I believe).
Optional but not recommended (have warrantied if that's still available or have it repaired at authorized service centers):
If that doesn't work, review articles and videos on how to open an Intel iMac and get an iPhone/iPad/another way to get to the 'net ready for research (I opened mine very carefully on the right side with a cutter with blade extended far prying it carefully then I inserted a flat end, sturdy plastic used for mixing epoxy then removed the cutter carefully to let the plastic mixing tool do the prying) to see if the cable connected to the logicboard which is on top of, is connected (mine was detached but I'm not sure if the adjusting and tilting of the screen overtime for 2 & 1/2 years, detached it) then do † above again.
It could to be a software problem, a possible Apple ATI driver bug that takes overtime to surface (2 1/2 years it resurfaced because this started in my case after upgrading to Lion when Apple coded things mostly from the ground up. Snow Leopard didn't have this problem).
Thank you for your time. Have a great upcoming sunday mass/great upcoming weekend. I hope this helps.
God bless, Rev. 21:4, Matt. 16:18

Does an external display also act in a similar manner as the internal one?
Some earlier Intel-based iMacs had graphic processor card issues; not sure what
the symptoms of the majority of them were, but some had odd patterns, others
went black, and some would range from OK to totally unusable. Among others.
So there is a chance the graphic processor may be going out; or just the circuitry
that controls the backlight. An inverter may be weak or other circuit to the display
could be wearing out.
http://www.apple.com/retail/geniusbar/
If you have access to an Apple Store with Genius bar, they can perform some kinds
of diagnostic tests there even though the computer is out-of-warranty; that may be
of help to narrow down the cause of the symptoms you've noticed. They may not be
able to repair it, however, at an Apple Store; as it is rather old by today's standard.
An Apple Authorized Service Provider could do repairs and testing on older models
the Apple Store's Genius and other may not be set up to handle due to vintage.
Find an Apple Authorized Service Provider
Visit an Apple Retail Store
There is a country locator page to help find either of the above in regions outside
of the US & Canada, not sure how the above links would work; and it appears my
bookmarks to the country locator page may not be accessible now to post here.
You may be able to get an idea about what kinds of parts support the display
function by name by looking into an iFixit.com repair guide for your iMac series.
Hopefully the parts supporting the display are the reason it is dimming down, as
a graphic processor failure likely would exhibit other behaviors than just dimming.
PS: I see you've added content to your thread after I'd started working on this
& the answer likely is a hardware repair; professional testing is worth the time
and you seem to have at least one other thread on the same topic....
Good luck & happy computing!
edited 2x

Possible "unlock" bug

Greetings.
I decided to post this here, as I dont have developer access for bugreporting site.
Using "The new iPad 3" with latest iOS 7.1.2
I found a strange bug by accident. I can repeat it, although it doesn't always work out.
Here it goes: When I turn my iPad on from black screen to start screen and slide unlock
bar like this (Finnish language set)
If I stop there (correct spot changes and not always the same) and then flip iPad, so
screen turns automatically (up and side both works).
This will result so, that unlock bar is stuck and I can't open iPad anymore. Not without turning
power off and then back on. This problem came with 7.0+
Would be intresting to know, if this is known thing and can others repeat this with other
iPads?
Thanks for your time.

I would suggest getting a copy of wireshark and see if the browser is behaving, I have seen
lots of issues where the server is closing the connection and Safari still tries to send more data, which
violates the RFC. You would also notice lots of tcp connections being opened possibly as well if the
site finishes loading. I have been trying to use Safari exclusively for a while, but somehow I always end up in Firefox. Hopefully they will have most of the gotcha's under wraps soon, but until than their is always
Firefox.

Possible Liquid Bug: Moving data into e-commerce layout

Liquid will not seemingly pass any data from outside an e-commerce layout into an e-commerce layouts is intentional or a bug.
If you create an include place it in a template then try to pass any data ie assign into any ecommerce layout it does not work.
If you need more help with reproducing this let me know.

What I have is a gloabal.inc this contains liquid that I would like to be used across a site ie url manipulations date manipulations and many many more. This is inside a head.inc placed at the very top of the template pages.
What this means is that the global.inc gets rendered first before anything else. You can then run liquid return results and then use it over and over with a simple {{myResult}} tag almost anywhere on a site. It works great, it is simple, fast to implement and has many applications. I can even create a library of .inc liquid files and can place their include's at will in global.inc and then access variables across a site to add and remove functionality. (Of course this is dependant on what you want to do and if it really needs to be global of course.)
I get that it is dependant on the way BC loads but if that is the reason then the ecommerce must render before the page template. Maybe it does, maybe there is another reason. If it is possible then it would be great to have working.
Is there other ways to get the result I want yes. But is it as simple, as fast and as easy to implement, add and remove no. If there is a better way I am all ears.

External FAT32 drive & Aperture possible?

(Sorry if this has been answered before, I could not find this topic searcing this forum.)
I have an external 250gb firewire drive that holds my photos in folders as well as my iphoto library.
Aperture does not recognize any files on this drive. When I choose to import from it, Aperture says 'no files to import' or something along those lines. (I am not at my computer at the moment, so I don't have the exact wording)
Iphoto reads the photos from this drive fine.
When I first setup Aperture, I was unfamiliar & chose for Aperture to manage my files & they are all added to my iMac drive as I import them directly from within Aperture.
I had been importing my CF cards from within Aperture to my iMac HD, but I now am importing them to the external 250gb drive in folders & would like to import them to Aperture from the 250gb external HD, but am unable to.
Does Aperture recognize FAT32 drives, or am I overlooking something?
Thanks in advance.
dave

Allan, I did do a few searches & only turned up 1 thread relating to my query, as noted above.
I saw that one reply did address the issue, but the topic turned to whether a HD was possibly faulty or not.
I posted my question with apologies if it had been addressed, also noting that I had used search in this forum. I also noted that I was interested in any further suggestions & confirmation that this conclusion was indeed true.
I apologize for the error.
Please pardon the mistake.
Hope this helps,
dave
Message was edited by: David Yuriar

Aperture 2 - Possible UI bug?

Similar Messages

Maybe you are looking for