Importing .tiff images

I am importing .tiff images on multiple layers.  How do I make the white background on each .tiff image transparent?

ASk in the Id forum and provide exact system info, versions of PS, details about your files and so on. There is an issue with legacy color profiles in some cases, but beyond that I'm not aware of other problems that may be relevant here.
MYlenium

Similar Messages

  • InDesign crashing when importing tiff images

    I have upgraded to InDesign CC 2014. I have trouble importing some tiff images. InDesign crashes. Not all tiff images create problems. It depends on which version of Photoshop, they are saved in. If I open the image in Photoshop and saves again, there are not any problems. Our database is very large and contains several folders, so it is a big task to archive all images again, even if I create an action in Photoshop. I have searched, but I can not find any settings in InDesign that helps. Does anybody else has encountered this problem and found a solution?

    ASk in the Id forum and provide exact system info, versions of PS, details about your files and so on. There is an issue with legacy color profiles in some cases, but beyond that I'm not aware of other problems that may be relevant here.
    MYlenium

  • Image Date error on importing TIFF images from Disk

    I have thousands of high quality (~100 Mb each) images in 20 folders on a 1 Tb hard drive. I have been using Bridge to manage the images, adding some metadata such as keywords and copyright data. I am considering importing all these images into Aperture and using it as the primary image management tool.
    But I am concerned about an apparent bug in the way Aperture handles the "image date and time".
    In Bridge (and GraphicConverter), the "image date" field is correct, directly from my CFV digital back on the camera and inline with the time of day the shot was taken (e.g. sunrise image at 6am). When I import the image into Aperture, the time gets shifted by 14 hours.
    For example, an image in Bridge that correctly shows Date Created as 10/05/2009 7:36am gets distorted to 10/05/2009 9:36pm, exactly 14 hours later than the correct time. It was taken at 7:30 in the morning but, in Aperture, looks like it was taken in the late evening. It does not look like a time zone issue as the image was taken in the same time zone as my Mac Pro is set to.
    I have tried deleting the masters and re-importing them with GMT +2 and GMT -12 in the two time zone adjustment fields. This gets the right time into the Image Date field but then the image has the wrong time zone data in the "Camera Time Zone" and "Picture Time Zone" fields.
    I have tried running MetaData > Update Date and Time (with Master files ON) but it comes back with an error "no master files were adjusted ... because they have a format that does not permit modification".
    I have tried running MetaData > Update Date and Time (with Master files OFF). It appears to work but I assume that the underlying file in the Aperture library still has the incorrect time.
    Have others faced this problem? Is there a solution? Is it a known bug that Apple might fix one day?
    Regards
    Peter

    I am seeing a very similar problem when importing TIFF files back to Aperture.
    This is what I do and what I see:
    1. I import RAW images from my camera into Aperture. They show the correct date and time.
    2. I open an RAW image in Photoshop (CS4) directly from the finder. The image inside Photoshop (file/info) shows the correct date and time.
    3. After editing I save my image as 16bit TIFF and it still shows correct date and time.
    4. I import the new TIFF back into Aperture. The time is shifted back 15 hrs!
    I can then go in and Metadata/Update Date and Time (no masters) and it works well, but it is a pain to do on each image I process.
    In all cases camera and image timezone is set to US Pacific as it should be.
    To me this seems like Aperture is somehow miss-interpreting the timezone when reimporting TIFFs.
    I have not tried importing JPEGs or PSDs back but I will and will report back...

  • Difficulty Importing a Properly Sized TIFF image (I think)

    Hello,
    I am having difficulty importing an appropriately sized TIFF image that is a screen shot from my film.  It seems to be a resizing issue of some sort.
    The TIFF image is a straight frame grab from my film, which is sized 1920 x 1080.
    here is the issue:
    The screen shot from the film has the reclining face buddha image overlay upon "the walk in the forest" perfectly centered in the frame of the film, but when I import that screen shot from the film, the mouth of the Buddha and chin is cut off on the left hand side.
    Any thoughts?
    Is this because I am making this into a smaller DVD frame in Standard Definition?
    Will it do this cutting off of the image for my entire film as well?
    Matt

    Hey Matt.  If you are using this tiff in a menu in your SD project, there is going to be some issues going from an HD size of 1920x1080 down to 720x480.  Is your project 4:3 aspect ratio or 16:9?  Generally you want your menus to match what the video elements are.
    If your encoded video elements are 4:3 (hard) letterboxed, then the menu should be 4:3 as well, although it could be 4:3 full frame.  No sense having black bars on your menu pages.  If this is the case, that 16:9 tiff image will be edge-cropped.
    Likely since your video was shot in HD, you want to have a widescreen dvd.  The source video will have to be encoded as 16:9 SD.  I usually make all my elements before bringing them into Encore.  For any menus, I start in Photoshop using the appropriate "Film and Video" preset.  Probably the 720x480 widescreen preset (1.21 pixel aspect ratio) will work for your project if it is indeed a 16:9 disc you want to make.  Being a 16:9 frame size, the tiff file will scale down almost perfectly into a 720x480 widescreen frame.
    I would suggest making a new file in Photoshop using the appropriate film and video preset.  Then open your tiff file in Photoshop and drag it into that one.  Scale it down and save.  That way when you bring it into Encore, the scaling has been done and you know what it is going to look like.
    Note that when you are working with files in Photoshop that are not square pixels, they will appear jaggy or squeezed depending on if you have pixel-aspect correction turned On or Off in the View menu.  The files are fine and will look good on a disc.  Also, I almost always change the viewer in Encore to 100% or some other whole number rather than "Fit".  Fit just seems to make things look terrible, especially text and the outer frame edges.  There is also the option to toggle pixel aspect correction On or Off in that viewer as well.
    Hope this helps.
    Cheers.

  • Two Different Imported TIFFs Show The Same Image in Premiere Pro

    I noticed sometime ago that some imported TIFFs with alpha channel are not showing the correct image. Recently I upgraded to Premiere Pro CC (for PC) to see if such issue was solved, however it is not.
    Basically just importing the TIFFs into the project panel results in Premiere showing the same text even though the actual TIFF files contain different text. This is quite bizarre. No other software (including FinalCut Pro) displays such odd behavior.
    I have uploaded the two TIFFs that replicate this issue consinstently here: https://drive.google.com/folderview?id=0B2IT1EAcyLlBZXRlMDkxNzY3d1U&usp=sharing
    To replicate, just create an new empty project and import these two TIFF files. You will notice that both show the same text within Premiere while outside they indeed show the different data.
    Anybody has any clues on why this is happening and on how to solve it?
    Thanks in advance for any help and clues.
    Valerio

    Thanks for your reply.
    At this moment we can't export PNGs with an Alpha channel so we are stuck with TIFFs.
    It is a bizarre issue though.
    Here is a Dropbox link for the images, seems Google Drive download links are buried deep:
    https://www.dropbox.com/sh/gktixc0cdbhr3oz/jPCI8yciY-

  • Iphoto photo import - best image type for max resolution (jpg vs tiff)

    What is the recommended image type for maximum resolution of photos brought into iphoto albums, since I will be enlarging them? (ie assuming everything brought into iphoto is set/reduced to a standard resolution, then jpg might allow more digital data for later enlargement; on the other hand tiff is often recommended for best resolution though it requires more space). Thanks, - D

    Thanks, Terence - OK, lets assume I shoot a 5-meg photo of a painting and adjust the paralax etc in photoshop so it is perfectly set inside the rectangular format. Now I want to import it into iphoto, knowing that I will use the crop tool to make two blow-up enlargements to go along with the original full-size image... total 3 related images of the artwork. As you mentioned these will eventually go into iweb as part of a series inside an album, with a hyperlink connecting the two enlargements to the full-size image... so viewers can tap to see finer detail and then go back to the overall composition. My question is, for the original photo image of the painting should I drag a 10-meg tiff into iphoto or a 2-meg jpg? (I do not know what importing the image into iphoto does to the original in terms of final image resolution and data size... Will a 2-meg jpg provide sufficient data to work with and enlarge via the cropping, or would the 10-meg tiff be better as a starting point? Or, if everything gets translated into a certain pre-ordained size anyway, would the tiff get watered down to, say, a 2-meg-size image anyway?) Thanks, - D

  • How to import and anlyze TIFF images in Lab View 7

    Is there any way to read images from a CCD camera in TIFF format with Lab View 7.0 for a subsequent intensity analysis? I would like to import the TIFF image and have it converted in an array of numbers...
    Thanks
    Kla

    Image Toolbox (http://www.geocities.com/gzou999/imgtool.htm) can read tiff files, and return image data for display in picture control.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

  • Fixed:  TIFF image display / import problems

    Hello All,
    I posted this in the discussion threads where I had previously discussed it with other members. But, felt that it would be good to share with everyone who is importing their photo's into the new iPhoto 6.
    I, like many others, have been having a terrible time getting my iPhoto collection imported into the new iPhoto 6 program.
    I have tried both the upgrade method (on a backup copy of my original library), and a fresh import of all my files.
    Without fail, all of my TIFF images gave me trouble. Some looked like squiggly lines. Some looked like a diagonally distorted image (like you see on old Televisions trying to tune in difficult stations). And, some just plain refused to work.
    All of my problem images look fine in the thumbnail (the library view). But, you quickly discover the problem when viewing the full-size image in the "edit" mode.
    Some of my TIFF images are 30 megabytes in size, and many of them are smaller files of a more typical size. I found that the smaller files were just as unlikely to work as the larger ones.
    And, while converting to JPEG may be an option, I didn't want to lose the depth and detail that TIFF offers (especially on pictures of documents / writing). The original TIFF images will offer greater detail when blown-up than compressed JPG files.
    All of these images worked fine in iPhoto 5, and display perfectly fine in every other program. But, iPhoto 6 just refused to display them properly.
    Well, I think I found the fix.
    Today I downloaded the new iPhoto 6.01 update. But, that didn't fix the problem either. So much for Apple fixing it.
    Anyway, I have been experimenting, and finally found a difference between images that worked and those that didn't.
    The images that worked, have an ICC profile embedded in them from the device that created the image (in my case my scanner).
    So, I set out to find out if simply removing the ICC profile would fix the problem.
    And, through my experimenting, I found that if I opened the image in another program, and then exported it as either a TIFF (the same format) or a JPEG that the resulting image would open in iPhoto 6 just fine.
    Further examination demonstrated that the ICC information was removed from the exported file.
    As I understand it, ICC is basically an image color correction / calibration tag. It enables different devices to properly display and print the image with the proper colors.
    Basically, each device has a color profile (scanner, monitor, printer, camera, etc.). This is to make sure that when you see something on the screen that it looks the same as when you print it out. Likewise, you want the image on the screen to match what the scanner and digital camera saw.
    So, these are essentially conversion tables to make sure that each device properly displays or prints the image as the original source "saw" it.
    Anyway, not wanting to manually strip this information from each file, I looked on the Internet for an automated solution. And, fortunately I found one.
    http://www.colormanagement.com/technicalresources/files_targets_and_utilities/mac_os_xscripts/
    The file you are looking for is "Mac Os X ColorSync Toolbar Script: Remove ICC profile". Click on the title just mentioned to download the script.
    It is a Macintosh Script that you simply download to your desktop (or anywhere else you would prefer). It is in a Stuffit Archive, so you'll need Stuffit Expander to decompress it (basically the Mac equivalent of a ZIP file).
    Once decompressed, you should see a "script" icon that is labeled "Remove Profile".
    Simply "drag" your original files and drop them onto this icon / script. The script will then remove the embedded ICC information from the image file.
    Once you have removed the ICC information from your image's file, try importing it into iPhoto 6 again. Then, see if it works
    It is important that you perform this on a backup / duplicate copy of your original files. You don't want to damage your only copy if something goes wrong.
    Now, one further note: If you do this, you may see the image looks different. In my case, the image is truer to the way it really looked when I scanned it in. The paper texture looks right now.
    If you want to do this while keeping the image's appearance the same as it looks now, then here's another way:
    Open the file in Apple's "Preview" program. This is usually the default image view.
    Then, do a "Save As" or "Export" to create a new copy of the image. If you perform an Export, be sure to set the image quality high or you may inadvertently reduce your pictures detail (especially if you export to JPEG).
    This essentially does the same thing. But, it will take more work if you have multiple images.
    Using the previously mentioned script, you should be able to drag and drop multiple files in a group.
    Anyway, I hope this helps the rest of you out.
    Let me know if it fixes the problem for you as well.

    Hello All,
    I have an update:
    It is definitely not a user account issue. I just completed a fresh install of OS 10.3.9 on my Mac Mini.
    I performed a fresh install (on a freshly formatted hard drive partition), and made the installation as bare as could be for the sake of preventing potential problems.
    I installed OS 10.3.9, and all the standard items in the usual OS 10.3.9 installation. I specifically left-out all the foreign language stuff, all the online programs (for other ISP providers), and misc. garbage.
    I also left off all the iLife programs (every iLife program) that came with the restore disks. I even left-off the original QuickTime installation. My thought here was that I wanted to make sure that there were no problems introduced by upgrading the original iLife Applications to iLife '06.
    So, this way, all the iLife '06 programs are installed fresh with no upgrading being performed.
    So, I installed this bare OS 10.3.9 installation. Then, installed all the updates that were available. I repaired permissions before and after each update. And, installed all the updates from downloads from Apple's website (Not using Software Update).
    After verifying that Software Update could not find any additional updates available, I then installed iLife '06.
    This required first installing Quicktime 7.0.4 from the iLife '06 DVD.
    After installing QuickTime, I then proceeded to install the iLife '06 package (remember that this is a completely new iLife install - not an upgrade install since I avoided installing the older versions).
    Once iLife '06 was installed, I then installed the recent 6.0.1 updates for all the iLife Apps.
    Then, I launched the iPhoto program for the first time to see if it would properly import my TIFF images.
    Unfortunately, it still displays them as if they are scrambled (like a blocked television / cable channel).
    So, with that done, I can confirm that it is not a corrupt file or another program on my system causing the problem. It is definitely a problem with iPhoto 6 / 6.0.1 and OS 10.3.9.
    Just thought I would post the update here for others to add to their knowledge-base. Maybe if we rule out potential problems we'll be able to find the actual solution.
    Again, this same set of images imports just fine into iPhoto 5 on OS 10.3.9 and 10.4.4. And, it also imports just fine into iPhoto 6.0.1 in OS 10.4.5. So, it is a problem apparently specific to OS versions 10.4.4 and older using iPhoto 6 or 6.0.1.
    As mentioned previously, these TIFF images can be made to import fine if I remove the ICC information from the image. So, that may provide some clue as to where the flaw is in the iPhoto 6 / 6.0.1 program.

  • Java returning incorrect values for width and height of a Tiff image

    I have some TIFF images (sorry, I cannot post them b/c of there confidential nature) that are returning the incorrect values for the width and height. I am using Image.getWidth(null) and have tried the relevant methods from BufferedImage. When I open the same files in external viewers (Irfanview, MS Office Document Imaging) they look fine and report the "correct" dimensions. When I re-save the files, my code works fine. Obviously, there is something wrong with the files, but why would the Java code fail and not the external viewers? Is there some way I can detect file problems?
    Here is the code, the relevant section is in the print() routine.
    * ImagePrinter.java
    * Created on Feb 27, 2008
    * Created by tso1207
    import java.awt.Graphics2D;
    import java.awt.Image;
    import java.awt.print.PageFormat;
    import java.awt.print.PrinterException;
    import java.io.File;
    import java.io.IOException;
    import java.util.Iterator;
    import javax.imageio.ImageIO;
    import javax.imageio.ImageReader;
    import javax.imageio.stream.FileImageInputStream;
    import javax.imageio.stream.ImageInputStream;
    import com.shelter.io.FileTypeIdentifier;
    public class ImagePrinter extends FilePrintable
       private final ImageReader _reader;
       private final int _pageCount;
       private final boolean _isTiff;
       //for speed we will hold current page info in memory
       private Image _image = null;
       private int _imgWidth = 0;
       private int _imgHeight = 0;
       private int _currentPage = -1;
       public ImagePrinter(File imageFile) throws IOException
          super(imageFile);
          ImageInputStream fis = new FileImageInputStream(getFile());
          Iterator readerIter = ImageIO.getImageReaders(fis);
          ImageReader reader = null;
          while (readerIter.hasNext())
             reader = (ImageReader) readerIter.next();
          reader.setInput(fis);
          _reader = reader;
          int pageCount = 1;
          String mimeType = FileTypeIdentifier.getMimeType(imageFile, true);
          if (mimeType.equalsIgnoreCase("image/tiff"))
             _isTiff = true;
             pageCount = reader.getNumImages(true);
          else
             _isTiff = false;
          _pageCount = pageCount;
       public int print(java.awt.Graphics g, java.awt.print.PageFormat pf, int pageIndex)
          throws java.awt.print.PrinterException
          int drawX = 0, drawY = 0;
          double scaleRatio = 1;
          if (getCurrentPage() != (pageIndex - getPageOffset()))
             try
                setCurrentPage(pageIndex - getPageOffset());
                setImage(_reader.read(getCurrentPage()));
                setImgWidth(getImage().getWidth(null));
                setImgHeight(getImage().getHeight(null));
             catch (IndexOutOfBoundsException e)
                return NO_SUCH_PAGE;
             catch (IOException e)
                throw new PrinterException(e.getLocalizedMessage());
             if (!_isTiff && getImgWidth() > getImgHeight())
                pf.setOrientation(PageFormat.LANDSCAPE);
             else
                pf.setOrientation(PageFormat.PORTRAIT);
          Graphics2D g2 = (Graphics2D) g;
          g2.translate(pf.getImageableX(), pf.getImageableY());
          g2.setClip(0, 0, (int) pf.getImageableWidth(), (int) pf.getImageableHeight());
          scaleRatio =
             (double) ((getImgWidth() > getImgHeight())
                ? (pf.getImageableWidth() / getImgWidth())
                : (pf.getImageableHeight() / getImgHeight()));
          //check the scale ratio to make sure that we will not write something off the page
          if ((getImgWidth() * scaleRatio) > pf.getImageableWidth())
             scaleRatio = (pf.getImageableWidth() / getImgWidth());
          else if ((getImgHeight() * scaleRatio) > pf.getImageableHeight())
             scaleRatio = (pf.getImageableHeight() / getImgHeight());
          int drawWidth = getImgWidth();
          int drawHeight = getImgHeight();
          //center image
          if (scaleRatio < 1)
             drawX = (int) ((pf.getImageableWidth() - (getImgWidth() * scaleRatio)) / 2);
             drawY = (int) ((pf.getImageableHeight() - (getImgHeight() * scaleRatio)) / 2);
             drawWidth = (int) (getImgWidth() * scaleRatio);
             drawHeight = (int) (getImgHeight() * scaleRatio);
          else
             drawX = (int) (pf.getImageableWidth() - getImgWidth()) / 2;
             drawY = (int) (pf.getImageableHeight() - getImgHeight()) / 2;
          g2.drawImage(getImage(), drawX, drawY, drawWidth, drawHeight, null);
          g2.dispose();
          return PAGE_EXISTS;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since version XXX
        * @return
       public int getPageCount()
          return _pageCount;
       public void destroy()
          setImage(null);
          try
             _reader.reset();
             _reader.dispose();
          catch (Exception e)
          System.gc();
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @return
       public Image getImage()
          return _image;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @return
       public int getImgHeight()
          return _imgHeight;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @return
       public int getImgWidth()
          return _imgWidth;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @param image
       public void setImage(Image image)
          _image = image;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @param i
       public void setImgHeight(int i)
          _imgHeight = i;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @param i
       public void setImgWidth(int i)
          _imgWidth = i;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @return
       public int getCurrentPage()
          return _currentPage;
        * <br><br>
        * Created By: TSO1207 - John Loyd
        * @since Mar 25, 2008
        * @param i
       public void setCurrentPage(int i)
          _currentPage = i;
    }Edited by: jloyd01 on Jul 3, 2008 8:26 AM

    Figured it out. The files have a different vertical and horizontal resolutions. In this case the horizontal resolution is 200 DPI and the vertical is 100 DPI. The imgage width and height values are based on those resolution values. I wrote a section of code to take care of the problem (at least for TIFF 6.0)
       private void setPageSize(int pageNum) throws IOException
          IIOMetadata imageMetadata = _reader.getImageMetadata(pageNum);
          //Get the IFD (Image File Directory) which is the root of all the tags
          //for this image. From here we can get all the tags in the image.
          TIFFDirectory ifd = TIFFDirectory.createFromMetadata(imageMetadata);
          double xPixles = ifd.getTIFFField(256).getAsDouble(0);
          double yPixles = ifd.getTIFFField(257).getAsDouble(0);
          double xRes = ifd.getTIFFField(282).getAsDouble(0);
          double yres = ifd.getTIFFField(283).getAsDouble(0);
          int resUnits = ifd.getTIFFField(296).getAsInt(0);
          double imageWidth = xPixles / xRes;
          double imageHeight = yPixles / yres;
          //if units are in CM convert ot inches
          if (resUnits == 3)
             imageWidth = imageWidth * 0.3937;
             imageHeight = imageHeight * 0.3937;
          //convert to pixles in 72 DPI
          imageWidth = imageWidth * 72;
          imageHeight = imageHeight * 72;
          setImgWidth((int) Math.round(imageWidth));
          setImgHeight((int) Math.round(imageHeight));
          setImgAspectRatio(imageWidth / imageHeight);
       }

  • How to retain the same resolution while croping a tiff image using jai api

    Hi all,
    I have designed a program to crop a tiff image.But after croping the tiff,the resultant file resolution is not the same as the original source file.
    In the program,the source file Nadeshiko_v1_02.tif has the resolution(X) of 1200 DPI and resolution(Y) has 1200 DPI pixels.
    But after croping the resolution of output file is 100 DPI.
    Please give me some idea on how to retain the same resolution.
    <code>
    package jai;
    import java.awt.Frame;
    import java.awt.image.RenderedImage;
    import java.awt.image.renderable.ParameterBlock;
    import java.awt.image.renderable.RenderableImage;
    import java.io.FileNotFoundException;
    import java.io.FileOutputStream;
    import java.io.IOException;
    import javax.imageio.*;
    import javax.imageio.stream.ImageOutputStream;
    import javax.media.jai.Interpolation;
    import javax.media.*;
    import javax.media.jai.JAI;
    import javax.media.jai.PlanarImage;
    import javax.media.jai.RenderedOp;
    import javax.media.jai.widget.ScrollingImagePanel;
    import com.sun.media.jai.codec.FileSeekableStream;
    import com.sun.media.jai.codec.SeekableStream;
    import com.sun.media.jai.codec.TIFFEncodeParam;
    import javax.media.jai.OperationDescriptorImpl;
    import java.io.*;
    import java.util.Iterator;
    import javax.media.jai.operator.*;
    // import javax.media.jai.widget.ScrollingImagePanel;
    public class crop {
              /** The main method. */
    public static void main(String[] args) {
    /* Validate input. */
    /* if (args.length != 1) {
    System.out.println("Usage: java JAISampleProgram " +
    "input_image_filename");
    // System.exit(-1);
    float a=(float) 70.3;
    float b=(float) 70.4;
    float c=(float) 3100.3;
    float d=(float) 5522.4;
    * Create an input stream from the specified file name
    * to be used with the file decoding operator.
    String TIFF="TIFF";
    FileSeekableStream stream = null;
    try {
         stream = new FileSeekableStream("D:\\tif images\\Nadeshiko_v1_02.tif");
    // stream = new FileSeekableStream("D:\\tif images\\Nadeshiko_v1_01.jpg");
    } catch (IOException e) {
    e.printStackTrace();
    System.exit(0);
    // Load the source image from a Stream.
    RenderedImage im = JAI.create("stream", stream);
    RenderedImage image2= CropDescriptor.create(im, a, b, c, d, null);
    ScrollingImagePanel panel = new ScrollingImagePanel(image2, 100, 100);
    // Create a frame to contain the panel.
    Frame window = new Frame("JAI Image Cropping");
    window.add(panel);
    window.pack();
    // window.show();
    // Define the source and destination file names.
    // String inputFile = "D:\\tif images\\Nadeshiko_v1_05.tif";
    String outputFile = "D:\\tif images\\Nadeshiko_v1_04.tif";
    // Save the image on a file. We cannot just store it, we must set the image encoding parameters
    // to ensure that it will be stored as a tiled image.
    TIFFEncodeParam tep = new TIFFEncodeParam();
    tep.setWriteTiled(true);
    tep.setTileSize(80,80);
    JAI.create("filestore",image2,outputFile,"TIFF",null);
    try {
                   stream.close();
              } catch (IOException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
    </code>
    Thanks,
    Sanat Meher

    Try the following,
    TIFFEncodeParam tep = new TIFFEncodeParam();
    // Create {X,Y}Resolution fields.
    TIFFField fieldXRes = new TIFFField(0x11A, TIFFField.TIFF_RATIONAL,
                                        1, new long[][] {{DPI_X, 1}});
    TIFFField fieldYRes = new TIFFField(0x11B, TIFFField.TIFF_RATIONAL,
                                        1, new long[][] {{DPI_Y, 1}});
    tep.setExtraFields(new TIFFField[] {fieldXRes, fieldYRes});

  • How to edit 16bit TIFF image sequence file in FCP?

    Dear all,
    I have a number of 16 bit TIFF image sequence files (2048 x 1024 resolution) - some of them are RED footage, and others came directly from our f/x guy. We are going into a color correction session in a post house and we've been asked to provide a sequential 16 bit TIFF image sequence of the edited time line.
    I need to do a cross dissolve b/w most of the clips I have. I have created image sequence QT movie (reference files) from the TIFF images. Though they play fine in QT player, when I try importing into FCP, I am met with a "general error". I tried both dragging it into QT, as well as File --> Import.
    I am wondering what can I do to get these clips into FCP in order to apply the cross dissolve transitions I need. Is this a problem relating to the 16bit nature of the TIFF files?
    I tried exporting the TIFF image sequence standalone QT movie, and those imported fine. However, I have a feeling that the standalone movie conversion also decrease my bit depth from 16 to 8. (When I do my final TIFF output from FCP after dissolves / transitions had been applied, each TIFF file is now 8 MB instead of 12 MB, hence my suspicion that the bit depth is adjusted).
    Are there any settings I am missing, or does FCP simply don't support 16 bit image sequence reference file. As a test, I had also converted all my TIFF to jpg, and created jpeg image sequence reference file. These reference QT file can be successfully imported to FCP and I can edit them as if they are a clip.
    If FCP is not able to handle these files, what are my other options? After Effects?
    Any help is appreciated.
    Thank you.
    Michael
    <Edited by Moderator>

    As far as I know, both FCP and Color only support up to 10 bit color, which is 1024 levels for each color channel, more than enough for avoiding color banding.
    If you need 16 bit for sure, I believe AE will support 16 bit output. Another 16 bit application would be the extended version of Photoshop, which has some limited time line capability.

  • Crashes while importing TIFFs.  Also, how to import directly into an album?

    Just got Aperture last night in the mail. Upgraded to 1.1.1.
    I have about 250 CDs with TIFF images that I've created over the years. The TIFF files were created by a Nikon film scanner. Some of those images were later re-touched and re-saved using Photoshop.
    In any event, I started importing all those CDs into Aperture to consolidate all my photographs in one place. On the first CD, Aperture crashed unexpectedly for no reason. The Aperture database would also get corrupted and I would have to delete it, and start from scratch.
    Here's what I discovered. If I wait for Aperture to generate a thumbnail of all the images in the CD before I click on the "Import All" button, there are four images in the CD for which Aperture does not generate a thumbnail. Furthermore, if I tried to import the same CD into iPhoto, all files but those four would get imported. At least iPhoto doesn't crash, and after the import is finished it would tell me that four photographs could not be imported because the format was not recognized. The interesting thing is that Photoshop can open every single file on the CD (again, all of them are TIFF images)
    So my (painful) workaround is to import all my CDs into iPhoto first, and then import into Aperture from iPhoto, which works very well. That way the Aperture repository doesn't get corrupted.
    So, question 1: does anybody know if there's a special setting in Aperture that would stop it from crashing and gracefuly skip over any photographs that it can't recognize?
    Question 2: I want to import every single CD into its own album so I later know what CD I can find the image on. Aperture seems to import always onto the project, not the album. Is there a way around this?
    When I import into iPhoto, I create an empty album and then drag the files from the CD onto that album. If I then import the iPhoto album into Aperture, Aperture automatically creates an album, which is nice. I'd love to do the same but with iPhoto out of the picture (excuse the pun). That would speed up the import process tremendously.
    Thanks for your help,
    Julian

    Are there two questions here?
    1. You can indeed create an album under a Project in advance and Import direct to that. One Album per CD? Works fine. Just point the Import Arrow at the Album. NOTE: the Masters are actually held in the Project (this is true across Aperture) and Pointers are held in the Album .... but the effect is of Albums with photos > Project containing all the photos.
    2. These TIF files are not corrupt, if Photoshop or iPhoto opens them. This has got to be an Aperture bug and I have the same issues with TIF's. Created a thread about it, so I hope the Aperture development team did read it (please, please, please). You could convert in Photoshop to .PSD vs. resaving (unless this is what you did) as I haven't noted this problem with .PSD files

  • Imported JPEG images are too light

    Imported JPEG images appear lighter/brighter than the scanned image.
    How can I make JPEG images appear with the correct lightness/brightness so they look like the actual book or magazine from which they were scanned?
    Using Apple's "Preview" to look at a JPEG- everything looks fine. But when a JPEG is imported into Motion 4.0.3 (and/or Final Cut Pro 7.0.3), the image appears lighter/brighter, as if it's washed out. To see if this is just the way a JPEG appears in Motion and not how the finished product will be, I exported a Motion project with one or more JPEGs as a QuickTime movie. The QuickTime movie does not bring the JPEG image(s) back to the "correct" lightness/brightness as the scanned image.
    Settings used:
    JPEG image, using a CanoScan LiDE 210 scanner, Color Space: RGB, Color Profile: sRGB IEC61966-2.1, current Monitor Gamma setting on the scanner is set to 1.80
    How can I make JPEG images appear in Motion (and Final Cut Pro) so they are true to the source from which they were scanned?

    Does it do the same thing when you use TIFFs?
    Patrick

  • Help with TIFF image sequence frame rate?

    I'm working on an animation sequence, its a 24p project.  Whenever I import an image sequence, Premiere automatically interprets this at 29.97 (though, per the help files, it should automatically interpret at the project frame rate, but it's not).  In the project panel, I use interpret footage so that it interprets at 24p.  However, when I bring this image sequence into the timeline it shows at the right duration, but the end of the sequence is cut off (essentially, premiere is still reading in at 30p, but gives it the duration of 24p).
    CS4 is the first version I've had this problem with.. usually, I just bring in the image sequence and it's fine.
    Any suggestions?
    Thanks.

    Hi, I have the same problem as my workflow is to import R3D into AE CC and render it into Tiff sequence. At first I had changed every setting to 24, and it rendered out choppy and clipped off a few frames in the end.
    Now I have tried this
    Once you import Tiff, right click> Interpret Footage > Main
    Then you will see black box. In this column box, there is Frame Rate column, then tick Assume this frame rate: 24 frames per second.
    You have to type in 24 yourself, then it works out fine.
    My guess is that Tiff is sequence image, and it DOES NOT have frame rate. So you have to tell AE to assume the imported image sequence's frame rate. Otherwise it always assumes 30 by default.
    Hope it works.
    DDH111

  • I imported 635 images into an iPhoto album so that I can share them via a photo-stream. However, iPhoto says there are only 600. When I try to add the missing images it says they are already there. Why can i not see these images in iPhoto?

    I imported 635 images into an iPhoto album so that I can share them via a photo-stream. However, iPhoto says there are only 600. When I try to add the missing images it says they are already there. Why can i not see these images in iPhoto?

    Generally I would not use Facebook for sharing any photos, it compresses the photos substantially, and when you have shadows and dark colours you get visible "bands" where there should be subtle gradients, ie at sunsets and sunrises.
    It sounds like you are using two methods to upload to Facebook:
    1. Sharing from within Aperture, which basically syncs Facebook with your Aperture album, so any changes made at either end gets synced, hence the deletions from Albums, although the original file should still be in your library, just removed rom the album. It is like a playlist in iTunes.
    2. Exporting pics and uploading to Facebook from the browser.
    I am not sure how method 1 gets compressed, but I know that uploading hi-res jpegs to Facebook using method 2 results in poor quality images.
    I wouldn't even bother comparing option 1 or 2, and they will both be poor images once you view them on Facebook, as opposed to viewing uploaded images on proper image sharing / hosting sites.
    Your problem is not with Aperture, it is using Facebook for showing your work.
    If you export pics form Aperture at high res jpegs or TIFFs your images will be fine.
    If you insist to use Facebook as your way to share your work, then your workflow should be this:
    1. Right click images you want to share.
    2. Select Export version.
    3. Export as 100% size and ensure the export settings are set at 100% quality.
    4. Upload this pic into Facebook.
    This will get you the best image size and resolution on Facebook.
    See how you go.

Maybe you are looking for