Forum Replies Created

Page 2 of 18
  • Seawild

    April 18, 2009 at 9:05 pm in reply to: New MacPro and REDRushes

    Hey Guys,

    Thanks for the info! Michael Kammes article was an interesting read..

    Would having more RAM increase the rendering speed you think?

    It’s to bad, we can’t manually control Processor allocation like the old days..

    I find that REDRushes only uses 1/2 the processor power even when it’s the only APP. running.

    Chris

  • Seawild

    April 4, 2009 at 10:12 pm in reply to: Red to Avid Workflow

    Thanks for the help guys!

    I have sent the editor a DNxHD 36 file and am waiting to see if he would like/able to go that route.

    The quicktime I made has the original TC info, but I have read that AVID might not read the QT timecode.. MetaCheater might be a work around I guess..

    But, I am now looking into using Automatic Duck. This workflow might go something like this;

    1) Render 23.98 HD ProRes HQ out of REDrushes.

    2) Sycn Prores to Audio in FCP – Organize clips into Scene and Take Bins

    3) Export as AVID project render media as 23.98 DV25 MXF Files or 14:1

    4) Editor completes cut in AVID Composer and use AVID OMF to online back to Prores in FCP.

    Waht ya think?
    thx,
    Chris

  • Seawild

    April 4, 2009 at 3:10 am in reply to: Red to Avid Workflow

    moo,

    Will rendering R3D in MetaFuse eliminate the long time to import DNx QT files into Avid? Or is this just like using REDrushes?

    thx!

  • Seawild

    April 4, 2009 at 3:04 am in reply to: Red to Avid Workflow

    Michael,

    >Ouch – You can certainly work in SD, but I would suggest 14:1 and not DV25. You will need to use M

    yes.. ouch. thanks. What is “M”? Isn’t 14:1 a Meridian thing? He said he wants DV25 specifically.

    >Import ALE, batch import the QT and select 14:1. His system will support HD and editing 1080p/23.976 works with the version he is running.

    23.976. That is what I wanted to hear, no reason to deal with pull-down in this day and age.. But can he use DNxHD files on a 3.1.2? And how can he avoid the 6:1 import time? How about 720P 60DNx..?

    Thanks much!
    Chris

  • Seawild

    April 4, 2009 at 12:46 am in reply to: Red to Avid Workflow

    Hi Terence,

    Thanks for the info.. Well this project just got a little more complex.

    Our Editor in New York is on a Composer 3.1.2 MoJo (G5 Dual 2.6) and wants to edit in SD because he thinks he can’t handle DNxHD files.. I’m not sure on this? He is asking for 5:1 DV25 MXF files.

    I was imagining that will be pulling everything together with Composer 3.5.

    The editor mentioned that he would put the project together in SD in FCP and use AutoDuck to convert it to an Avid project. Not so sure on this either..

    Any help would be awesome..

    thx,
    Chris

  • Seawild

    April 3, 2009 at 10:11 pm in reply to: Red to Avid Workflow

    Hi!

    Another question.. Does anyone know if the New Mac Nahlem’s work with Avid? Or does anyone have a link with the Avid system requirements?

    thx,
    Chris

  • Seawild

    March 4, 2009 at 1:32 am in reply to: HDCAM Question

    Hi Mark,

    It’s not moot.. it’s moooooo : ) (academic)

    Chris

  • Seawild

    March 4, 2009 at 1:27 am in reply to: HDCAM Question

    So if I understand you correctly..

    I’m going to lose around 25% of my Luma info and about half of my color info… right? ouch.

  • Seawild

    March 3, 2009 at 11:39 pm in reply to: HDCAM Question

    Thanks Dino,

    So when I playback a 10 bit ProRes 422 (HQ) and record to an 8 bit 3:1:1 HDCAM… How much, if anything, am I loosing..

    And is there any truth to HDCAM playing back at 4:2:2?

    I’m just curious.

    thx,
    Chris

  • Seawild

    February 28, 2009 at 12:42 am in reply to: Title safe in 16:9 & 4:3

    Yo Andy!

    This is a sweet little tool! It really is the best way to know if your stuff was shot protected for 4×3.

    Keep up the good work!!

    Chris

Page 2 of 18

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