Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy DPX workflow (and another question!)

  • DPX workflow (and another question!)

    Posted by Michael Nichols on September 28, 2008 at 9:14 pm

    I am struggling a little bit here as to how to skin this cat most effectively.

    I have a sort of round about, rube goldberg offline/online thing going here. Let me start from the beginning:

    Shot on 2 perf 35mm
    SD telecine direct to quicktime
    Did offline cut in FCP
    Generated EDL and did a 2K scan with 1 second handles

    My questions are two fold.

    First, is there an easier way to conform my DPX stacks (I have gluetools)? I am doing it by eye at the moment, but it is painful. I am basically recreating my edit. The timecode from the DPX stacks match the timecode from the quicktimes.

    Second: I have to do some cropping on the DPX files. I was told to batch them in photoshop and save to cineon files and automator them back to DPX. This seems lossy and inelegant. Any thoughts there?

    Thanks!

    Michael Nichols replied 17 years, 7 months ago 1 Member · 1 Reply
  • 1 Reply
  • Michael Nichols

    September 29, 2008 at 12:44 am

    Here’s an update:

    I imported my EDL into FCP. I took a folder with my DPX stacks and laid them out sequentially in a sequence and exported a reference movie and named the file with the same name as a filename in my EDL, hoping a simple reconnect would solve my problem. No go. Didn’t work. So, what I did was the following:

    In my offline sequence, which refers to back to my original cuts and lab rolls, I selected each clip and made it independent. Then, one by one, I reconnected each edit with the corresponding DPX sequence. Thanks to the wonders of timecode, this is working! Sure, it’s tedious, and it anyone else has a better solution, I am all ears, but this seems to be working fine for me.

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