Forum Replies Created

Page 2 of 2
  • If you configure your keyboard with a render keystroke (I use the tilde key beside the 1 key), it won’t autosave at the end of the render. That makes no sense but that’s the way it is.

    Two notes on that trick:

    First, also put the ALT key on your render keystroke so that it doesn’t ask you to select a render drive everytime you render.

    Second, the render behavior is a bit different from using “Render in to out” or “render at position”. If you have selected clips in the timeline, it will render those clips regardless of any track selection or mark in mark out. If you have nothing selected, it will act like “render at position”.

  • Annaël Beauchemin

    July 21, 2010 at 9:34 pm in reply to: Sorenson and Avid – Levels problems

    MainConcept. I am aware of the QT H.264 gamma problem.

  • The post suggest rendering to the uncompressed NONE codec and essentially disabling AE’s color management. But this creates HUGE files that I need to render again when I use them in my FCP timeline.

    What i’m trying to acheive is a complete ProRes workflow where I can composite both REC709 and sRGB material without any gamma shift inside my comp and outside my comp when I render.

    According to Adobe (here), i’m supposed to be able to work with ProRes in and out of AE without any shift.

    I’m confused..

    Here’s my specs:

    AE CS3
    FCP 6.0.6
    QT 7.6.4
    10.5.8 on Powermac G5

  • I’m ressurecting this thread from the dead..

    I get the same gamma shift when round tripping from fcp to ae.

    Funny thing is that if I generate a colorbar in fcp, export it and import in ae then render out to fcp, it’s fine. This is in a prores timeline.

    If I use the same timeline with my prores camera clips, it ends up gamma shifted. What a nightmare!

    My prores test clips were transcoded to prores using Log and Transfer from an HMC-150 AVC HD camera.

    All clips are imported to AE using REC 709 colorspace, REC 709 project, Prores REC 709 output.

    Seems like a bug to me…

    Anybody has a fix?

  • Annaël Beauchemin

    February 4, 2010 at 5:07 pm in reply to: G5 video card- FCS2 HELP

    PCI cards are not supported by either Quartz Extreme and Final Cut. It is explicitely written in the System Requirements.

    All G5 came with AGP videocard that supported QE. Maybe the previous owner removed the AGP card because it was faulty and decidec to save money with a PCI card?

    The cheapest compatible card you could get would be an ATI 9600 XT which is what the computer probably came with. Search on ebay, there are plenty for sale at around 100$.

  • Annaël Beauchemin

    January 26, 2010 at 4:56 am in reply to: Original IO problems

    thanx, that was it.

  • Annaël Beauchemin

    January 17, 2010 at 7:43 pm in reply to: HD Monitoring?

    [John J. Cooney Jr.] “Even with my Mojo rebate, DX is brutally expensive; and it doesn’t look like Avid has plans on making a stripped down/ cheaper version of the DX. “

    I would say that the MojoDX is already stripped down… but cheap it is not.

    On the newer MC (4.0.x to 4.0.5) you can get a pretty decent downconvert of HD via the Mojo but it requires a relatively fast system. On the XW8200 I work on, it drops frames when I activate the function (“High quality downconvert”) so I don’t know if your laptop would be enough.

    If you really want full HD monitoring, until Avid release a cheaper Mojo, you need ot buy the DX.

  • I have a Flip MinoHD which probably uses the same file format as the UltraHD.

    On my G5 at home (first generation dual 2Ghz), it works fine except that it cannot play the files without dropping frames. You have to convert them to another format such as ProRes or the Intermediate codec using a tool such as MPEG Streamclip.

  • Annaël Beauchemin

    November 5, 2009 at 5:26 pm in reply to: HDW-1800 Reference

    That makes sense.

    Thank you, Bob!

Page 2 of 2

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