Forum Replies Created

Page 11 of 21
  • Nicole Haddock

    August 17, 2009 at 4:07 pm in reply to: FCP won’t mount my p2 volume anymore

    Yes it does. You need to run the update from FX’s website. It breaks the Log and Transfer for P2 cards.

    https://www.noiseindustries.com/fxfactory/download/

  • Nicole Haddock

    August 14, 2009 at 4:05 pm in reply to: PNG-24 Transparency Issue

    Do you have a mask on that particular layer?

    For grins, just try making an alpha channel for that layer, and then bringing it into FCP. I know it’s now how you’ve been doing it, but it may work. Crazier things have happened.

  • Nicole Haddock

    August 14, 2009 at 4:01 pm in reply to: Importing captured P2 footage into FCP 4.5

    Many many moons ago, I worked in a similar workflow (it was a 48 Hour Film project, which made it even more insane). Ingested P2 on a 5.1 machine, and then had an assistant cut scenes on a 4.5 machine after we duped the media onto his drive. Similar problem- instead of 4 channels of audio coming in, I think there was 2, but it might’ve been one. At the time, I had no time to figure out what the problem was, so he edited away and handed me the scenes. I match framed them in 5.1 and brought the 4 audio channels back, and that worked pretty well.

    Maybe the gurus here will have a way to fix that, but you might have to do a workaround like I did, which could be a huge pain in the butt.

  • Nicole Haddock

    August 13, 2009 at 9:39 pm in reply to: PNG-24 Transparency Issue

    Actually, the PNG file needs an Alpha channel (as does a .TIFF). Make sure there’s only one Alpha. If there’s 2, FCP won’t know what to do.

  • Nicole Haddock

    August 13, 2009 at 7:43 pm in reply to: PNG-24 Transparency Issue

    When you say Transparency, did you run the Video Action for creating an Alpha channel? Having a transparent background in Photoshop isn’t enough for FCP to understand- you have to create an Alpha channel. I just imported a .PNG that was originally a .TIFF with an Alpha channel, and it imported fine into FCP.

  • Nicole Haddock

    August 13, 2009 at 7:32 pm in reply to: PNG-24 Transparency Issue

    Actually, TIFF files work fine with layers. I do all my graphics in TIFF with Alpha Channels and keep the layers for editing later if needed.

  • Nicole Haddock

    August 13, 2009 at 6:09 am in reply to: 853×480 and 720×480

    Is the 720×480 footage widescreen, or 16×9 anamorphic, or full screen, aka 4×3?

    If you make a new sequence that’s 720×480 anamorphic, DV pixels and sink your clips in, the 853 footage should fit in fine. If the 720 footage fits, it’s anamorphic. If there are black bars on the side, it’s 4×3, at which point you can either 1) blow the footage up to fill the screen, 2) live with it, or 3) reverse engines, make a 720×480 non-anamorphic timeline, and when you pop your 853 footage in, bars will appear on the top and bottom, which you can either keep, or blow the footage up, thereby cutting off the edges.

    Let me know if this doesn’t make sense. It’s late and the insomnia is making me loopy.

  • Nicole Haddock

    August 13, 2009 at 5:28 am in reply to: Strange??

    Yes, we’re seeing that fun error on 1 of the 3 machines we’ve moved to FCP7. And yes, we did clean OS wipes and clean installs. It’s totally ridiculous, but what can you do.

  • Nicole Haddock

    August 13, 2009 at 5:26 am in reply to: FCP 7 audio

    That’s not it, because all the video I ingest is P2 media recorded at 48. It’s just weird voodoo, because 2/3 fcp7 machines will get the render bar for mixed 44/48. The fcp6 machines don’t. There’s one fcp7 machine that will re-name the sequence if you paste in a graphic from another sequence with the graphic name. Not terribly handy little bug 😉 And yes, both machines had a clean OS install, clean FCP7 install, done by the book. I love new software!

  • Nicole Haddock

    August 12, 2009 at 9:12 pm in reply to: Compressor won’t connect to background process

    Yeup.

Page 11 of 21

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