Crop not in "New Develop Preset"?

Crop is conspicuously absent from the preset setup. Any reason for this? I'm trying to reduce the number of edit passes I have to make on a series of action shots, and a preset that crops would eliminate a step.

For my purpose it doesnt have to be exact at that point. In gallery mode these subjects are in about the same place in the frame, but are too small to evaluate. It would be nice to apply a mass crop from gallery mode using a preset, so they can be more easily seen. I would then adjust the picks in a later pass. It looks as if any cropping from gallery mode (as well as certain other edit functions) is intentionally designed out of the preset setting dialog.

Similar Messages

Save crop in develop presets

I've been using LR's auto-import feature for tethered capture. It would be extremely helpful to be able to save the current crop (exact location - not just ratio) to a develop preset that I can than set to be applied to all auto-imported images. I am often shooting to fit a specific layout and have to resort to sync and/or previous to get things where I need them to be. Interestingly, I find that sometimes the crop will carry over to new images, but it isn't consistent or predictable.

Add me to the list.
Using the 'original' size for a D300 is not what I want since the frame ratio 1.5056 rather than 1.5. This can cause some confusion later when printing. There should be a way to create a cropping preset or, lacking that capability make the crop ration 'sticky' until it is changed again.

Trouble moving Develop Presets to new Vista machine

I have moved my library from an XP machine to a Vista machine, and am losing a lot of work. What I think is happening is that my images are "detached" from a Preset.
Many of my images have a Develop Preset applied upon import. So the first step in the edit list is Import/XXXX Preset.
I have moved the images and the catalog to the new machine. The preview image looks right, but as soon as I do something to trigger a refresh, the image turns red and loses its rotation. It seems that it is applying all of the steps, except the first one. I am guessing it cannot "find" the preset to reapply it.
I have moved the Presets to the corresponding folder, but b/c Vista renamed somethings, it is not the same path to get to the Preset.
In WinXP:
C:\Documents and settings\UserName\Application Data\Adobe\Lightroom\Develop Presets
In Vista:
C:\Users\UserName\AppData\Roaming\Adobe\Lightroom\Develop Presets
Maybe I will create a folder in Vista with the XP Path name to fake it out?
I can probably go back to my original machine and try some things, but it will be a lot of work. My edits were not saved to XMP, the edits are in teh LR database.
It's not a problem I expect can be solved here, but if anyone has idea, let me know.
Rob.

I know... it is difficult, because there are a lot of variables.
New point (and probably key) -- The ones that I am having trouble with are RAW+JPG and I just realized that in the new installation, even thought both RAW and JPG files are present, the JPGs are being displayed. So the JPGs are getting all of the edit steps that the NEFs should be getting.
I just caught that now, not sure what I will do next.

The "My Mixology" is not Showing up in my Import or Develop Presets of LR3

The "My Mixology" is not Showing up in my import or develop Presets of LR3. Do I have to download this?
Thanks for your assistance.

Hello dj_paige.
Thanks for the reply.
Here is a YouTube video which shows the presets in LR3, which is what I have. At the 1:50 mark you will see in the develop module where he clicks on the Lightroom Presets drop down. In a "LR4" Youtube video which I viewed (I can't find the dern thing!) a group called "My Mixology" was shown under which their were some other presets.
http://www.youtube.com/watch?v=VOdC561kt5I
I am unsure if My Mixology is available only in LR4 or if I can import these or what. I have looked googled for the answer but have been unable to locate it.
Thanks again for your assistance.

I opened a new developer account but shows The item you've requested is not currently available in the U.S. store.

i opened a new developer account but shows The item you've requested is not currently available in the U.S. store.

actually my ios developer account has been approved two days ago, and transfer an app from other account. when i try to enter my user account via iTunes then it shows "Item Not Available, The item you've requested is not currently available in the U.S. store." So what should i do??!!

Generate DDL works in old version of SQL Developer, but not in new versions

Hello all,
How to generate DDL in new versions of Oracle SQL Developer for production Oracle database?
For production database, the generate DDL feature works fine in old versions (version 1.5.5) of Oracle SQL Developer, SQuirrel, Toad and many other similar tools, but not the new versions of Oracle SQL Developer (such as 2.1.1.64.45).
The SQL tab for a table is blank for me in production databases. Of course, it works fine in development Oracle database.
I did some research that many articles describe SELECT_CATALOG_ROLE as the required read-only role in production database. Our DBA did a test to grant me this role temporarily, and it worked for me to generate DDL using new Oracle SQL Developer. It is pain for me to ask for this role.
Is there a plug-in or work-around, so the new versions of Oracle SQL Developer can have this generate DDL feature in production without the mentioned SELECT_CATALOG_ROLE?
I could not find the answer in older forum threads.
For now, I will have to install older versions of Oracle SQL Developer.
Thanks

I've seen a couple posts about people not being able to generate DDL for other users. To date, I've never seen a anybody post a workaround, nor have I seen one of the developers post a response, nor have I seen anybody say they've submitted a SR.
I think I remember reading somewhere that the new version of SQL Developer uses dbms_metadata.get_ddl to generate DDLS, rather than some custom query built on top of catalog views...which could explain why it use to work, but no longer does. But whether or not this is true, I don't know.
You could try submitting a SR and see if Oracle responds saying that it's a known bug and will be fixed in the next release. Until then, unless you get the role, you're stuck using something else for DDL generation.

Can not change vendor when creating a new Development Component in NWDS

Dear friends,
Im trying to create a new Development Component in NWDS. Our NWDS is connected to NWDI and we are using CM Services option of NWDI.
Before I could create a DC and change the vendor but now I cant change it anymore. Now, the vendor is by default sap.com and we cant change it and it seems that we also have to put our project in a separate directory. home/ directory or other directories in the list.
See below screen shots...
If I make a new DC than we see it like this: home/bpm_test [sap.com].
If I make a new DC in my LocalDevelopment I can change the vendor and I dont have to choose a home directory.
Do you have any idea how to change that?
Any help would be greatly appreciated.
Thank you in advance,

HI,
it seems that the vendor is defined in the NWDI track. That's why you can't change it.
regards,
Vasils

Develop presets: "Unavailable Preset"

When I enable the library filter Develop Presets I see three instances of "Unavailable Preset" with counts of 1, 23, and 323. In detail these are
(1) no presets at all, just a Clarity adjust. Click on import, then back on the Clarity --> applies correctly. Then when I refer back to the Develop Presets filter the count has changed from one to zero.
(23) these images all reference a long-used and active preset that is just Clarity + Vibrance. Clicking on the image history shows that the final image is correct, and the before/after preset results are correct. But after cross-checking several images this way the count has now been reduced from 23 to xxxxxxxxxx
(323) these images all reference a preset created today that I accidentally mis-applied to those images. (I'll refer to the mis-applied preset as GOOFY -- more on this below). Sampling some of these 323 images I see that the GOOFY preset is correctly applied. When I click on the previous history step, then GOOFY the "Unavailable Preset" count is decremented and a new "Custom" preset is incremented. I have never seen "Custom" preset before today.
Now, the story of the GOOFY preset. When I could find nothing in the documentation, forum or web, I decided to try disabling the unwanted preset by these steps at the Mac OS Finder level:
- duplicate GOOFY to GOOFY-2
- delete GOOFY file (I hoped LR3 would remove the references to the deleted GOOFY)
- in grid view mass-apply GOOFY-2 to the correct images
- quit, restart LR3
I've forgotten exactly what happened next, but for sure LR3 did not remove the non-existant preset links. For some reason I decided to rename the duplicated GOOFY-2 back to GOOFY. Now the images that correctly referenced GOOFY have two references to presets named GOOFY the oldest one is a NO-OP (does nothing), the latest one works as expected.
Any advice would be appreciated:
** how to mass-delete an unwanted preset reference from a selection of images?
** how to clean up the above "Unavailable Preset" errors?

When a preset is created, it stores the current level of the chosen parameters at the time of creation; in the example below, the preset which will be named CurrentPreset1 will store the current levels applied to the selected photo at the time the preset was created, and in this case will only store values corresponding to Color, Lens Corrections, and Process version.
To update the values recorded in a preset, the various levels must be changed on the currently selected photo and then the "Update with current settings" must be selected on the preset to update. The "Update with current settings" therefore updates the preset itself with new values corresponding to the values set in the current photo and has nothing to do with how it was applied to photos in the past. A preset is not related in any way to photos on which it is applied; a preset simply applies the set values recorded in the preset on the selected photo as if these same values would be manually entered for the selected photo.

Develop presets ordered in a directory like structure

If you are having a ton of develop presets you have to do extensive scrolling in order to find the proper presets.
Moving to LR4 I wish to have an directory like structure for the presets.
This makes even more sense because the new 2012 versions treats presets (not all but some) different than the "old" 2010 Version.
I can't imaging there will be something like a preset upgrade in the official version.
Having the mentioned structure it would be possible creating new presets under this structure and it would be easyly to differntiate the version.
e.g
2012-version
     --- wedding
     --------high contrast
     --------low contrast
     --------sepia
     -------------foobar1
   -------------foobar2
     --- nature
2010-version
     --- wedding
     --------high contrast
     --------low contrast
     --------sepia
     -------------foobar1
   -------------foobar2
     --- nature

As it may not make the final release, and we wouldn't want the request to get lost in beta land, might I suggest adding it as a suggestion on the Feature Request forum http://feedback.photoshop.com/photoshop_family where it can easily be tracked? In fact, if you search over there, I think you'll find a similar request to add your vote to.

Where does LR3 install develop presets?

I ask this question because, on my system, the answer is not obvious:
I have 8 catalogs. Everyone of them is configured to store presets within the catalog. When I examine the contents of the presets folders (different for every catalog) I find that only 1 catalog out of the 8 contains any items in its Develop Presets folder (other than the folder 'User Presets') and these develop presets appear to be the default ones that are shipped and installed with the product. However, all 8 of the catalogs list these default develop presets under the group 'Lightroom Presets' in the left hand panel in Develop mode.
The 'global' lightroom develop presets location, at ~user\AppData\Roaming\Adobe\Lightroom\Develop Presets\Lightroom Presets is empty. However the parent folder (Develop Presets) does contain folders for the 3 volumes of the free OnOne PerfectPresets as well as a User Presets folder (not empty). But, those OnOne presets are available only in 1 of the 8 catalogs, and not the same catalog as that referred to above.
How do catalogs, which do not have the Lightroom default develop presets present, find them?
Why can't catalogs find the free OnOne presets which are installed at the architected system (or global) location or any of the User Presets at this location?
Finally, I do have a 'spare' Lightroom Settings folder which does not appear to be connected to any catalog: when I rename it to a garbage name I can find no immediate problem in any of my 8 catalogs. Is it safe to delete this spare Lightroom Settings folder?

XEyedBear wrote:
I have 8 catalogs. Everyone of them is configured to store presets within the catalog.
This is where I think you are misunderstanding how the "Store presets with catalog" option works. For a start, you cannot configure an individual catalog to use this option.....it is a global Lightroom preference which applies to any and every catalog on that specific system. Once you have slected that option, the effect is that Lightroom will create a "Lightroom Settings" folder in the same folder as the catalog.....so if you have 8 catalogs, and they're all in their own individual folder, you'll eventually end up with 8 x "Lightroom Settings" folders. Keep all 8 catalogs (and preview sub-folders) in the one folder, and you'll get away with just one "Lightroom Settings" folder.
A couple of other things to understand about this option:
1. On initial creation, the "Lightroom Settings" folder contains only a subset of the main settings folders contained at the default user appdata location....and all the sub-folders are initially empty. Lightroom does NOT copy any presets (Lightroom's own or your User Presets) to the equivalent sub-folder in "Lightroom Settings".
2. Furthermore, from the second that you select that option, Lightroom will no longer look at the default location for any User Presets that you had.....so the immediate effect is that the User Presets 'disappear' from the Develop Module (they haven't really been deleted, it's just that Lightroom no longer sees them).
3. When you create a new User Preset after setting that option, it will be stored in the appropriate sub-folder within the "Lightroom Settings" which is specific to the catalog in use at the time, but would not be copied to any other "Lightroom Settings" folders. Easy in that circumstance to end up with each catalog having different user presets available to it, and easy to see maybe why the OnOne presets are only available to one catalog.
4. And not all Lightroom settings are 'switched' to the "Lightroom Settings" folder, some remain in the default location.
To be honest, unless you have a really good reason to store different presets with different catalogs, I think you're making a big mistake in selecting the 'Store Presets with catalog' option in your multiple catalog situation. I did a write-up on this subject not so long ago for the folks over at Victoria's Lightroom Forums, you might find it worth a read:
http://www.lightroomforums.net/showthread.php?14169-What-is-the-purpose-of-the-quot-Store- Presets-with-Catalog-quot-option
Hope this helps....

LR3/LR4 Develop Presets Behavior

I'm a little bit confused about LR3 Develop Presets that do not include the Process Version information when applied to an image that is in PV2012. Let's assume a Develop Preset for Clarity +25. Here are the steps and the results:
1. Image PV2012 - apply Preset - Clarity slider stays on 0 and it looks like Clarity has not been applied to the image
2. Change image to PV2010 in Camera Calibration - Clarity slider changes to +25 - Clarity is applied
3. Change image back to PV2012 - Clarity slider stays at +25 and the rest of the new PV2012 settings are applied as well
So, is this the correct behavior? Shouldn't the Preset alrady be applied in step 1 ?
What am I missing here?
If the Preset contains the PV information everyhting works "as designed" with the sliderers reverting back to PV2010 if applied to a PV2012 image.
Is the lesson here to always include PV information into any Develop Preset?
Andre

I can follow you technically. But from a user perspectice this is getting difficult to manage. How do I know which preset will work and which doesn't? Right now it seems, its trial and error. And if I switch between PV versions the setting will be applied but it won't be the same because Clarity2012 is different. Don't get me wrong, it is absolutely fine to improve image processing, but it would be nice to make these changes more obvious to the end-user who might not be so technically inclined. I could think of a little warning saying: You're trying to apply a preset setting that does not work in PV2012, or something along this line. It would be even nicer if Adobe would provide something like an Preset upgrade utility, which would help users to migrate to the new PV.
I just try to figure this out so that I know what to tell my students at the community college where I'm teaching LR and where I'll be facing these same questions.

Develop presets

Can anyone share their develop presets for a Canon 5D mk II in LR 4?

I'm not sure if it's still the same deal, but I had "joined" the X-Rite site and was able to download the Passport software for free. Then if you happen to have a new or like new 24 patch Color Checker chart you could essentially do the same thing as having the Passport chart, except it's not as portable or durable.
On a side note, I have made numerous Camera Cals with the Passport software from both charts, shooting the chart in daylight, strobe, tungsten or mixed whatever. The strobe/daylight (direct sun) versions have similar characteristics (I use one as a general import for that camera body). If you get into shade it will probably be best to make another. And you can make dual Cals from mixed lighting, which is best to make custom for each scene, due to the narrow spectrum sources. If you have several cameras, also make custom Cals for each.
Of course all this hinges on having a good display with good calibration and profiling. There's no sense fighting the color with a poor and/or uncalibrated display.
Ciao,
John

Develop presets gone after installing LR 1.0

Hi all,
Having a small issue here. I upgraded to 1.0 30 day trial - and all the Adobe develop presets have disappeared. Right now I have absolutely no presets. How can I get these back? I am on a Mac by the way.
I have tried to uninstall LR but can not figure out how to do it.
Regards,
PhotoJ

You didn't read the documentation, it's made clear there.
New location
~/Library/Application Support/Adobe/Lightroom/Develop Presets
from
~/Library/Application Support/Adobe Lightroom/Develop Presets
where ~ is your user folder

Develop presets: after preset "updated" what happens to all existing references?

Testing the develop preset "Update with current settings" I've noticed that the existing images referencing the updated preset do not change. If you click the associated history steps before/after then the image updates.
Is this "correct" or is this a bug? If it is correct, what is the point of "Update with current settings"?
Related question: what happens to images referencing a preset that one deletes in the preset pane?

When a preset is created, it stores the current level of the chosen parameters at the time of creation; in the example below, the preset which will be named CurrentPreset1 will store the current levels applied to the selected photo at the time the preset was created, and in this case will only store values corresponding to Color, Lens Corrections, and Process version.
To update the values recorded in a preset, the various levels must be changed on the currently selected photo and then the "Update with current settings" must be selected on the preset to update. The "Update with current settings" therefore updates the preset itself with new values corresponding to the values set in the current photo and has nothing to do with how it was applied to photos in the past. A preset is not related in any way to photos on which it is applied; a preset simply applies the set values recorded in the preset on the selected photo as if these same values would be manually entered for the selected photo.

Develop Preset for Import in LR4.2 (iMac 10.8.2)

Can any please tell me how to set up a preset on the Import page (there are some there now) that I can use when I import my photos into LR. I am tired of going to Lens Correction in the Develop mod to put the nikon lens in that I used for the shoot. It is always turned off and I would like to have it activated when I import my shots. I know that while in the Develop mod, I can change it for one photo and then use "sync" to have it address all the other photos. But then it is a pain in the butt. There must be a way of doing it on import and that is the reason I am asking for your help. Either that or else have it recognize the lens that I used automatically.
Thanks for taking the time to respond.
Tunney
Tunney Moriarty
Ph: Res 519-746-0236
Cell 519 584-5253

Hi Tunney,
I would second JimHess: of course you could employ a develop preset during Import, but then all images would be labelled as having develop adjustments. And you do not see where you have invested develop work already.
I consider the Adobe defaults just as a starting suggestion, which may or may not apply to my taste per camera.
So I would rather tweak the default develop settings: just make sure that you include only stuff that virtually applies to ALL of your images.
I, too, have included automatic lens correction and defringe edges.
First decide in your catalog settings if you want the develop defaults specific per camera type or serial number or even ISO ( a nightmare if you ever use auto-ISO).
Then select a sample image, goto develop module and set only the stuff that should apply to all imported images. Then save them as new default settings.
You do nit change anything during import then.
If you hit the Reset button it will always revert to these defaults.
Cornelia

Crop not in "New Develop Preset"?

Similar Messages

Maybe you are looking for