Forum Replies Created

Page 1132 of 1228
  • David Roth weiss

    July 14, 2006 at 5:30 pm in reply to: FCP export to self contained shows artifacts

    Wow, those are indeed ugly. Calling them artifacts seems too nice. This looks more like corrupt data or bad tape. Was this on the camera original?

  • David Roth weiss

    July 14, 2006 at 5:19 pm in reply to: compressor

    That’s good to know Chris, I am using 5.1.1 now and was kind of hoping that was one of the things that had been fixed.

  • David Roth weiss

    July 14, 2006 at 2:59 pm in reply to: compressor

    Arty,

    Six hours sounds like a very long time — in my 2.3ghz G5 an 85-min. project takes only 50-mins to encode to MPEG-2 using Compressor. Is your MAC an older slower G4? Are you exporting directly from the timeline? If the answer to the later question is yes, don’t do that, export from the timeline first either to a reference or self-contained movie, then encode using Compressor. This will save you considerable time. Also, the 2-pass encoding was broken and still may be, you should pobably change the prest to one pass before starting your encode. The results are still very good, sometimes better even than the best 2-pass depending on tghe material, and that wil also save time.

    DRW

  • David Roth weiss

    July 13, 2006 at 6:19 pm in reply to: Need Help Reconnecting Media

    [walter biscardi] “Media 100, Avid and FCP we’ve use colons, periods, backslashes, hyphens, quotes, etc…. Just about every key on the keyboard has been used in file names and I’ve never seen it cause an issue in any of our FCP projects.”

    Walter,

    This is an industry standard that goes back much farther than your 17-years, and much farther than non- linear editing. The fact that you are not aware of these industry standards does not negate the fact they are standards nonetheless.

    Its not just me, Mark, and Apple saying this, nor is it based upon our own anecdotal evidence, which is the basis of your argument. The Apple manual clearly explains why conservative file naming procedures without “special characters” are best adopted, and anyone who expects to interface seamlesly in this global industry should make a habit of adhering to these standards. You’re free to use use whatever procedures you want, but, you should be aware of the standards and the reasons they exist before encouraging others on the forum to use other conventions.

    DRW (over 34 years professional experience)

  • David Roth weiss

    July 13, 2006 at 5:14 am in reply to: Need Help Reconnecting Media

    Walter,

    It is not a great idea to encourage the use of “special characters” as file naming conventions, and it is frowned upon in the industry for good reason. While you may get away with it in FCP, many systems will reject any file name or reel number containing any of the most commonly used special characters. In fact, even the FCP manual states the following on page 38:

    Avoiding Special Characters
    The most conservative filenaming conventions provide the most cross-platform
    compatibility. This means that your filenames will work in different operating systems,
    such as Windows, Mac OS X and other Unix operating systems, and Mac OS 9. You also
    need to consider filenaming when you transfer files via the Internet, where you can never
    be certain what computer platform your files may be stored on, even if temporarily.
    Most special characters should be avoided. Here are some suggested conservative
    filenaming guidelines for maximum cross-platform compatibility:

    Avoid
    File separators : (colon)
    / (forward-slash)
    \ (backward-slash)
    You cannot use colons (:) in the
    names of files and folders
    because Mac OS 9 (Classic) uses
    this character to separate
    directories in pathnames. In
    addition, some applications may
    not allow you to use slashes (/)
    in the names of items.
    These characters are directory
    separators for Mac OS 9,
    Mac OS X, and DOS (Windows)
    respectively.
    Special characters not included
    in your native alphabet
    ? ?

  • David Roth weiss

    July 12, 2006 at 11:02 pm in reply to: Annoying Cameraman!!!

    David,

    You’re identified the problem. Looking at playback in the camera is just bad.

    DRW

  • David Roth weiss

    July 12, 2006 at 7:56 pm in reply to: Annoying Cameraman!!!

    [David Smith] “are you saying you expect timecode to be reset for every take?”

    David,

    No, he’s suggesting the cameraman hit the button that returns the tape to the place where the timecode left off so that there is continuous timecode on the tape.

  • Sean,

    I’m not totally certain, but I did read some reviews in which people reported having issues running the Maxline Pros at 1.5gb/s. You never know if people are just too dumb to configure them, but it was enough to scare me off of them until I heard otherwise. And, I heard that the Seagates are easy to configure. So, if I find anything out thats different I’ll let ya know…

    DRW

  • David Roth weiss

    July 11, 2006 at 8:10 pm in reply to: bizarre video playback problem

    Flash is a delivery format, not an editing format. This is the source of your issue. Why may I ask did you export Flash from AE if your were going to do additional editing?

  • David Roth weiss

    July 11, 2006 at 7:29 pm in reply to: how to capture web page for video?

    [Dave LaRonde] “I have had great success using OSX’s Grab software, animating the grabs in After Effects, and rendering for use in FCP. The quality is great.”

    Me too!!! I’m very discriminating, and it works really well for me…

Page 1132 of 1228

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