Feature Request: Exporting to Photoshop at gamma 1.0 and 32bit resolution

Hi,
In terms of maximum fidelity, it'd be nice if Lightroom had a setting to tell it to hand of copies of photos to Photoshop at gamma 1.0 or Lightroom's native profile (which is apparently also based on gamma 1.0), and 32bit resolution, so that maximum fidelity is guaranteed. I feel the current settings are restrictive, and while I can retroactively change the edited image to gamma 1.0, I'm exporting a 16bit image from LR to Photoshop. Depending on how creative someone goes on the sliders and tone curve, eventual color banding may happen when converting between color profiles.
Thanks for considering,
-mg

Interesting responses everybody. I do think LR is a good program as I have been using the beta as well as Aperture and comparing the two. Extensis Portfolio , although not a "developing" program from the beginning had no size limitation in its cataloging. It extracted(or created) a thumbnail, generated jpg previews and automatically updated changes to files each time the program was started. In contextual menus you could export a copy, open in PS, and various other commands right out of the program without hogging memory. Nobody has offered an educated reason for the size limitation. Can it not manage memory ? Ok, maybe not, but that doesn't mean it couldn't at least catalog the large files. If this is the case , my suggestion would be to implement a "lock out" feature that would not let you "develop" large files in LR but could still generate and update thumbnails and allow you to organize them within your filing system. Then you could at least manage versions and changes within LR with out having to switch to Bridge or the like. Making JPG versions is not a good workaround.. to assume people only have a "few" large files to keep track is very one-dimensional thinking. I personally know of several mural photographers that work exclusively with digital cameras/backs , are they not considered a valued target market for LR ?

Similar Messages

  • Feature Request: Export catalog for 2nd editor/machine

    Since there isn't a shared network environment for LR, to involve multiple editors or multiple locations for the same editor on large projects, I often need to export a subset of a catalog so someone else can work on it, or I can work on it off my laptop somewhere other than the studio, using only the proxy 1:1 previews to make my decisions from and then re-assimilate those edit changes to the master catalog of that job, usually back on my primary workstation.  This process also allows me to start processing out parts of the job while other parts are being edited on other machines, or letting my primary workstation process while I use a 2nd workstation to continue editing at speed on.
    I can make this happen, but it's all on me to remember which portions of the catalog have been exported, where their destination was/is, remember not to make any changes to that portion of the library while the subsection has been exported, and an over-lengthy and complicated merging of exported and internal catalogs.
    It would be incredibly useful if LR could show the status (checked out for primary edit, checked out for client approval, etc.) of any exported catalog by mousing over that visibly different section and build in a preference for those varied conditions to potentially limit any changes to that subset of images while the export is still 'checked-out.'  A true merge would be nice to allow possible overlaps of work on the same images, but a managed lock-out would be sufficient to start with.
    As it is, the re-assimilation process for me involves removing images from the master catalog leaving the raw files in place, and re-importing the exported catalog which also necessitates the needless redundancy of bringing the 1:1 previews back in as well.  At the scale I'm doing this it's overly time consuming, compared to the speed of just bringing in the library itself.  The process also puts me in the place of deleting images from a catalog while they're essentially still in use, which is scary from a file management standpoint, usually with me having 4 and 5 copies of that library lingering around until all the manual merging actions are finished.

    That's a feature I've asked for myself Brad, in the absense of true network use.  As it's not likely to 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?  If you post the link to your request here, others can also vote on your request.

  • Feature Request: Export and Import all or part of vCenter configuration from the GUI

    One of the challenges we face is how to recover a large vCenter to a different VM, without having to restore any databases or use vCenter VMs and databases on replicated storage. We currently have a PowerCLI based process for exporting vCenter configurations - vCenter settings, roles/privs, alarm definitions, datacenters/clusters/hosts - to an XML file, which can then be used to import that vCenter configuration into a recovery vCenter. Three part process - export the vCenter configuration, import the settings and structure (datacenters, clusters, alarms), then import the hosts. This last step pulls in the hosts once by one from the original vCenter, complete with their running VMs and once all hosts in a cluster are imported creates the required Resource Pools and moves the VMs in to them. A subsequent script moves all the VMs into appropriate blue folders based on their CMDB classification/OS.
    The above process is OK, but has a number of faults:
    It's all or nothing for a migration, unless there is some serious editing of the XML dump to extract, for example, a specific datacenter or cluster, which could if incorrectly done result in configuration issues, hosts not being imported, etc.
    It can't (at least not in vc4.x) migrate dvSwitches. If we have those in a datacenter, we're going to have to reconfigure the hosts and VMs back onto conventional vSwitches
    We'd really like to see a native tool built in to vSphere Client or the Web Client that will allow all or part of a vCenter configuration to be exported to an XML or other flat file and then imported into another vCenter in one easy step, taking running VMs, dvSwitches - the lot. In the same way you can export host and vCenter logs with a few clicks, it should be possible to do something similar for vCenter configurations. This would be useful for a number of things - vCenter recovery, vCenter upgrade, individual datacenter or cluster migration.

    I got the answer: http://forum.java.sun.com/thread.jspa?threadID=577129

  • Feature request - export strokes

    With the new open in Illustrator feature (which is excellent) it would be much more useful to have the strokes to refine rather than outlines. This would give so much more control when refining an illustration

    P_werner, I'm curious...  Are you actually sensing a significant amount of time to do a Copy/Paste?
    What kind of computer do you have?  What size images do you work on?
    Your description surprised me because it's been a long time since I've sensed any delay with this operation,even with big operations.  I just copied / pasted large chunks of a 21600 x 7200 pixel image and honesty I could barely sense the time between Control C, Control V, and the layer showing up.  And yes, I have the export preference checked.
    I tend to use high-end computers, but my workstation is no screamer by today's standards.
    -Noel

  • Feature Request: Export Clipboard

    Currently, I keep "Export Clipboard" off because almost all of my Copy & Paste actions happen exclusively inside of Photoshop and having the option active slows down Copy & Paste actions. However, on the rare occasion that I do want to paste content into another application, I have to go to preferences, enable "Export Clipboard", perform the copy operation, paste inside the other application, go back to my Photoshop preferences and turn "Export Clipboard" off again.
    As a solution, I propose that a simple "Export Clipboard" or "Copy to Clipboard and Export" item be added to the edit menu when the "Export Clipboard" option is disabled in Preferences to make that whole workflow quite a bit easier, faster and far less annoying.

    P_werner, I'm curious...  Are you actually sensing a significant amount of time to do a Copy/Paste?
    What kind of computer do you have?  What size images do you work on?
    Your description surprised me because it's been a long time since I've sensed any delay with this operation,even with big operations.  I just copied / pasted large chunks of a 21600 x 7200 pixel image and honesty I could barely sense the time between Control C, Control V, and the layer showing up.  And yes, I have the export preference checked.
    I tend to use high-end computers, but my workstation is no screamer by today's standards.
    -Noel

  • Feature Request  - Export Available Preview.

    Let's assume you have a library built from many separate Hard Drives, (my library is on a separate small 500g HD) and your heading out on location (cottage/holiday) for a few days and you'd like to do a rough edit of some project, it would be nice to be able to export the 1:1 previews (they are already there in the previews file) to work with.
    Just me?

    +1 vote.
    In the mean time, I use PreviewExporter for this purpose.

  • Feature request - Export Draw files from Creative Cloud to Illustrator

    It's really annoying that you can't export Draw files from assets.adobe.com to Illustrator CC, that you have to do this from your iPad. If my battery is flat, or I have left my iPad somewhere I can only export REALLY crappy low res jpgs or pngs. Coupled with the recent issues the Send to Illustrator function has suffered it's annoying that work is being locked up in this way. I understand that it's important for Adobe to protect their products, but these restrictions are making workflows really hard work. It would be ideal if we could access the mobile files using the Place tool in inDesign etc too so we could drop a drawing file in to a document in the same way we can a regular image or ai/psd file

    This is a bug. Will update this thread once it is fixed.

  • Feature Request : Export (3rd Option)

    When I re-export from a catalogue I am working on, sometimes I am exporting images I have exported before.
    So . . . Lightroom asks me: Do you want to
    a. Overwrite exixting files or
    B. Create unique filenames.
    . . . which, BTW -in my humble opinion, is flawed anyway since the unique filenames do not appear in the file listing anywhere near their companion.
    Example: Img008 does not get a uniquely named copy like Img008-b, but instead gets something like copy-Img008 - which does not allow for quick side-by-side comparisons in an image browser.
    (SO: Unique filename option should be fixed!)
    But there should also be a third option: (the real reason I write)
    C. Ignore duplicates (Do not overwrite or create new file when there is already an existing file.) This will save my computer lots of processing time trying to re-export over existing files.
    Now for arguments sake, you could tell me just to not select the pre-existing exported files when I export, but in my particular case, that would involved nearly as much brain power as not doing it consumes computer time, since I have already exported selected non-sequential files for my first export, and I'll be damned if I can remember which ones they were until the export "expert" tells me which files are about to be duplicated.
    -Mike

    It keeps the password. Whatever issues you are having are the exception, not the rule. However, without any system info, nobody can really help. Start by reviewing these steps:
    Sign in or activation errors
    And since you are in a corporate environment, definitely talk to IT and have them release the necessary network ports and grant sufficient user privileges to make this stuff stick...
    Mylenium

  • Feature Request: 1. Clarify metadata updating in Guide, and 2. make errors visible.

    A couple things would help immensely:
    1. Clarify metadata schema/version updating in the guide, and
    2. make errors visible - as it stands, these flash by so fast they are unreadable. I've a feeling there's some useful information in them thats going straight to bit bucket instead of eyes/brain.
    Rob

    One thing thats confusing in the guide is the example update function is provided, yet 'noAutoUpdate' is not provided.
    I thought if no-auto-update is nil, then the update function would not be called. Is this just a whoops in the doc, or is there something I'm missing? i.e. is it possible to use auto-updating in conjunction with the manual update function? Say if item versions are changing but not the schema version?
    What is the purpose of noAutoUpdate if the mere presence or absence of an update function would do the same thing? I'm starting to think it must be possible to have auto update and manual update concurrently, but if so - how would that work? auto-update runs first, then manual? Or, maybe auto-update (only) runs if no schema change but item version changes, and manual update runs (only) if schema changed. Or maybe auto runs first to handle item version changes, then manual runs to do the schema update - I'm getting confused again.
    Also, if previousSchemaVersion is nil, will the update function still be called? If so, then one had better check for it or no first-time users will ever be able to install the plugin, since update func would "error out" when comparing nil to a number. Actually, it may be that update function errors dont hurt in this case - my previous problem was errors that I think kept the update function from being called at all - which made it impossible to enable the plugin.
    PS - I miss the days when Eric Scouten would at least occasionally respond on the SDK forum.
    Where in the world is Chet Drarvik?

  • Multiple Imperative Feature Requests

    I am a MN Photographer and have been using PS Lightroom through 2 betas and 2 release versions. I have been amazed at the improvements Adobe has added, but from my point of view, they need to add a few more features to make LR more robust and efficient!
    I love the way LR makes terrific web galleries!
    I am running LR from a Seagate Barracuda 300 External Hard Drive with Firewire connection. I am using a Mac Powerbook (1GHz Processor) with 60GB HD and 55% free, w/ 2GB DRAM, and an Apple Cinema Display. I can't complain about slow downs, but keep my permissions tuned once a week, both on the Mac PB and all EHDs.
    LIGHTROOM FEATURE REQUESTS
    1. From the Web module, there is only one option for adding Copyright Info to images in the Web Galleries, either ON or OFF. It would be a great addition to have this option variable by type size, type placement on images, and opacity. I last generated a web gallery and some of the images said, "2007 Alex Bachnick All Rights Reserved," but many of the images said, "Alex Bachnick All Rights Reserved," without a year. A few images said, "Copyright 2007 Alex Bachnick All Rights Reserved," like it is supposed to! The LR application has been inconsistent so far in this area. By adding a line of copy that can be saved, and by varying the opacity and placement on images would be a huge step forward!
    2. It is IMPERATIVE that you embed metadata into the Web gallery images. This is primarily for adding keywords and copyright information, but LR is inconsistent so far. Sometimes metadata is preserved, but it doesn't always get embedded when exporting images.
    3. When I generated a Flash Web Gallery, some of the color was good, some of it was terrible. I have suggested before that you write into the action that takes the original image, reduces it in size, then convert to profile from Prophoto to sRGB. I suspect that you have a script in there "Save for Web". This script is denigrating the color when Convert to Profile would preserve the color. Admittedly Safari is the primary web browser I use, and it's color-centric, whereas most of the others IE, Netscape, and Mozilla, aren't.
    4. When I use HTML for the web galleries, the color is spot on, but a young friend told me it would be better to hit one button to go through the images as in a rapidly advancing slide show, rather than hitting each image, and then wait for it to enlarge. This could be another marked improvement, if you made the output a slideshow from the Web Module.
    5. I tried generating a slideshow from the Lightroom menu, and had about 200 images in a collection. The application went through the motions, but I tried opening the slideshow but it didn't work. I tried it in PDF format and it output a 135MB file that ADobe Acrobat couldn't open. It is still not working. I have also used a third party application Photo to Movie (www.LQGraphics.com). This is a $50 application that you can add music to and vary the zooms and dissolves and this works incredibly well!!!
    6. One of my biggest problems so far is the sort mechanism. I have about 9500 images in my library, and about 5% of those were made from about 2004 and on. My images are sorted by "capture time," but the images shot back in CY 2004--2005 are mixed in somewhere way down in the pile. There are some bugs in the program for reading the capture time, and so far this is not working accurately!
    7. From the Lightroom Library module, several times I have exported images for 3rd party needs and the application puts out varying results. In March I output some images for Communication Arts magazine. They specified file size and format, and it took me several times to export the images to their specifications. I recently exported some images for submission to a UK based stock photography agent. The images came from 5 different cameras~~Hasselblad w/ Imacon Digital Back, Kodak DCS-14, Canon 1ds MkII, and Canon D-20. There were 10 images that needed to be output as JPEGs (

    1. LR uses what was written in the copyright field so it's your data entry that is inconsistent.
    2. Are you 100% certain this is not working reliably under 1.1? It definitely wasn't working at all under 1.0 and Adobe responded to complaints. Since 1.1, I've taken large numbers of Web-generated pictures into iView and not found any cases where the metadata was missing. "Sometimes" is too vague. How exactly can you prove it? What programs prove it?
    3. Not sure, but isn't this a problem because of Flash? Also the browser you use is not important - it's the browser that your visitor uses that you need to focus on.
    4. Realistically, Flash is better for this. You can always get someone to write/modify HTML templates to do such a slideshow, but the built-in templates are already very complex and this suggestion would add another layer of browser incompatibility.
    7. This isn't a feature request. Raise this in the main forum - and be specific (your post was also too long and got truncated). How can anyone help you if you say "varying results"? It's unlikely that any variation is random.
    John

  • Feature Request: Color code lightroom folders

    I have several hundred folders inside of lightroom. I would like to colorcode "favorite" folders to make them easier to find when moving imported photos from "Dated" folders into subject specific folders. Seems like this should be easy,
    Or is there already a way to do this?
    Collections will accept selected pictures but how about selected folders?

    The place to add your voice to an existing feature request.
    http://feedback.photoshop.com/photoshop_family/topics/colour_coding_folders_and_collection s_to_simplify_navigation_cataloguing
    This is a user-to-user forum.

  • Feature request - Non-destructive export to Photoshop Touch

    It would be pretty nice if we could export .idea files into Photoshop Touch as a layer (like a smart object in Illustrator/Photoshop) and link the file so any future edits would be reflected

    Why do repeat it here, as you have already filed a feature request for it?
    BTW AFAIK this is already implemented: you can use Adobe Illustrator or InDesign or Opensource Scribus to edit layouts.
    They are just not ready to publish how - another sign of the quality processes at Adobe.
    But you do not send from the book module.
    You create upfront layout templates, which you can import for use inside LR book module.
    This is a one-way street.
    The book module designers did not acknowledge a use case where you might want to fiddle the exact placement of really chosen images.
    It is always you first design a template, then use it.
    Love it or leave it - *change it* is not an option that Adobe seems to give to their beta testers.
    Cornelia

  • Feature Request // Book Module: Export as indd file and management

    Book Module: Export as indd file and management
    I would like to request a feature to export a book module as indd file. 
    I like PDF's but .indd is nice also so we are able to to more in depth layouts.
    Having Lightoom being able to manage all your pictures and book layouts would be nice, alot of things can be done in one application.
    Another Feature:  Using Lightoom as book layout management.
    Being able to send a page(s) of the book from lightroom into InDesign to do indepth layout and editing, then being able to send it back into lightroom
    Almost similar to how you can send a photo from LR in Photoshop to do indepth editing and then send it back into lightroom.
    This could and will ease the workflow of book management and layout design.  So lightroom will not only be able to manage photos, but also indesign and book layouts.
    http://forums.adobe.com/message/4238530#4238530

    Why do repeat it here, as you have already filed a feature request for it?
    BTW AFAIK this is already implemented: you can use Adobe Illustrator or InDesign or Opensource Scribus to edit layouts.
    They are just not ready to publish how - another sign of the quality processes at Adobe.
    But you do not send from the book module.
    You create upfront layout templates, which you can import for use inside LR book module.
    This is a one-way street.
    The book module designers did not acknowledge a use case where you might want to fiddle the exact placement of really chosen images.
    It is always you first design a template, then use it.
    Love it or leave it - *change it* is not an option that Adobe seems to give to their beta testers.
    Cornelia

  • Can`t post replies in photoshop feature requests section

    the reason is probably obvious but not to me,
    I cannot post a reply to anyones comments or thread in the photoshop feature requests, it usually reads "reply" to be able to comment on anothers comment,
    but only reads "report abuse" in the photoshop features request thread.
    when I select "new"and search for the photoshop features request thread, its greyed out so you cannot select it,
    what am I getting wrong here,
    I am logged in by the way.
    cheers.

    They created a new feedback site. The feature request site is read only now.
    Read the text above the discussions sections. There you will find the link to the new site.
    Or click here:
    http://feedback.photoshop.com/photoshop_family
    :-) miss marple

  • Feature Request: Make a Setting Option for Export - Media - What to Render

    As I just changed after many years with Premiere Elements to Pro, I certainly find many things just anconversant.
    But there's one thing I really can't take: When I'm trying to render a project, there's a small selection list near the bottom of the "Export Media" window saying "export area". Here I can choose between "complete sequence", "work area", "sequence in/out" and "defined by user". This option jumps always back to "work area"!
    That's at least for me very unconveniant, because in 99+ % of my renderings, I need "complete sequence". Normally the software remembers the last used setting, but not in this case. I can imagine that one can fight about what's the best default setting: I Guess everyone is using Premiere differently. So in my opinion a predefined setting option would solve best for all: Just add one mor setting in the Presets section, maybe in "General" or make a new rubric "Export" or something. Just a place where everyone can predefine which setting for the export media area option he likes.
    No big deal, just one more presettings option!
    I hope I could make myself clear what I'm meaning
    Thanks in advance!

    Hi Lutzz,
    When I'm trying to render a project, there's a small selection list near the bottom of the "Export Media" window saying "export area". Here I can choose between "complete sequence", "work area", "sequence in/out" and "defined by user". This option jumps always back to "work area"!
    That's at least for me very unconveniant, because in 99+ % of my renderings, I need "complete sequence".
    You can create a feature request here: http://adobe.ly/feature_request
    Thanks,
    Kevin

Maybe you are looking for