Forum Replies Created

Page 2 of 2
  • Diego Lopez

    May 2, 2011 at 10:00 pm in reply to: offline/ online workflow for file based media

    Somehow things are getting worse…

    Now I tested editing a regular clip with no markers and no subclips into a sequence, using media manager to make that sequence offline… then when I try to “batch capture”, FCP complains about the A/V settings.

    What should they be set as when doing the offline/online tapeless workflow?

    The settings that were working for me before were:

    Seq preset: ProRes 1208×720

    Capture preset: generic capture template

    Device control: non-controllable device.

    Now those same settings no longer work

  • Diego Lopez

    May 2, 2011 at 9:41 pm in reply to: offline/ online workflow for file based media

    So I just figured out the link between all the files that won’t “batch capture” properly…..

    Markers.

    Our production house has moved away from subclips and used markers instead to log footage. We find it to be cleaner and easier to navigate around a long interview (go to next marker instead of clicking on next subclip, etc). When I try to execute the offline/online tapeless workflow with these clips with markers, it doesn’t work. These are the clips that FCP for some reason thinks are tape-based.

    Has anyone come across this and back up my assertion?

    Does anyone have any way of resolving this issue aside from re-transferring the whole clip again and re-linking?

    Further, if you make subclips from longer clips and then try the media manager offline/online workflow, does it work?

    Thanks in advance

  • Diego Lopez

    May 2, 2011 at 7:36 pm in reply to: offline/ online workflow for file based media

    [Shane Ross] “[Rob Nairn] “How does batch capture know to transcode the files on drive rather than capture from tape?”

    Because it’ll know the footage was imported via Log and Transfer opposed to captured from tape. It’s part of the metadata.”

    I ran a quick test of this before I started my most recent project and it worked well (after I had to make some changes in the Audio/Video settings). Things reconnected with handles nicely.

    Now I am trying to do it after picture lock and I’m having problems.

    I isolated only the clips that I wanted to recapture (as this edit is mixed with HDV and full res ProRes) and went to batch capture after using media manager to create an offline sequence.

    Half of the clips connected just fine… the other half refuse to.

    One confusing issue is that when I try to recapture the sequence, FCP tells me that there is tape-based media mixed in with the tapeless stuff, and that it will do it first. It then complains about the A/V settings (I have the capture preset set to “Generic capture template” because that’s the only way I could get it to work before), and when i click through, FCP goes ahead and recaptures the rest of the media.

    This leaves me with offline clips that are found on the SAME CARD as some of the clips that were successfully recaptured. I can’t figure it out and it is quite frustrating..

    Has anyone come across this or have any ideas?

    Also, I might as well double-check, where should I have my A/V settings for recapturing in a tapeless workflow?

    I hope I’ve described this well enough.

  • Diego Lopez

    April 13, 2011 at 7:31 pm in reply to: Edit ProResProxy then ReTransfer/Capture

    One important note that I had to figure out on my own…
    (don’t think it had been mentioned)

    When trying to “batch capture” on your tapeless workflow, please make sure to adjust your Audio/Video settings.

    Capture Preset: Generic Capture Template
    Device Control: Non-Controllable Device

    Device control might be the only relevant one, but those are the settings I used. If you don’t change your Device Control preset, FCP will complain that it can’t initialize the capture device.

    Maybe I’m the only fool that needed that tidbit…

Page 2 of 2

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