Forum Replies Created

Page 368 of 414
  • David Bogie

    January 12, 2006 at 5:54 pm in reply to: Editing profanity ridden dialogue?

    There are other issues you might wish to consider as a filmmaker.

    Do you disguise or obscure the profanity dramatically or with subtlety? Bleeps can become terribly distracting but the right bleep carries THE message. Subtle obscurations carry a completely different message.

    However, consider the sensitivities of your audience and decide whether you are a documentarian or a social engineer. Are you portraying the subject as an illiterate bottom-feeder whose message is unworthy of attention or is this a human being, perhaps in a weird situation, expressing himself in the vernacular.

    It’s not so much censorship as your film’s style and your vision or mission.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 11, 2006 at 3:08 pm in reply to: Audio Timecode Reader

    Don’t think so.
    You will need an external LTC reader.

    But you really don’t need the LTC. The fact that your production used LTC (instead of jam syncing with VTC) implies they also knew how to properly shoot with timecode. So you’ve got legible head’n’tail t/c marker slates, right?

    You can easily create two auxiliary t/c tracks within FCP; specify time and frame formats and starting points for every clip.

    Tedious but cool.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 10, 2006 at 11:07 pm in reply to: Real Media, real problems

    Non-advice:
    Find a buddy with a PC who can handle the quick fix for you. Figure it out later.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 10, 2006 at 11:05 pm in reply to: black bars on side when capturing DV from XL1

    It’s not FCP, you’re just making a clone of the DV file when you capture via FW. It’s on your video from the camera. Or it’s in how your file is being displayed by FCP, project settings are not congruent with clip settings. Impossible to tell from here and there are so many weird little things that can go wrong.

    All I can tell you is that my buddy’s XL1 does NOT have this issue.

    Canon’s DV codec is notoriously odd. Check the Canon DV forum here on the cow.

    If you cannot find a quick fix, you start an extensive binary test, changing only one aspect of the test procedure each iteration. Eventually you make an intuitive leap and figure it out.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • Use the Animation codec.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • [mushyosh] “I’ve been having “error: out of memory” messages recently on a big project (the project file itself is around 140MB). They were annoying but not too much of a problem, it happened every 15 mins or so, the message came up, the canvas went red, but then it went away again.”

    Good god, you had all that warning and you just kept working?
    Your karma, baby, but you SHOULD have made a backup copy of your project file immediately and considered your worst case scenario and then made some intelligent plans to prevent it from happening.
    There’s a long list of prophylactic measures including incrementing your project to a new version, Media Manager-ing a new copy containing only used media, and backing up everything perceived as critical to a cheap FW drive just because it would feel good to have a backup.

    While we wish the best of luck–no on wants to see anything bad happen to you or your media–but you’re on the edge, you got there yourself and next time we hope you’ll know better.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 9, 2006 at 11:54 pm in reply to: find bin when duplicating clips

    You’re saying you’ve added bins and duplicated your clips or are you saying you added bins and delted your original clips?

    Delete the original bins and the clips they contain.

    If you’re nervous about that, save your project with a new title and then delete the unnecessary bins. You can always return to the original project’s file structure if you need to and copy/paste across from one to the other.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 9, 2006 at 10:45 pm in reply to: closed capt.

    Fred, very cool, I’ve added that product to my bookmarks, thanks for the link.
    Expensive is relative, of course, unless you are required to have captions for compliance. So everyone knows, the DV version is about $5k, the light version is about $2k. that seems to be about what these products run. I’m guessing that we will see many new products at NAB in May, 2006.

    This information is from the CPC Web site but I’m still a bit confused on whether or not the “closed captions” are permanently burned-in or switchable. I’ll contact the publisher someday when I need this tool at my shop.

    >Adding closed captions to DV
    DV video contains closed captions in its VAUX data area. CCaption and MacCaption can insert closed captions directly into this data area. When you have a time stamped text file, you can add captions to a DV video by a simple mouse click. MacCaption will create a copy of the DV video with captions in the VAUX data area. Then when you use a print to tape function to dump the video to a a tape (DV or BetaSP) via FireWire, the caption data is tranferred to line 21 of NTSC video by most DV recorders or digital to analog converters< This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 9, 2006 at 8:18 pm in reply to: Any opinions on switching to FCP from Media 100?

    Jerome, welcome to the family, soon.
    There are many of us here, I don’t think anyone ever looked back. However, you must realize FCP is a completely different animal, built to please a broad base of users but built to satisfy no one. You are going to miss the mature elegance of Media 100’s interface but you will rapidly appreciate FCP’s tremendous flexibility. Capable and cool, FCP is full of holes and stupid glitches, bad design decisions and lame features no one wants or can make work like AutoSelect and Media Manager.

    The learning curve is long and shallow because you must unlearn so many keyboard shortcuts and logical workflow pathways, replacing them with new habits and trying to figure out why those bozos at Apple did stuff the way they did instead of the way Media 100 did it. You get over it but you will never forget what it’s like to have dedicated hardware.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • David Bogie

    January 9, 2006 at 8:10 pm in reply to: 4.5 to 5, not gonna happen? Help…

    It’s the AGP card, probably. Check the card model against the acceptable list?

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

Page 368 of 414

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