Forum Replies Created

Page 27 of 35
  • Dom Silverio

    May 28, 2005 at 12:52 am in reply to: 23.98 pulldown removal makes strange timecode

    [JeremyG] “If FCP generated new timecode for captured clips, there would be no way to recapture offline clips.”

    You are incorrect because there is a direct relationship with 30i TC and 24p TC with pulldown. If there was not – how you think Avid, Quantel, Discreet can take a 30i EDL and recapture in a 24p project? Basically TC ending in 0s and 5s are pulldown frames. It is up to FCP to calculate the proper TC.

    And yes I have worked on 24p Advance and normal pulldown – DV25/DV50, HDCAM and film.

    HTH

  • Dom Silverio

    May 27, 2005 at 4:32 pm in reply to: 23.98 pulldown removal makes strange timecode

    That is bad advice. If you are capturing 24p via 29.97 pulldown removal FCP SHOULD generate a new TC. Anyways, if I remember correctly FCP does not actually capture TC, it just conforms the first first frame to the first TC value and calculates the rest. So in theory it should be easy to implement for capture. But for sequence and other metadata? Who knows.

    I will check later with the Io system. Maybe it is just a settings thing.

  • Dom Silverio

    May 27, 2005 at 1:10 pm in reply to: Dual Link RGB 4:4:4 editing with FCP

    For XPress Pro and Adrenaline, the ReadMe file states which FX are 16 bit- most of them, including the most commonly used like PiPs, dissolves, wipes etc.
    This is based on the latest release [5.x for XPro and 2.x for Adrenaline]. So a full 10 bit workflow is possible.

    Avid Symphony Nitris will be interesting. Symphony’s old code is 8 bit mostly [only the CC was 10 bit, but SDI out was only 8 bit] but it will be using Nitris hardware. That is 8/10 bit native.

    Back to topic…. I thought FCP supported up to 32 bit FP? The engine renders at 32 bit but writes only 8 bit?

  • Dom Silverio

    May 25, 2005 at 9:13 pm in reply to: Win XP Pro 64-Bit OS

    No point. Until Premiere is 64 bit ready, 64 bit drivers will not do you any good.

  • Dom Silverio

    May 25, 2005 at 8:00 pm in reply to: avid vs final cut…pc vs apple

    FAST and FCP are in 2 different planets. Heck the trim tool is laggy as hell.

    For long form, Avid is king. Media management, Trim Tools, mature workflow, low res offline support, 24p/23.976 support better and more seamless than any other, renders extremely fast, plugin support -including RT with After FX plugins via Elastic Gasket, cross platform, etc.

  • Dom Silverio

    May 25, 2005 at 7:56 pm in reply to: avid vs final cut…pc vs apple

    The hammer analogy is an oversimplification of the issue. Ask Jeff Gordon what car he drives is a bit more apt.

  • Dom Silverio

    May 24, 2005 at 3:56 am in reply to: Grin

    Avid Tech Support is one of the few people I know who can actually help you with 24p workflow. Not a big deal for some but if you deal with it [HD or film] I must say it is a life saver.

  • Dom Silverio

    May 20, 2005 at 3:48 am in reply to: AVID LVD drive replacement

    I guess owning a particular product equals honesty? Or are you saying COW AJA is more honest than COW Avid?
    There is less censorship in Avid owned forum than Apple’s.

    .02

  • This happens once in a while. Rare. Nevertheless I have seen it enough to say it is a bug [4 & 4.5].

    Part of an audio clip will disappear from exported QT movie. Your solution, creating a brand new sequence and pasting it in, is the only solution I have found. Deleting your pref or restarting the computer does not solve it. Neither is mixdown. In fact if you try to mixdown the offending sequence it will have the same flaw.

  • Dom Silverio

    May 17, 2005 at 12:55 am in reply to: avid vs final cut pro

    What to say about rendering? Hard to compare when they are 2 different platforms and applications.

    XPro renders better with 3D because it has 3D features. FCP does not really. Also, there are better 3D cards on the PC side.

Page 27 of 35

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