Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Can’t Import .tif files

  • Can’t Import .tif files

    Posted by Rob Grauert on April 9, 2010 at 1:22 pm

    I’m updating a project that was made last year. I was having problems with their still images, so I checked the size and they were HUGE, and I thought it was making FCP angry. So I opened it in Photoshop, flattened the layers, scaled down, and added an alpha channel. Then I saved as a .tif.

    That has always been my way of bringing stills into FCP, and I’ve never had problem until today.

    The original problem I was having – the reason why i brought them into Photoshop to begin with – was that the image seemed to have a layer turned on that should not have been turn on. It was all scratchy looking and appear behind the subject of the image. It’s weird though because there is no scratchy looking layer when I open the .tif in Photoshop. But I wanted to flatten the layers and add the alpha anyway to see if that would fix the problem.

    Well now that I’ve added the alpha, FCP won’t let me import the image. It says “Error: Unknown File Error.” I can import the image if I delete the alpha, but then the scratchiness behind the subject of the image still appears.

    The file is NOT CMYK and the dimensions are approximately 1280X720 at 72ppi. So the image isn’t too big for my timeline either. I also have my timeline compressor set to ProRes (not HQ).

    Any other ideas of what the problem may be?

    Robert J. Grauert, Jr.
    http://www.robgrauert.com
    command-r.tumblr.com

    David Callahan replied 15 years, 11 months ago 6 Members · 12 Replies
  • 12 Replies
  • Alfi Randy

    April 9, 2010 at 4:10 pm

    If you want to save it with an alpha channel, save it as a .png not as a .tiff.

  • Rob Grauert

    April 9, 2010 at 4:14 pm

    ok i’ll give that a shot. That’s strange though, I’ve never had a problem using alpha channels on .tif. In a tutorial on the COW, Rich Harrington even suggests using the .tif

    Anyway…thanks!

    Robert J. Grauert, Jr.
    http://www.robgrauert.com
    command-r.tumblr.com

  • John Pale

    April 9, 2010 at 4:26 pm

    Alpha channels are supported with Tif… No problem there.

    Layers are not supported with Tif…
    LZW Compression can cause problems.
    32bit might cause an issue too.

  • Rafael Amador

    April 9, 2010 at 4:34 pm

    Shouldn’t be any problem for a TIIF, but if it doesn’t work I would try with PNG or even PS.
    The conversion is lossless.
    rafel

    http://www.nagavideo.com

  • Alfi Randy

    April 9, 2010 at 5:57 pm

    Yes, it shouldn’t be a problem with a .tiff but it is in his case.

  • Rob Grauert

    April 9, 2010 at 6:57 pm

    the .png works! who woulda thunk?

    Strange…I really have no idea what the problem was with the .tif. Like I said, it’s been the norm for me, but it’s nice to know I can use .png if I have problems again in the future. I had no idea .png supported alpha channels.

    Thanks guys!

    Robert J. Grauert, Jr.
    http://www.robgrauert.com
    command-r.tumblr.com

  • Rafael Amador

    April 10, 2010 at 11:23 am

    You can also use TG files.
    All of them hold the same 8b RGB.
    PNG is an older format and supports less options, but this makes the files more simple and easier to manage.
    Normally I use PNG for stills and still with Alpha.
    Photoshop only for the layered images.
    rafael

    http://www.nagavideo.com

  • Gary Adcock

    April 11, 2010 at 5:19 am

    “All of them hold the same 8b RGB.”

    I don’t understand where people get this stuff.

    the Tagged Image File Format (tiff) supports up to 32bit CMYK and 24Bit RGB imagery.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows for the Digitally Inclined
    Chicago, IL

    https://blogs.creativecow.net/24640

  • Rafael Amador

    April 12, 2010 at 2:00 am

    32b CMYK, means 8b per channel.
    24b RGB, means 8b per channel.
    I think you are forgetting the most basic maths, Gary:-)
    Some of these formats can support more than 8b per channel.
    If I’m not wrong PNG supports 16b per channel, but that’s nothing for FC, that only supports 8b RGB.

    Gary, this question is about a normal scenario where people works with normal software and hardware.
    Nothing about these kind of special workflow that only people like you are able to fallow and understand.
    You should concentrate in posts about 10b up workflows.
    8b is too little for you.
    Happy New Year.
    rafael

    http://www.nagavideo.com

  • John Pale

    April 12, 2010 at 4:16 pm

    Actually Tiff does support up to 32bit PER CHANNEL…not just 32 bit total..

    From the Photoshop CS4 Manual…

    TIFF

    Tagged-Image File Format (TIFF, TIF) is used to exchange files between applications and computer platforms. TIFF is a flexible bitmap image format supported by virtually all paint, image-editing, and page-layout applications. Also, virtually all desktop scanners can produce TIFF images. TIFF documents have a maximum file size of 4 GB. Photoshop CS and later supports large documents saved in TIFF format. However, most other applications and older versions of Photoshop do not support documents with file sizes greater than 2 GB.

    TIFF format supports CMYK, RGB, Lab, Indexed Color, and Grayscale images with alpha channels and Bitmap mode images without alpha channels. Photoshop can save layers in a TIFF file; however, if you open the file in another application, only the flattened image is visible. Photoshop can also save notes, transparency, and multiresolution pyramid data in TIFF format.

    In Photoshop, TIFF image files have a bit depth of 8, 16, or 32 bits per channel. You can save high dynamic range images as 32‑bits-per-channel TIFF files.

    I would not recommend trying to use it FCP…and this may be why the OP’s file won’t import properly…as I indicated in my earlier posting.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy