Forum Replies Created

Page 565 of 668
  • Michael Gissing

    March 3, 2010 at 10:47 pm in reply to: Removing dirt from still images

    I would do it in Photoshop before importing into FCP. That way you have both the stills and the video fixed. If you fix it in FCP, then the still are still dirty.

    Also Photoshop is better equipped for that sort of work.

  • Michael Gissing

    March 3, 2010 at 9:05 pm in reply to: Can you stretch without blowing up?

    Andy Mees to the rescue

    https://web.mac.com/andymees/Free_and_Easy/main/Entries/2008/3/3_Andy%E2%80%99s_Elastic_Aspect.html

    Another great free plugin – thanks Andy!

  • If your camera shoots 1920 x 1080 then that is the correct size for your sequence. In Photoshop you use the same aspect ration which is true 16:9 so square pixel.

    I don’t see what the issue is here as you are not working with anamorphic sequences. HD sequences in FCP are true 16:9.

  • Michael Gissing

    March 3, 2010 at 8:11 pm in reply to: avchd, prores and interlacing

    If your output is digi beta, then your final is standard def and therefore interlaced for broadcast. Do not deinterlace.

    I suspect your problems are in the way you are connecting to your monitor. You need a proper interface like Kona, Matrox or Decklink to output to an external monitor.

  • Michael Gissing

    March 3, 2010 at 4:59 am in reply to: anamorphic pal widescreen 16.9 prset

    Hope,

    Happy to help. Yes your 1024 graphics will display correctly in the anamorphic timeline as they are the square pixel version of the 720 anamorphic as you have realised. Not sure what the blue line is. Does it show up on the output file?

    In Compressor, you can change the pixel aspect to 720 x 405 which is true 16:9 square pixel by going to the geometry tab in the inspector and setting the frame size you want. Once you have your favorite settings, save that to use for all exports from this FCP setting. Do some tests.

    If your source clips are all progressive, then yes, set field dominance to none and make sure the clips are also set to none.

    If you Googled Michael Gizzing, then that is someone else. I am Gissing and yes I have some credits and enough knowledge to be a total nuisance sometimes.

  • Michael Gissing

    March 3, 2010 at 12:56 am in reply to: FCP 7.0 Crashes when using text tool

    No problem here with a Kona3. Try unistalling the Decklink drivers completely and see if you can make it crash on using text tool. If not then it might be a Decklink problem.

    Have you updated your FCS3 and OS since install? There was an OS update to 10.6.2 and FCP went to 7.0.1 a while ago.

  • Michael Gissing

    March 3, 2010 at 12:51 am in reply to: FCS3 to Avid gamma shift – need help!!

    Did you try 10 bit uncompressed? ProRes is a 10 bit file.

    Also are you judging the gamma on both FCP & AVID on an external monitor?

  • Michael Gissing

    March 3, 2010 at 12:48 am in reply to: anamorphic pal widescreen 16.9 prset

    Every system is different depending on I/O cards and versions.

    Choose ProRes 422 720 x 576. Then go to the sequence settings tab and duplicate, naming it as anamorphic then open it up. Check the anamorphic box and close.

    You now have you ProRes422 PAL 48 Khz Anamorphic easy setup which you then save as a custom setup.

  • Michael Gissing

    March 3, 2010 at 12:04 am in reply to: Black Screen Keyer

    As was mentioned earlier, try a luma key.

  • Michael Gissing

    March 3, 2010 at 12:01 am in reply to: rendering General Error in FCP-HELP!!!

    Check you timeline for anything that has big pixel aspects. Prime culprit is usually stills that have bigger than 4K pixel sizes.

    Aslo you may have a clip that is corrupt. Render small sections or even clip by clip to see if you can isolate the problem clip(s).

    The very helpful general error comes up for this specific problem so try to sort that first.

    Otherwise it may be a corrupt sequence, preference problems etc.

Page 565 of 668

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