Passage de Lightroom 4 à Lightroom 5...

Bonjour,
J'utilise l'exportation vers Fickr à partir de Lightroom 4. Je me demande si cela va bien se passer pour Lightroom 5 ? En effet, j'ai un souvenir douloureux lors d'une précédente mise à jour de Lightroom 4 suite à laquelle j'avais du recréer complètement l'exportation vers Flickr ce qui avait abouti à :
- l'obligation de ré-exporter les images de ma gallerie,
- entrainant la perte des titres des images ainsi que les commentaires et autres données statistiques....
Quelqu'un a-t-il l'expérience de la chose ?

>
J'utilise Google Translate, donc je m'excuse pour mon mauvais français.
Il ne devrait pas y avoir de problème avec la publication sur Flickr
après la mise à Lightroom 5.
Hello Ben,
thank you very much for this reply ! Google translate is great, your
french is such good :-) I have done the upgrade for one of my catalogue.
You are right : no problem at all, my Flickr export is here and work fine
!!! Hurrah for Adobe !
Sincerely,
Vince
PS: I had written my question in french, but it was an error, since this
forum is world wide ! I apologize for this...

Similar Messages

Lightroom strips very valuable EXIF data - details

Hey everyone - I've just been playing around with some EXIF stuff, and I noticed something very concerning.
I do a lot of macro photography, specifically with Canon's MP-E 65mm 1x-5x Macro. This lens records its macro magnification factor in the EXIF data, and does so far more accurately and conveniently than I can.
I know that Lightroom and Photoshop strip out A LOT of obscure EXIF data when processed, but this magnification data is extremely valuable when reviewing my photos at a later date.
I can provide sample files if needed, and here is my observations so far:
- data stays intact when converting from .CR2 to .DNG
- data is stripped when converting to JPG, TIFF, and other formats
- data is stripped by both Lightroom and Photoshop
Here is the EXIF data (from exiftool) right from the Canon CR2 or DNG file (both are identical):
http://don.komarechka.com/exif/exif-original.txt
Here is the EXIF data (from exiftool) from a jpg that has gone through Lightroom:
http://don.komarechka.com/exif/exif-lightroom.txt
You'll notice a HUGE amount of extra data in the original raw file. It is certainly worth noting that the EXIF data in a JPG, unaltered from the camera, contains all of the same data as the RAW file.
So, is this something that has been overlooked, is there any way to change this behaviour? Even though Lightroom might not be able to decode this data, I don't see a reason why it cannot be left intact.
Thank you.
- Don Komarechka
http://don.komarechka.com

donkom wrote:
clvrmnky, thanks for your response.
Here's an example for you, the one I've been giving:
I shoot with a special macro lensm the Canon MP-E 65mm f/2.8 1-5x Macro. This lens does not zoom, but the magnification can change from 1x to 5x.This lens communicates its magnification to one decimal point accuracy to the camera, which adds it to the maker notes.
This is important in reviewing images for a number of reasons, including calculating the effective aperture and depth fo field. This is a valuable piece of information that is stored within the makernotes that is removed from the image when sending it through LR, Photoshop, or ACR.
That isn't the only valuable information, however.
The makernotes will tell me if the image was captured using LiveView, if Mirror Lockup was used, if the shot is part of a bracketed set, what the internal camera temperature was, etc. etc.
I'm not sure you've justified your reasoning behind why this block of data shouldn't be blindly copied. If it is removed simply because it is not understood, I would like the option to understand this data on my own, using third-party tools, after the image has left LR.
I understand that this can be proprietary, but likely far less so than the RAW file formats that LR and ACR already understand. It would be trivial to understand where this block of data begins and ends and to leave it in the file on export.
I think this would allow for more in-depth searching based on metadata, for whoever wants to take up that torch. For example, what if I want to see all macro photos I took at a 4x magnification or higher. What if I want to see all photo I took using LiveView. Even if LR doesn't want to do this, stripping the data out prevents anyone else from doing it in the future.
Well, there is an SDK for metadata that has been around for awhile, which allows for custom metadata definitions. But, according to the SDK:
"Values stored in custom metadata fields are stored only in Lightroom's database. In the current release, a plug-in cannot link custom metadata fields to XMP values or save them with the image file."
So, this is more for searching and interfacing with tagset plugins.
Even so, using the SDK to get at maker notes is a losing proposition.
Note that some metadata is proprietary and will not be read into the database. This is to be expected. Lr is not an arbitrary metadata reading app, and there is no guarantee that any app could read all metadata. For example, Lr tries its best to get the serial number info, but this is because there is a lot of value in that for other Lr operations. So the contortions necessary to reliably get that is worth it. Another example is lens info (which is a twisty maze of passages; no app is ever guaranteed to actually retrieve lens info reliably in all cases) where there is a lot of value trying to extract the information that makers often store in very interesting ways. In some of those cases I think Lr will look in the maker notes, but only after exhausting other avenues, and with the caveat that it may never be able to get some information. The app does its best to get at the most valuable info it can get that fits with the standardized metadata models in place.
However, the key here is that maker note data is not in exported files that Lr makes, because it is not normalized data that belongs to the vendor. (This obviates the recommendation of using Metadata Wrangler, which can filter out only that metdata that exists in Lr; I had vaguely remembered a setting that referred to this section but was wrong.)
The field and data formats are not standardized, so you are asking Lr to understand most or all data from all or most lenses and bodies (all of it in varying degrees of similarity and difference) not just data from this lens and this body.
This is also not a trivial matter of "copying" the maker notes over, because copying implies parsing and duplicating what is essentially unknown formatted data containing proprietary data, possibly by custom serialization routines. Remember that maker notes were never intended to be editable, and could be composed of any number of data formats. Some cameras make maker notes that are megabytes of nulls and nothing else!
I think you are out of luck for this specific case. Perhaps with EXIF 3 we will have a more standardized interface cameras and software can more easily interoperate on shared data. Makers need to stop using the maker notes! It was always an egregious hack.
One workaround I can think of is to have a post-export action that uses EXIFTool to update exported images. For those cases where it matters, you could create your own "sidecar" file that has only the maker notes, and then shove those into the JPEG after they are created, or just read it from the on-disk copy and then put it in the new file (possibly in the same directory and added back into the catalogue for convenience.)

Lightroom 5 issue with publish to facebook export plugin: not authorized status

Hi,
trying to connect Lr 5 to fb and being stuck at the authorization process.
In the facebook publish plugin within Lr I hit the 'authorize on facebook'.
IE is launched, facebook opened and it guides me throug the usual step, everything looking normal and fine.
Facebook finally states the app is added and authorized (this is showing up under apps as well looking good).
However Lr is taking a moment to realize the authorization process is done, but then it goes to 'not authorized' status instead of authorized.
I simply tried doing it again, it restarts the process but facebook than gives an error.
I assumed this was due to the app already being there listed under authorized apps, so I removed the app on facebook. fb worked again through the process, but Lr keeps getting not authorized out of it while it is perfectly fine and authorized looking on facebook..
Umm.. help?
Thanks for any clues, I'm a bit well clueless right now ;p
Cheers

Hello,
this is a Facebook problem and not a Lr problem !
Go into Facebook, open your account and go into account settings. There you will find a passage called apps, open it and you see all programs and apps that are allowed to 'play' with your account. There you will find Adobe Photoshop Lightroom in the list. Delete it from there, so that Lightroom has no more the permission to do anything with your Facebook account.
After this, go into Lightroom, chose the exporting services for Facebook, right click on it and connect it to Facebook with your account name and password like you did it before.
That should solve the problem in complete !
Good luck
Robert

Lightroom 3 crashes on import every time

Hi.
I have just installed the demo version of Lightroom 3 on my Windows XP (3GB RAM). It installed and opened fine, but when I click on the "import" button, it crashes every single time. I have not been able to import anything at all. I have tried folders and just one single image (I tried drag-n-dropping it too)
I have re-installed the program once to no avail. I have deleted the prefs (or so I think) and tried numerous other things.
Very thankful for any help!
Regards
Sebastian

32-bit operating systems are limited to 32 bits of address space. This is 4GB.
Windows places some additional restrictions on this by reserving 2GB of total physical RAM for the system, leaving 2GB for user processes. Because each process needs space for various libraries and stacks and other private stuff, the theoretical 2GB is actually somewhat less, but it depends on the application the exact value.
The /3G switch is a way to take part of the system memory away and give it to user processes, but not all applications and environments can operate in such an environment. It is only recommended (barely) for Windows servers where you need to make sure some small set of services have the largest user space.
Lr is not "restricted" to 1Gb. As a 32-bit or 64-bit application it will ask for whatever resources it needs to the maximum addressable space and will use that or make do and recover (in most case) if the resources are unavailable. If this means Lr starts swapping to virtual disk, so be it. Since Lr has to share that physical RAM with other processes on the machine, it is up to the OS to balance what it can give out. It will usually give foreground user apps as much as it can, but memory is a precious resource, and every process can ask for it at any time.
64-bit version of the Windows OS and 64-bit applications can theoretically see a 64-bit address space, but Windows (and, actually, most other operating systems) restricts the user space to some much reasonable smaller number that depends on the flavour of Windows (there are something like 7 kinds of Windows 7.) In the "premium" flavours it is something like 16Gb, with 15Gb being the reasonable maximum because of libraries, stacks &etc. This is a little different because 64-bit pointers and stacks are twice the width of their 32-bit counter-parts.
(This is all from memory, BTW, and Windows memory management is a twisty maze of passages, all different. See here: http://msdn.microsoft.com/en-us/library/aa384271(VS.85).aspx)

Aperture conversion to LightRoom

With the passage of time, is there an automated way to convert from Aperture to LightRoom? I'm fed up with Aperture, but intimidated by the idea of converting one project at a time, via Export Masters. Is there a better way?

It's understandable enough because their priority had to be on coding core features. And on two platforms. It's more a matter of Apple not providing an easier way to get data out of Aperture - what's so hard about coding a "Save metadata to xmp sidecars"?
I have tested my idea on a small sample. I guess it's this bit that I didn't explain.... I select a project, selected its thumbnails (all raw files), and then went into Metadata > Batch Change, typed in the project name (I wrote it "A-Test project" so it would be easy to identify the ex-Aperture keywords), and then I chose keywords. Clicked OK, and Batch Change adds the new keyword to the masters.
Then like you I did an export masters with the sidecars, and imported them into LR. The keyword came into LR. I selected the keyword, and Cmd N saved the pictures into a new collection. Its main advantage is that you can leave Aperture exporting loads of files. It is worth looking at for raw files at least.

Plantage lightroom 5.7.1

Bonjour,
je viens a vous pour un problème de plantage aléatoire de lightroom en module développement (rien a priori en bibliothèque/ autre modules non utilisés pour ma part et non testés) (version 5.7.1) depuis 2 jours.
Je suis désolé par avance de de la longueur des explications qui est à la mesure de mon incompréhension:
Voici ma configuration :
Windows 7 64 bit/ Intel quad core i5 3.3GHz/ 8giga de RAM (testée et fonctionnelle) / bi-écran (24+22pouces)/ 4 disques internes dont un SSD Samsung 128 Giga rajouté il y a un mois.
Les photos sont sur un disque interne (WD caviar 7200t/min) avec backup sur un autre disque interne et un 3° externe en USB.
Jusqu’au mois précédent (sans le SSD) : aucun plantage tout fonctionnait correctement (à par des lenteurs mais rien de rédhibitoire).
Il y a 1 mois installation du SSD Samsung sur lequel est installé uniquement le catalogue et le cache LR ainsi que lightroom 5.7.1 : Pendant 4 semaines que du bonheur, réactivité de lightroom très satisfaisante aucun plantage : ravi.
Il y a 2 jours sans aucune modification logicielle ou matérielle : import de nouvelles photos dans LR: De manière totalement aléatoire en module développement ( quelque soit le curseur utilisé) lightroom plante en moins de 1 minute (que ce soit sur des nouvelles ou anciennes photos) avec le message : lightroom 64 bit à cessé de fonctionner Windows tente de trouver une solution… et tout se ferme. Bref inutilisable.
Je précise que mon ordinateur marche parfaitement par ailleurs/ aucun logiciel récent installé. Cela se produit surtout lorsque l’écran secondaire est activé.(ma config de base).
Voila ce que j’ai fait dans l’ordre :
1°Passage antivirus/antimalware : RAS
2° test de la mémoire : Ras/ test du ssd (utilitaire Samsung : RAS)
3° : préférences de lightroom supprimées : pareil cela plante toujours.
4°Désinstallation/ réinstallation à plusieurs reprises de LR sur le SSd puis sur le disque system C (conventionnel) avec nettoyage de la base de registre : pareil plantages aléatoires
5° mise a jour des pilotes graphiques: pareil
6° en désespoir de cause : formatage de l’ordinateur/ réinstallation complète de windows 7 à neuf et des tous les programmes sur le SSD samsung avec réinstallation de lightroom sur le SSD avec sur une partition dédiée du SSD le cache (15 Giga) + le catalogue avec suppression et reconstruction de tous les aperçus :Idem toujours des plantages de LR après moins d’une minute de travail en module développement avec le même message...
7° création d’un nouveau catalogue avec moins de 100 images : pareil ça plante…
Je n’y comprends rien…
Les pistes que j’évoque:
1:le SSD est défectueux mais alors pourquoi tous les autres programmes installés sur le SSD n’ont aucun souci ?. l’utilitaire et logiciel Samsung fourni avec me dit qu’il fonctionne parfaitement de même que Windows.
2:Le disque ou sont installées les photos est en train de lâcher ? mais lightroom ne touchant pas aux originaux mais se servant des aperçus … cela ne devrait pas provoquer de planbtage. je vais tenter de les installer sur un autre disque pour voir même si l’utilitaire SMART ne m’indique pas de problème sur le disque.
En dernier recours,
1° installer mes photos sur un autre disque/ 2° installer lightroom, le catalogue et le cache sur un disque autre que le SSD pour voir si cela solutionne le problème/ 3° je n’ai aucune autre idée de plus et soit je repasse à une version antérieure.
je pense à un problème matériel mais lequel et comment le mettre en évidence... si c'est le SSD (neuf) qui débloque comment s'en rendre compte?
Merci pour votre aide.
Nicolas.

voici le rapport de windows; une idée??
Nom de l’application défaillante lightroom.exe, version : 5.7.1.10, horodatage : 0x547e35e8
Nom du module défaillant : CameraRaw.dll, version : 5.7.1.10, horodatage : 0x547e3551
Code d’exception : 0xc000041d
Décalage d’erreur : 0x00000000000bd763
ID du processus défaillant : 0x7e4
Heure de début de l’application défaillante : 0x01d055298752e247
Chemin d’accès de l’application défaillante : C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.7.1\lightroom.exe
Chemin d’accès du module défaillant: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.7.1\CameraRaw.dll
ID de rapport : 11c80c0f-c11d-11e4-92ed-5404a6a43d81

Le nouveau Lightroom CC installé par creative cloud refuse de se lancer ?

Par Créative Cloud, j'ai téléchargé Lightroom 5, il y a quelques mois et je voudrais faire la mise à jour en Lightroom CC aussi téléchargée très récemment mais, il ne se lance pas. Existe-t-il une procédure de passage de LR5 à LR6 ? Merci pour vos réponses.

Hi,
I believe you mean the Lightroom CC (latest).
Please download the installer from the link below:
New Adobe Lightroom 6 (CC) Direct Download Links – Free Trials | ProDesignTools
Regards,
Sheena

Taille/Qualité photo sur lightroom mobile

Bonjour,
Lorsque j'importe une photo sur lightroom mobile à partir de la galerie de mon smartphone, la photo perd en qualité (passage de 10Mo à 1Mo). Est-il possible de modifier les réglages de lightroom pour que la photo ne soit pas redimensionnée automatiquement ?
Merci d'avance,

Bonjour,
Lorsque j'importe une photo sur lightroom mobile à partir de la galerie de mon smartphone, la photo perd en qualité (passage de 10Mo à 1Mo). Est-il possible de modifier les réglages de lightroom pour que la photo ne soit pas redimensionnée automatiquement ?
Merci d'avance,

Problème avec Lightroom 2.5... Help!

J'ai un problème avec Lightroom 2.5 que j'utilise avec mon macpro sous OS 10.5.5 ...
Je sélectionne des photos dans le module bibliothèque et souhaite faire imprimer ma sélection par un labo distant.
Je vais dans le module "IMPRESSION"
Tout va bien, je choisis mon format, mes marges, mon encadrement, j'incorpore ma plaque d'identité qui devient ma signature dans la marge ..
C'est superbe, automatique, rapide ... J'utilise pour celà l'onglet en bas, à droite : "imprimer dans fichier", et toute ma sélection est enregistrée en .jpg , il ne me reste plus qu'à envoyer par Cyberduck ou Filezila au serveur FTP du labo et le tour est joué ... Bravo Lightroom2 ....
MAIS...
Gros ennui, cependant ... C'était trop beau !.. Mes photos se sont faites débaptisées au passage, et par exemple, celle qui s'appelait IMG_4240.JPG est devenue : nomdudossier-1 ... ! Si j'envoie 1000 photos, toutes différentes, avec des noms différents ( ce qui est OBLIGATOIRE pour m'y retrouver !), je me retrouve avec 1000 photos numérotées de 1 à 1000 !...
HELP ! Comment faire pour que Lightroom2 conserve les noms de fichier de chaque photo !
Je ne peux pas croire être le seul photographe de France à être confronté à ce problème !
J'espère que quelqu'un saura me répondre !
Je le remercie à l'avance.
Gérard Changeux, Photographe.
http://photosdechasse.com

Are you using a PowerPC (e.g., G5 Mac) machine?
Your thread title says "2.5" but your original post mentions upgrading to "2.6" ... I bet you're actually using 2.5. Is that right?
If the answer to both is yes, then yes, this is a known issue for specific camera models. It is fixed by updating to 2.6.

Runtime error in starting Lightroom

I receive the following message when I try to start Lightroom:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:...Files\Adobe\Adobe Photoshop Lightroom 1.2\lightroom.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Lightroom ran well for several days and then failed to open with the above message.
I have tried everything I know to do (uninstalled and reinstalled the application, restored the computer to a restore point before Lightroom was originally installed, etc.) and do not know were to go from here. Suggestions would be appreciated.
I am using Windows XP sp2 and have 4 GB of ram and 250 GB of hard disk space.
Thanks,
Cliff Culp

Aha! A fix! Please look at this...
http://www.adobeforums.com/cgi-bin
bob frost, "Help! Runtime error after Lightroom 1.1 install!" #10, 27 Jun 2007 6:54 am

Lightroom imports photos to wrong folder

I've been importing lots of photos from my hard drive into lightroom and been moving/renaming them in the process. I only got lightroom a few weeks ago.
This has worked fine but i've recently imported a few hundred photos off my iphone and doing the same thing - move and rename. The trouble is, these photos keep going into the 2009 folder, instead of the 2012 or 2013 folders that they should be. When i look at the photos, they have the correct name, and the capture date seems to be correct, its just lightroom keeps wanting to put them in the wrong folder by year. Does anyone understand why this might be happening?
naturally I want all my photos sorted into the right date folders as this is the way ive decided to organise my photos...

hmm so still not making sense. it keeps wanting to import my photos into the wrong destination. have removed all the photo from lightroom. how do i change it so it automatically puts the photos into the corresponding year/month they were taken..
I understand its something in the import settings/destination but cant seem to change this. not sure what parts of the import box your wanting to see Dj.
the structure now is my pictures/2009/21-7-09 then its creating new year folders and sorting them within this 21-7-9 folder..
can't see to change this?

I am trying to import developed images from LightRoom 5 in o Photoshop 6. I am receiving this message and the images will not open.....'Could not open scratch file because the file is locked, you do not have necessary access permissions or another progra

I am trying to import developed images from LightRoom 5 Photoshop 6 for further editing. I am receiving this message and the images will not open.....'Could not open scratch file because the file is locked, or you do not have necessary access permissions or another program is using the file. Use the 'Properties' command in the Windows Explorer to unlock the file. How do I fix this? I would greatly appreciate it if you would respond with terms and procedures that a computer ignorant user, such as me, will understand. Thanks.

Have you tried restoring the Preferences yet?

Have a problem with Lightroom 5.4. Since the program crashed yesterday it won't launch, it comes up with the message "Lightroom encountered an error when reading its preview cache and needs to quit". " Lightroom will attempt to fix this problem net ti

Have a problem with Lightroom 5.4. Since the program crashed yesterday it won't launch, it comes up with the message "Lightroom encountered an error when reading its preview cache and needs to quit". " Lightroom will attempt to fix this problem next time it launches". Except that it doesn't, I keep getting the same message and the program closes. Does anyone know what I can do to repair it? Can't back up, can't do anything.

There are dozens of threads in this forum that describe the fix

When I try to open my Lightroom 5 program it comes up with this message, "Lightroom encountered an error when reading from its preview cache and needs to quit." How do I fix this?

Can someone please let me know how I can fix this error and open my Lightroom? Thanks.

You might be quicker help posting in the LR forum rather than the ACR forum, but I believe the way to fix this is to delete the preview cache.
Find your catalog folder.
Close LR.
Within the catalog folder, delete the FOLDER called Catalog-Name Previews.lrdata
Start LR.

Lightroom will not launch and comes up with the following message "Lightroom encountered an error when reading from its preview cache and needs to quit". Lightroom will attempt to fix the problem next time it launches, except it doesn't fix and I now can

Can anyone help with the above problem?

Here is your fix: Lightroom says my preview cache is corrupted—how do I fix it? - The Lightroom Queen

Passage de Lightroom 4 à Lightroom 5...

Similar Messages

Maybe you are looking for