Forum Replies Created

Page 2 of 5
  • Gustavo Mendes

    May 15, 2010 at 11:17 am in reply to: Proper setup to do 444 RGB in Final Cut

    Seems to me that it’s the old quicktime gamma bug with RGB footage. If you capture ProRes 444 I would advise you to duplicate the Kona setup, change the setting in the advance button where it says gamma correction to “none”.

    What it does is it tells FCP that your captured file has a RGB gamma 2.22, which, I assume, is the tape gamma. If you don’t do it QT will think the file is 1.8 and it will apply a gamma correction in FCP, causing the gamma shift.

    Do a test and see if it helps, that basically solved all my issues with gamma shifts in FCP. I have not captured files as Uncompressed since the release of the ProRes, but if you need to, trying changing the setting in the User preferences>Editing tab where it says “Imported Stills/RGB Video gamma” to 2.22.

  • Gustavo Mendes

    May 14, 2010 at 5:20 pm in reply to: instant RED on a MacBook Pro – kit spec

    I have not tested the new laptops, but the old Core 2 models will not handle Red footage really well in FCP.

    The Aja IO HD can help you to monitor, but the picture size will be non standard ( as you are aware) and the laptop will have to do the first pass of th scaling, and that usually does not go really well.

    I always used Esata drives, but might be doable on FW 800, I\’m not sure about it.

  • Gustavo Mendes

    May 12, 2010 at 5:34 pm in reply to: PS3 TO FCP capture

    HDMI is a no go, unfortunately. You’ll have to get a capture card and use component for video.

    For audio, it depends on what kind of equipment you are gonna using. If you have the right decoders you can use the optical out, or you can just use stereo from the RCA cables.

  • Have you tried using the timecode tab on the AJA control panel? You can downrez and have your timecode right IF you use that tab. It controls what timecode you’re sending to the deck. Just make sure the timecode int the tab is the same as the in point of your sequence in your timeline.

  • Gustavo Mendes

    May 6, 2010 at 4:02 pm in reply to: Multiclip nightmare

    After some tests I did, I would say to not use the LT codec, something is not right about it. It crashes my FCP and uses more processing power than the other codecs.

    It’s easy for me to say for you to recapture as 422 or Proxy, but I do not know how far along you’re into the gig…

  • Gustavo Mendes

    May 5, 2010 at 4:47 pm in reply to: Problem with IO HD and ProRes LT

    Oh well, new laptop is the solution, it seems. Thanks for the help Gary.

  • Gustavo Mendes

    May 5, 2010 at 4:39 pm in reply to: Problem with IO HD and ProRes LT

    Firmware is updated. Had I chat with Aja yesterday, according to them the codec is “heavier” and takes more processing power than the others….. Not exactly what I imagined….

  • Gustavo Mendes

    May 4, 2010 at 2:19 am in reply to: Problem with IO HD and ProRes LT

    Forgot to write that, everything is up to date, and I reinstalled the drivers.

  • Make sure your QuickTime export settings ProRes advanced tab says gamma correction “none”, that was was destroying my renders for a while…

  • Gustavo Mendes

    March 30, 2010 at 6:17 pm in reply to: MacBook Pro stuttering on viewing in FCP

    Solid state drives( https://en.wikipedia.org/wiki/Solid-state_drive ). Convert one file and test the performance. Files that come off of the camera are H.264 based and really heavy for playback.

    I would suggest ProRes ( regular or HQ ), but other codecs can work as well.

Page 2 of 5

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