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.

Similar Messages

Develop Module and Preset Application

I would love a way to apply my general adjustments to a copy of a photo and reset all adjustment sliders so I can then consistantly apply a Develop Preset. I have a large number of develop presets that provide me with particular "looks" I use a lot, but these are not "relative" to the global adjustments made correcting the original photo, i.e. exposure, brightness, contrast, etc. If my photo has these global adjustments made to it and then I apply a preset, it never looks the same as the previous photo I used that preset with. Even if I make a virtual copy the original slider adjustments are maintained rather than reseting them to a neutral starting point. Right now, I export my photo as a PSD file to PS and immediately close it and then apply my develop preset to the PSD file to get consistant results. This is the same reason why people have to develop RAW and JPG presets, which is double the work.

Not sure if you found a solution or an efficient way to "export" your photo to psd (seems like you "edit in photoshop" and just save) but you could build an Export preset with these options
     same folder as original
     check "add to this catalog"
     existing file = choose a new name for the exported file
     filename = custom text + filename (to end up with something like COPY_originalname.psd)
     file settings / format = PSD or TIFF
     rest leave empty (or as per your preference)
If you have a large number of files to export, you can go for a coffee (or a full lunch) while it exports. Then you can apply your develop presets to the new image.
Additionnally you can create a smart collection with filter = filename starts with your custom text (i.e. "COPY_" in the example) to access your copies quickly
Hope this helps

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.

Relative Adjustments in Develop Module and Presets...

Hi there,
the new Lightroom 4 beta is great and has some really good improvements inside (e.g. the "new" shadows/highlight or the new possibilities in the adjustment brush).
But what I really miss is the possibility to make relative adjustments in the Develop Module. Primary this is useful in presets to make steps of correction. I can do very limited relative adjustments for single parameters partially in the Library Module, but it goes not far enough and I can not save any preset from that or even combinations of adjustments.
An Example:
I have an image which is nearly perfect. All adjustments are almost done. Now, I want to give the image a +10 in Clarity or -3 in Brightness relative to all current adjustments. Those relative adjustments are perfectly to increase or decrease simple adjustments stepwise, but also really helpful for stepwise bringing in or out more complex adjustments.
Another Example:
I have an image with no corrections. No I can push Clarity, Shadows/Highlights, Saturation etc. from a preset which brings in more and more of a complex set of adjustments, which are just right for this type of image.
I think, a small checkbox behind a slider would be perfect to set relative or absolute adjustments. This settings should be saved within a preset to make some/all adjustments relative to the exisiting ones, or - if deactivated - absolute adjustment, like in the current version of Lightroom.
What do you think about that? It would be great to see that in future betas or the final Lightroom 4 product.

If they've been discussed at length, I'm surprised not to see them. Much has been provided that I would have guessed has received less requests.
And while I understand that Adobe might simply want feedback on what they have provided, what would be the best forum for letting them know what we feel has not yet been provided.

Printing Presets unavailable?

There seems to be some presets missing from my print dialogue when in Photoshop.
In the print dialogue for the printer (that shows up after Photoshop's print dialogue) I expand the dialogue to show the presets. The drop down menu that includes "layout" "paper handling" "cover page" "scheduler" also includes an option "hp deskjet PDE" that is crossed out. Choosing this option produces the following message:
The bundle "hp deskjet PDE" could not be loaded because it does not contain a version for the current architecture.
Contact the bundle's creator listed here for the latest version.
hp deskjet PDE v2.7.1
As far as I've seen, this only happens in Photoshop. I've tried printing with preview, and iphoto and they both display a full set of presets for this printer.
The computer I'm working with is new and I just discovered this problem. So it's not a case of "it worked before and it doesn't now."
I'm a little confused as to where to go from here. Any help is appreciated, thank you!

Your are running a PPC version of PhotoShop. You need a UB version of the HP Printer driver. Or the other way around. Somehow you did not get the full sent of drivers pre-installed from Apple. Two choices: Upgrade to 10.5.4 and then use the new HP Drivers posted on Apple Software Updates. Or download the UB driver from HP web site.

Logic presets unavailable

Hello
So recently I was at a 1 to 1 appointment and was expeirementing with the strings presets in logic 9 (staccato, vabrato, etc)
But when I went on my own computer the presets were not available or even located in my files or in logic.
I was wondering if that is a preset or sample pack i must purchase or if it is an update to logic.
Ps. I use the version of logic that was available in March of 2012. I have not updated it

Hi
Did you download all the additional content via the Logic Pro menu?
CCT

[IDS CS2] How can I load printer presets & pdf presets

To create compliant artwork, for different media we use predefined printer and pdf presets, in InDesign.
My question is simple, in InDesign you can load these preset files via a load function in the menu, is there a similar function to load these presets into InDesign server?
Or do I have to something like the example printpreferences script for InDesign server, setting all properties manually.
Erik Bruinsma

Whow, if I had only know before...
I think I wasted a whole day, trying all kinds of complex scripts, while it could be done in two lines :-(
I almost had a working solution with Dirk's tip, but this is way easier.
Thanx

Adobe PDF Preset: Save Presets

I'm trying to locate where this data is kept for this preset. I want to save PDF files on several machines with the same PDF preset settings. I will do this manually if there is no other way.

These are actually .joboption files.Try setting one up as you want in the PDF options panel of the Save dialog and give it a name. It should be saved to HD>Users>yourname>Library>Application Support>Adobe>Adobe PDF>Settings. Try looking there. You can then put copies of the preset in the same place on any computer you want to use the same preset.

Brush presets / tool presets - confusion

I'm by no means a beginner (I think this I'm in my 15th year using Photoshop..), but something that's always bugged me is the difference between brush presets and tool presets. It's never been much of an issue in the past, but I'm spending an increasing amount of my workflow drawing digitally using various brushes, and I'm finding these two different ways to save and import brushes quite confusing. If I've altered a brush, and want to save it, what are the advantages / disatvantages of saving it as a tool preset, or as a brush?
I have my favourite pencils saved as tool presets, which works fine, but I don't see what the brush presets do that is different from this. Is there a 'right way' to organise / save brushes? What's actually the difference between the 2 things? Are they totally interchangeable?

So going by what you said, that means the Tool Presets store tool specific settings (flow, opacity etc), as well as the brushes themselves. Is that correct?
Brush Presets (see Brush Preset Panel, not just the Brush Panel) can be used by all painting Tools. Tool Presets refer to a specific Tool but can indeed hold a Brush tip that has been removed from the Brush Presets.

New capture preset/Easy preset for 12-bit camcorder audio

I just got a bunch of camcorder tapes to edit in FCP 6. I've read on the internet all about the 12-bit /32 kHz audio issue. Most of the solutions seem to involve importing the clips via iMovie, and then exporting with 16-bit / 48 kHz settings. This adds an extra step to the workflow and time is money. Plus, it seems a bit odd that FCP can't import 12-bit / 32 kHz video directly. I know that FCP is a professional program and the documentation implies that 12-bit /32 kHz isn't professional quality but since most camcorders are set to 12-bit / 32 kHZ as a default and people don't know how or didn't know to change the setting to 16-bit / 48 kHz, it seems like FCP would include this ability.
I've posted a screen capture of the capture preset window here http://www.macgeoffster.com/files/easypresetscreen.jpg
Does anyone know why FCP doesn't have an option for 12-bit / 32 kHz?
Does anyone know how to get 12-bit audio as an option in the capture/easy preset screen?
If I choose 16-bit / 32 kHz (the closest option) what will that do to the audio?
Thanks in advance!

macgeoffster wrote:
This adds an extra step to the workflow and time is money. Plus, it seems a bit odd that FCP can't import 12-bit / 32 kHz video directly. I know that FCP is a professional program and the documentation implies that 12-bit /32 kHz isn't professional quality but since most camcorders are set to 12-bit / 32 kHZ as a default and people don't know how or didn't know to change the setting to 16-bit / 48 kHz, it seems like FCP would include this ability.
Well time IS money in the professional arena, but a camcorder doesn't belong there, neither does an operator who doesn't know how to change this setting or the necessity of doing so.

Using imovie cannot change to av capture session preset photo preset

Using the iMovie app when we try to take video for the movie, pushing the start movie button stops the app.

I have the same exact camera and the same issue. It is very disheartening to me that there does not appear to be a working solution posted for this issue...what gives? JVC promotes this camera as tailor made for FCP and Apple even sells it for that purpose on their site. Yet no one can tell us how to get the files from the card into FCP? I am attempting this via a card reader that appears on the desktop but the files are never ever recognized - AHHHH! I was soooo hoping that my transition from Premiere Pro to FCP would be smooth, I researched all my options, bought what I thought was the ideal camera and here I sit once again spending time on discussion boards instead of getting work done. Great!

Bridge CS4 does not see ACR presets in Develop Settings

I think that this is new with CS4. I create a Preset in ACR in the Preset Panel. That Preset works fine on photos in ACR. The Preset is listed in the Camera Raw Settings folder in the Finder.
But, when I try to apply the Preset in Bridge via Edit > Develop Settings, the Preset does not appear. Is this correct? I believe that a preset did appear in CS3 in Bridge Develop Settings.
The preset was created with a Raw file from the 1DS MkIII. Could it be camera-related?
Am I missing something here?
Thanks,
Sonny

Strange. I Quit Bridge. Relaunched Bridge, and the Presets now appear in the Develop Settings list.
I presume that I should not have to Quit and relaunch for the presets to appear?
I created another preset. It only appeared in Develop Settings when I again quit and relaunched Bridge, even though it appears in the Camera Raw Settings folder.
Sonny

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....

Develop presets have different effects after saving file as either .tif or .psd

When I open a raw .dng file in Photoshop and MAKE NO CHANGES and then save it (either .tif or .psd), the resulting photo appears to be identical to the original raw .dng file. HOWEVER when I then apply development presets (whether my own or Lightroom presets), the presets have a COMPLETELY DIFFERENT effect on the .tif or .psd file than the .dng file. More precisely: the .tif or .psd files have significantly more contrast, saturation and are significantly more exposed. And in fact, despite using the exact same preset, the histograms for each of the pics are different. In addition, the same preset on the .dng file treats colors differently than on the .tif or .psd file. After much experimenting and comparing of each development module and each individual slider, the sliders that seem to behave differently are Brightness, Contrast and Saturation. With each of these sliders, however, the difference in effect is only minimal and should not affect hue, but when applying a preset that affects hue, the actual change in hue is different for the .dng file vs the .tif. or .psd file. All of this even though all of the presets are the same. Whatsmore, applying Auto Tone on the two apparently identical files results in dramatically different affects: the .tif or .psd file is properly corrected, whereas the .dng file has its Brightness decreased and Contrast increased, i.e. the Auto Tone moves the sliders different for the .dng file than for the .tif or .psd file. Is there a solution to this problem?

I'm one of those who eventually migrated from PS to LR. I used to do a layered TIFF for every selected image. With 17-21MP raw files, that amounted to usually between 180-250MB files in addition to the raw. After completely changing my approach, for 99% of my work now I only work from the raw file, including printing / generating web JPEGS. This was really enabled by having the spotting and local editing at the raw file level. But pretty much no more TIFFs as working / final images, just raws with settings. Obviously different people have different requirements, but it's well worth looking into the switch in approach, even if you still end up using PS / Bridge / ACR.

Standardise definition & selection method for ALL third party plugin presets!!!

Over at LogicProHelp there is a very useful topic relating to Logic presets - in which many users have spent time saving individual third party plugin settings as LOGIC presets... which is enormously helpful when selecting instruments etc because they can be selected using a keystroke etc and found within the Logic Library browser window - which is of course searchable!
These presets have then been uploaded to the forum for others to download.
http://www.logicprohelp.com/viewtopic.php?p=367267#367267
I posted on the topic recently and thought it worth mentioning over here on the Apple forum.
Here's what I said - does anyone agree/disagree? Is this something that Apple should work on? For me it's a no brainer but I'd like to know what others think....
"MO 3rd party instruments that rely on mouse-clicks or anything more than one button press to change a preset are incredibly badly designed. It's massively frustrating and impedes creative flow to have to use a mouse, or press several keyboard buttons just to move from one sound to another. Native Instruments interfaces are amongst the worst offenders - you even have to MANUALLY specify what presets you want to use with specific MIDI Program Change messages - because the latter are the only way I know of using anything other than the NI interface to change sounds in their plugins.
The Logic Channel Strip settings saved along with 3rd party Plugin settings saved as Logic Presets have proved a recent revelation for me.
Now I can change instrument presets using a keystroke, a midi message, almost anything I want.
And then there's the Logic Library browser - now that so many sounds are saved as Logic Presets, the Logic browser window has become really powerful - being able to search my entire library for "bass" or a particular instrument name - REGARDLESS of which third party plugin is required to play the sound - IT JUST LOADS AND PLAYS!
Maybe I'm in the minority but I think of a sound I want first, NOT which instrument I should load and then browse through - the latter is kind of backwards for me.
I really think that we users should pressure Apple and plugin developers to provide Logic (and indeed other DAWs) presets with ALL of their products because the amount of effort on their part is minimal compared with countless end-users doing this task manually over and over. The current situation is ridiculous.
DAWs are incredibly powerful these days but the lack of a plugin preset/sound library definition standard is quite crippling to work flow.
I mean if there were a STANDARD LIBRARY DEFINITION such as with Native Instrument libraries or Apple loops where sounds are defined universally and supplied as such in a common preset it would revolutionise sound discovery/selection within DAWs.
Kind of like a document management system that applies to ALL plugins, by ALL developers and the installer for a plugin would then add all its presets to the management system/common library"

Sid Merrett wrote:
Can you give me an example of a plugin that doesn't work with the Logic save preset function?
Sure, I could give you lists of plugins for each of those particular scenarios I addressed.
In that specific case, for one example, Spectrasonics instruments for a few years did not support the hosts' save/recall settings function (at least in Logic), and when contacting them and asking why Stylus RMX could not recall settings saved via Logic's preset system I was given the explanation that it wasn't supported for technical reasons.Basically, it only save/recalled a small handful of settings, the rest were lost, meaning it was impossible for quite some time to use the Logic's save/load settings feature to save user presets, you had to use the plugin's own internal save features. (Yes, the instrument's state was saved in the song, but *wasn't* able to be saved via the preset handling, for technical reasons).
A year or so later, and later Logic versions, they finally got round to making it work as the varioous parts of the host and instruments were upgraded to handle larger data requirements. Spectrasonics instruments are examples of instruments with very specific, custom browser features, many of which you lose if you save data using Logic's functionality - not to mention the effort of saving, naming and organising 8000+ patches per instrument. Plus you have many levels of data - you often load a loop into a part, and a part into a group of parts, and they are different types of data. The hosts save/load feature only saves the state of the plugin - it can't be used to load Loop 14 into part 2, for example. It's the whole plugin, or nothing. More workarounds in terms of how you organise your loading/saving of different types of data.
There are other instruments too, and ones I've beta tested where I've got into the technical details and had to have the preset format changed or simplified because hosts had difficulties storing the data correctly. It's quite a complex thing, in the main, and different instruments implentation of preset handling mean that the whole thing is full of workarounds, compromises, or plain failure to use the feature completely.
Other instruments, such as Minimonsta, lose functionality when saving via the host - for example, you only get the meta patches and patch morphing functions when saving via the plugin's own file format, and that stuff doesn't happen when saving via the host.
I could go on and on about this - every develop has different requirements and they mostly all either do it very basically and rely on the host, or bypass the hosts save/load functionality and implement their own which they can be in control of and that will work across hosts and across platforms. For instance, there is little point having a beautifully organised Oddity library if all those sounds are now unavailable to me if I choose to work in Live...
That's why the whole preset thing is a complicated mess and isn't liable to be sorted soon.
There is a developer over on the PC trying to make a system to unify this stuff between plugins - it's PC only right now, and I forget the details this second, but it's acknowledgement that people recognise this whole thing is a mess and looking at ways to improve the situation.
Sid Merrett wrote:
I hadn't spotted that - thanks. You can't use the Logic Library window to search for Plugin Settings, only Channel Strip Settings.
You *can* use it to search for plugin presets, but only within the context of a single plugin. Ie, if I select the ES2, I can see, and search, the ES2 plugin settings. But often I want "a bass sound", I don't necessarily know that I was an "ES2 bass sound", or a "Minimonsta bass sound" or whatever.
The point being, I just want a sound that will work, and I don't know where it will come from. Forcing me to choose and instrument first can be counter productive. How many times have you needed a sound, and you go "Ok, there might be something in pluginX that'll work?" - you load up pluginX, flip through the sounds, don't find anything useful, then go "Ok, let's try pluginY", no... pluginZ etc etc
I miss Soundiver in many ways. *Ideally*, I'd like one central method of storing my presets which will work cross-plugin, cross-host, cross-format and cross-platform that is a standard that all developers and hosts support, and that offers the main core features that developers need, from simple, single patches with names, up to full meta data, cataloging, organising, author and notes tagging and so on. You can still give the users a choice to use the individual plugin and individual plugin's gui for patch selection, but you can get far more standardised if you want, with the advantages that gives - and you don't have to export patches into the system, as it's developer supported, all presets for your instruments would be instantly available in the library, just as they are in the instrument directly.
But it's difficult to get developers to agree on much, these days - the most likely thing to happen is someone somewhere creates a cross-platform standard for this that gains momentum and that developers and hosts want, or *need* to support.

Develop presets: "Unavailable Preset"

Similar Messages

Maybe you are looking for