Forum Replies Created

Page 77 of 1230
  • Just duplicate the picture (without the ChromaKey filter on) a new layer on top, and crop or use a mask (4/8 Points Garbage Matte) to isolate the problematic area.
    rafael

    http://www.nagavideo.com

  • Rafael Amador

    December 16, 2012 at 4:46 pm in reply to: BDMV files back to FCP

    If you have the H264 or MPEG-2 files, you may try to cut them on a time-line with the same setting.
    Might work.
    rafael

    http://www.nagavideo.com

  • Rafael Amador

    December 16, 2012 at 4:37 pm in reply to: Will re-transcoded media link in FCP7?

    But what for you wan’t to relink to the original files?
    If you were working with some heavy stuff (RAW, Uncompressed), makes sense editing with proxy files, but shooting in some kind of compressed codec and editing in Prores after L&T, I don’t see the point to relinking nothing.
    rafael

    http://www.nagavideo.com

  • Rafael Amador

    December 14, 2012 at 12:44 pm in reply to: FCP weird white frame problem

    Lisa,
    MP4 is not supported by FC, so you can expect whatever funny (no funny) behavior.
    rafael

    http://www.nagavideo.com

  • Rafael Amador

    December 14, 2012 at 8:40 am in reply to: Editing .moov with final cut pro

    QT can’t “export to” but still playing most legacy codec.
    In case of problems, as suggested, change the extension or delete it.
    rafael
    PS: “.moov” sounds like a QT movie from the COW.

    http://www.nagavideo.com

  • Rafael Amador

    December 14, 2012 at 8:36 am in reply to: FCP weird white frame problem

    Hi Lisa,
    Normally you get a full white screen when the codec of the clip is not present on your computer.
    Which kind of codec are you using for exporting?
    rafael

    http://www.nagavideo.com

  • [William Carr] “29.97 for all. The 23.98 won”t suffer much by adding frame”
    Better adding Pulldown.
    Instead of adding full frames, will add fields and will look less choppy.
    Rafael

    http://www.nagavideo.com

  • [Grant Wilber] “I do use the 3D filter in the perspective plugin folder. I tried the crop but it doesn’t crop at the same angle that the video is altered. So if the video is tilted at an angle the crop will just crop a edge straight across rather than at an angle. Don’t know if there is a way to crop differently.”
    Motion effects (crop) are applied after filters on FC pipeline, so if you want to crop, you must crop, nest the clip and apply the 3D filter on the nest.
    But is not about cropping.
    rafael

    http://www.nagavideo.com

  • You can also apply a it of gaussian Blur to the picture Alpha channel.
    Make sure that you set “Render in High Precision” and “Render Motion Effects BEST”.
    Avoid using the “Rotation” of te Motion tab. That force lower rendering quality (Linear).
    Instead, use the 3D filter or, better, the Andy’s “Better 3D”.
    rafael

    http://www.nagavideo.com

  • Rafael Amador

    December 13, 2012 at 2:18 am in reply to: Compression, rendering and exporting FCP or QT

    [jay agoglia] “SO even if you choose 10 bit settings in “FCP export using QT conversion” the footage is really being crushed to 8-bit? Why would we be able to select these parameters if not really using a 10-bit processing?”
    When you go through “QT Conversion”, is not any more FC, but QT who process, and as I said (and Apple too), QT player is limited to 8b.
    QT Player only keep stuff in 10b when you “Save as..”. Never on “Export”.

    [jay agoglia] “If you had a QT 10bit uncompressed that came from Adobe premier which QT recognized as “none” “
    10b Unc and NONE are completely different stuff.
    10b Unc is 10b YUB. NONE is uncompressed 8b RGB.
    If you are dealing with 10b Unc stuff edit on a 10b Unc sequence and export with current settings (QT, no QT Conversion). The rendering will be done in 10b Floating Point (High Precision), and your stuff will keep 10b Unc.
    rafael

    http://www.nagavideo.com

Page 77 of 1230

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