Iphoto 6.0.6 bug? raw displays banding

Last night I imported a couple CF cards into iphoto that I took on my canon 20d and they display all funkay!
the image is covered with black and magenta horizontal stripes, and green ones too.
but wait! That's not all. it gets better. When I click in the image the colors change. sometimes more of the image gets colors on it. BUT! other times the image will go back to normal. how is that for Funky?!
this is iphoto 6.0.6 and osx 10.4.10. None of my previous RAW images were affected (those that I imported using iphoto 6.0.4). all of my images are canon RAW (cr2).
Has anyone seen or heard of this problem? or know how to revert back to iphoto 6.0.5?
thanks,
doug

do you still have the images on your cf card?
try re-importing one of the cards and see what happens.
sounds weird... also try importing with the canon software instead of iphoto and let me know how you get on

Similar Messages

What method does iPhoto 6 use to convert Raw photos for Books?

I shoot Raw. I like to have the odd soft cover iBook for Holiday memories.
Obviously iPhoto does not upload the RAW files to the printers, so what is its conversion process? Would I get better results if I converted them first before creating a Book File? I have followed the list of disappointments people have with these smaller books. Old Toad was most helpful with the Pref Setting 300 tip, but I wonder if in the process of conversion from Raw iPhoto uses a lower quality route?
Any one out there who knows the best practice for Raw Shooters. By the way I am based in London and so the alternative printing websites do seem to take a bit too long with postage.

Adobe Camera Raw is the way to go – it will do all you want and more.
You can pick up the basics very quickly but it pays in the long run to discover its incredible versatility by visiting the Camera Raw forum.
And read the book too!

IPhoto v7.x (iLife 08) RAW workflow

I'm looking for some opinions on a workflow here.
I have an Olympus E-510 and shoot in RAW. For my amateur needs, iPhoto's editing tools are sufficient and I like iPhoto's library characteristics. I import the Oly RAW files and then edit as needed which of course creates a jpeg. There are some pictures that I really don't care about keeping the RAW file as it considerably increases the size of the iPhoto library. I can of course right click on the particular photo and select show original file which shows the RAW file in the Finder, and of course can then delete the RAW file if so desired.
The problem (which I guess isn't really a problem, just kind of anal on my part) is that the edited (jpeg) picture in iPhoto still "points" to the original RAW file's location. I.e., you can right click on the jpeg and select show original file and it opens the folder in the finder where the original RAW file was. I've tried rebuilding the iPhoto library after deleting the RAW file but it makes no difference.
I could of course use another editing program first to edit the RAW image and save a high quality original size jpeg to import to iPhoto, but I kind of would like to keep everything to one application.
If there's no solution to this I simply need to make the decision to either keep the RAW files or ignore the jpeg thinking there is still an original RAW.
Just wondering if anyone else has considered this or has any opinion/suggestion.
Thanks,

Terry:
Deleting the RAW file as you've described is tantamount to committing the cardinal sin of iPhoto, messing with the contents of the library via the Finder. There's really no way to do what you want other than exporting those edited photos you want to keep to the desktop at full size and quality, import into iPhoto and delete the first copy of them.
Another possible workflow would be to upload the RAW files to a folder on the Desktop from the camera. Using a 3rd party editor create a folder of jpg files from the RAW, burn the RAW files to disk or another drive to store as digital negatives and import the folder of the jpgs.
Since iPhoto uses nondestructive editing you're always only one generation away from the originals jpg file. You won't get any significant image quality loss due to multiple edits.
Unless you use a 3rd party editor, like Photoshop, to edit the RAW files there's little advantage to using RAW in iPhoto. With an application like PS RAW files can be handled/edited far better than any other format but you need such an editor. Also, all edits are then saved to another format leaving the RAW untouched.
Since you're only using iPhoto for your editing needs just shoot jpg as that will eliminate several steps in your workflow and save lots of disk space.
Happy Holidays
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 created 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. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

IPhoto does not support Olympus Raw

Understand that IPhoto does not support Olympus Raw, and since IPhoto will disappear from support next year, will the new Photo support this version of Raw?

It isn't just iPhoto - if RAW is supported, it will also be in Aperture and ( I believe, but am not sure) in Image Capture.
babowa,
I think, only Aperture and iPhoto are supported.
See the requirements in the Raw Compatibility updates:
Digital Camera RAW Compatibility 6.01
System Requirements OS X 10.10 w/ iPhoto 9.6 or Aperture 3.6

Graphical vs Raw Display

I'm sending my output to a spool request. When I look at it online in the "Graphical" display, a sample of a line is below:
JOEXX
4569878
STAT44
I'm using a pipe as a delimiter.
When I switch to "Raw" display, the same line as above looks like what is below:
#5JOEXX#54569878#5STAT44#5
The pipe delimiter displays as #5.
Is there a way to get around this where my pipe delimiter shows in the "Raw" Display or another delimiter that will display in both display mode?
Any help would be appriciated,

It is not possible, as I have created one spool of the standard transaction SM51 and tried to see in the RAW Display.
the output was the same...#5 for pipe, #4 for horizontal line
#COL0N#COL0H#0#4#4#4#4#4#4#4#4#4#4#4#4#4
#COL1H#5 No Ty. PID Status Re
#6#4#4#4#4#4#4#4#4#4#4#4#4#4#4#4#4#4#4#4
#COL0H#5#? #COL4H 0 #COL2NDIA 508154
#5#COL0N#? #COL4H 1 #COL2NDIA 504056
#5#COL0N#? #COL4H 2 #COL2NDIA 421970
#5#COL0N#? #COL4H 3 #COL2NDIA 528390
Sorry..
Regards,
Naimesh Patel

IPhoto's nasty habit of automatically displaying any mounted camera disc

As far as I know, iPhoto has always done this. It automatically defaults to showing the contents of any mounted camera disc.
This is highly irritating and useless for me because my camera discs tends to contain hundreds of photos, only a few of which I intend to upload to iPhoto. So why try to display all of them every time I have a camera disc mounted? In fact, sometimes I have a disc mounted and I don't even intend to upload or look at anything on the disc via iPhoto.
Since iPhoto does not have a multi-window capability I transfer my photos by locating the photos in a Finder window and dragging them to a suitable album in iPhoto. I may not be a sophisticated iPhoto user but my approach is simple and intuitive.
It is a pain to have iPhoto spend a long time trying in vain to load several hundred MB or a couple of GB of photos when I only want to load one photo - the most recent shot. When I am in a hurry, this iPhoto behaviour is downright obnoxious. Yes, I can short-circuit the display by selecting an album but there is still a senseless and needless distraction and delay.
Can Apple not offer a simple preference setting to turn OFF this annoying iPhoto habit? Thanks.
Michael

Old Toad wrote:
"mounted photo disc"
Do you mean the camera's memory card and are you mounting it with a card reader? If so then the No Application setting in iPhoto should handle that.
I mount memory cards from my cameras with a card reader all the time without iPhoto opening up. However, if iPhoto is open then it will automatically recognize the card and show the photos.
Maybe what you need to to is use Image Capture to selectively upload the new photos to a folder on the desktop and import them from there.
Thanks for your input but I think you misunderstand what I mean.
The problem has to do with iPhoto displaying the contents of any mounted photo disc as soon as I open iPhoto.
I do not want iPhoto to automatically open and display all the photos in my camera disc without my directing it to do so. iPhoto should not assume I want to import photos from my camera disc whenever I start up iPhoto. For instance, I may want to EXPORT a photo from iPhoto to my camera disc instead. I sometimes use my camera disc as a temporary photo storage device. Sometimes I have my camera disc mounted but have not intentions to interface it to iPhoto even though I may want to run iPhoto while the disc is mounted on my computer. iPhoto's software logic is making too many rigid assumptions.
When iPhoto opens my camera disc it has to struggle to read hundreds of files to display them. I am using a 2.53 Ghz MacBook Pro so it is not a slow computer issue.
As I said I used to work for Apple and I know its programming strategy. The APPLICATIONS software Apple bundles with its SYSTEM software are purposely watered-down so as not to compete with commercial software of 3rd party developers. iPhoto lags in features and updates and upgrades because Apple wants it that way.
However, the suggestion I made is not intended to make it compete with 3rd party pay-for applications. It is simply to correct a flaw.
Using Image Capture to interface with camera photo discs is counterproductive - you have to save the photos to a folder before transferring them to iPhoto.
Anyway, I have made my point and I believe the forum should understand my complaint as should Apple.
I will wait to see if Apple decides to make iPhoto work a bit better. Thanks for your input - I have a lot of non-computer work to do so I have to sign off.
Cheers,
Michael

Colour Band in RAW display

AMD ATHLON +5200 64 x 2 Processor
2Gb Memory
Radeon 1600 Graphics card
Catylist Software Suite 8.2
LG L1710B and EIZO GE210 Monitors
XP Professional
CS3 Extended 10.0.1
Camera Raw 4.3.1
Color Management active
When Camera Raw screen displays in full screen mode on the CE210 monitor (21" wide screen), a vertical bar is visible (very slight) on the right hand edge of the picture frame - very slightly darker (or browner) than the image. When the image is switched to zoom mode, the colour band remains on the right side of the picture frame, but as the picture reduces in size, the band remains static in the frame area, visible against the grey background. This suggests it is a part of the display area, and not part of the image. If the complete desktop area is reduced in width, the band becomes narrower, and may move out of frame.
Picture content needs to have plain colours - say sky or sea, of pale colour for the band to be visible.
If the desktop is drawn over to the other monitor, the band will most likely remain, but by "jiggling" the image a few times left-right, it may cause the band to disappear. However, immediately the desktop is drawn over to the main monitor, the band reappears.
If color management is disabled on the L1710B monitor, the band most often disappears.
Images whether originating from my camera, or sourced on line produce the same result.
When the image is displayed within Photoshop, this band does not appear - all is normal.
I use other software to display and adjust raw files, and images are perfectly normal under this software.
My current analysis is that the problem is Photoshop Camera Raw and/or Graphics controller, or interaction of these, quite possibly associated by the processing of the colour management information file(s)..... where do I go from here?
I believe I have fully uninstalled all Catylist files prior to updating to new version. As I am currently learning Photoshop, I am unable to identify if this is a new / recent problem, or if it has occurred following any software / driver update.
Any guidance will be appreciated.

Corrupt or otherwise bad display profile or bad VRAM would be my guess...

IPhoto 09 not reading Nikon raw files (.nef) properly?

Hey everyone. Over the weekend I upgraded from Leopard to Snow Leopard. Everything seemed to be working correctly until I started using iPhoto. Since the upgrade, I've noticed that photos that I imported from a Nikon D700 seem to look pixelated. I took it to a Genius Bar and the dude helping me was at a loss. He said to try and re-install Snow Leopard, which I did, and that didn't help. I went back and he upgraded me to iPhoto 09...also didn't help. He said he thinks that maybe it's Snow Leopard/iPhoto bug. He said that it's not reading the raw files correctly and seeing them as thumbnails. We looked at the photo info of a random photo, and even though it was a large 10MB file (indicative of raw format) its pixels were 160x160. Weird. Also of note, both Photoshop and Lightroom view and display all photos correctly.
If anyone has any suggestions or solutions on how to fix this it'd be much appreciated!!

Welcome to the Apple Discussions.
We looked at the photo info of a random photo, and even though it was a large 10MB file (indicative of raw format) its pixels were 160x160.
That means that what you're seeing is the jpeg Preview inside the NEF and not the actual file.
My guess is that the your Camera Raw bundle is damaged.
Go to
HD / System / Library / Core Services / RawCamera.bundle
What version of this do you have?
Regards
TD

IPhoto 09 folder structure bug

Let me start by saying that I am a big Apple fan. I have a Macbook Pro (end 2006) running 10.6 with a 30 inch Cinema Display, a 23 inch iMac (mid 2007), and an iPhone 3G and a Nano 5th G. I am an Apple Certified Systems Administrator and was also the first person in Japan to be certified on OS X 10.5 as an Apple Certified Support Professional, however I am primarily an Windows Active Directory/Exchange Server engineer.
I have been using iPhoto since version 06 (end of 2006). I upgraded to 08 as soon as it was released then last year I upgraded to 09. Until recently I had about 18,000 photos in my iPhoto library, but due to the issue listed below I have now switched to Windows Live Photo Gallery on Windows 7 for managing my photos (these are synced using Windows Live Sync to my Mac's Photo folder where I then use Picasa for Mac. Sounds complicated but actually not and it means I can import my photos on my Mac or PC and they are synced both ways. Anyway...
I posted the following Bug Report to: http://www.apple.com/feedback/iphoto.html
If you use iPhoto and don't want to spend days/weeks fixing your folder names and reorganizing photos into correct folders if your library becomes corrupt or you ever want to move your photos out of iPhoto then please provide feedback to Apple so that they know that we are not happy about this.
Bug Report.
The problem with iPhoto 09 is that the the folder structure inside the iPhoto Library package no longer matches the event names in iPhoto.
Previously in iPhoto 08, when renaming an event in iPhoto the folder structure would also be updated. Additionally splitting or merging events would move the files in the iPhoto Library package's folder structure. This is a major problem for me and many other users on the Apple.com iPhoto 09 discussion forums, and this issue has existed since the beginning of 2009!
I need my photo's folders named correctly for the following reasons:
1). Incase I should ever need to move photos out of iPhoto and to another application or platform, I would' have to spend days or even weeks renaming all the folders.
2). If my iPhoto library ever become corrupt and I needed to recreate it then I would loose ALL my event names (hence the details) if iPhoto doesn't keep the folder names the same as the events.
I have recently spent many hours migrating my photos out of iPhoto and renaming the folders manually. iPhoto really was all I ever needed in a photo management application but with this underling bug/issue I can't trust all my photos to it's library format of storage, but I do hope this gets fixed so that I can migrate back to iPhoto in the near future. Might I suggest that the best way forward for the future would be change iPhoto so that it can monitor folders (the same way Picasa does so, this is open and then gives customers the choice of using multiple apps for accessing their photos).
Regards,
Andrew

A bug can be an error or fault in the software but it can also be a design flaw which IMO this is.
No it can't. A design flaw is just that. A bug is when the software fails to works as designed. iPhoto is working as designed. You may prefer it work another way, but that's your preference. Remember you can always use a different product for managing your photos. You're not required to use iPhoto, you know.
Exporting dumps all the photos into a single folder which again doesn't solve either points 1 or 2 that I made.
Yes - if you export the entire Library at once.
If, however, you export each Event in turn (an process that can be automated with either Automator or AppleScript) then it will export to appropriately named folders.
And, as to any issue of corruption, the simple fact is that backing up is the ultimate protection.
What you want will possibly preserve your Event names. But that's all. It won't preserve albums, slideshows, metadata, the relationship between original and modified versions, the non-destructive editing and so on and so forth. All you'll get will be some folder names.
Now that's both your points answered. For the second time.
I'm not sure why there are so many Apple apologists on these forums.
I see, so someone who explains to you that you have misunderstood something, explains to you a better way of doing what you want to do is an "apologist"? Just like your definition of "bug" it's a mite idiosyncratic. And rude.
I am pretty sure that at some point there will be many users who will want to migrate out of iPhoto and when they do they won't be very happy when they realize that they are locked in.
Nobody, I repeat nobody, is locked into iPhoto. That statement is a falsehood. File -> Export and off you go.
we can either sit back and just accept these limitations, anti-competative vender lockins and design flaws or we can voice our concerns to Apple and get things changed for the better of everyone.
Every software has limitations. What you have failed to show is that any of the matters that concern you are actually "limitations". There are no
anti-competative (sic) vender (sic) lockins (sic)
iPhoto works with entirely standard formats. All your files and metadata are easily accessible throughout the OS and can be easily exported.
Regards
TD

IPhoto 7.1.3 bug - drops longitude sign on import

Hi,
After importing a given geotagged jpeg or raw file, iPhoto 7.1.3 drops the negative sign for longitude. Naturally this only effects those who live in a negative longitude. This bug is easily demonstrated.
Has anyone else seen this? Any workarounds?
Thanks
Ken

I've not tried this yet (I just ordered a Photo Finder to GeoTag my photos - it won't arrive for about a week)M and guss that I will not be in a Negative longitude soon anyway - have you reported to Apple - iPhoto Menu ==> provide iPhoto feedback?
LN

Preview and iPhoto do not open correctly raw or tiff files: they appear in false color!

Lately my macbook pro 13 ' with OS X Mountain Lion does not open files .raw correctly: they appear false color in "Preview" and also in iPhoto! What can I do?
This only happens with .raw or .tiff files, not with jpeg pics.

Lately my macbook pro 13 ' with OS X Mountain Lion does not open files .raw correctly: they appear false color in "Preview" and also in iPhoto! What can I do?
This only happens with .raw or .tiff files, not with jpeg pics.

IPhoto 9.6.1 is not displaying the photos in my iPhoto library.

My computer: I'm running Yosemite 10.10.2 (14C1514) on an iMac (21.5 inch, Late 2009) with a 3.06 GHz Intel Core 2 Duo processor. Memory is indicated as: 4 GB 1067 MHz DDR3
The problem: Yesterday, I installed an update of iPhoto from the App Stere. My new version is 9.6.1. I opened iPhoto today, and it said that my iPhoto library needed to be updated and that permissions needed to be repaired. Then iPhoto opened to a start screen with a graphic that says "To get started with iPhoto, do any of the following: Connect a camera or memory card, drag photos into iPhoto, and choose File>Import to iPhoto library.
My photos are not showing up.
I went to File>Switch to Library... which brings up a dialogue: Which photo library do you want iPhoto to use? The default indicated is the location of my existing iPhoto library. Nevertheless, iPhoto isn't displaying any of my photos.
I should note that the hard drive on which I keep my iPhoto library is working really hard. So maybe the updating and permissions repair is still happening? A look at the hard drive's finder window indicates that it was last updated at 1:36 PM today. It's now 2:02. Can repairs and updating be still going on?
I'll wait it out, but in the meantime, if anyone can advise another course of action, I'd appreciate it.
Beedubya

Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.

IPhoto 6.0.6 and RAW images - compatible??

I've taken some RAW images with my Panasonic Lumix DMC-LX3. I thought I had read somewhere that I would be able to import RAW images into iphoto 6, although it wouldn't be exactly straightforward, but now can't find the instructions. Can I do this? I have an imac G5 PowerPC.

Yes iPhoto works with Raw images from supported cameras. But no, not with yours.
The Raw format is specific to each camera model. The Raw produced by your LX3 is not the same as produced by any other camera - Lumix or not. Therefore support has to be added for each camera individually.
Let Apple know you want your camera supported: iPhoto menu -> Provide iPhoto Feedback
Note: there is zero chance of v6 iPhoto being able to work with the LX3 Raws. It hasn't been updated since 2006, and I don;t see them adding features now.
Regards
TD

BUG: iPad displays 1cm border around content in task flow popup window

I have tried this out on JDeveloper 11.1.1.6.0, 11.1.2.1.0 and 11.1.2.2.0 and each one seems to have the same problem. When displaying a taskflow in-line popup windows on an iPad (iOS 4.3.5 and iOS 5.1) a ~1cm border is displayed on the left, bottom and top of the window's content, with some of the content (also about 1cm) on the right being cut-off.
I have also tried my app out on a Android Samsung Galaxy Tab (built-in browser), Android Samsung S1 (built-in) and on my Windows 7 PC in Safari and Firefox. None of these devices/browsers have this problem.
To replicate this problem the following steps can be followed.
1) Create a normal fusion web application.
2) Add a wild card control flow rule to the default unbounded task flow.
3) Add a new bounded task flow to the unbounded task flow.
4) Set the bounded task flow 'Run as Dialog' to 'true' and 'Display type' to 'inline popup'.
5) Link the wild card control flow to the bounded task flow.
6) Add a single jsf page to the bounded task flow.
7) Add a panel box to the jsf page (or any other content for that matter)
8) Create a test page and add a button to it. Set up the button's action properties such that it opens the bounded task flow as a window ('UseWindow' - 'true'; 'WindowEmbedStyle' - 'window'; 'WindowModalityType' - 'modeless' and set width and height).
Are any workarounds for this? Is there currently a available patch to fix this problem?

Hi,
Are any workarounds for this? Is there currently a available patch to fix this problem?
if nobody dares reproducing this and filing it as a bug then a fix can take a while. I'll put it on a list of my follow ups, but this is not a high priority list. So if you can I appreciate if you can file the bug and provide a testcase. Note that 11.1.2 (11g R2) is not yet optimized for tablet PCs. So JDeveloper 11g R1 (11.1.1.6) is the build that should be used as a reference for filing the bug
Frank

17" MacBook Pro (late 2008) display banding in smooth gradients

While running the Screen Savers: RSS Visualizer or Spectrum, I noticed the graphics background looked different in sort of a high contrast, banded, sort of way. I compared it to the same Screen Saver on my Mac Pro w/30" Cinema Display and that looked fine and smooth, with no banding what-so-ever. Has anyone noticed a difference? Is this what I am to expect with this latest 2008 17" MacBook Pro LCD glossy display??? As a pro-photographer I find it less than perfect for editing purposes and will probably take it back, unless it is malfunctioning and it can be fixed. I've even seen 24" iMacs look practically indistinguishable to the 30" Cinema Display. Are they not able to make the 17" display as well?

I made an appointment with the Genius Bar and they ran an external FireWire Video Graphics Card Tester on the 17" MacBook Pro and found no problems with the NVIDIA GeForce 8600M GT card itself. Although, after consulting with other repair technicians and observing the Screen Saver "RSS Visualizer" and more notably "Spectrum", the Genius's agreed that they was an obvious undesirable increase in dithering contrast compared to LCD iMacs and LCD Cinema Display panels. They concluded it may be a problem with the LED display and wrote up a ticket and took it in for a display replacement repair.
I went nearby to a Best Buy store to see if other 17" and 15"LED MacBooks exhibited the same appearance and found that they also had an undesirable increased contrast in dithering of gradient tonality compared to Apple LCDs. While I was there, I received a call from the Apple Genius requesting I pick up the MacBook Pro since he reneged on his decision to replace the display after further checking and found no evidence of a faulty display. He said "That's the way it apparently is supposed to be." So, currently, my conclusion is that the new LED displays regardless of model are inferior to an LCD in representing smooth tonal gradations.
I hope others more knowledgeable will chime in here to explain what the heck is really going on and offer their experience with these new LED displays. For me, I will continue to test this 17" MacBook Pro LED display with high res images from a Nikon D300 and PhaseOne P45+ comparing them on my MacPro Quad Xeon w/NVIDIA GeForce 7300 GT card and 30"LCD Cinema Display. It may be that the resolution in the Screen Saver is not up to par for these new LED displays.
Visually Yours,
Bruce Christianson

Iphoto 6.0.6 bug? raw displays banding

Similar Messages

Maybe you are looking for