Side Car

Hi All,
I checked the forum, i havent got any crystal clear output.
My queries are as follows
1. what is SAP hana side car approach?
2. On what usecase SAP hana side car will work?
3. Can sap hana sidecar can connect to multiple ERP running on sql server, oracle?
4. what are tools to connect ? how it works
Any relates sap notes for the same
Thanks

Hi Prag,
Side car scenario is not just used for POCs . My be in any circumstances, if the customer does not want to run their solution(ERP may be) on top of HANA, but still want to do analytic on top of the data, side car scenario can be used. But that is a rare case no a days. Sometimes customers do not want to disturb critical systems.
Sree

Similar Messages

How do I convert raw images with side car to Dng and

How do I convert raw images with side car to Dng and preserve the sidecar info in the DNG?
I have tons of raws + xmp sidecars that i want to convert to dng, because the raws are from different camera brands and i want to get everything simplified. so that i do not have to worry if I will be able to access the raws in the future, if I decide I want to rework some of the files.
T.I.A.

If the images are already in your catalog you can select them then choose Convert Photos to DNG from the Library menu. You'll be given the option of deleting the original raw files. Either way, Lr will only display the newly created DNG files.
The alternative, which is better suited to images not already in the catalog is to use the Adobe DNG Converter

System refresh in HANA (Side-car)

Hi Experts,
I have some queries around system refresh in HANA.
I have a side-car implementation of HANA. Data is replicated by SLT from ECC to HANA.
Question is - Can we directly perform a system refresh from prod HANA to Quality HANA box?
or we can only have below option:
Refresh prod ECC to Quality ECC & reload all the tables again from quality ECC to quality HANA?
I am particularly interested to have answers/thoughts on -- "Can we directly perform a system refresh from prod HANA to Quality HANA box?"
I have not heard of this approach so far.
I know the other option - "Refresh prod ECC to Quality ECC & reload all the tables again from quality ECC to quality HANA?" is feasible.
quick response is much appreciated.
Best Regards
Sachin Bhatt

Sorry I thought it was clear, let me explain.
HANA with SLT, is a replica copy of ECC tables. If you copy HANA Prod back to QA then SLT will no longer be operational.
You could re-enable SLT but you would have to re-initiate replication which would wipe out all the HANA tables, thereby making your system copy worthless.
If you don't re-enable SLT then you won't be able to do any testing or any table changes into QA.
So really there is no choice, you need to copy ERP Prod and HANA Prod, or just copy ERP Prod and re-initiate replication.

System Refresh with HANA & HANA live (side-car) data

In a scenario where HANA live co-exists with HANA DB (aka side-car approach), trying to understand the impact of system refreshes to HANA Live content. Is there a method to choose only HANA DB specific data for the refresh i.e. excluding HANA Live data? If we use the backup/restore method to refresh QA from PROD it will bring Prod data over for HANA Live too. Is there a way to export QA HANA Live data prior to the refresh and re-import it post DB refresh?

Sorry I thought it was clear, let me explain.
HANA with SLT, is a replica copy of ECC tables. If you copy HANA Prod back to QA then SLT will no longer be operational.
You could re-enable SLT but you would have to re-initiate replication which would wipe out all the HANA tables, thereby making your system copy worthless.
If you don't re-enable SLT then you won't be able to do any testing or any table changes into QA.
So really there is no choice, you need to copy ERP Prod and HANA Prod, or just copy ERP Prod and re-initiate replication.

Side car files off, for a dropbox folder

Hi Everyone,
I think this is not possible, but hopefully i'll be proved wrong!
I want to set one folder to not use side car files - is this possible on a single folder?
(It's a shared dropbox folder, and my system is set up to always write to side car files ... but because it's shared, i don't want to clutter the folder with my side car files - and also don't want my xml files getting in the way of other people's xml files.)
Cheers!

Hi dj_paige,
Thanks for your response.
The use was to collect images of family members taken at a funeral, with each person who had a camera having a folder. Because these images are just presented as a list of files, it seemed to me the easist thing for me to do would be to have all of the images within LR - that's because it's the DAM app that i use.
I'd like to make a blurb book from the files for the family - which also points to using LR.
The reason why i'm not keen on exporting is that if someone was to add filess to their folder, then it would involve a bit of work finding out which file it was and then transferring them - rather than just syncing the top level folder (that contains all the other folders) every now and then.
As you can see, it's more of a one off thing, than a course that i'm going to regularly take.
I think what i'll do is turn off the write to xmp - then work on the files - and turn it back on again and go back to my regular work.
Cheers,
and thanks Rob too
slaterk

Subtitles. with "Side car" via Media EncodeurCC under Encore CS6. thank you

Hello,
I have with Premiere Pro to place subtitles.
Although I followed the method with "Side car" via Media EncodeurCC the subtitles do not appear under Encore CS6.
thank you

Did you add the subtitle track and import the subtitles? If so, describe more about what you are doing.

I (kind of dropped) my rMBP 15" from the floor of the passenger car side to the ground. It was protected in a Thule Gauntlet sleeve inside a Thule Crossover Backpack. Should I be worried?

My rMBP 15" was protected in a Thule Gauntlet sleeve which was then inside a Thule Crossover Backpack. The machine fell just from the bottom of the passenger side car to the ground and kind of rolled over a bit on the ground.
I am extremely worried about anything being wrong with my machine, whether it be one of the fans messing up or a RAM issue. I ran AHT (Apple Hardware Diagnostics) and everything was fine. Should I take it in to the Genius Bar and have it looked at?
It may not be anything since the fall was so minisucle (knocks on wood) but any insight from you would be great.
Currently, there are no problems with my rMBP 15" since the minor fall.

Thanks, mende1.
I just get extremely worried when these kinds of things happen and expect the worst. rMBP is still in pristine condition (I got it 2 days ago) but get apprehensive when these types of things happen.
Due to this minor fall, do you think anything would happen internally to the machine? Any insight, good or bad, would be greatly appreciated.

Adobe AIR Runtime Redistribution and Native Installer

Will there be new instructions for Adobe AIR 2.0 Runtime Redistribution? In particular, I'm looking for instructions on how to use the runtime redistribution installer to perform a "side-car installation" of AIR 2 alongside an application that uses the NativeProcess API (and so must be built into a native installer instead of a .air file).
Thanks!

Thirded!
On a test deployment using SCCM and the supplied Adobe AIR Runtime Installer files, we have managed to install our application with the 1.5.3 Air Framework with no major issues other than having to disable the Auto Update feature that doesnt really work in a corporate environment. Everything was absolutely fine until the release of AIR 2. Now, the test machines are prompted to install the updated Adobe Air 2 framework once a week, see an excerpt from an Adobe blog post below:
"In addition, once a week AIR apps check to see if an AIR update is available, and if so, users are presented with the option to update to the most up‐to‐date version, helping to ensure that end users get the benefits of improved security and performance."
That sounds great right? Except my users (like many other corporate users) don't have Admin permissions on their machines (hence the use of SCCM), with the result being resultant error messages when a user attemptes to install the AIR framework update without the necessary permissions.
All of the above would be fine if the Adobe AIR Runtime Installer files were updated to include the latest version of the runtime. This of course hasn't been done yet - does anyone know when this may happen? Can anyone help me with this or offer any advice?
I hope the above makes sense and I would really appreciate any help or advice!
Thanks!

Why does Bridge open raw files (ndg) in Raw window even though the 'Open in Photoshop' option is...

I don't understand why in Bridge there are 2 choices, -1- Open raw and -2- Open in Photoshop and yet both choices give you the same result--The raw window opens with PS below it. After having worked on my raw NEF files I save it to dng. My thinking behind this, is that I alreay have done what was needed and would now like to start working on it within Photoshop. It seems that the only way to automatically open it directly within PS is if I save it as a tiff, psd or jpg. But since this is not what I want to do then why must I add extra steps as opposed to just opening it hwere I want. I mean the 2 choices are there, so why not do what it is being asked?

If I may step in in this discussion, I always use DNG but never have used ACR to achieve this result.
As Curt stated the changes made in ACR to a Raw file (or for that matter a DNG file) are undoable without problems.
My workflow (using Canon CR2 but that is not important, let's say a dSLR generated Raw File) is to use Photodownloader in Bridge (not perfect by far but still the best and easiest way for me).
I connect my CF card using a card reader and let Adobe Photodownloader do the work.
Inhere I use several options:
- convert the CR2 file to a DNG
- back up the original CR2 on a separate disk
- rename the DNG to yyyymmdd (shot date) and sequence number
- add a metadata template for copyright to all the DNG files.
Sorting out the keepers I open the DNG in ACR and either hit Open (for open directly in PS) or use save as Tiff or PSD depending on next step in development or simply hit Done to apply changes and leave it for later use.
The advantage of having both ACR in PS and Bridge is huge. The only difference between both is that by default PS has the Open Button selected and Bridge (open in Camera Raw) has the Done button selected, thats all.
But here is the good part, you can use both simultaneously! For example have PS in film strip mode with multiple files selected and when changes are ready hit Save as start the process but locks up PS itself. Switch to Bridge and use Open in Camera Raw and start with the next job while ACR PS is still running in the background
When I open a DNG in PS using ACR in either PS or Bridge I continue developing with actions and fine tune with layer mask, brush etc etc.
Sometimes use Save As for PSD with the layers still active (huge files) when needing to revisit or not quite ready. But mostly I use an action to flatten the files and save as PSD.
Both DNG and PSD are ending up in my archive, my clients receive whet they want, PSD, Tiff but mostly jpeg and resized.
When having the job finished and every once in a while I clear out the original CR2 files from Back up because in all the years I use DNG (at least 5 years) I never had to use the original CR2 instead of the DNG that is thoroughly backed up as is the original PSD.
But since disk space is cheap you can choose to keep them.
An other option is to include the original raw file in the DNG but I would not recommend that because the file size is getting almost twice as big.
The biggest plus side for me using DNG is that the xmp data is written directly to the file while original CR2 or NEF needs an xmp side car file next to it with this data.
However saving changes to metadata is taking a bit longer to a DNG then to an XMP side car file, depending on system resources and time this never been a real problem for me

Adobe XMP Files not deleted with Raw Files in ACR

I am using Photoshop CS3 on a Windows XP platform. My camera raw files are mostly kept on a Windows 2003 file server, which has a gigabit connection to my workstation. However, I have the same problems when using PS CS3 on my Windows XP laptop.
I take many hundreds of 'technical' photographs using an Olympus E1 and Canon G9 cameras. I usually bracket the exposures on the E1, specially when photographing white painted yachts, and then rate and select the images that I want in ACR 4.1.1. Unwanted images are deleted at this time.
The problem I am having is that the associated *.xmp files are not always deleted with the camera raw files, with the result that I now have literally thousands of these 'orphaned' files cluttering up the server. The only options I have are to delete the files manually, which is a pain, or to leave them on the server, wasting unnecessary space.
I have the same issue with Canon and Nikon raw files, so this problem is not specific to Olympus files.
This is a long standing problem, and I would be grateful if anyone has any answers?
If any Adobe programmers are watching, it would be handy if you could provide a simple utility to delete orphaned *.xmp files, or at least compress them into some kind of archive.
Thanks,
Nigel.

[quote] As far as Photoshop and ACR go, ALL raw files are treated as read-only.
Your original raw files remain untouched, no matter what you do to them.
Any adjustments you make to a raw file are kept only as metadata (flags, if you will) in that XMP side-car file. Every time you want to re-open that raw image file, ACR will reach for the XMP file and apply the adjustments automatically, transparently. [/quote]
That is not quite correct. Camera RAW files can be permanently deleted from within Adobe Camera Raw. The problem with ACR 4.1 to 4.4 4 was that the XMP files were left behind. This now seems to have been rectified in the latest version (ACR 4.5).
Thank you Adobe!

Sidecar Installation on Mac problem?

We have applied for the redistribution license and have all the necessary files ( .exe and .app for pc and mac respectively) to perform a sidecar installation.
We made a hybrid CD using toast on MAC.
This works great on PC but it has some trouble on mac.
The application requires AIR 1.5.3.
If the user has AIR 1.5.3 already installed and our application installs directly bypassing the AIR runtime installation and it works great. Code signing certificate is there and the application is installed with read/write permission for the Admin(me) and all aspects of application works well.
The problem starts if the user does not have AIR runtime installed. The side car installtion first installs AIR runtime environment and then proceeds to install our application which installs without any error but with read/write access to system and not me. In this case certain parts of the application do not work ( these parts read and write data to SQLite Database on local dissk).
I went a step further and added me with read/write permision manually just because it worked in the previous instance as expalined above. Even this did not work. I restarted the computer still it did not work.
I tried to delete system user so that our app has the same permissions as in the first case, but mac does not allow this user to be deleted.
I beleive that beacuse AIR runtime installs first and needs System permissions, even my application gets installed with these same permissions.
Now if I delete my application by dragging it to trash and reinstalll it then it works fine again ( As now Air runtime is already there).
I again checked the permissions and they were same as if AIR runtime was already present, which is true now because when I removed the application and reinsatlled it, it keeps the AIR runtime and deletes only my application.
If using sidecar insatllation my application somehow installs with read/write permission for (me) and no users as "system" the I think it wll work.
I dont know if this is a bug or if there is a solution around this.
Please Help ASAP as we want to go live with this project next week.

Hi Harjeet,
This is what I encountered in my testing.
In the first scenario, both the runtime and application are being installed. The runtime installation requires the process to elevate, you are asked to enter your credentials. This allows the runtime to be installed successfully, but the application is also installed as part of the elevated process, so the final permissions on the application end up with the owner being "root" and the group "wheel".
In the second scenario, where the runtime is already installed, only the AIR application is being installed from the disc. If the user is an Administrator, the application install process is not elevated, you are not asked to enter your credentials. The final ownership permission on the application is the user who performed the install and the group "staff", at least on the Mac OS X 10.6 system I tried this on.
juan

LR 4.4 (and 5.0?) catalog: a problem and some questions

Introductory Remark
After several years of reluctance this March I changed to LR due to its retouching capabilities. Unfortunately – beyond enjoying some really nice features of LR – I keep struggling with several problems, many of which have been covered in this forum. In this thread I describe a problem with a particular LR 4.4 catalog and put some general questions.
A few days ago I upgraded to 5.0. Unfortunately it turned out to produce even slower ’speed’ than 4.4 (discussed – among other places – here: http://forums.adobe.com/message/5454410#5454410), so I rather fell back to the latter, instead of testing the behavior of the 5.0 catalog. Anyway, as far as I understand this upgrade does not include significant new catalog functions, so my problem and questions below may be valid for 5.0, too. Nevertheless, the incompatibility of the new and previous catalogs suggests rewriting of the catalog-related parts of the code. I do not know the resulting potential improvements and/or new bugs in 5.0.
For your information, my PC (running under Windows 7) has a 64-bit Intel Core i7-3770K processor, 16GB RAM, 240 GB SSD, as well as fast and large-capacity HDDs. My monitor has a resolution of 1920x1200.
1. Problem with the catalog
To tell you the truth, I do not understand the potential necessity for using the “File / Optimize Catalog” function. In my view LR should keep the catalog optimized without manual intervention.
Nevertheless, when being faced with the ill-famed slowness of LR, I run this module. In addition, I always switch on the “Catalog Settings / General / Back up catalog” function. The actually set frequency of backing up depends on the circumstances – e.g. the number of RAW (in my case: NEF) files, the size of the catalog file (*.lrcat), and the space available on my SSD. In case of need I delete the oldest backup file to make space for the new one.
Recently I processed 1500 photos, occupying 21 GB. The "Catalog Settings / Metadata / Automatically write changes into XMP" function was switched on. Unfortunately I had to fiddle with the images quite a lot, so after processing roughly half of them the catalog file reached the size of 24 GB. Until this stage there had been no sign of any failure – catalog optimizations had run smoothly and backups had been created regularly, as scheduled.
Once, however, towards the end of generating the next backup, LR sent an error message saying that it had not been able to create the backup file, due to lack of enough space on the SSD. I myself found still 40 GB of empty space, so I re-launched the backup process. The result was the same, but this time I saw a mysterious new (journal?) file with a size of 40 GB… When my third attempt also failed, I had to decide what to do.
Since I needed at least the XMP files with the results of my retouching operations, I simply wanted to save these side-cars into the directory of my original input NEF files on a HDD. Before making this step, I intended to check whether all modifications and adjustments had been stored in the XMP files.
Unfortunately I was not aware of the realistic size of side-cars, associated with a certain volume of usage of the Spot Removal, Grad Filter, and Adjustment Brush functions. But as the time of the last modification of the XMP files (belonging to the recently retouched pictures) seemed perfect, I believed that all my actions had been saved. Although the "Automatically write changes into XMP" seemed to be working, in order to be on the safe side I selected all photos and ran the “Metadata / Save Metadata to File” function of the Library module. After this I copied the XMP files, deleted the corrupted catalog, created a new catalog, and imported the same NEF files together with the side-cars.
When checking the photos, I was shocked: Only the first few hundred XMP files retained all my modifications. Roughly 3 weeks of work was completely lost… From that time on I regularly check the XMP files.
Question 1: Have you collected any similar experience?
2. The catalog-related part of my workflow
Unless I miss an important piece of knowledge, LR catalogs store many data that I do not need in the long run. Having the history of recent retouching activities is useful for me only for a short while, so archiving every little step for a long time with a huge amount of accumulated data would be impossible (and useless) on my SSD. In terms of processing what count for me are the resulting XMP files, so in the long run I keep only them and get rid of the catalog.
Out of the 240 GB of my SSD 110 GB is available for LR. Whenever I have new photos to retouch, I make the following steps:
create a ‘temporary’ catalog on my SSD
import the new pictures from my HDD into this temporary catalog
select all imported pictures in the temporary catalog
use the “File / Export as Catalog” function in order to copy the original NEF files onto the SSD and make them used by the ‘real’ (not temporary) new catalog
use the “File / Open Catalog” function to re-launch LR with the new catalog
switch on the "Automatically write changes into XMP" function of the new catalog
delete the ‘temporary’ catalog to save space on the SSD
retouch the pictures (while keeping and eye on due creation and development of the XMP files)
generate the required output (TIF OR JPG) files
copy the XMP and the output files into the original directory of the input NEF files on the HDD
copy the whole catalog for interim archiving onto the HDD
delete the catalog from the SSD
upon making sure that the XMP files are all fine, delete the archived catalog from the HDD, too
Question 2: If we put aside the issue of keeping the catalog for other purposes then saving each and every retouching steps (which I address below), is there any simpler workflow to produce only the XMP files and save space on the SSD? For example, is it possible to create a new catalog on the SSD with copying the input NEF files into its directory and re-launching LR ‘automatically’, in one step?
Question 3: If this I not the case, is there any third-party application that would ease the execution of the relevant parts of this workflow before and/or after the actual retouching of the pictures?
Question 4: Is it possible to set general parameters for new catalogs? In my experience most settings of the new catalogs (at least the ones that are important for me) are copied from the recently used catalog, except the use of the "Catalog Settings / Metadata / Automatically write changes into XMP" function. This means that I always have to go there to switch it on… Not even a question is raised by LR whether I want to change anything in comparison with the settings of the recently used catalog…
3. Catalog functions missing from my workflow
Unfortunately the above described abandoning of catalogs has at least two serious drawbacks:
I miss the classification features (rating, keywords, collections, etc.) Anyway, these functions would be really meaningful for me only if covering all my existing photos that would require going back to 41k images to classify them. In addition, keeping all the pictures in one catalog would result in an extremely large catalog file, almost surely guaranteeing regular failures. Beyond, due to the speed problem tolerable conditions could be established only by keeping the original NEF files on the SSD, which is out of the question. Generating several ‘partial’ catalogs could somewhat circumvent this trap, but it would require presorting the photos (e.g. by capture time or subject) and by doing this I would lose the essence of having a single catalog, covering all my photos.
Question 5: Is it the right assumption that storing only some parts (e.g. the classification-related data) of catalog files is impossible? My understanding is that either I keep the whole catalog file (with the outdated historical data of all my ‘ancient’ actions) or abandon it.
Question 6: If such ‘cherry-picking’ is facilitated after all: Can you suggest any pragmatic description of the potential (competing) ways of categorizing images efficiently, comparing them along the pros and contras?
I also lose the virtual copies. Anyway, I am confused regarding the actual storage of the retouching-related data of virtual copies. In some websites one can find relatively old posts, stating that the XMP file contains all information about modifying/adjusting both the original photo and its virtual copy/copies. However, when fiddling with a virtual copy I cannot see any change in the size of the associated XMP file. In addition, when I copy the original NEF file and its XMP file, rename them, and import these derivative files, only the retouched original image comes up – I cannot see any virtual copy. This suggests that the XMP file does not contain information on the virtual copy/copies…
For this reason whenever multiple versions seem to be reasonable, I create renamed version(s) of the same NEF+XMP files, import them, and make some changes in their settings. I know, this is far not a sophisticated solution…
Question 7: Where and how the settings of virtual copies are stored?
Question 8: Is it possible to generate separate XMP files for both the originally retouched image and its virtual copy/copies and to make them recognized by LR when importing them into a new catalog?

A part of my problems may be caused by selecting LR for a challenging private project, where image retouching activities result in bigger than average volume of adjustment data. Consequently, the catalog file becomes huge and vulnerable.
While I understand that something has gone wrong for you, causing Lightroom to be slow and unstable, I think you are combining many unrelated ideas into a single concept, and winding up with a mistaken idea. Just because you project is challenging does not mean Lightroom is unsuitable. A bigger than average volume of adjustment data will make the catalog larger (I don't know about "huge"), but I doubt bigger by itself will make the catalog "vulnerable".
The causes of instability and crashes may have NOTHING to do with catalog size. Of course, the cause MAY have everything to do with catalog size. I just don't think you are coming to the right conclusion, as in my experience size of catalog and stability issues are unrelated.
2. I may be wrong, but in my experience the size of the RAW file may significantly blow up the amount of retouching-related data.
Your experience is your experience, and my experience is different. I want to state clearly that you can have pretty big RAW files that have different content and not require significant amounts of retouching. It's not the size of the RAW that determines the amount of touchup, it is the content and the eye of the user. Furthermore, item 2 was related to image size, and now you have changed the meaning of number 2 from image size to the amount of retouching required. So, what is your point? Lots of retouching blows up the amount of retouching data that needs to be stored? Yeah, I agree.
When creating the catalog for the 1500 NEF files (21 GB), the starting size of the catalog file was around 1 GB. This must have included all classification-related information (the meaningful part of which was practically nothing, since I had not used rating, classification, or collections). By the time of the crash half of the files had been processed, so the actual retouching-related data (that should have been converted properly into the XMP files) might be only around 500 MB. Consequently, probably 22.5 GB out of the 24 GB of the catalog file contained historical information
I don't know exactly what you do to touch up your photos, I can't imagine how you come up with the size should be around 500MB. But again, to you this problem is entirely caused by the size of the catalog, and I don't think it is. Now, having said that, some of your problem with slowness may indeed be related to the amount of touch-up that you are doing. Lightroom is known to slow down if you do lots of spot removal and lots of brushing, and then you may be better off doing this type of touch-up in Photoshop. Again, just to be 100% clear, the problem is not "size of catalog", the problem is you are doing so many adjustments on a single photo. You could have a catalog that is just as large, (i.e. that has lots more photos with few adjustments) and I would expect it to run a lot faster than what you are experiencing.
So to sum up, you seem to be implying that slowness and catalog instability are the same issue, and I don't buy it. You seem to be implying that slowness and instability are both caused by the size of the catalog, and I don't buy that either.
Re-reading your original post, you are putting the backups on the SSD, the same disk as the working catalog? This is a very poor practice, you need to put your backups on a different physical disk. That alone might help your space issues on the SSD.

Can I open Adobe Camera Raw from LR?

I use LR 3.4.1 as my image browser but occasionaly would like to edit images using ACR as well as Photoshop. At the moment I have to go to "Edit in Photoshop ..." then switch to ACR via Bridge but would like to go straight to ACR without opening PS or bridge first. Is this possible? I know if open an image from finder it will automatically open in ACR first then PS, then have to import to LR but wondered if there was a shortcut from Lightroom.

I have been evaluating LR as an adjunct to Photoshop (or maybe the other way around!) and was amazed to see that an .nef opened in LR, developed and saved with, I assume, a sidecar, nevertheless does not allow that same file opened in ACR, to access that xml file as at least a choice. I was going to ask why, or how to do it, when I discovered this thread.
The path to doing so is convoluted but doable. Once you open in ACR from the Smart Object file, one needs to copy the settings save them and then when opening another nef in ACR without going to LR, one then loads those settings.
Makes for a big file of short time sidecars, unfortunately.
I assume the reverse is also true: Opening an nef in LR that has an ACR side car, that sidecar is ignored. Hafta try.
Why do I do this, you ask? The UI is far better in ACR than in LR. That bittsy side panel of tweaks is fussy and is similar to DXO in layout. I don't like theirs either. But lightroom does have it's stregths, and that is the data base.
Ok, I opened an nef already possessing a sidecar from ACR and LR did use it. So why not the other way around, or am I missing something?
Lawrence

Can't get LR3 to import photos from one external hard drive to another?

I'm wanting to move thousands of raw photos from a folder in one external hard drive to another folder in a different external hard drive so all my photos are in one photo folder instead of two. I've gone through the importing routine inside of lightroom to move the folder over to the new hard drive. However, the photos don't move because they still show up on the old hard drive and not the new one. What's weird is when I try to import it again, the grid view shows all the photos I'm wanting to import and when I move my cursor over any of the photos they are faded out and it says the photos are already imported. However, if this is true why aren't they showing up in the new folder on my new external hard drive? I know the new external hard drive works fine because I've successfully been putting all my newer photos there since I started using LR about one year ago. The one's I'm trying to move over are older photos I shot try to using LR.
I'm stumped and need some help. Thanks in advance.

You wrote
"Are you saying while I'm in LR just grab the folder I want to move and drop it into the new hard drive"
Yes, that's the way to move photos & folders from within LR.
LR will then update its catalog with the new location and everything should be fine.
Importing is not a good way for moving photos / folders. Since the photos are already in the catalog you had to uncheck <Don't import suspected duplicates> or all the photos will be greyed-out in the import dialog. If you did that LR would import the photos from drive A and put it on drive B. But they would still be on drive A, so you'd have the photos on both drives and would have to delete them on drive A.
But more important: By default LR saves all edits in the catalog, they are not saved with the images themselves. That means by doing an import instead of a drag-and-drop move you'd lose your edits.
You can save your edits to xmp, a side-car file that is stored together with the image file, and the xmps would be imported. But LR does not store everything as xmp. For instance Virtual Copies, Collections, Stacking are saved only in the catalog, so by doing an import you'd lose these things.
Unless you know LR very well, it's best to use the Import Feature only for images that are NOT yet in LR.
And another thing: Before doing major operations like moving big amounts of photos, it's best to backup your catalog first.
WW

When moving a folder between drives in the same catalog I get an error message

Hi everyone,
Lightroom Version: 5.0
Operating System: Mac OS 10.8.4
File Type: Canon RAW CR2
I recently upgraded from LR4 to LR5 and I've found that when I try to move a folder within my catalog but between different drives I get an error message saying that not all the files could be moved. It then refers to the .xmp side car files in the folder. However when I look at the source location the folder is empty yet still there and the destination folder looks like everything has copied over successfully. The files in LR seem to have all the metadata in tact along with ratings and colour labels. So not sure why LR is saying it did not copy over successfully.
Anyone else had this happen? Is there a work around other than moving the files withing Finder and re-importing them using the 'Add'feature?
Any help greatly appreciated as I am looking to move a lot of folders around my catalog in an attempt to organise it more and I would prefer to move these folders within LR but worried this may keep happening.
Thanks, Pete

Great, thanks for letting me know Jim. As I said it did look as if the move had worked but I was just worried by the fact that an error message came up. Guessing this will be fixed in the next update. Is there any regularilty to the updates or are they just done as and when Adobe feel they are needed.
Thanks again, Pete

Side Car

Similar Messages

Maybe you are looking for