32 bit TIFF from Lightroom

When I import a 32 bit TIFF sequence (which has been developed then saved in Lightroom) into After Effects it seems to ignore all the develop settings. The only way I can get this to work is to export the developed TIFF's from Lightroom as DNG files, then import those into AE.
Am I missing something? I would have expected AE to read the changes made to the TIFF's.
Any help appreciated.

Yep, same issue here. You can Export using 16 bit depth and ProPhoto RGB to create a copy, which is what you are actually working with in LR anyhow. It would be nice if 'Edit In' would give you a warning that "LR can only create a 16bit copy with adjustments applied, do you want to proceed," instead of simply failing. Perhaps log this a 4.1 bug?

Similar Messages

Exporting TIFFs from Lightroom 5 to Photoshop CC. Banding problem.

I get this annoying problem with color banding when i export 16bits TIFFs ProPhoto RGB (with no compression) from Lightroom to Photoshop CC. Both LR and PS working space is set to ProPhoto RGB color space. Miraculously, the banding dissapears when i convert to Adobe RGB or sRGB. Theres no banding in Lightroom, only in Photoshop. I have encountered others with the same problem, but no one have come up with a solution. Is there a solution to this problem?
Best wishes
Kenneth

Actually, i already have the latest drivers for my graphics card. Its an old card, so drivers is no longer updated every month with new drivers.

Re-edit 32 bit tiff in PS doesn't work?

Hi,
When I generate a 32 bit tiff (HDR) in PS CS5 from bracketed pictures within lightroom 4.1, import the tiff back into lightroom, adjust it in lightroom, and then send it back to PS (option "Edit a Copy with Lightroom Adjustments" selected) for further editing, the file won't open in PS. Opening the file directly in PS works, but without the adjustments made in lightroom.
I have tried the same with a 32 bit tiff from Photomatix. Same behaviour.
Has anyone else noticed this behaviour?
Haya.

Yep, same issue here. You can Export using 16 bit depth and ProPhoto RGB to create a copy, which is what you are actually working with in LR anyhow. It would be nice if 'Edit In' would give you a warning that "LR can only create a 16bit copy with adjustments applied, do you want to proceed," instead of simply failing. Perhaps log this a 4.1 bug?

Lots of 16 bit Tiffs & no idea how to delete

Hi,
I'm really new to photo editing & Mac's, but by following various sources of advice from the net, I think I've created myself a big problem - please advise!
I use Aperture 2.0 for my library & most of my editing of Raw files, but to interpolate these images, I "Edit With" Photoshop CS3. I have the default Edit With set to 16 Bit Tiff, which instantly creates a big TIFF file along with the Raw Master. I then interpolate in Photoshop & reimport an 8 Bit JPEG back into Aperture [I'm sure this is a really poor workflow, but I'm struggling with all this techy side to Photography & I know no-one with a Mac).
The problem, as I'm sure you can guess, is that I have lots (& lots) of unnecessary TIFF files in Aperture that I can't delete without deleting the RAW too.
I use CS3 for interpolation because this is a system that works for my needs (plus I know Photoshop from my pc past-life).
Can you advise of a better workflow that can get 16 Bit Tiffs from Aperture into Photoshop that allows me to delete it whilst keeping the RAW master? Any suggestions for a better workflow really, really appreciated.
Cheers!

BigDwarf wrote:
Hi,
I'm really new to photo editing & Mac's, but by following various sources of advice from the net, I think I've created myself a big problem - please advise!
Many people believe there are too much info - both correct and incorrect - out there. Filtering what you need can be difficult at times, especially if one is learning new material.
I use Aperture 2.0 for my library & most of my editing of Raw files, but to interpolate these images, I "Edit With" Photoshop CS3. I have the default Edit With set to 16 Bit Tiff, which instantly creates a big TIFF file along with the Raw Master. I then interpolate in Photoshop & reimport an 8 Bit JPEG back into Aperture [I'm sure this is a really poor workflow, but I'm struggling with all this techy side to Photography & I know no-one with a Mac).
Not sure why you do this. The default external editor is set to PS, and you are creating 16bit tif files - just fine. The odd thing is what you do after your edit in PS. When you say interpolate, I'm guessing that you are resizing the image? Going from 16bit to 8bit is not interpolation. Rather, it is data reduction in the file. By definition, jpeg is 8bit so I understand why you want to convert 16bit tif into 8 bit.
If you simply save your edit without doing save as, then the edited tif will go back to Aperture as tif file. You can export jpeg from Aperture to suit your needs.
Two different approaches exist to do what you want to do. Since you ultimately end up in jpeg, you can simply export jpeg from Aperture and open the file using PS, do your thing and save, then import jpeg into Ap and stack with raw. Sounds close to what you are doing now.
A different approach is to set your externally edited file preference to 8bit tif and use PS as an external editor and do your edits there (do not convert to jpeg and use save as), and simply save - which will bring you back to Ap environment. Images will already be stacked and all you have to do is export the edited 8 bit tif file as jpeg. Files will be stacked an need not worry where the file is.
The problem, as I'm sure you can guess, is that I have lots (& lots) of unnecessary TIFF files in Aperture that I can't delete without deleting the RAW too.
Depends. If you use referenced master files, then the newly created tif file will be saved in the same location is the master file is located. In which case, if you have no need for it, you can simply delete it from Ap and will get rid of the tif file also (as long as you unstack and check the box that say move the file to trash). Raw original will still be in Ap database as well as in your referenced folder.
If you use managed masters, then bit more complicated but using the same method should work. You can see how the files are kept within Ap Lib by showing content and dig your way into the folder structure, if you're willing.
I was going to suggest you can simply just delete the tif files, if referenced, but it would leave broken links in Ap, so bad practice...
I use CS3 for interpolation because this is a system that works for my needs (plus I know Photoshop from my pc past-life).
Can you advise of a better workflow that can get 16 Bit Tiffs from Aperture into Photoshop that allows me to delete it whilst keeping the RAW master? Any suggestions for a better workflow really, really appreciated.
You have constrained the problem by specifying 16bit tif and delete, as your current workflow dictates. Try thinking about the workflow from the perspective of what you'd like to get done. Not necessarily how.
If the objective is to have high quality jpeg from your raw and keep your raw files and jpeg related, then tif is just a intermediary file. Recall that jpeg is 8 bit by definition and the reason people don't like to edit using jpeg is because of truncation issue with compression, everytime you do something with jpeg. Tif does not compress so there is no loss issue with tif.
If you go from Aperture handled raw to tif (8bit), then edit using PS and save, you have made 1 translation from raw definition (12 or 14 bit in most cases) to 8 bit tif. Editing and saving tif will not degrade your image (there is a loss of IQ, if you up scale resolution, as data needs to be interpolated to fill in the missing data). Once back in Ap, saving as jpeg is simply format change.
If your objective is to enlarge the image beyond the raw size, then use 16 bit tif and interpolate to upscale in PS. That said, unless you have a small raw file (4~6mp) and are printing large images (say beyond 12x18), there really is no need to do so. Upscaling becomes quite noticeable beyond 25% past the original size, even using 16 bit data set.
This long winded response is really the short version Others will have different opinion so keep in mind that this is yet just another info on the web..
Good luck,
Cheers

Exporting from 16 bit Tiff sequence

I am using Premiere Pro CC. I've imported 16 bit Tiff sequence that was exported from Lightroom. Each frame is 5472x3648 and about 115mb. I'm using the Red plugins so that I can create a UHDTV video at 3840x2160. Any attempt to export as dpx or even mp4 or even render the video crashes the program or the computer within seconds or at the most a minute. This same thing worked as long as the files were 8bit, but i wanted the higher quality. The computer is a:
Alieware R4 Aurora
Windows 7
16 Gb ram
3.6 Ghz Intel i7 processor
AMD Radeon HD 8950 (graphics)
Is it premiere pro or the computer hardware that is the hangup?

Just a follow up on what I found out for someone's future reference. If I reduced the file size to 4800x3200, a slightly smaller but still in the same 3x2 ratio as the originals, then Premiere Pro CC would render the files and export them without crashing. This still allowed me to do some pans and zooms within Premiere. Not sure if that is the largest size Premiere excepts or not, it just worked for me. Also, Premiere will only export 10bit DPX sequenses, which is still fine with me.

Photoshop CS5 64 bit crashes at launch, save as, and when opening photos from Lightroom.

I have had this problem intermittently for years with different versions and different computers, but this time it is not going away. I need to use the 64 bit version for large files, but it keeps crashing in several different ways.
1- I open the program from the desktop. It shows the spash screen, shows the workspace for a couple of seconds, and then crashes with the message:
Problem Event Name:
APPCRASH
Application Name:
Photoshop.exe
Application Version:
12.1.0.0
Application Timestamp:
4d90d339
Fault Module Name:
StackHash_8d67
Fault Module Version:
0.0.0.0
Fault Module Timestamp:
00000000
Exception Code:
c0000096
Exception Offset:
0000000078e650ac
OS Version:
6.1.7601.2.1.0.256.48
Locale ID:
1033
Additional Information 1:
8d67
Additional Information 2:
8d672743ada8a2e1e75c51ac7051c8c2
Additional Information 3:
354b
Additional Information 4:
354bf194360e47150cf5d5ca4e71d674
I am using the latest version.
My video card drivers are totally up to date.
I am using a decent computer with 16 gig of ram.
I am opening the program as an administrator.
I have reset the prefrences too many times to count by deleting the prefrences and holding down ctrl+alt+shift at startup.
2- If by some wild stretch of the imagination I get the program to start with totally cleared prefrences and running as administrator then the program will crash about 75% of the time when using "Save As".
If I try to do anything special like create a new folder to put the file into then the chances of a crash increase greatly.
3- If I try to open up a file from Lightroom, even if the files are opening every other way, Photoshop will crash very often.
What is going on here? I have made no changes to my computer, have not installed any new programs, and, as I stated earlier, have everything updated. I even stopped using plugins a long time ago because I did not want to take the chance that it was going to cause this fragile program to crash, so all plugins are uninstalled. Why does this keep happening? When this has happened before everything will work fine for months and then suddenly I cannot get the program to open. When it does open again, for seemingly as unknown a reason as when it stopped, it will work anywhere from a few minutes to another couple of months.
This seems to be a problem that tons of people have, but I have not been able to find any answer other than "Delete Settings" or "Run as Administrator" or "Update *****."
What can I do to keep this from happening and to fix it when it happens?

Update - Problem Solved.
The problem turned out to be with with Avast. I found other people that were having the same problem with Outlook and they pointed to this problem. The live scripts protection seems to have been causing the crash on startup. Why it was intermittant at first and got worse I have no idea, but since disabling Avast temporarily while starting I have not had the problem again. Now I am just going to have to start shopping for more Photoshop friendly antivirus software.
Thank you for the advice Mylenium, unfortunately (or actually fortunately for me) I did not have any 64 bit conflicts.
The other action that I took was to remove all programs installed since the problem started. This did not fix the problem but it certainly cannot hurt to keep everything that I am not using off the computer anyways.

Opening CS4 32bit from Lightroom 2 64 bit

I am using Lightroom 2.6 64bit on a Windows 7 64bit PC. I have both 32 & 64 bit versions of Photoshop CS4 installed. I need to use the 32 bit version of CS4 as I have plugins that will not work in the 64 bit version. When I try to open a file for editing from Lightroom it automatically opens in the 64 bit version. I would like to know if there is a way to enable Lightroom to open the files in CS4 32 bit version by default. Thanks to anyone who may be able to help. A Merry Christmas to one and all.

Hi Hal,
Thanks for the prompt reply. I tried it and it worked. Someone else suggested setting the 32bit CS4 as the secondary editor but I have not tried it.
Rob....

Migrated from Lightroom to Aperture: TIFF's in LAB mode don't work

I migrated from Lightroom to Aperture and I noticed many TIFF's were black, or strangely colored (reddish, greenish). I couldn't figure it out, but I think I know what is the problem. I used to work in LAB-mode in Photoshop for quite some time, and I see that those files cause the problems.
Not only can't I see the previews correctly, Ican't do anything with these files (not even open them in Photoshop). What can I do? Because these files are my portfolio (the material I sell, exhibit, etc.). They're extremely important for me. What can I do? I'm willing to convert them to RGB if necessary.

There have been some issues with greenish previews lately. Browse this forum for threads with the tags "green" and "Previews". If that is the problem, then only your previews look strange and your original images might still be o.k.
So I recommend to check if the images or only the previews are faulty.
If you have a referenced Library reveal the masters in the Finder and look at the master with Preview or another Photo Browser.
If your library is managed, you can reveal the masters inside your Aperture Library by opening the package (in Aperture 3.2.1), select the Library in the Finder and click "Show package contents". You will see folders "Masters" and "Previews". Compare the Masters and the Previews.
If only the Previews are faulty, then select the the images in question in the Aperture Browser, ctrl-click them and select "Update Preview". If that does not help ...
What can I do? Because these files are my portfolio (the material I sell, exhibit, etc.). They're extremely important for me. What can I do? I'm willing to convert them to RGB if necessary.
I assume you have a backup or can access the originals you imported into Aperture.
Convert a copy of one of pictures to TIFF in RGB mode and see if Aperture can handle that properly.
If you are satisfied with the quality do that with all your important pictures.

Can I upgrade from Lightroom 3/32 bit to Lightroom 5/64 bit?

I'm considering the purchase of an ASUS Republic of Gamers laptop using a Windows 7/64 bit OS with 16 gig of ram. So far my research tells me a 32 bit program running on a 64 bit OS will be limited to, I think it was the use of no more than 4 gig of ram. Therefore there seems no sense in using my current version of lightroom (v 3.6) since I would not be able to take advantage of the greatly increased ram. can I upgrade from Lightroom 3.6/32 bit to Lightroom 5/64 bit?

Yes, you can.
Installation software for Lightroom for Windows normally comes with both a 32 bit and a 64 bit installer packet. This means you can also, without upgrading install the 3.6 64 Bit version.

Opening RAW File from Lightroom is automatically saving a PSD or TIFF. How to turn this off?

I recently upgraded to LightroomCC and Photoshop CC however now when I go to open my RAW files from lightroom it is automatically saving a PSD copy when the file is opened. I don't want it to do that because I don't need those files - for some of my stuff I just need to open the file, edit, and save a jpg when done. This was not a feature on the older version of Lightroom and I can't find any place to turn this off.
Any help would be much appreciated!
Thanks!

Maybe this extension: Second Search 0.7.2012122901
Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
*Do NOT click the Reset button on the Safe mode start window or otherwise make changes.
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

Images sent from Lightroom 5 won't appear in Elements 12

About one month ago I've bought and installed on my computer Photoshop Elements 12. However since then I had never launched the programme, which I did for the first time yesterday by trying to send five TIFF shots from Lightoroom 5.4 to Elements (Photo > Edit in > Merge to HDR in Photoshop).
Elements did open but the five images were not displayed. The same exact thing has happened when I've tried to send from Lightroom to Elements six other shots to merge to Panorama.
I'm working on a brand new computer with Windows 7. The operating system and both Adobe softwares have the latest updates installed.
Could the problem be that I've waited too long before launching Elements after having installed it? When the program opened for the first time yesterday it appeared a message which read that the first launch should have happened within 7 days from installation and never during the process I was asked to input the software's serial numbers (is this the way it's supposed to be?).
Do you think that I should uninstall Elements and start from scratch all over again?

Have you set up the PSE12 Editor correctly in Lightroom?
If not click Edit >> Preferences from the Library and then choose the External Editing tab. Then click on the choose button under the additional editor section and navigate to the editor.
C:\Program Files (x86)\Adobe\Photoshop Elements 12
Make sure you choose the application and not a shortcut (see image below) and select 8 bit tiff as your pref (not 16 bit images)
You can’t use merge to HDR with Elements. That function only works with Photoshop CC or Creative Suits. But you can choose a thumbnail in the LR Library and open it for editing in PSE12 by pressing Ctrl+E or using Edit In >> Photoshop Elements 12 Editor.

Cannot export Luminance settings when exporting TIF from Lightroom 4

Hi All,
A problem that's come up today!
I use quite heavy Luminance noise reduction on my images as they are shot at very high speed ISO...
I adjust this in L4, picture in preview looks as smooth as a babies bottom and perfect...
I then export as a TIF file at Adobe 1998 and when I open it in Photoshop 5 the image is really noisy like I've not done the adjustments at all...
I use a 17inch Macbook Pro with the lastest operating system, this is the second performace issue over the last few week (problems with LB too)...I export my files manually using a card reader as RAW files, from a Canon 5D Mark 3...
Is it worth re-installing?
Thanks!
Sarah

Hi Rikk,
Thanks for the feedback :-)
My Photoshop is actually CS4 rather than 5...sorry for the misinformation!
I'm rendering 16 Bit Tiff's from Lightroom 4 into the above but it seems to only happen to images with a really blue hue...
I'll upgrade to 6 via a trail and see how I get on...Thanks for the info :-) I'll get back to you...
Cheers!
Sarah

CS2 problem with 5D MKII RAW files from Lightroom 2.2

Ok, this one is weird. I have tried it on two different computers with the same resulting problem. If I convert a full size RAW 5D MkII to Tiff in the new Lightroom 2.2, then bring it into CS2 and covert it to 8-bit and try to save as JPG, it always comes up with a program error. I tried an sRAW file with the same process and it worked fine.
Just to make sure I did have something else messed up, I converted in DPP to tiff and then went to CS2 and saved as JPG just fine.
Anyone else try this and see a problem? Looks like it's a combination of a problem with the new Lightroom, plus CS2.
It almost seems like CS2 doesn't have enough memory to convert the file to jpeg. I have had this program error before in CS2, but with much larger files. The 5D MKII should not overrun memory.

This is a known bug in CS2 where it trips up because of the (valid) metadata written by Lightroom. You need to delete the xmp metadata written by Lightroom from the file before saving as jpg or export from lIghtroom with minimize metadata checked.

Saving PSD files after exporting from Lightroom saves incorrectly

I've only recently moved to Lightroom from using Photoshop/Bridge together, so I'm not 100% sure how saving files exported from Lightroom should go. But here's what I experience:
Base edit of file within Lightroom
In library view, right click on image -> Edit in -> Open as Smart Object in Photoshop
Perform all my necessary edits and such
File -> Save As, and save it to another location as a PSD file (totally different HDD)
Perform more edits....
Shortcut CTRL+S to save, and it saves it as the TIFF file under the location it was originally in within Lightroom
Eh...? Am I missing something. It should just save as the original PSD I created when I went "Save As". I have seen on a few occasions, immediately after "Save As", the file name resorts back to TIFF and not as PSD.
My settings for External Editing in Lightroom are as follows:
File Format: TIFF
Color Space: ProPhoto RGB
Bit Depth: 16 bits/component
Resolution: 300
Compression: None
Does anyone have any ideas what I'm doing wrong? Also, to note, that sometimes I double click on the Smart Object within Photoshop to load Camera Raw and perform some edits, but not often.

Modesto Vega wrote:
Replying to your last 3 posts.
Re Camera Raw being used to pass an image to Photoshop
a) I am assuming this is independent of the Compatibility level in Preferences\File Handling DNG creation.
b) Does the same apply to other photo editing software made by Adobe like Elements?.
Reply: Yes, the principle is the same. Photoshop Elements cannot read raw data either. That's why it has to be converted before it's opened.
c) Assume that I have LR 5.7.1 and CS5. Is Camera Raw is still used to pass an image to Photoshop? If so, why is there a need to get LR to behave differently?
Reply: Camera Raw is used IF you choose the option to open anyway. Then Camera Raw will be used to convert the image that's opened in Photoshop. But since it is older than Lightroom some of the new adjustments might not be transferred to Photoshop. That's why there is a need to let the user make the choice.
d) Sometimes it does seem as if Adobe might be using Camera Raw updates and process version updates to get consumers to change their habits, this includes having to buy subscriptions or having to change workflow to some ideal that somebody at Adobe or working with Adobe might have in mind.
Reply: The fact is that in the past, when a new version of Photoshop is released then all support and updates cease for the previous version. Since the introduction of the creative cloud, at least users of Photoshop CS6 get support for new cameras. They just don't get the new features. Yes, there's motivation to upgrade. Adobe is a business. What do you really expect?
Re stacks
I find impossible to see collapsed stacks on the film strip. Stacks are only visible on the Library module and using a grid view; I don't say clearly visible because they are only recognisable by the label at the top left corner with the image count; I don't even think it is possible to change the colour of that label or the grey colour surrounding an image. Also I cannot name stacks. If I could name stacks, see them as virtual folders underneath a library folder and make them glaringly visible I would use them extensively.
Reply: The only reason I can think of that you are unable to see collapsed stacks on the filmstrip is if you have the filmstrip reduced in size to the point that Lightroom can't display all the icons. I'm able to see the collapsed stacks in the library grid view and on my filmstrip
Re storing your Raw files and processed files in separate locations
Assuming Raw files are negatives and Photoshop files are transparencies or prints, would you want negatives being handled/read on a regular basis? If anything happens to your negatives, you would never be able to produce another print or another transparency again.
Reply: The raw files or the negatives, as you put it, are never modified by Lightroom. They always remain in their pristine state they were in when they were imported. If I have a backup of that raw file then I can do whatever I want to the one in my working folder. Resetting that raw file so that it looks unaltered is just a click away.
I have worked extensively with databases and database systems, it is a standard feature of database systems to be able to choose where to store different database objects. I don't see why LR cannot do the same, it is a database after all. I do agree with both the OP and photo.
Reply: Well, I won't argue that point. If that's what you really want than lobby for it. It just won't get my vote because I don't see any real advantage.
If you read back through this quoted message you'll find that my replies are included. I don't know how to separate them out so they are highlighted properly. Read through it and think about it. But personally, I don't want to waste anymore time on this discussion because it isn't accomplishing anything in my opinion.

Major problem: I can not export NEF files from Lightroom

This is just plain weird: I can't export NEF files from Lightroom 2. I can export any other file format, but not NEF. With Lightroom 1 this was no problem.
It makes no difference whether I choose the export command with my mouse, via the menu or with a key stroke - nothing happens.
Lightroom version 2.0
Camera Raw version 4.5.0.175
Camera Nikon D3
Photoshop CS3 version 10.0.1
MacOsX version 10.5.4
I've called Adobe, and they simply don't know. I have reinstalled Lightroom 2 with no succes. Restarting, repairing permissions, nothing helps.
Any ideas will be greatly appreciated.
Marsel

Marsel, your language is confusing, First, you cannot 'export' NEFs to PS. You can send a copy there from within LR as a tif or psd.
Exporting per se takes place through the Library module under the Export function. When Nef's are exported by choosing 'original' in the export dialogue, the file is the 'original' NEF accompanied by an XMP. That Nef, if opened directly in PS from your file system should appear in the Camera Raw window, where you can make whatever new edits on it you want or change the original adjustments you made in LR. Then, once you open that file in PS from the Camera Raw window, any further work you do will be pixel editing. That work can then be saved in a number of formats, but not as a NEF.
Transferring files to PS from LR for editing is another matter. That sends a copy of the original NEF, including LR adjustments to PS as either a Tiff or a PSD (your choice via the dropdown). After you have edited that Tiff or PSD in PS and hit save, it will send a copy back to LR as a Tiff or PSD, which will appear next to the original nef.
These procedures work perfectly on both my windows 32 and 64 bit machines with LR2 and 2.1. with all my NEFs from several camera models.
When you say 'export' do you really mean sending a copy to PS or do you mean 'Export' as LR defines that term?

32 bit TIFF from Lightroom

Similar Messages

Maybe you are looking for