Forum Replies Created

Page 2 of 8
  • Jeff Carson

    February 12, 2008 at 10:27 pm in reply to: about to SNAP!

    Annaël… there is no perfect editing software for any of us. They all have issues. But it DOES seem Apple is not asking real editors about these potential software changes or features. We own 4 seats of the software here. There are a lot bigger facilities out there, but I wish for once, they would ask us to offer a suggestion or two.

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 11, 2008 at 11:44 pm in reply to: Opening scopes cause timeline force render issue

    Thank you John. That did it. I forgot about that one.

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 11, 2008 at 11:27 pm in reply to: about to SNAP!

    Another excellent post from Bogie! What WERE they thinking?

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 11, 2008 at 9:33 pm in reply to: about to SNAP!

    Thanks Walter. That works here. You made my Monday a little better!

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 11, 2008 at 6:11 pm in reply to: about to SNAP!

    Before FCP2, tapping the “n” key would turn snapping on or off in the timeline. Very handy, and perfectly suitable way to trim clips or ensure they were lining up snugly against adjacent clips. Now, in FCP2, snapping turns on at every conceivable moment. Seems if you do not want snapping on, while you are trimming/dragging a clip, type “n” to disable snapping. Next time you touch any clip, snapping is back on, whether you need it or not.

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 11, 2008 at 5:34 pm in reply to: Opening scopes cause timeline force render issue

    No, it will not play back without rendering.

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 8, 2008 at 8:11 pm in reply to: 16mm transfer/edit question

    So, let’s say I shoot 23.98p on our HVX-200 on P2 cards , and I want to archive them to tape with our AJ1400. Simply playing back the 23.98 seq with all the P2 clips does not seem to “tell” the AJ1400 to record at 23.98. Is that a Deck software thing that I don’t know about?

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 8, 2008 at 8:02 pm in reply to: 16mm transfer/edit question

    [Jeff Carson] “Does the AJ1400 for example, really have the ability to record at 23.98?”

    Sean – Yes.

    So true 23.98 or is is 23.98 while still recording at 59.94 (I see nothing in our AJ1400 manual about that)?

    Sean – What are you monitoring on? A broadcast CRT it will look fine. The problem is that on progressive scan consumer televisions, it will look awful.

    I am monitoring on the Panasonic 26″ BTLH2600

    Thanks Sean. I remember when it was all just television. This gets complex.

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    February 8, 2008 at 5:32 pm in reply to: 16mm transfer/edit question

    Sean makes good points. Cadence issues are a mother to manage. It makes my head hurt. Can a person can get film at 24 frames telecined onto HD tape recorded at 23.98? I recently used Flying Spot Film Transfer in Seattle to transfer 35mm to an AJ1400 DVCProHD deck at 1080i @ 29.97 (59.94 actually, I think). We shot scenes at various frame rates, transferred at 24fps, and it all looked really nice on tape, and in FCP, captured at 59.94, editing on a 59.94 timeline. However, this was for TV spots, and not for a broadcast show. Does the AJ1400 for example, really have the ability to record at 23.98? Or is it possible only at 29.97/59.94) and then you remove pulldown once it is captured to create 23.98?

    The biggest mystery I have is the pulldown cadence when mixing all these factors. Even though 24p material (either shot on our HDX-900 or 24fps film transferred and captured at 59.94) looks right in my 59.94 final timelines when playing, stepping through those timelines gives no clue as to the actual pulldown. I have a new AJA ioHD. How automatic is the 23.98 timeline to 29.97 conversion? Anybody have some Tylenol?

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, QT 7.3, FCP2 6.0.2, CS3, AJA ioHD

  • Jeff Carson

    January 16, 2008 at 2:13 pm in reply to: AE CS3 slow down

    … In fact I am running Nucleo Pro. Just installed it and I am a total newb (maybe even a genuine noob) about how to optimize it. So. I turned off multiprocessing in AE, and am learning what setup will solve this.

    Dual 3Gb Mac Pro Intel 8 Core, 5GB RAM, OS 10.4.11, FCP2, CS3

Page 2 of 8

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