Tiff 8 or 16 bit

hi,
is there a way to realize when a scanned tiff file is saved as 8 or 16 bit?
thanks!

Use a metadata set which shows the EXIF tag 'Depth'. The built-in set 'EXIF - Expanded' shows it.
Ian

Similar Messages

When shooting source images for "HDR Pro", is it better to using 16 bit TIFF rather than 8 bit JPEG?

When shooting source images for "HDR Pro", is it better to using 16bit TIFF rather than 8 bit JPEG?

Yes, you will bracket the exposure.
Take as many shots as you need. Take a normal shot, underexpose twice or even three times and then overexpose twice or three times.
That's how the camera will register all teh details in the image - in the highlights, in the shadows and in the midtones. When you bracket, remember to change shutter speed (if you shoot manual, that's what I do), not the aperture because you will end up with different depth of field.

TIFF vs PSD (16 bit) pros cons?

Hi everyone,
I am trying to streamline my Aperture Photoshop workflow and I was wondering what are the real differences and pros and cons to using TIFF or PSD in 16 bit? What would I gain/loose by using PSD or TIFF when editing in PS and saving?
Thanks

TIFF is an open standard format where PSD is an Adobe proprietary format. Both support layers, and there is little difference between them.
I'd recommend using 16 bit TIFF. Most of the Adobe folks would as well, unless you're planning on using the PSD files with Illustrator and InDesign.

Convert 16 bit Grayscale tiff file to Bitmap

How can I do a batch conversion of 500+ pics (in TIFF format) from 16-bit grayscale to bitmap in Photoshop?
Thanks.
Chris
PS - I know how to change them manually (Image>Mode>drop to 8 bit and then to bitmap).

Record an action that does this: "change them manually (Image>Mode>drop to 8 bit and then to bitmap)"
Then use scripts > image processor to process the files, running your new action at the same time. !! Be sure to work on a duplicate set of images !!

Dirty tiff display in InDesign CS4

Hi there,
I have built a number of simple images (rings with solid colour, solid colour with a gradient effect applied etc.) in Photoshop Extended CS4 and then saved them as tiff images at 300 ppi CMYK/16bit files. I have then placed them in an InDesign CS4 document and they have come up with yellow pixels. I have noticed that when I scroll through the document that the areas I'm scrolling into come up a similar colour until I stop scrolling and my machine catches up. I have ensured that my display in preferences is set to the highest setting and still the image is dirty.
Can anyone help out a novice please?
Cheers,
Philamon

You'll do yourself a favor if you convert those TIFFs from 16-bit to 8-bit before opening them in InDesign. InDesign can only handle 8-bits of those file. I'm not sure how it handles 16-bit TIFFs but for 16-bit PSD files it reads the 8-bit composite saved with the file.
Your files will be considerably smaller, and will preview better.
The value of 16-bit is in making image adjustments BEFORE saving the file for other applications.

Unable to save exported Aperture TIFFs as jegs when opened in Photoshop

I'm using the latest version of Aperture and need to do major retouching of the images I have edited using Aperture. When I "export versions" of the images, I normally choose "TIFF-50% of size" or "TIFF - fit within 1024x1024", but when I open them with Photoshop, after I worked on them I am unable to save them as a jpeg. The option just doesn't come up.
The only save options I am offered are - SAVE AS - Photoshop, Cineon, Dicom, FXG, IFF Format, Large Document Format, Photoshop PDF, Photoshop Raw, PNG, Portable Bit Map or TIFF.
Any idea why this is happening and how I can rectify? I need to use photoshop for my retouching and I don't want to have to export RAW files from Aperture, it's much simpler exporting a TIFF.

The tiff is a 16 bit file. Go to images/on the photoshop menu and convert to 8 bit. then the jpeg option will show up.
Cheers

Rendering of an 8Bit-tiff with java.awt produces crap

Hi Folks,
i do a downsampling of tiff images. The source tiffs are colored 8 Bit greyscale with a 256 color-table. Now i have 2 possibilities to resample with java.awt:
1. the target-tiff is of 24Bit true color:
BufferedImage objDownsample = new BufferedImage(iTargetWidth, iTargetHeight, BufferedImage.TYPE_INT_RGB);The result is a perfect looking, but oversized tiff with 16 million colors each pixel.
2. the target-tiff is of 8Bit like the source-tiff:
BufferedImage objDownsample = new BufferedImage(iTargetWidth, iTargetHeight, BufferedImage.TYPE_BYTE_INDEXED,(IndexColorModel)image.getColorModel());The result is a small sized tiff image of 8Bit. Problem: it now has visible vertical stripes of two colors (which both composed result the source-color i assume).
Does anybody know what's wrong here and how to retrieve the 8Bit color-image without stripes?
Here comes the whole source:
    private BufferedImage resize(int newHeight, int newWidth, BufferedImage image) {
        int iTargetHeight = newHeight;
        int iTargetWidth = newWidth;
        //Create a BufferedImage that fits
        BufferedImage objDownsample = new BufferedImage(iTargetWidth, iTargetHeight, BufferedImage.TYPE_BYTE_INDEXED,(IndexColorModel)image.getColorModel());
        //A map with all necessary rendering hints to optimize the quality of the image
        Map<java.awt.RenderingHints.Key, java.lang.Object> obj_Map = new HashMap<java.awt.RenderingHints.Key, java.lang.Object>();
        obj_Map.put(RenderingHints.KEY_DITHERING, RenderingHints.VALUE_DITHER_ENABLE);
        obj_Map.put(RenderingHints.KEY_ANTIALIASING, RenderingHints.VALUE_ANTIALIAS_ON);
        obj_Map.put(RenderingHints.KEY_INTERPOLATION, RenderingHints.VALUE_INTERPOLATION_BILINEAR);
      // Draw the scaled image
      Graphics2D graphics2D = objDownsample.createGraphics();
        graphics2D.addRenderingHints(obj_Map);
        graphics2D.drawImage(image, 0, 0, iTargetWidth, iTargetHeight, null);
        return objDownsample;
    }Thanks
Albrecht

As far as I can tell, this solution only allows compositing within the component that is currently being painted. What would be nice is if I could add a custom composite to say .. a JLabel, which paints based on the colors of the underlying pixel data (ie. from its parent container). In this way you could make a JLabel that always inverts the color of what's underneath.
Here, painting to the screen using a composite allows me to get the pixels underneath as the destination raster, the pixels in the JLabel as the source raster, and what actually gets painted which is the destination output raster.
If I paint to a BufferedImage instead, the composite's 'destination raster' is the new BufferedImage's default values which are all black. Thus compositing over this would not have the desired effects described above (inverting the underlying image for instance). The missing piece when rendering to the BufferedImage is first copying the underlying screen data into a BufferedImage before painting to it. How do I do that? Something tells me it's very difficult.

Aperture 2.1 (Trial), NEF, 14 bit

disclaimer: I'm new to digital photo stuff...
question: As of 8 May 2008, does Aperture 2.1 support NEF files that are 14 bit?
My files are coming from the Nikon Coolscan V ED.
Aperture 2.1 can open 14 bit TIFF file coming from the Coolscan,
but the 14 bit NEF files results in an unsupported format message in Aperture.
(even though the thumbnail can be seen)
Is it my system?
Is it the 14 bit NEF file?
Is it Aperture?
Please help

Here's a note on Vuescan's RAW files from Ed Hamrick, claiming they are just "normal TIFF files with 3 bits per pixel:"
http://www.openraw.org/node/1546
There are a number of discussions on the Coolscan RAW format as well... all saying it's a TIFF wrapped in a Nikon "RAW" wrapper. I haven't really felt like digging into it... I just scan as TIFF and it works great. Frankly, I use Vuescan as I've found Nikon Scan to be rather flaky, and it hasn't been updated in like 4 years so it's not an Intel-native application. Vuescan is well supported by Ed Hamrick.
As far as RAW files and the demosaic process of converting the RAW data into RGB values... there are tomes written on it. It's a deep subject, beyond the scope of this post

Unable to export picture in AdobeRGB(1998) and 8 bit.

Hi all
Im trying to export a picture from Lightroom with the following file settings:
- TIFF
- AdobeRGB (1998)
- 8 bits/components
When the picture file is exported is instead has sRGB and 24 bit in the settings.
Im not quite sure where it goes wrong.
I hope anyone of you can help me out on this one.
/Chris

This is a minor bug in LR, on both Windows and Mac, that you can safely ignore. LR sets the wrong value for the EXIF:ColorSpace field, and that's what Windows File Explorer is showing. But LR does include the correct ICC profile, which is what color-managed apps pay attention to. If you open the exported TIFF in Photoshop or some other color-managed app, you'll see that it thinks the TIFF is in Adobe RGB (1998).
Note that neither the Mac Finder nor Windows File Explorer can be relied on to display photo metadata. In this case, Windows File Explorer doesn't show you the ICC_Profile field, and the Mac Finder doesn't show EXIF:ColorSpace.
Please vote and add your opinion to this bug report in the official Adobe feedback forum:
Lightroom: Incorrect value for EXIF:ColorSpace in exported TIFFs

How to filter all images with 16 BIT colordepth?

is there a way in LR (or bridge) to filter all images that are saved as 16 bit images.
i noticed i have a lot of scanned photos/slides that don´t need to be in 16 bit TIFF format.
8 bit is enough for them and would save me a ton of HDD space (even when most of them are LZW compressed).
but i need a way to find them in my 80000 images database.
so that i can make a further selection which of these 16 bit images i can convert to 8 bit.

>
but this plugin changes a lot in the database right?
Right.
im always a bit fearsome when a plugin changes the database entrys.
Apart from increasing the database file size, I don't think there's
anything to be afraid about. First, the plugins do not do it directly, but
via and SDK provided by Adobe. Second, all the plugin data is stored in
separate database tables, so they don't mess with stock data.

Even though I have checked "Automatically open all supported TIFF's" in Camera RAw Preferences - My tiff files do not open up in camera RAW

Even though I have checked "Automatically open all supported TIFF's" in Camera RAw Preferences - My tiff files do not open up in camera RAW - PS 6

Sorry I'm taking to along, but I checked a few things using ACR 8.6
Saved a png as an 8 bit tiff, then to 16 bit. Changed the background layer into a floating layer, all opened in ACR.
It was when I added an adjustment layer, that it no longer opened in ACR.
Now what can I recommend? If you have Lightroom, you can Import and work on your layered tiffs that way. I hope this is a viable alternative for you, because I think ACR does have a problem with layered tiffs and I don't really know of any workaround, but you are free to explore.
Gene

Workflow question- psd - tiff- jpg

Here are the submission rules I need to follow:
* Convert your image into a 8 bit Tiff file (save as, Tiff)
* In an image editing program such as Photoshop, upsize the image to a minimum of 48MB. (If you make your longest side 5200 pixels and keep it in proportion to the shortest size, this should give you a file size of just over 50MB)
* Make any alterations as needed, inspect the image carefully at 100%
* At the very last step save your image as a Jpeg and send us that Jpeg. Remember, the Jpeg is the compressed size so this will typically be between 3MB-15M
Here is what I am doing, starting with .raw to 16 bit .psd :
Flatten finsihed final psd
Change image size to approximately 2x original to 96-104 Mb (5200 = 51.6Mb) using bi-cubic smoother
Change mode to 8 bit color (reduces file by 1/2)
Save as tiff
Save tiff as jpg highest quality
My question:
Is this the best flow to use or should I be editing the tiff, or going 8 bit at a different point in time? Should I be using something other than bi-cubic smoother? Or...?
Thanks for the help.

Actually sound like you are following some really out of date advice for up sizing for
Alamy or some other agency with a minimum file size requirement.
With the LR Beta 3 this can be done easily enough directly from the export dialogue. With LR 2 it is best done using LR/Mogrify in the export dialogue. The setting for LR/Mogrify to up size with size and quality that will be acceptable by them are
File Settings TIFF, no compression, 16 bit sRGB
Image sizing, and sharpening off
Mogrify Image Processing Options resize to fit total number of pixels 16.1 automatic algorithm
Mogrify Format Options change format to JPEG, quality 95%
The jpg so outputted will meet the requirements of Almay in terms of size and quality every time.
There is also the Alamy plug in which you may want to use, that makes this even easier if it is specifically Alamy you are uploading to

I am unable to edit an image in Photoshop.

I just installed Lightroom 5.3, and I have Photoshop CS5.1 installed. The problem is that I am unable to edit an image in Photoshop. When I click Photo>Edit In, the option for Photoshop is not active (i.e., it's not black), so I can't click on it. Why are the options for Photoshop and all of the other Photoshop related options, such as Merge to Panorama, etc., not active? In Preferences I have the following settings: File Format = TIFF; Color Space = ProPhotoRGB; Bit Depth = 16 bits; Resolution = 240; Compression = None. I am using Windows 7.

Chris:
I have to apologize for being misleading on my request for help in
resolving the problem.
Actually the version I am using is CS2 not CS3.
Yesterday I tried numerous times, and ways, to edit an image and each time
it refused to allow me to save it.
The software program just shut down. This evening when I decided to give it
another try it worked perfect.
Guess the program just took the day off.
Thank you for offering to help
Regards,
Doug

Zip and directory or package

How on earth do I zip a package like an Omnigraffle file? I have a nice folder-action script that zips a file into an archive when it is dropped into the folder, but when I dropped an omnigraffle file into the folder it broke it into all the files that the original omnigraffle file consisted of, in other words it treats the file like a directory and breaks it open. I guess omnigraffle files are packages. If I use ditto it complains and tells me that the file is a directory. I cannot find any zip parameter that allows me to compress an omnigraffle file and keep it is a single compressed file. If I right-click and select compress on a file OS X has no problem and I get a single compressed file with the name and a .zip appended, but if I execute the zip application in terminal, or from my script, I get all the tiffs and jpegs and bits and bobs that the omnigraffle file is built with and the file it a goner.
Most frustrating.
Thanks for any help.
Lawrence

Well - that's done, works fine. The issue I was having was that I wanted files to be zipped into an archive without any path, so I would include the -j parameter. The -j parameter however would not only NOT store the path of the file, but it would also NOT store directory names.
Okay - I thought. There is the -r parameter, this tells zip to travel the directory structure recursively thus picking up sub-directory content. However the -j conflicts with this and what I found was that zip would take the contents of any sub-directory and stick it at the same level as anything outside the folder.
At first I thought this would be okay as I wanted this script to be used for ONLY files. However when I added an Omnigraffle file I was stuck as these are packages, and zip views them as directories. So any omnigraffle file would essentially be burst into its component parts, all rendered as files, at the root level of the archive folder. A total no-no.
If I removed the -j, so that directories would be read and compressed, as well as the omnigraffle files, everything worked fine. Only now each file had a great long file path rooted at /System/user/me..... If I decompressed the zip archive I got a folder named "System" inside which was a folder named "user" and inside that was "me" and on and on until I finally got a folder with my unzipped files in it.
Horrible.
I realized that the key word in "man zip" was that the file path zip uses is relative to where the zip is running, and I was running it as a folder action which defaulted to the root, hence the vast great file path. So all I needed to do was to modify the script so that the zip command references just the file names without path, and then do a cd to the archive directory immediately prior to the zip command itself. Thus I implemented a "do shell script" which had two commands on the same line, separated by a semi-colon, the first command being the cd with the full path to the archive folder and the second being the zip without any paths at all and using just the -r parameter.
Bingo.
Thanks for everyone's help.
Lawrence

Can't open image in External Editor.

Hello. I'm using Piccure as external editor for LightRoom 5.2. When trying to open image, I get "Image file -psn_0_S784964 doesn't exist", when my original image has different name. Image name is accepted by Piccure as first command line argument. Looks like LightRoom starts Piccure with wrong arguments.
Could it be that LightRoom starts external editor with different syntax then "/Applications/Piccure/Piccure.app/Contents/MacOS/psplugin /pathToFile/imagefile.tiff". Maybe in some cases it adds more arguments, or corrupts existing path to image?
Thanks.
Here is the OS sys info as well:
Hardware Overview:
Model Name: iMac
Model Identifier: iMac13,2
Processor Name: Intel Core i7
Processor Speed: 3.4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 32 GB
Boot ROM Version: IM131.010A.B05
SMC Version (system): 2.11f16
Lightroom version: 5.2 [922700]
Version: 10.8 [5]
Application architecture: x64
Logical processor count: 8
Processor speed: 3.4 GHz
Built-in memory: 32768.0 MB
Real memory available to Lightroom: 32768.0 MB
Real memory used by Lightroom: 1667.0 MB (5.0%)
Virtual memory used by Lightroom: 2996.2 MB
Memory cache size: 1042.0 MB
Maximum thread count used by Camera Raw: 4
Displays: 1) 2560x1440, 2) 1920x1200
Application folder: /Applications
Library Path: /Users/Jasper/Lightroom/Lightroom 3 Catalog (original)-2-2.lrcat
Settings Folder: /Users/Jasper/Library/Application Support/Adobe/Lightroom

What "original" camera file type are you using, how are you creating the TIFF files, and what bit depth (8, 16, 32)? The Piccure FAQ says raw images need to be converted to 32/channel TIFF files, but under 'How To' it says:
Select “Filter/Piccure/Reduce camera shake...” (Lightroom®:Select “Photo/Edit in/Piccure”. Save the current photo as a copy(TIFF,16 Bit) and run piccure).
Also what are your External Editing Preference settings for Piccure?

Tiff 8 or 16 bit

Similar Messages

Maybe you are looking for