Forum Replies Created

Page 5 of 6
  • Thanks Steve. The only problem with that, is that XML contains a whole lot of other information as well, and I can’t ask the lab to weed through all that text for every clip. They need a clean spreadsheet, with clip or sequence timecode, and repos information. Do you know of a way to extract a specific type of info/ tag from the XML and place it into a spreadsheet so it can be more easily read?

  • George Mandl

    March 20, 2008 at 3:52 pm in reply to: timecode generator at 23.98?

    Just another thing to add here. When you nest a sequence, and want to use the timecode reader on the nest……if you want to change the start timecode for the reader, you must do this in the sequence settings (since its a reader and not a generator). You have to make this adjustment to the original sequence. The nested sequence timecode has no bearing on what the timecode reader will display. I thought that was interesting and wanted to share.

    -george

  • George Mandl

    March 20, 2008 at 3:43 pm in reply to: timecode generator at 23.98?

    Don’t you love when the answer is right in front of you and you can’t see it? Thank you Andy.

  • George Mandl

    November 19, 2007 at 7:01 am in reply to: FCP audio panning trouble

    Tom, When I press those keys, nothing really happens.
    Matte, yes, thank you. I did try that setting as well, and tried a few of the configurations there just to be sure. That wasn’t it. I did figure it out though…. I quit FCP, trashed all of my audio render files at the finder level, and then re-opened my project. I re-rendered the audio and it now works properly. Not sure if this is a bug with FCP or possibly something to do with the HDV format in FCP.
    If any of the moderators know about this, maybe they can weigh in.
    Thanks for your help.

    -george

  • George Mandl

    November 19, 2007 at 1:29 am in reply to: FCP audio panning trouble

    Well, the audio meters in FCP reflect what I am hearing. Its definitely not a monitor problem. I tried trashing prefs and that didn’t seem to work either. I’ve got a feeling it has to do with a sequence or clip setting, but still don’t understand it. Items on tracks 2, 4, 6, 8 and so on are coming out of my right speaker, and are playing as thought panned right (even though clips are individually panned center). The FCP meters are also only playing on the right side. Items on tracks 1, 3, 5, 7, etc are coming from the left speaker, and showing up on the left meter in FCP.

  • George Mandl

    June 23, 2007 at 6:17 pm in reply to: FCP reconnect problems

    I figured something out here. The capture scratch sub-folder had also been renamed. I named it back to what it had originally been, and then the media was willing to reconnect. I don’t fully understand why it would not connect in the first place, as the whole purpose of reconnecting media is to link media to references, regardless of where that media is located. Oh well, quick fix is to rename the folder your media is in to whatever it was originally named.

  • George Mandl

    November 21, 2006 at 9:45 pm in reply to: Avid is no bicycle

    I just got to LA a few months ago, and have not used an Avid since Media Composer, which is what I learned to cut on in college, in 1999. Now I’ve been editing professionally for 5 years, and love using FCP. I haven’t touched an Avid in my pro career. But now that I’m in LA, every other job opportunity is on the Avid. And I can’t take those gigs. Help! Where does an FCP proficient editor go to learn how to use the high-end Avid stuff? Hopefully as an FCP editor in LA, you can shed some light. Its not that I want to switch, but I want to get good enough at both so I can work more gigs. There is a book called something like “Final Cut Pro for Avid editors”. When is the reverse title coming out?

    Thanks,
    George

  • George Mandl

    November 7, 2006 at 7:33 pm in reply to: Compression for the web

    Thanks! This really clears things up for me. There are so many options and variables out there that things can get overwhelming. Those are good specs and I am going to use them myself. Thank you.

    George

  • George Mandl

    November 4, 2006 at 7:28 pm in reply to: Compression for the web

    Thanks so much to both of you. I think my main issues were too high of a bitrate, not using progressive download, and possibly too long of a reel (both technically, and professionally).

    So I did the following: exported from AE to a 640×360 animation codec QT file (which essentially was the same as dropping my letterboxed 4×3 footage into a square pixel frame and losing the top and bottom crops, resulting in a 16×9 frame). Once I had the animation codec file, I encoded to 300kbps H264 in Compressor, did the scaling in Compressor, and used progressive download. The resulting file size of the 5 minute reel was 13.6mb, and of the 2 minute reel – 5mb. These now load very quickly, and playback is nice (no stopping to catch the stream). The only issue now is that PC users who don’t have Quicktime 7 are prompted to adjust MIME settings. The general result has been audio playback, but no video.

    Does anyone encode for IPOD settings and just embed that onto a page? I’m guessing that would eliminate some compatibility issues, since IPODs are so popular.

    THANKS FOR ALL YOUR ADVICE. Here are the links if you want to check out the playback.

    https://www.georgemandl.com/reels/promo300.mov

    https://www.georgemandl.com/reels/real%20doc300.mov

  • George Mandl

    December 29, 2005 at 5:27 pm in reply to: Very Basic Multiclip question

    Thanks for the advice. I know the manuals are always the first place to check. I did get into the manual, and had everything else figured. Sometimes the manuals are a little overwhelming, and dont always give an intuitive answer. Thats when I check in with the Cow community. I appreciate what you said, and thank you for your advice
    (which was good advice) on the problem at hand. No harshness taken.

    GM

Page 5 of 6

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