Image import bug

This past weekend I was setting up my new macbook pro and transferred about 2000 photos from a networked PC onto my mac. I was able to import all my photos successfully into iphoto and organize them there but whenever I did I would get errors in front row and imedia when i tried to view them through those programs. I would get an error that no photos were in my library.
After hours of playing and testing i discovered that some of my photos - for seemingly no reason whatsoever - successfully import into iphoto but break the library connection to other programs. I attempted to change file formats and resave them through photoshop and reimport them. This worked some of the time but not with any real consistency i could discern.
I eventually abandoned it because the process was taking FOREVER in trying to narrow down the issue. I know have all my old photos in a seperate folder where i can view with preview but can't import into iphoto.
Anyone ever experience this or have any insight into what might have happened? The photos were not corrupted in anyway i could see. Any clues???

johnnymal
There was a post here over the weekend where a gentleman could not get the library to show up in other applications, including Front Row. He finally tracked it down to a non-ascii character in one of the keywords applied to the photos. I guess this might also affect if there are non-acsii characters in titles etc. Worth checking out.
He made the discovery from the error messages he got with iPhoto Library Manager, which can be downloaded form here:
http://homepage.mac.com/bwebster/iphotolibrarymanager.html
Regards
TD

Similar Messages

Plantage d'illustrator avec des images importées (CS6 64 bits pour Windows)

Bonjour,
Je travaille (en entreprise) sous Adobe CS6 (64 bits). Depuis ce matin, lorsque j'essaie d'enregistrer (ou d'imprimer) mes compositions qui contiennent une image importée, Illustrator se ferme avec une petite fenêtre windows "Illustrator a cessé de fonctionner".
Je suis certain que c'est la faute aux images importées car tout fonctionne très bien quand je n'enregistre que des textes ou que des formes (plume, autres,...).
Je voulais savoir si ce bug était répertorié (je n'ai rien trouvé sur internet) et quelle pourrait en être la solution ?
Merci d'avance,
Cordialement

Re-bonjour Machinvert,
Il faut savoir qu'un compte utilisateur et donc restreint peut être la cause du problème, il faut savoir que ce type de compte ne vous donne pas un access total en droit de lecture et d'écriture comparativement à un compte administrateur.
Un compte en serveur peut être également le problème dû par la configuration faite et de leurs paramètres different de ceux d'un compte local normal Windows.
Si votre collègue a eu le même problème et me doutant que la configuration des comptes Windows soit indientique à la vôtre, cela peut expliquer le problème et donc il faudrait dès lors faire un test sur un compte Admnisitrateur en local Windows.
La désinstallation n'est pas la solution appropriée étant donnée que le problème ses presente sur 2 PC different, sauf, si l'installation a été faite en déploiement et dès lors il faudrait peut-être revoir et voir refaire l'installation si celle-ci n'a pas donné un succès escompte.
Une coupure de courant a certainement cree pas mal de problème dans l'ordinateur comme certainement au niveau du serveur.
Je ne pourrais vous conseiller que de prendre contact avec votre service informatique et de leur faire part de mes notifications.
Merci de votre comprehension.
Arnaud.

LR 3.2-Images Imported Not Always In Order. Why??

This problem did not exist in LR 2.x.
With v3.2, images imported from SD card do not always import to LR based upon the order in which they were captured by the camera.
Using Windows Vista Home Premium.
Am I missing a default setting that needs to be changed?
Thanks for any help/info.........

Question answered. I wish I had dug around just a bit before whining:
In the full up import dialogue, the bottom of that screen has various sort options.
One of them is capture time. That will take care of my concern.
However, it appears that the selected capture time option must be reselected prior to each import.
Too bad that it is not in the software memory, as is now the option for "Copy As DNG". In LR 3.0, that was a bug, as it too was not in memory and had to be selected prior to each import.

Images imported from QT exported image sequence have jagged edges

Hi
I've come across something strange which I'd like to resolve.
I export an image sequence from QuickTime.
I then import this into Aperture.
But the images imported into Aperture now have jagged edges where there has been any movement in the original footage.
The images originally exported from QuickTime look absolutely fine when viewed with preview, they have the expected blurring on moving objects, but no jaggedness.
Now, a bit more detail.
The footage I'm exporting from was shot by me and came from a Final Cut Pro edit.
The codec in the QT movie is Apple Intermediate Codec and this is interlaced.
The jagged edges on movement look to me like the problem of interlaced not being converted to progressive.
However the exported images from QuickTime don't display this when viewed in Preview, it is only when viewed in Aperture that the jagged edges become apparent.
I have tried exporting from QuickTime to jpg, png and psd, but the problem is identical no matter which format I use.
I really want to now use Aperture to improve these exported images, but with this jagged edge problem I can't.

Hi JNorris--
Sounds like you need to apply the deinterlace filter (Effects tab: video filters: video: deinterlace) to the stills your exporting.
See if that makes a difference to start.
T.

Star Rating bar does not appear with images imported from file

Using Elements 11, cannot get the Star Rating bar to appear under images imported from file, although the intro to the program shows this as happening automatically.
Hope this goes through, as I have also created an account, but the question does not seem to be get a post.
Help!

Have you enabled Organizer to show details? You can enable show details by checking View > Detail is not already checked

Lightroom 4.3 import bug

Why is an image imported into Lightroom 4.3 significantly lighter than the same image displayed in Windows Photo Viewer at the same time and on the same screen?
This basic problem also applies when using an external editor such as Elements 11 where the image is returned much lighter than what appeared in Elements.

Thanks for your reply.
I take your point about windows Photo Viewer but what about Elements 11? Also if the two versions of the image were displayed on the same monitor at the same time would that not invalidate the need for screen calibration?
As perhaps a better demonstration of the problem, if I export an image to a jpg with "add to this catalog" checked the added jpg is returned significantly lighter.

Do images imported to Keynote retain their previous color profile? In other words, if the Keynote presentation will be shown using an sRGB profile projector, should the images be converted to sRGB prior to importing?

Do images imported to Keynote retain their previous color profile? In other words, if the Keynote presentation will be shown using an sRGB profile projector, should the images be converted to sRGB prior to importing or can they be batch adjusted in Keynote?

While I feel your comment doesn't directly address my question, why I am worrying is this.
This presentation is to a camera club. Color is important. Images shown in meetings are projected by an sRGB color profile projector. Most serious photographers us a color profile with a bigger space than sRGB (typically RGB1998). If you project an RGB1998 image on an sRGB projector the colors go to crap. More precisely they become dull and lifeless. Thus, I am trying to determine whether I need to convert the images I plan to put into my Keynote to sRGB and boost the saturation PRIOR to importing them or whether Keynote has a way to do this as part of the software.
Jerry

Nwrfc 0.0.5 with important bug fix!

I have just pushed version 0.0.5 of the new gem to rubygems.org (you can also access the latest repo at GitHub).
0.0.5 introduces an important bug fix in Table#each. Previously only the first row would continuously be returned. Now you can actually treat a Table like an Enumerable!

To quote Metalink Note 161818.1 (Oracle Server (RDBMS) Releases Support Status Summary)
"Terminology Used in this Article
Patch Set
*Patch sets are cumulative. For example, 10.1.0.4 includes all the fixes in 10.1.0.3 as well as new fixes for 10.1.0.4.* "

CS6 default image import is different than CS5

The default image import option for CS5 was "Crop" now with CS6 it's "Bounding Box"
Any ideas on how to change the default so I don't have to keep using the dialogue box?
Thanks

I just figured it out.
I was actually replacing an image and not importing. And I was using the link button in the links window, not the Command D shortcut.
The reason I used the term "image import" in the title of my question is that the dialogue box used when replacing an image says "Show Import Options". This is where I found the Crop option and this is the procedure that would not "stick".
I remembered that I could use Command D also to replace an image and that since this is the Place keystroke then the window would give me the same option. I chose "Crop" in the dialogue box, successfully replaced the image, closed InDesign, opened InDesign, used the link button in the links window to replace my image and Voila! it stuck.
So, just in case somebody else asks, to make it stick you MUST use the Command D shortcut or the Place menu item. Using the link button in the links window will not make your choice stick.
Thanks for your help Peter, I can see now why you were pulling your hair out on this, you must have been assuming I was using the Place menu item.

I cannot view images imported from nikon d4

i cannot view images imported from nikon d4.
I have just upgraded to the most current version of aperture and when I import images from my qxd card it looks like it is importing but no images show up.

So the images show up in the Import pane of Aperture but after you press the Import button they do not show in the project you are importing into?
Does this happen for both Raw and JPG images?

Images imported via card reader from Eye-Fi chip are garbled

Laptop is g580 20157, factory installed windows 8
Eye-Fi Pro x2 8 GB WiFi
When using the Eye-Fi via the sd media reader, imported images are garbled. Some thumbnails look ok, others not. All images when previewed are bad.
When using the Eye-Fi sd to usb converter, images import just fine. When using usb cable to import from camera, images import just fine. When using a non-Eye-Fi sd chip, images import just fine.

Hi JayWilson,
Thanks for posting and welcome to the Lenovo Community,
I’d like to ask you to share with us the status of using the wireless connection is it stable with you and working fine?
And I’d like to advise you to try to contact the service provider for your Eye-Fi card as i need to share with you the
requirements for the Eye-fi card that you have:
Computer with Windows 7/XP (SP3)/Vista or Mac OSX 10.5+ (Intel only) and 100MB of free space.
And as I understand from your post your machine came with windows 8.
Hope the information helps. Let us know.
Regards
Soha
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

I believe I found an import bug in LR 5.4

I believe I've uncovered an import bug in Lightroom 5.4 under Mavericks. I noticed a folder with 19 photos and videos, but LR was only showing 18. So I tried synchronizing the folder, and still only 18 were found. So, in the import screen I unchecked "Don't import suspected duplicates", and it still would not import. So, I removed the folder containing the photos from LR, then re-imported them, and still only 18 photos!
So, the .jpg file listed here will NOT import into LR regardless of my efforts. The mp4 imports just fine. It seems like a bug pertaining to files with the same name but different extensions, or something similar. Here are the file names:
bernie3_blue_baby_shopping_walmart-09-2.mp4 - IMPORTS OK
bernie3_blue_baby_shopping_walmart-09-2.jpg - WILL NOT IMPORT

I’m not sure it’s a bug but rather by design. For example if you do external editing from Lightroom in Photoshop the word Edit is automatically added to the tiff or PSD file with the same name. Simply change the file name for the jpeg and it will import. LR does permit jpeg and raw files with the same name but it requires enabling in the prefs. I assume there is no similar pref setting for videos, as they would always be numbered separately when importing directly from a camera card; so the situation would never usually arise.

Safari image appearance bug

Hi all,
There is a image rendering bug when viewing images in this site:
http://en.fotoalbum.eu/kodead/a595746/slideshow
Try to change the images backwards. It appear when smaller image is displayed first and then when you change to bigger one the bigger image borders are displaced. The bug disappear when you click next (or changing from bigger to smaller image) or when you move over some object (ex. notepad window) over the wrong displayed image.
I reported this bug in the safari, but there is no backlink or any number to track the issue, so I decided to write here - I want to check it regularly for solution.
Thanks!
PS and sory for my nickname. the system didn't accept shorter one several times

If you'd like to track a bug, first register (for free) as an Apple Developer:
http://developer.apple.com/programs/register/
And then you'll be able to submit a report via the Apple Bug Reporter:
http://developer.apple.com/bugreporter/
... which will allow you to track the bug.

IDML Import Bug?

Hi All,
Just wondering if anyone can reproduce what appears to be a CS4/CS5 IDML import bug.
I typed
11
22
33
44
55
(first 3 digits in bold) then tagged "22" as an XML element before exporting an IDML file.
When the IDML file is imported, I get
11
22
33
44
55
(all digits in boldface except for the trailing 2.)
The problem seems to be on the import side of CS4/CS5 since the exported IDML looks okay to me:
<ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/$ID/NormalParagraphStyle">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>11</Content>
 
 </CharacterStyleRange>
 <XMLElement Self="di2i7i6" MarkupTag="XMLTag/Story">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>2</Content>
 </CharacterStyleRange>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 <Content>2</Content>
 </CharacterStyleRange>
 </XMLElement>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 
 <Content>33</Content>
 
 <Content>44</Content>
 
 <Content>55</Content>
 
 </CharacterStyleRange>
</ParagraphStyleRange>
Comments anyone?

Hello Larry,
i am the developer of the IDMLlib http://idmllib.com/ a Java library which is able to read/modify/create IDML.
I have also noticed some strange behavior regarding the importing of IDML, where the order of elements affect the parsing of the IDML in CS4/CS5.
My first thought was, i have created an invalid IDML, but the IDML Relax NG compact schema is very explicit, order doesn´t matter.
The best example i have at hand, which is very easy to reproduce is the TabList. A valid tablist attached to ParagraphStyleRange for example looks like this:
<TabList type="list">
 <ListItem type="record">
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 <Position type="unit">144</Position>
 </ListItem>
</TabList>
If you change this by moving the Position to the top, which is no problem regarding the schema which doesn´t enforce a strict order of the elements:
element Alignment { enum_type, TabStopAlignment_EnumValue }&
element AlignmentCharacter { string_type, xsd:string }&
element Leader { string_type, xsd:string }&
element Position { unit_type, xsd:double })
So if you change this example to this, and reimport the IDML into CS4/CS5 INDD the <Position/> will not be parsed and you wont see a TabList
<TabList type="list">
 <ListItem type="record">
 <Position type="unit">144</Position>
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 </ListItem>
</TabList>
If you export this again as IDML the <Position/> if set to 0
I circumvented this problem by forcing the creation of TabList Items with a constructor that will only allow to create TabListItems with all values present and therefore i can force the order of the created childs. But i think this will not be the only problem where parsing doesn´t do what it is supposed to do.
There has been a posting from a guy complaining about different import results regarding the attribute order of IDML element:
http://forums.adobe.com/thread/637711
I will try to reproduce the behavior you decribed.
Cheers, Andreas

Limited image import from scanner

I find only limited image import options under Photoshop CS5 and CS6. Under CS3, I have a number of options which I have used frequently, regarding preview, zoom, desceening, filtering, stretch, noise removal, fading, grain, etc. None of these seem to be available under either CS5 OR CS6. In fact, under CS5, under "FILE>IMPORT", I I don't even GET the Canoscan 8400F opton. This is pretty basic stuff, getting good quality off a scanner. What's up? Do I need to go back to CS3 for everything? It actually worked.

Hi there, I'm sorry you aren't able to scan.
What operating system are you using? There are known issues with scanning while running Mountain Lion, in particular. If this is the case, Adobe engineer reccommends trying Image Capture:
Image Capture is a utility program in the Utilities folder inside the Applications folder, and is a standard part of Mac OS X. As far as I know, Image Capture does work properly in Mountain Lion.
ImageKit refers to the underlying Cocoa frameworks (programming interfaces) used by Image Capture as well as by Photoshop and other applications to perform scanning. For reasons I won't go into here, these are not working correctly in Photoshop, but are in Image Capture, which is the problem we're working to resolve with Apple.
The scanners that work with Image Capture/ImageKit are also a standard part of Mac OS X, which means that users do not have to go to a different web site (e.g. Epson's web site) to download and install drivers for their specific scanner, which you do have to do with TWAIN. Scanner support (numbering in the hundreds) through Image Capture/ImageKit is already included in Mac OS X "out of the box".
We added support for ImageKit scanning to Photoshop CS6 because we recognized it was unlikely that scanner manufacturers would go back and rewrite their TWAIN drivers to work in 64-bit mode (especially older scanners that are no longer manufactured).
One advantage is that as improvements are made to ImageKit and as more scanners are added by Apple to their Mac OS X releases over time, Photoshop users get those "for free", so to speak. Unfortunately, changes to ImageKit made for Mountain Lion have had the effect of breaking this feature in Photoshop, but we are confident this will get sorted out.
Here is an article talking about known issues with scanning in CS6, and some workarounds. It suggests downloading a TWAIN driver (more information here) or using your scanner's scan utility (although this might not be the optimal solution for you, considering you came to the forum).
I hope this information helps!

Image import bug

Similar Messages

Maybe you are looking for