Forum Replies Created

Page 323 of 413
  • John Pale

    August 19, 2007 at 6:16 am in reply to: Onlining DV

    Keep in mind also, that you lose any benefit of rendering or recapturing uncompressed, if you master back to DV. You will be recompressing once the signal hits the tape.

  • John Pale

    August 19, 2007 at 6:11 am in reply to: DVCPRO HD Wrong Resolution and Pixel Aspect Ratio

    Its not the length of the export that matters.

    Some, or even just one, of the clips in your timeline is erroneously being read by Quicktime as having square pixels instead of DVCPRO HD’s anamorphic pixels.

    I determined this by gradually exporting sections of my timeline…getting the correct result…until…BAM…I found the one clip that caused the export to go awry.

    Add the Broadcast safe filter to that clip, and the export works correctly. It doesnt have to be the Broadcast Safe filter…any filter, even one that changes nothing, will fix the problem, as FCP now reads the render file instead of the original media.

    I believe, randomly, Quicktime is messing up in the metadata department and this is causing the issue. I had several timelines which exhibited this problem and there was no pattern to the offending clips. They all appeared normal in their properties (the correct DVCPRO HD pixel aspect and size).

  • John Pale

    August 19, 2007 at 3:18 am in reply to: Downconvert/Field Issues-Upper vs Lower?

    [gary adcock] “I am on the most current versions of everything,
    running on 3 Quad intels and a Dual 2.5 PCI-x

    So that means
    OS 10.4.10 / QT 7.2 / FCP 6.01 / Kona Build v4 (on all 4 machines)”

    MacOSX 10.4.10/QT 7.2/FCP 6.0.1/Kona v4
    PowerMac G5 Dual 2ghz/Kona 2

  • John Pale

    August 19, 2007 at 3:14 am in reply to: XDCAM Ingesting

    FCP 6 has a feature where you can rename the files the same names as the clips. This may be helpful to you.

  • John Pale

    August 18, 2007 at 3:09 am in reply to: Downconvert/Field Issues-Upper vs Lower?

    [gary adcock] “Thats interesting John,
    in my testing the ghosting results were not seen on a CRT or my scopes (were it should show up), just on the uprezed output signal the plasma. “

    I worked on a Kona 3 system today at a different facility and did NOT see it on their CRT. The bug may be limited to certain board revisions or hardware combinations. Should be a piece of cake to troubleshoot this 🙂

  • John Pale

    August 17, 2007 at 4:39 pm in reply to: Downconvert/Field Issues-Upper vs Lower?

    Gary,
    I see this too on with my Kona 2 on a CRT broadcast monitor.
    I dont think what’s going on is what you think it is. It may not be affecting everyone, but it is real.

  • John Pale

    August 17, 2007 at 2:51 am in reply to: Downconvert/Field Issues-Upper vs Lower?

    I see it on my Kona 2, for what its worth. have not found a workaround.

  • John Pale

    August 15, 2007 at 12:42 am in reply to: Applescript to convert IMG SEQ to DVCPro HD
  • John Pale

    August 14, 2007 at 2:32 am in reply to: DVCPRO HD Exporting as 1920 and not 1280!

    I had this happen randomly shortly after 6.0 came out (not any of the recent updates).
    Certain clips in the timeline (which were the correct 1280 x 1080 size) would cause the export to be at 1920 x 1080. I added the Broadcast safe filter to them and rendered. FCP now referenced the render files instead of the original media, and the export would then work at the the correct size.

    It could be any filter (I just picked that one, since it seemed like a good idea anyway.)

  • John Pale

    August 13, 2007 at 1:58 am in reply to: AJA & Blackmagic use same UC right?

    This is from Blackmagic’s website, explaining that they use Apple’s Uncompressed Codecs starting with FCP 5.0. Apple wanted this standardized among the different manufacturers… I have read that AJA did the same thing, though I have not found that link as of yet. The Googlefest is ongoing, unless Rudy from AJA wants to put this to bed once and for all.

    FINAL CUT PRO 5.0
    Apple were keen for DeckLink cards to standardize on using Apple’s codecs so that there would no longer be the potential for confusion between the Apple and Blackmagic codecs.

    Apple and Blackmagic Design have worked together on this issue and, starting with Final Cut Pro 5.0 and the DeckLink 5.0 drivers, all DeckLink cards use the Apple uncompressed 8-bit and 10-bit codecs for all standard definition and high definition uncompressed 4:2:2 video. The Blackmagic codecs are no longer installed for uncompressed 8-bit and 10-bit 4:2:2 video.

    ARE ANY BLACKMAGIC CODECS STILL USED OR INSTALLED?
    Yes, the DeckLink 5.8 and newer drivers install the following Blackmagic codecs:

    Blackmagic 8-bit (2Vuy) – this is our original 8-bit codec and is still included to support legacy files captured in this format and also is what was used by the Cinewave.

    Blackmagic 10-bit RGB – Apple do not currently have a codec with the RGB color space for high definition 4:4:4 dual link video. Blackmagic Design will need to include this codec until such a time as Apple might introduce its own codec for 4:4:4. We would probably discontinue the Blackmagic 10-bit RGB codec at that time.

    For the full story check out this link.

    https://www.blackmagic-design.com/support/detail.asp?techID=78

Page 323 of 413

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