Photomerge DNG files stitches 16-bit/32-bit RGB/8 * panoramas

Similar Questions

• Convert a sweep of 16-bit grayscale tif to DNG and getting 48-bit RGB?

  I have scanned hundreds of old black and white negative using Vuescan to TIFF 16-bit grayscale. If I open in Photoshop CC2014 the tab indicates that they are a single 16-bit grayscale channel. But if I have Lightroom convert them into DNG and then open them in Photoshop, they appear as 48 bit RGB or three 16-bit RGB channels. The three channels are identical. What happens here? Is it only returned as a 48-bit RGB or the DNG image byPhotoshop to store the RGB image? The DNG format is not much bigger than the TIF, so it doesn't seem to be store 48 - bits of information. I lose all the data on your way to the DNG format with a scanning in grayscale?

  Given that I can export the DNGs to a tif and it refers to a single channel 16-bit, I suppose I don't lose all the information, but I'd rather not use DNG for scans in grayscale? Or should I edit in Photoshop with the three RGB channels on and understand that I am change the grayscale channel should ever export back to tiff?

  It seems at least that there is a gap in the rendering of the shades of gray DNG in Photoshop?

  I think that the best way to answer here is to explain my own workflow.

  I have to be a little brief: it's getting very late, and I start tomorrow a roadtrip of six weeks.

  I do a lot of work with TIFF scanned, and it never occurred to me to convert to DNG.

  I start with rough tonal corrections, noise reduction and retouching in PS and then import the image (with all the shadow and highlight details present) in LR.

  Here, I'm very good tuning and capture sharpening, but sometimes the image must return to the PS for editing. I use then change the Original and the image opens grayscale in PS. After check-in PS, I click on the exclamation mark on the thumbnail and choose import disk settings and updates to images in LR.

  Given that I find the release of LR sharpening unsuitable for scanned images (it's probably optimized for digital capture), I export a new LR tiff image, open it in PS, conversion of RGB to grayscale and use Smart Sharpen for output sharpening. I wish you that LR could export in grayscale, but I've learned to live with it. You could easily implement an action of conversion in levels of gray (and 8 bits) and use it regularly.

  My knowledge of the technical aspects of the dng files is limited, but my impression is that they are files in grayscale, which explains the small size of the file.

  The color is added in the process of deconvolution in LR.

  I do not think that your workflow with convertin to DNG will affect the quality, so stick with it if you wish.

  I gladly carry on this discussion, but since I'll be on the road, you answer could take some time.

• Camera Raw offers only to open the raw files to 16 bits in 8 bit mode

  I use a Bridge CS6 windows = > Camera Raw (8.2) = > Photoshop CS6 (13.0.1 x 64) to try to open the various raw files to 16 bit (.dng, .nef, .arw), who sees bridge 16-bit, but only a 8-bit version done in photoshop.

  How to convince Camera Raw to accomplish his task?

  Lightroom (4.4) is able to export a 16-bit .psd that kind works but should not be necessary.

  Thanks in advance,

  Steve

  You set the bitdepth in your dialog box options work, which you access by clicking on the line that looks like a link under the overview of ACR:

  

  

  Feel free to read the files help or any other documentation provided with Photoshop (otherwise known as Read The Fine Manual).

• Whenever I have download an image with the command "save the image under...". ", it records in a useless file of 168 bits.

  As stated, whenever I have download an image with the command "save image under" he recorded in a useless file of 168 bits. This does not happen everytime I have save an image, but more often the not, and I don't have a lot of useless files hang out because of this. Is it possible to re - download each image 168 bits that he should have been downloaded in the first place? Is it possible to ensure that this does not happen?

  Here's what it looks like:
  http://i.imgur.com/yzgwwgC.gif?1

  This means that you are not allowed to do this action.
  The site could use a transparent overlay image to protect the actual image or otherwise has put in place a protection.
  You can check if see you the image in "tools > Page Info > Media ' and save it.

• How can I convert 16-bit files to 8-bit in 5 Lightroom?

  How can I convert 16-bit files to 8-bit in 5 Lightroom?

  You can actually convert a 16-bit image to 8-bit using Lightroom image. You can export a copy and make the copy an 8-bit image. Lightroom does not change the content of the image or makeup. The images that you import into Lightroom are kept in State of origin. But you can export copies in different configurations.

• I can't open a file HDR 32-bit with HDR in Photoshop in Lightroom.

  I can't open a file HDR 32-bit with Photoshop HDR. I saved the file in Photoshop with the maximum compatibility option. In Lightroom, the file doesn't show a preview and an exclamation point in the upper right. Anyone an idea why and how to solve this problem?

  The 32-bit file must be saved in TIFF format.

  HD ++

• Photoshop "in edit...". "no longer works for my DNG files

  OK, I have read many discussions on this topic and tried all the solutions given, but the option no longer works for me because I've updated both programs.

  Currently working on:

  Mac OSX 10.11.6

  CC 2015.6.1 the Photoshop Lightroom and Camera Raw 9.6

  Photoshop CC 2015.5.1

  Photos with Cloud backup external HARD disk

  Lightroom catalog on computer

  Backup catalog Lightroom in the clouds

  Lightroom preferences for editing in Photoshop:

  File format: PSD

  Color space: ProPhoto RGB

  Bit depth: 16 bits

  Resolution: 300

  Metadata settings: automatically write changes into XMP

  Tried:

  Uninstall/install the two programs with reboots and even with uninstallation of preferences.

  Uninstalled and installed creative cloud.

  deletion of com.adobe.Photoshop.plist

  TIFF, Jpeg, opening... gives no problem. I always get the possibility to decide to open original/copy with LR adjustments/copy without LR adjustments

  Open a DNG by LR in photoshop open Photoshop, however, is no longer opens the image and so I can't save as PSD thereafter.

  It's completely dead my workflow because all my pictures are stored as RAW/DNG files

  After a chat with Adobe Support all issues have been resolved:

  Apparently, when you use an external source for your photos, this is the case for me save space on my local drive and for security and backup reasons, once I had problems seems to happen.

  The solution is quite simple: unplug the external source, import a random picture to LR by using the import function 'Add', open it in Photoshop using "change in". It worked flawlessly and subsequently when you reconnect my main source for the photo I have, I could again open DNG files in photoshop using the function "change in" LR.

  Adobe support thank you!

• Lignthroom CC 2015 .dng files, HDR and pan do not show thumbnails in the OSX Finder, Ditto with the extract to DNG 7.1, but extract format DNG 5.4 the thumbnail is ok. Ditto in On1 browser?

  Lignthroom CC 2015 .dng files, HDR and panoramic do not show thumbnails in the OSX Finder, only a black rectangle or logo DNG, Ditto with extraction to DNG 7.1, but if to extract the format DNG 5.4 vignette is ok. Ditto in On1 browser? Is this a bug?

  Thanks for the test on Windows too.

  Yves/CH

  Apple has not updated their libraries to support raw yet to be able to understand the new 16 - bit floating point dng files created by Lightroom. If the Finder cannot generate a file icon to show you. Usually the DNG support built into OS X only knows how to treat direct dng files conversions of files from cameras raw is already in favor.

• Why LIGHTROOM changes the DNG files on it s own?

  I noticed this quite a while and it s annoying as hell when you have an automated backup process.

  LR regularly DNG files... and LR changing again and again DNG files.

  This means that files that are modified yesterday are perhaps changed again today.

  I've noticed this with all versions of LR4.x and also LR5.

  so I just create a catalog from TEST to test.

  I Don t change anything on this catalogue of test images.

  all I do is open the catalog and browse the files and allow the LR open and idle for some time.

  and guess what... my DNG (and only the DNG files) files are constantly changed for no apparent reason.

  to check what has changed in the DNG files I use exiftool and this is the result:

  new file:

  InstanceID xmp.iid:c0474916-c24c-2448-b42c-522076f5a25d

  old file:

  InstanceID xmp.iid:2e88ce2a-2e5a-b34d-a85b-2af2ab3494da

  I also did a comparison hexagonal just now on these modified files:

  http://i.imgur.com/FAaZz.jpg

  Another example:

  http://i.imgur.com/vzMbS.jpg

  I have the function "automatically write changes to the XMP" lit.

  but when I Don t change anything... There is nothing to write in the files... right?

  Once again to do this 100% clear...

  DNG files are in the LR catalog for months or years (not in the test catalog but my catalog of actual work).

  DNG files are not affected by me (no changes are made in the LR modules, no new keywords or metadata changes etc.).

  only what I posted above is changed in DNG files.

  Does any other file formats (JPG, PSD, TIFF) in my catalog.

  I don't use DNG files with any software then LR. I have not the same seen in another program.

  PS: of course, I wrote about it in adobe... but as usual, nothing happens.

  even with regard to my graphic problems... I send a sample file of adobe... they write in return that the mistake could be reproduced... and 5 point later the error is always in LR.

  I do not use the DNG file format, but tried a test DNG file and could not resume this problem on my 64 bit Windows 7 using LR4.4.1 System. I checked the InstanceID by using EXIFToolGUI and he only changed when you do a CTRL + S save metadata in the file. Simply navigate the image in the library module or develop as well as other images in the same folder has NOT caused the InstanceID to change. I also did a search on 'DNG write metadata' in the Photoshop family forum and only found this post regarding the behavior of CTRL + S with DNG files:

  http://feedback.Photoshop.com/photoshop_family/topics/only_write_metadata_if_out_of_date

  If what you say is true, I believe there are many posts complaining about the issue. I have no doubt this problem, but logically it should happen only if somehow a CTRL + S or ' save metadata to File command is get called.

  Maybe send a file and we can test it on our systems. Please provide some details on the procedures of LR you use that causes the InstanceID to change with this file. Do not assume that we understand what you are doing!

• DNG files appear darker after importing in Lightroom

  I just started with the demo version of Lightroom, having always managed so far with Photoshop and Bridge. There are a lot of things about Lightroom that I like, however, I am a little confused on why DNG files especially who were already resolved using the ACR in Photoshop are change appearance after having been imported into Lightroom, if I select an image, and in general, they become quite a bit more dark. With thousands of images to process I really want to be in a situation where they all need adjustment once again, so I was wondering if anyone knows why this is happening?

  In both cases my chosen, work space is Adobe RGB and Lightroom do these changes if yes or no I option lets you apply adjustments to your car in development. Another folder that contains only files Tif and Jpeg derivatives does not seem to be affected in the same way.

  According to your description, it seems that the JPEG preview embedded in JPEG format is based on the image before the ACR changes *. Fortunately, it is quite easily solved in Lr, less (actually less obvious) in Camera Raw.

  In the grid view, select all images, then select Update DNG previews and metadata in the metadata. Be warned that it will probably take some time that Lr has to recreate the DNG files in the background.

  * in general, this occurs when you convert the raw unedited files originals to DNG using the DNG Converter.

• DNG files, metadata and catalog

  Hello I currently have LR2.7 64-bit running on W7 64 bit. My camera captures native DNG (Leica M9). I import via "Convert to DNG and add to the catalogue" worth compression without loss for files when importing (for copy and extra copy on external hard drive). I prefer not to rename files on import as my first sorting level is contiguous numbering of all original.

  I'm little upgrade to LR3, however I'm waiting for the resolution of the problems reported with the catalog updates. My plan is to first import the images to the laptop when traveling and important copies to my desktop, a first action to return. I understand that there may be issues of import and export of catalog files on both machines currently duplicate with. I prefer a lot to keep multiple copies on computers apart until I swallowed the files in my normal diet at home.

  I'm looking options to avoid rebuilding a catalog, if something is not bad. I prefer to keep initial develop information, Keywords, changes of ratings made on the laptop.

  I understand that the development parameters are stored in the DNG itself rather than in a file. I'm not sure just where each type of information is stored, which is listed in the file and in the lrcat file. I understand that previews are inconsequential, because I need to be updated in any case those who, after the changes.

  So specifically, if I just copy the DNG files after my initial changes on the laptop with the main machine, what information willl be kept and who will be lost if I throw the laptop catalog to reduce to nothing all the problems with import/export?

  Development settings?

  Keywords?

  Ratings/labels?

  I have the ability to import via CS5 on both machines but try to optimize my use of LR for as many functions as possible.

  Develop settings are the final position of the sliders in the develop module. With this information, Lightroom can make the photo with your changes. You do not lose this information if you write to XMP and then reimport into Lightroom.

  Develop the story is the sequence of steps that you followed to reach the final position. You lose that when you write to XMP and then reimport into Lightroom.

  I guess I don't understand the point of the exercise (unless it's purely an educational exercise). If you export in the catalog, and then import from catalog, something that Lightroom is very easy to do, you don't lose any of the catalog information.

  So, you have at your disposal, a method that retains all the information catalog; and a method that doesn't work. Which one will you use?

• Some .dng files won't open in PS/ACR

  I have version 5.6 of Adobe Camera Raw.  I am using PS CS4 Ext both 64 and 32 bit running on 64-bit Windows 7U.  Version of Lightroom is 2.6.   All Adobe applications are fully updated.

  I have a lot of files .dng sample from the book of Scotty Kelby for Lightroom 2 training.  All these files are visible and editable in Lightroom 2.6, but only some are editible and viewable in Bridge/PS.  The rest give and error (in PS) that it cannot be opened because it is the wrong type of file.  ACR does NOT open.  In Bridge, right click on the image icon doesn't 'open with ACR' available as one of the options.

  The example files are available here: http://www.KelbyTraining.com/downloads/books/Lightroom2/chapter_4.zip

  Anyone know why Bridge & PS are 'problems' with these .dng files?

  I don't know why all these files are named as. DNG; He must be a fool on behalf of JPEG and PSD as DNG files. In any case, Exposure.dng is a JPEG file. SaveYourPresetsx, UsingClarity and VirtualCopies are the PSD files. The others are good Nikon D3 files to DNG.

  Gabor

• Layers and DNG files

  So, I just discover the RAW function in Bridge in order to make the output of my camera JPG and converted .dng while doing a little control interesting features of the image. But, big but, when I transfer the file in Elements 8 I can't apply layers. Why is this? Is there a way around it other than to resume the .dng to JPEG file?

  First of all, I'm glad you like editing .jpgs in the Adobe Camera Raw interface. I love her. He did a good job, easy.

  There is no point to save the .jpgs in the form of .dng files. It is simply a waste of time and a waste of disk space. Does not improve the quality of your image.

  When you open a file in the editor of PSE, you can only apply layers on 8 bit images. You cannot apply layers on 16-bit images. Then... either in ACR, either in the PES Editor, change the number of bits from 16 to 8.

• Is this large normal DNG file format?

  Hello

  1) I get this picture in RAW and then decided to convert to DNG cause, it is easier to use the DNG format as the original Canon RAW format. The DNG format is now 8Mb in size.

  Now, the idea is to post-processing, the DNG in Lightroom, but I kinda need to do some pixel changes first in Photoshop and for that, I'll opt for the opening of the DNG format in Photoshop. As usual, the window pop up ACR and since I did not have to do any editing here, I'll just open a copy of the image (Alt + open). Before that, I configure the settings of openness, that I chose "sRGB; 16 bits; 240ppi"because I want to keep the more possible data.

  I do my editing of pixels in Photoshop, save the image as a TIFF with ZIP compression and the file is now 52Mb in size. Which is a little strange because if I save the TIFF file without any compression, the file is only 58Mb in size.

  In any case, I have then open the TIFF file in Lightroom and do all my editing necessary. When I finished, I want to keep this photo to DNG as opposed to TIFF cause I think it is a most versatile and for that format, I export as DNG from Lightroom (or I could convert the menu library). At this point, the size of the DNG file is like 43 MB and I still think that its way too big.

  Is this normal file size? How is this new file has more than 40 MB? Is it because the file is 16 bit and there is no way around it? I think because save the same 8-bit, produced only 12 MB file with ZIP compression. But I still don't quite get it... I mean, all the data of the original RAW file installed on the first conversion to DNG with only 8 MB file, how will the other needs like 40 or even 12 Mo (if it is stored in 8 bits) when the original has only 8 MB? This becomes even more confusing when both files (the original DNG and the 16 bit TIFF) report as of 48 cases of depth, which means that the two are 16-bit files. Why the huge difference in size? I'm doing something wrong?

  Above is the main question, but I have a couple more if you don't mind associated with the workflow described above. Please respond separatedly and listed as I did if this isn't a problem.

  2) as you can see above, I chose sRGB but I know that Lightroom works in ProPhoto RGB. Should I have selected ProPhoto RGB instead of sRGB when opening a DNG copy in Photoshop?

  3) no matter what the color profile, I select, save dialogue of the TIFF file after the Photoshoping as a little checkbox saying "ICC profile: xpto ' and if it is enabled, the color profile is saved in the TIFF metadata XMP part. Is it really necessary to save this metadata field or can I just ignore it?

  That's all for now

  A RAW is 1-color-by-pixel, maybe 12-bit or 14-bit.  A TIFF file is

  3 colors per pixel and in your case, 16 bits per color per pixel.  If a

  TIFF should be approximately three times larger than the RAW format, but there is

  a compression without loss with RAW so the actual size is difficult to predict.

  Agree with other people that can answer, it is better to use LR, first make your

  adjustments, then as a last step, make any remaining editing in Photoshop,

  Save as either TIFF 16-bit ProPhotoRGB if you're going to be a edit

  further and save a copy as sRGB if you have finished editing.

  ProPhotoRGB holds more colors than sRGB or AdobeRGB PP is 'better' as a

  intermediate color space until the edition is no longer will be performed to

  This time usually converting you to sRGB for viewing online or work with

  in a non color workflow.  Here is a gallery of images that

  demonstrate why use of PhotoPhotoRGB:

  http://www.PBase.com/ssprengel/tech_colorprofiles

  XPTO suspicious noises as a color space.  If you do not know how this

  color space is assigned to your image in Photoshop, you need to understand

  Why.  Out of Photoshop, I think a picture is

  ProPhotoRGB (if you have not finished editing), AdobeRGB (if you're on a Mac or)

  He's going to a printer off site there), or sRGB (if you have completed

  Edition and it will be consulted online or locally on your computer and you are

  on a PC).

• Cannot save a big TIFF 16-bit RGB Image in JPEG format

  Hi all

  I use Photoshop CS5 Extended on Windows 7 64 bit (Home Premium).

  I sewed a panorama in Photoshop using the fusion of 19 RAW (Canon 5 d mkII) files in 16-bit. Everything was fine, I saved the image merged under TIFF 16 and worked on it. Panoramic image resolution is approximately 33000 x 4900. Place the flattened selections and active left.

  Once I was happy, I ran the Image processor on it with a watermark action and add the copyright EXIF data. There is no need to say that it cannot save in JPEG format (he performed the action correctly, just stopped to save). Normally, this works very well with other images RGB TIFF 16 I did.

  I tried to save it manually, but at this time, I noticed that the "Save for web" option is grayed out and the dialog box "save under" showed no JPEG options.

  What I did:

  1.) tried to open it with ACR and save it in JPEG format. It worked well

  2.) tried to resize to 20000 x 3600 (more or less) and it worked fine (which means that the option to save it as a JPEG back where it)

  3.) tried to convert it to full-size 8-bit and who did not

  I'm not too bothered because I have the solution of ACR, but it's boring and in the past, I've done more large panoramas with CS4 and I never had this problem before.

  Any ideas?

  The image is nearly 1 GB, so I'll not post...

  Thanks for your help!

  The CAB code has a limit of 64 k according to the width and height of JPEG files.

  The Photoshop code has a 32 KB limit, because of the old code for JPEG.