Feature Request - If a Save to PSD fails because of image size, offer to Save to PSB

Feature request — If a save to a PSD aborts when the file size grows beyond 2 GB, offer to save the file as a PSB instead of just displaying an error message and quitting.  Better yet, if the image is to big to begin with, make the offer before starting the save operation.  Similarly, if an image is too large to save to TIFF, offer to save it as a PSD or PSB.
When you’re working on large files, it would be nice not to have to redo a Save as a Save As to PSB after several minutes delay.
BTW, I tried without success to post this at the feedback site.  Once again, a dialog opened asking for a verification code that would be sent to me by e-mail, which in past attempts has never arrived.

Not a bad idea, though really what would be even better is if other 3rd parties would embrace the PSB format so we could just use PSB for everything and leave PSD behind.  There's almost no difference in size.  Here's the same file saved in both formats:
C:\TEMP>dir egb.ps*
Volume in drive C is C - NoelC4 SSD
Volume Serial Number is 00ED-C11E
Directory of C:\TEMP
06/30/2012  01:04 PM         1,411,420 EGB.psb
06/30/2012  12:14 AM         1,397,248 EGB.psd
In my case, I don't send PSDs to anyone, they just represent archives of my master work, and I will always have a modern version of Photoshop to read them with.  So if I could I would just use PSB for all master files.  Problem is, two 3rd party tools I like to use don't currently handle it:
IrfanView
FastPictureViewer Codec Pack
Probably some day in the future they'll work.  I encourage you to write to the people whose tools you'd like to see be able to read PSB to implement support.
See also this thread:  http://forums.adobe.com/message/4393244
-Noel

Similar Messages

  • Clipboard export failed because the image is too wide to save as a PICT

    Am I the only one who keeps getting this message in a new window,
    "Clipboard export failed because the image is too wide to save as a PICT"
    while working in Photoshop?
    I know little about a PICT file, except that it's some kind of file.
    Seems to pop up out of nowhere after I've been doing some copy/pasting.
    The really annoying part: it never shows up while I'm still working in PS,
    it's only after I click onto a folder or start working in another application.
    THEN the message won't let me do anything with the folder or application,
    but instead returns me to the PS screen for a few more seconds, then fades out.
    It's only after the fade-out that I can click on a folder or use
    another application.
    I have plenty of RAM (50%) and backup drive space assigned to PS, and
    again, this does not happen while still in a PS screen. Using Cache Level 6.

    While I haven't seen that particular message, I have had the "clipboard is too large to export" message. What you need to do is go to the Photoshop preferences and tell it to NOT export the clipboard. You should be able to find it the General section of preferences, just UNcheck the box in front of "Export Clipboard"--of course, if you copy something in Photoshop that you want to paste into another program, you'll have to re-check it. But bear in mind the limits of Clipboard.
    Francine
    Francine
    Schwieder

  • Save Image size setting in Save for Web

    I'm using Save for Web (CS3) and scaling the file to different sizes with "scale image". I'm wanting to use the same scale settings for many images but when I save the pre-set the image size settings don't get saved. I'm wanting to use it as part of an action but the setting wont stick. Any suggestions? Alternative work flows?

    That's never been saved as part of the S4W presets. Bloody annoying.

  • Image size change when save as jpeg

    Hi
    I have recently encountered an issue when I save file as jpeg in CS6. I prepared my image for printing and my image is a bit smaller than the print size (20" x 40") so I created a new file (8 bit) with new exact print size. Then I placed my image into this newly created layer and adjust my image size to fit. After this, I flatterned the image and went to file>save as and picked JPG extension. Dialogue box appeared and I selected 10 for quality (scale 1-12) then I hit ok to save. After that I went to open the newly saved JPG file and check the file size and for somereasons, It has been halved to around 10"x20". However, pixle dimension of the image remained unchange because I have unticked resample option. Does anyone have any ideas of why this is the case as It's doing my head in.
    Thanks
    Dean

    This has been discussed ad nauseam here.  Please do a forum search.  < sigh >
    Bottom line:  If the pixel count remains the same, your image has not been "reduced or halved" at all.  Just change the ppi resolution accordingly without resampling.
    Save for Web defaults to 72 ppi regardless of what you had specified earlier,´.

  • Why is Save to Web greatly increasing my image size?

    Hi!  I am starting with a 6 inch by 6 inch 600 pixel TIFF image.  When I use Save to Web to create a JPEG, it decreases pixels to 72 which is what I want--but the image size of the new file shows as like 20 inches by 20 inches.  I know that the original is untouched.  Should I be ignoring the image size here?  Here is my concern.  I want the viewer to see the complete image.  Is Save to Web truly jumping up the image size here?  If I email myself the image---I do see the whole picture.  I am concerned that the new file says 20 inches by 20 inches.  Will a recipient be receiving a 20 inch by 20 inch file that might not be viewable on their screen.  Hope this makes sense--confusing to me!  I have read a few websites that say when using Save to Web just focus on the pixels--not on the image size.  Why is image size showing as much bigger than original?  Thanks!!!

    SaveForWeb is just removing the resolution value (600), and the image loads at the default (72).
    Web browsers don't care about resolution, just the number of pixels - which remains the same.

  • Feature Request: Photo Borders and Copying in Books

    These are a few related feature requests. If anyone knows of a better way to do this with the current software, then I would love to hear it.
    When making books I like to have borders around the pictures of various colors (usually black or white) and various widths. In Apeture this is a pain to do. I fiqured out that I could fake it by making a picture box and inserting a solid black picture into it and then creating a smaller picture box in front of it for my real photo. This might be tolerable if I could at least then select both picture boxes and their contents to copy and then onto other pages as a template that I can resize as needed.
    Ideally I would love to be able to copy and paste multiple elements on a book page and I would like to be able to define photo borders. Any chance of seeing this in the near future?
    Thanks,
    Sean

    Thanks for the reply. You are right, the cut and paste works fine, it just didn't work the way I expected it to. Maybe that is a GUI design thing to consider. I was actually trying to click and drag a selection box like you might do in iPhoto to select multiple images that are right beside each other. This doesn't work at all in Aperture, but your method does work just fine.
    I agree with the other poster that some additional features like:
    Photo Borders
    Export to PSD (with layers)
    Custom page sizes and Custom themes
    would be very nice and start to make that tool truley useful.
    Thanks for a really nice product. Keep up the good work and stay ahead of the pack.
    Sean

  • Version 1.2.0.2998 (Windows XP) "Save As" feature request

    The "Save As" dialog does not remember the last directory saved to, nor can I find a way to customize the three Location buttons (Project, Home, Work) or add any additional Locations.
    If I save a package body as "R:\foo.pkb", the next time I "Save As" from the same window, it reverts to saving in my home directory (C:\Documents and Settings\username" with a ".sql" extension.

    As stated in the Feature Requests sticky post, requests go to the Exchange.
    There you will find various requests about this already; vote and add comments on them.
    Regards,
    K.

  • Feature Request:  Auto-save in Background

    Here's a feature request I've submitted.  If you agree, please submit your request to:
    http://www.adobe.com/go/wish/
    *******Enhancement / FMR*********
    Brief title for your desired feature:
    Background Auto Save
    How would you like the feature to work?
    Auto-save would work just as it does today, except it would work as a background process, as it already does in Photoshop (without the Autosave popup getting in the way of the edit).
    Why is this feature important to you?
    The current autosave feature is terrifice and expected in any application today, but the current autosave popup dialog is useless.  It only has a "Cancel" button.  What's the point?  I can't imagine when I would ever want to cancel an auto-save.  And let's say I *did* want to cancel.  The dialog is only on screen for a second or so.  That's not enough time for user interaction, but it is just enough time for my work to be interupted, and for me to potentially hit the enter key as I go to Render something at precisely the same time.

    Hi cscouper2013,
    Thanks for taking the time to point out that my BSODs might be a problem with my RAM!  Yes, I'll test it with the program you mention.
    cscooper2013 wrote:
    While I'm thinking of it, too.  Sometimes Premiere will do an auto save only moments after I've done a hard save.  That also seems like something to address in the next auto save feature update.  If I have my autosave increment set to 5 minutes, then it seems to me there's no need to do an autosave for another 5 minutes after my last manual save.
    I fully agree!  That's something I requested during the CS5 beta program.  I requested that every time a user does a manual save, the Autosave reset its counter.  So for example, if the delay is 10 minutes between auto saves, and the user does a manual save two minutes before the next scheduled autosave, the autosave counter resets to 10 more minutes.  But with the better solution of the current project constantly being saved after each edit, as Jim suggested, this feature wouldn't even be needed anymore.
    MonkeyEatsMonkey wrote:If Premiere could "borrow" that functionality, while still retaining a "save as" option for versioning, I feel like we'd have the best of both worlds.  It would even make dynamic linking more seamless, since changes wouldn't require saving. Any thoughts from the community on this?
    That would be a perfect solution IMO!  And yes, retaining the 'Save As' option would be very important!
    I also like the idea of automatic versioning/backups (could be renamed to 'versions' since with a constantly saved project file, automatic 'backups' would no longer be necessary.
    To resume, based on what has been discussed in this thread, I believe these would be the ideal saving options in Premiere:
    Autosaving of every edit in the background without slowing down editing performance (as suggested by Jim).
    Ability to create a user defined number of automatic backup versions, by setting maximum number of versions and time intervals (as is currently the case with Premiere).
    In other words, the current project file would constantly be updated as the user edits.  The automatic backups/versions would be created at user defined intervals.
    Users would retain the ability to create a copy of the current project at any moment through the 'Save As' and 'Save a Copy' commands that already exist in Premiere.
    Pop-up Auto-save dialogue boxes and the 'Save' command would be a thing of the past!
    IMO, this would truly give us the best of both words as MonkeyEastMonkey suggests: constant saving as per FCPX, with the comprehensive versioning options Premiere currently offers.
    Anything missing?

  • (feature request) Save bookmarks

    I've been using sqld to do some pl/sql development recently and it is great. A feature that would make it even better would be the ability to save bookmarks. If I have a package nicely bookmarked it's great....until I shutdown sqld. At which point all my bookmarks are lost. This essentially makes bookmarking useless. I'm not going to bother setting up bookmarks if they're going to be lost every time I shutdown.

    I like the idea. Please post over at http://sqldeveloper.oracle.com under feature requests so that people can vote on it.
    Regards,
    Eric

  • Feature Request? Need to be able to see save progress in fullscreen.

    Absolutely loving the new background saves in PS6! It's changed a lot of my workflow for the better.
    One thing I don't like, and this might be an oversight on my part, but the two save progress indicators are not visible in either fullscreen mode. And I always work in fullscreen mode.
    A very common thing for me to do is to save my PSD and then immediately save as a matching tiff (after every time I complete a change). Because I can't see the save progress I see the error message about not being able to save as when the file is saving. And then I end up waiting longer than necessary before trying again.
    And while I'm at it for fullscreen notes; I'd really like too see the delay when exposing pallets and tools by mousing to the screen edge removed. I don't know why it's there, but it makes me crazy. The one second clunk as it shows the little bar and then does the animated slide every time feels like a stall in my thinking. Go to the edge *and* clunk comes the bar *and* swoosh comes the panel *and* then get back to work…
    I know it's a small thing, but there you go.
    Thanks Adobe! A great piece of software otherwise!

    This made me think as I was working:
    That point where I see that error — it's one of the most common things I do with my day and I've never been able to automate it. I'd love to have an option or method that takes less steps.
    The thing I usually need is a matching, flattened tiff with all my working PSD files (the "print" file).
    As things currently stand I save my PSD and then do a save as, switch the file type to tiff, hit okay (usually hit rreplace), then hit "discard and save a copy" and hit okay (least number of steps I've ever come up with).
    This is something I've done literally thousands of times, every day, day after day. I'd love to have it save automatically, or run an action, or something.
    And I've never been able to engineer an action to handle it, the replace and filename issues just make it too unwieldy.
    Sorry for getting in on this whole beta process so late, but there you go…
    Thanks again!

  • Feature request: auto-save timer reset

    The auto save timer currently runs continuously: every n minutes, it auto-saves if the project has changed. It should auto-save n minutes after the last save whether auto or not. That is, any save action should reset the countdown timer. Also, auto-save shouldn't start while a manual save action is in progress.

    There is a better way.
    http://forums.adobe.com/thread/1369232?tstart=0

  • + Camera Raw Feature Requests +

    UPDATE:
    We're interested in what changes you would like see in our products. Do you have an idea for a feature that would help your workflow? Is there a small change that could be made to make your life a little easier? Let us know!  Share an Idea, Ask a Question or Report a Problem and get feedback from the Product Development Team and other passionate users on the Photoshop Family product Feedback Site on Photoshop.com.
    In future it would helpful if you could use this thread as a means to add
    "Features" that you would like to see in future releases of Adobe Camera Raw.
    Please do NOT create additional new Topics and try not to duplicate requests by other users. Also, be thorough in your description of the feature and why you think Adobe should consider it.
    Oh, and if you find it necessary to comment on someone's feature request/suggestion, try not to get into a shouting match. The penalty for doing so is...
    b If you're asking that a particular camera is supported in a future release or just taking the opportunity to carp that yours isn't then please do so in another thread!
    IanLyons
    Forum Host

    Here's my wishlist for ACR. I'll list the feature first and then in a separate section afterwards, I'll explain why I want it.
    1) Shadow/Highlights
    2) Multi-instance and modeless behavior for ACR so I can truly have ACR open, Bridge open, PS open and work in all three and even open another ACR window.
    3) The ability to open one image into PS and keep the rest going in ACR when you have multiple images open in ACR.
    4) The point locator feature for curves like curves has in PS so you can find out what tone area on the curve a given area in the photo is, just by clicking/dragging over an area on the photo.
    5) White balance assist to make it easier to get skin tones right when there are no good grayscale references in the photo.
    6) An ACR pref to have a suffix automatically added to each filename when it goes into PS so after editing it in PS, I can just hit Ctrl-S and not have to manually add a suffix onto every single image I edit in CS.
    7) A drag/drop bin for recently used saved settings in ACR and shortcut keys for cycling through a preview of those settings (described in more detail below).
    8) A pref to allow the Save Images folder in the Save dialog in ACR to default to the directory of the RAW files rather than the last directory used.
    9) More sophisticated sharpening in ACR (like smart sharpening).
    10) Ability to set label or rating when only one image open in ACR.
    11) Ability to delete and close when only one image open in ACR.
    12) An easier way to see how a rotated image looks. There is no way in ACR to see the straight version of an image you've rotated slightly.
    13) Shortcut keys to cycle through saved curve settings.
    Here's the explanation for why I want each of these:
    1) Shadow/Highlights. A significant percentage of my images need no other adjustments in PS except shadow/highlights and it's a big workflow savings to be able to finish a picture in ACR instead of having to take it into PS.
    2) Multi-instance and modeless. The CS2 behavior is better than it was before because you can set it up for Bridge to host ACR and still be able to use PS. But, I often open many images in ACR and the current design still forces me to serially finish all those images in ACR before I do anything else becuase I'm blocked from going back to either Bridge or PS (depending upon who's hosting ACR) and I can't open any other images in ACR. This forces a serial workflow when sometimes I'd like to be able to be in the middle of one workflow (a hundred images open in ACR), but go do something else in Bridge and PS for a short period of time. I can't do that today.
    3) The ability to open one image from ACR into PS while keeping the other images in ACR. When I see the preview in ACR, this is often the first time I've seen my images at any decent size. I often find I want to take a few into PS just to see how well they fix up with certain changes or to see if they benefit from things I can do in PS and can't in ACR, without discarding all the other images I have in ACR at the time. So, again, I am forced to serially finish all the image I have in ACR before I can take any into PS. I'd like to be able to open the selected images in PS and keep the others in ACR.
    4) The point locator feature that PS has in the curves dialog is very valuable for finding out where on the curve a given feature in the photo is. I'd like that feature in the PS curves.
    5) White balance assist for skin tones. One of the hardest things in ACR is getting the white balance right for skin tones when there is no easy gray reference in the photo. I don't know how it would work (I think this is an area for your invention and cleverness), but I'd like some sort of white balance assist that helps me pick a white balance that leads to a pleasing skin tone. I'd be willing to tell ACR where the skin tone is by pointing at it.
    6) I add a suffix of "-edited" to ALL images that I open in PS from ACR. That means I have to type that suffix on every image when I hit the Save command in PS. I'd like a preference in ACR to automatically append a suffix onto the filename when it goes into PS to save me that typing on every single image. I've even tried to figure out if I could write a script in PS to do this for me (if file extension is a RAW file extension when user hits save, then add default suffix to the filename before Save dialog comes up), but I haven't figured out whether it can be done via script or not. I know that others save their PSD or JPEG files to a different directory than their RAW files (I keep all of mine in the same directory so this isn't an issue for me), so I imagine they'd like the ability to specify a default relative path also to save having to point every PSD they save in PS to a new directory.
    7) Drag/drop bin for RAW settings. In a workflow of processing 200-800 RAW files, I'd like the ability to easily and temporarily save a small number of RAW file settings (10 would do). I know you can do it in the pull right menu in ACR today, but that's too much typing and clicks to make it worth it. I'm looking for something that allows me to pick a bunch of files from a shoot, identify a representative "sunny" shot and drop it's settings into a bin that I quickly label sunny. Then, when other sunny shots come up, rather than having to scroll around to find that image or go back to bridge to find that image, I just drag it out of the bin an drop it on the selected images. I don't want it to persist globally because then they pile up and I have to clean them up. I do need them to persist between ACR sessions as long as Bridge or PS is still running because I often process my RAW files in many ACR sessions. The whole point is to make an easy place for me to deposit a small number of saved settings so I can easily (very few mouse clicks or keystores) use them again while processing the same shoot. It's all about speeding up the workflow and letting me re-use work I've done earlier in the workflow. In my experience, this happens most often for white balance and curves since I'm more likely to tweak exposure on nearly every shot anyway.
    8) When I hit Save Images in ACR, it remembers the previously set directory. In my workflow, I want it to default to the directory of the first image I'm saving. The way it is now, it is NEVER the right directory so I always have to change it. It could be smart enough so my normal workflow never has to change it. Even better, I'd get to set a pref that was a relative path from where the first image is located. So, when I'm saving JPEGs, I could have a default path of ./JPEG (a sub-directory under where the RAW files are located). Other people would want ../JPEG (a sub-directory at the same level as where the RAW files are stored).
    9) In the spirit of getting as much of my work done in ACR as possible, I'd like to see a unification of the sharpening functionality so that ACR can do smart sharpening with all the same features. That would again keep many of my images out of PS and drastically improve my workflow.
    10) I'd like the ability to set a label or rating when there's only one image open in ACR. Because you can do this when you have multiple images open in ACR, I'm programmed to set this in ACR, but that workflow programming is busted when I only have one image open.
    11) I'd like the ability to delete an image from ACR when there's only one image open in ACR. Just like with labels and ratings described above, I'm programmed to want to delete a ruined image when I see it up close in ACR and determine it's no good. In this case, I think I'd like to just hit the trash can icon and have the ACR window close and have the image deleted in one single step.
    12) When I straighten an image in ACR, there's no good way to see how the rotated version looks at full size. All you get to see is a thumb in ACR (if you have multiple images open) or a thumb in Bridge. To see whether it rea

  • Feature Request:- Option to reply to reply to emails in text

    Hi there....
    Is it possible to set up replying to emails to send text (with no html)
    If not, can i get a feature request to send emails in text, or is there an app that has this feature?
    It is sad I get maybe between 40 and 100 emails a day, that I cannot reply to on my Touchpad, or Pre 2, as they only allow text email return.
    as of 2007, there were over 109 million yahoo group members across 8.8 million groups. Mostly support forums, sending and recieving emails to and from 109 million people.
    These support forums and other ghelp yahoo groups, require emails to be received in text, and in our email apps had to set for text only, to avoid viruses and other attempts at marketting.
    I get my yahoo support emails, on webos, but cannot reply from webos, and have to wait until i get to my laptop with thunderbird.
    please can you add text send/reply option for those 109 million plus yahoo group users who cannot reply to yahoo groups emails.
    thanks....
    this is a major pain and must be for others.
    ta
    Ralph :-)
    Sorry for typos
    Post relates to: Pre 2 p102ueu (Unlocked EU)

    Managing layered PSD files in Aperture
    For those who absolutely must manage layered PSD files in Aperture, here is the way to do it...
    1- In your original PSD file, HIDE ALL LAYERS above the background layer
    2- IMPORT this PSD file into Aperture
    3- CREATE A VERSION in Aperture by choosing to edit externally in Photoshop.
    4- Back in Photoshop OPEN THE ORIGINAL PSD file along with the new version
    5- LINK all the LAYERS in the original PSD file and DRAG them TO the new VERSION (holding the shift key down so they pin register)
    6- SAVE the new version in Photoshop
    7- Back in Aperture your version is now an exact layered copy of your original which will not flatten when reopened from Aperture into Photoshop.
    Obviously this process will be rather tedious if you need to deal with hundreds of layered PSD files, but if you are in that situation that implies you already have a workflow and a storage strategy that works well for you. So why change, especially to Aperture?
    Adobe Bridge or Media Pro or Portfolio are the obvious programs for you !
    Dual 2ghz G5   Mac OS X (10.4.3)  

  • My traditional feature requests

    Once more, with feeling and four-part harmony....
    1. Tools that operate on pixel opacity instead of RGB. Many times I wish to clean stray pixels in a layer, and the workarounds are annoying. I want to select by opacity (with all the selection tools), and be able to manipulate a layer's opacity info with a Levels-like tool. Doing things with interim alpha channels is very time-consuming and introduces many opportunities for error.
    2. Save As option to recall the last Saved As folder and format, for each open file that was Saved As during the current session. I keep source PSDs in one folder tree, and output TGAs in another. And Save As, every time, takes me to the folder the PSD lives in. I don't mind that the first time, but every time, that makes for a lot of renavigating the folder tree in the dialogue. The Recent Files link is ineffective, because I have destination folders that share a naming convention (so there are lots of "sourceimages" folders, with no context as to which is which), and because I see often that certain recent files just don't make it into the list, for one reason or another. I continue to pray for this.
    3. When saving a PSD to an alpha-supporting format, a dialogue to choose which alpha channel I wish to use. Right now, if you have more than one alpha channel, you get none of them, but instead get a pure opaque alpha channel.
    4. When you Save As to an alpha-supporting format, please look at the image and make an assumption about 24- or 32-bits based on the image. Current behavior is to use whatever the setting was the last time you Saved As to that format. If there is no alpha channel present, assume 24-bit and default the dialogue to that. If there is an alpha channel present, assume 32-bit and default the dialogue to that (and offer me a list as to which alpha to use, per request #3). I often embiggen images that could be 3-bytes per pixel and are now 4, or I blow away the much-desired alpha channel, because the dialogue uses whatever the last setting was.
    5. I'd like a more interactive Offset filter, similar to the arbitrary canvas rotation that we have now (yay to that, of course). I offset the image within the canvas window, work on it, and hit Esc to have the image invert the Offset. This would make doing tileable textures much easier.
    6. Also in-line with doing tileable textures, I'd like layer styles to act as if edge pixels repeat infinitely off the edge of the canvas. If you have a horizontal line in your image that has a drop shadow, the drop shadow shows artifacts of the lack of extension of your layer data off the canvas. The workaround is to put off-canvas info there by sliding the layer over, painting in some pixels, and then sliding it back. But this then screws up things like your ability to Offset that layer if you need to. A general behavior like I describe would make life much easier if you use layer styles in images intended to tile.
    7. Temporary brush palette. Many times, I hack together a quick brush for one tool, and would like to apply it to another tool without the hassle of creating a preset. If there were a "six last manipulated brushes" palette (that did not include size change as one of the changed parameters), then I could easily apply one temp brush to another tool.
    8. Global brush size option, and lack of required size specification in brush presets. Brush size is something I change all the time, and is not something I really care about when saving a preset. And when I'm working on something, and flip back and forth between, say, eraser and brush, I'm generally working at one specific scale. I'd like an option to have all brush-style tools (stamp, brush, pencil, etc) all just use one size value, whatever the current size value is. When that option is set, the size specification in brush presets would be ignored.
    9. Editable presets. Right now, you have to load the preset, change some aspect of it, save a new preset, and delete the old one. Let me just resave the existing one. Like the old days.
    10. A new one! I'd like Image Size and Canvas Size to not automatically use my default unit type (which is pixels). I most often do percent adjustments with those panels. If there could be a preference for those panels that would stick, session to session, that would be nice. I don't know if that's too picky: I just find, especially with Canvas Size, that I'm always changing that value to percent. I haven't found any issue with any other feature using my global choice of units, just those two. I have no idea if anyone else finds themselves working this way.

    If I quickly set up a scattering, size-jittering, dual-brush freakout, and it's on the brush tool, there's no fast way to move it to the eraser. I have to create a preset, and then select that preset when the eraser tool is active. That's not nearly fast enough for my tastes. And it makes very particular, very temporary brushes on an equal footing as my permanent brushes.
    I'd love a scratchpad on the toolbar of the last 6 brush definitions (or last N, really). So when I create my freakout brush, it enters itself there, bumping the oldest one off the list. When I switch to my eraser, I can select that brush, and have all of those behaviors on my eraser. As part of my painting technique, I switch between painting and erasing constantly, and I often need both tools to have the same behavior.
    I would exempt size or hardness changing from creating an entry on that palette, as I change those all the time, and tweak them all the time, and it would very quickly result in losing brushes that have real variation in them, and result in a palette of nigh-identical brushes mildly tweaked in some minor, pedestrian way.

  • LR3 Feature Request - Heal Preset/Import Capability and Stuck Pixels

    (Note: I posted something similar some time ago but the original thread seems to be inaccessible although a cached Google version is available here. )
    2 features requests but with a common theme :-
    1) Spot removal/cloning/healing added to a preset. Currently the only way to do this is to copy and synchronise during an editing session of photos that have already been imported.  The capability to save spot removal as a preset would be very useful for dealing with recurring dust spots and similar issues.
    Which leads to request 2 -
    2)  The ability to manually 'tune' the hot pixel removal capability. Currently LR is failing to deal with some stuck/hot pixels on one of my cameras (a Ricoh GRD III) if this is linked to the way DNG has been implemented in the Ricoh, as suggested in the earlier thread re this subject, then a response from Adobe to confirm this would be appreciated, either way some ability to 'tell' LR what to do would be of benefit.

    Thanks for the response Rob, saving a 'target' image is a good idea, but other than that I don't see this workaround as being particularly different from the approach I outlined in my initial post. One of the most useful capabilities LR has is being able to apply presets during import, yet Adobe for whatever reason have not allowed any of the tools (other than graduated filters) to be applied this way, I would love to know why. There was a 'bug' with LR 1 if I remember correctly whereby spot settings could be saved to a preset, but this was 'fixed' in a later release, so it appears to be possible to implement this functionality, yet they have decided not to do so.

Maybe you are looking for