Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP7 – reveal patch info

  • Juan Manuel

    March 20, 2012 at 12:23 pm

    Well, you can right click on them in the timeline and choose “reveal in finder”, but you’ve probably done that already. You can also use the Media Manager to move or copy your source files to a new location.

  • Alex Elkins

    March 20, 2012 at 3:12 pm

    [Trevor Asquerthian] “trying to identify the source audio tracks used”

    As in, did the editor use A1, A2 or A3 etc?

    I don’t think FCP has any way of doing this other than to compare the waveforms of the original against what you have in your timeline. Very frustrating.

    I expect that the info is carried within an XML if you were to export one from your timeline. I just had a look but couldn’t see anything that seemed to clearly identify a source channel, but it must be there in order for FCP to reconnect to the correct files when importing XMLs.

    Alex Elkins
    Twitter: @postbluetv
    http://www.postblue.tv
    Post Blue showreel
    Latest work: Greyhounds in Motion at 500fps
    My Vimeo Pro page

  • Trevor Asquerthian

    March 20, 2012 at 7:10 pm

    [Alex Elkins] “As in, did the editor use A1, A2 or A3 etc?”

    Yes

    … obvs the info is there, if I ‘send to soundtrack’ then the source track is listed in the soundtrack timeline. but that is a bit of a cumbersome workaround. EDL doesn’t contain patch info.

    reveal in finder doesn’t help. Unfortunately

  • Alex Elkins

    March 20, 2012 at 9:59 pm

    [Trevor Asquerthian] “obvs the info is there”

    The info certainly is there. The question is “where?”. I don’t believe there is a simple way to find out within FCP. The best way that I’m aware of, as mentioned, is to compare the waveforms of the original against the one used in the sequence. Or send the clips to Soundtrack, as you’re already doing.

    Sorry, but I don’t think there’s a good solution for you and it’s not getting fixed either.

    Alex Elkins
    Twitter: @postbluetv
    http://www.postblue.tv
    Post Blue showreel
    Latest work: Greyhounds in Motion at 500fps
    My Vimeo Pro page

  • Trevor Asquerthian

    March 21, 2012 at 5:54 pm

    [Alex Elkins] “it’s not getting fixed either.”

    Surely this is the kind of improvement that will be in FCP8?

    Together with a better use of memory so that it doesn’t crap out on long sequences with lots of plug-ins.

  • Ken Conrad

    March 21, 2012 at 6:33 pm

    FCP8? hmmmmm nope sorry 🙁

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