Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Wierd SLUG behavior in PAL land

  • Wierd SLUG behavior in PAL land

    Posted by Kim Rowley on January 29, 2007 at 5:30 pm

    I just realized that the “slug” in FCP is showing up as an NTSC clip even though my setup is 100% PAL. I never noticed this or run into any problems until the other day. I output a finished documentary on Digital Beta using the 10 bit uncompressed codec. I then needed an emergency DVD of the prject,so a technician took that Master and did a copy manually using a professional external DVD recorder. The DVD recorder kept stopping when it reached a piece of slug. He noticed that the NTSC light on the recorder flashed when it got to that point. I went back to FCP and low and behold when I look at the “properties” of the slug, it’s NTSC! I always encode my Master tapes using a hardware encoder and never ever had a problem… Anybody else have this problem?

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP 5.1.2, OS X10.4.8

    Ron James replied 19 years, 3 months ago 3 Members · 6 Replies
  • 6 Replies
  • Ron James

    January 31, 2007 at 10:09 pm

    That’s weird.

    I’m not a big fan of the slug, though. It’s always caused problems for me. What I’d do is export some black as a self-contained clip, import it and use that as your slug.

    One of the problems I was having with the generated slugs was when using the TC reader for TC burn. At first, it just dropped the timeline timecode whenever it would hit a slug, but then it started messing with the TC values (in the reader) throughout the rest of the show. More trouble than they’re worth, IMO.

  • Andy Mees

    February 1, 2007 at 3:13 am

    yep the slug Generator is NTSC and can’t see any way of changing that. for a quick workaround, you could create your own slug using Generator > Matte > Color and make it a favourite.

  • Kim Rowley

    February 1, 2007 at 8:09 am

    Thanks all. That sounds like something Apple should fix. I’ll report it. Thanks for the suggestions. In fact I’m putting in a solid black color for now. At least I can vary the length as necessary, the only drawback is that when it comes time to output to tape it needs to be rendered (green line above clip). Not a big problem, but nonetheless a needless step.
    Thanks again.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP 5.1.2, OS X10.4.8

  • Ron James

    February 1, 2007 at 10:44 pm

    That’s why I suggest making a self-contained clip. It only needs to be a 10 seconds or so, and then you can just use it over and over and easily file it away on your HD for future use.

  • Kim Rowley

    February 2, 2007 at 8:03 am

    Point well taken. I’ll do just that.
    Thanks for the tip.

    Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP 5.1.2, OS X10.4.8

  • Ron James

    February 2, 2007 at 9:21 pm

    My pleasure. Just a little something I picked up from Walter. Hope it helps.

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