Forum Replies Created

Page 19 of 46
  • Lee Berger

    June 27, 2007 at 1:58 pm in reply to: capturing footage with cheapo camera

    Since you are capturing data over FireWire there is no playback quality difference between el-cheapo and your XL2.

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 23, 2007 at 10:17 am in reply to: Thinking of switching…

    [walter biscardi] “Media 100 I think still has the best codecs on the market.”

    Great media manager as well. It was a snap to recapture at higher data rates.

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 22, 2007 at 7:56 pm in reply to: Levels change when using Witness Protection

    Thanks Mark,
    That’s an interesting thought, but Boris Continuum (BCC) for Final Cut Pro is a plugin with controls native to the FCP interface. In other words the familiar Boris FX or Red Keyframer does not open when you apply a BCC filter in FCP. All settings and keyframes are done in the Filters tab of the Viewer Window. Aside from Help and Open/Save Presets, there is no preferences setting. It seems that if you want safe colors you have to add a BCC filter called (what else) “safe colors.”

    Perhaps the color safe setting is hard coded into the plugin?

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 21, 2007 at 3:27 pm in reply to: Levels change when using Witness Protection

    Peter,
    Thanks for responding.
    [peter mcauley] “What effect method are you using?”

    I’m not sure what you mean by effect method.

    [peter mcauley] “And within what host environment / platform?”

    I’m using Final Cut Pro 5.4.1. and Boris Continuum 4.0 filters. It doesn’t make any difference if the effect is rendered on not. I tested a few other Boris Filters (page turn, lens flare) and the same thing happens. Video is clamped to 100 IRE. This wouldn’t be a big problem if I was applying to an entire chip and not trying to match frame to the split portion. The problem does not occur when applying FCP or other third party filters.

    I’m monitoring analog using AJA IO and a Tektronics Waveform Monitor.

    Interestingly enough when I tried to export a couple of example frames to post both frames were identical in level, clamped to 100 IRE. As a workaround I exported the full clip as a sequence of stills, opened in QuickTime and then exported as a movie. This solved the level mismatch, but is cumbersome.

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 21, 2007 at 2:30 pm in reply to: Accidental Canon XL-H1 24f footage

    It’s one of the worst possible scenarios, Aerials! Thanks everybody.

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 21, 2007 at 12:46 pm in reply to: Accidental Canon XL-H1 24f footage

    [Will Griffith] “It is a lot easier to make 60i look like 24f.”

    Thanks Will. I thought about that, but less than 10% of the material is 24f and I want to avoid a lot of renders.

    [Will Griffith] “You should be able to just capture as 1080 60i HDV
    if you want to go that route.”

    I’ll give that a try. Thanks again.

    Lee Berger
    http://www.leebergermedia.com

  • You’re welcome. I believe it will. Make a test limited to a couple of minutes of material with several markers added.

    Lee Berger
    http://www.leebergermedia.com

  • Because of the two-hour length I would export as a “by reference” quicktime movie and then use Compressor to encode MPEG2 and AC3 audio. When exporting be sure select DVD Studio Pro Markers and uncheck Make Movie Self-Contained.

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 4, 2007 at 6:20 pm in reply to: problems capturing because of source tape

    Does it fail in the same spot each time? If so use device control (mark in and out) to capture before and after the failure.

    Lee Berger
    http://www.leebergermedia.com

  • Lee Berger

    June 4, 2007 at 5:31 pm in reply to: problems capturing because of source tape

    I’ve run across that problem when there is a bad spot on the tape resulting in a data error that usually cannot be seen as would a drop out. The way I’ve solved the problem is to capture around the bad spot which in my experience is right where the capture fails. I you can afford to loose the material capture right up to the error and then 5 or more seconds after the failure. The other work around is to capture vial analog device such as AJA I/O using the component inputs. I know not everyone has this capability, but it works.

    Lee Berger
    http://www.leebergermedia.com

Page 19 of 46

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