[Matt Dowling]

Hi Rajeshr,

“hdyc” is the fourcc of that format. 2Vuy is the fourcc of the 8 bit QT format. I am not sure what you are wanting to do exactly with the 2Vuy clip? If you could give us some more detail on what exactly you are trying to do – we can assist you further.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Shane,

That’s right – our current drivers do not output HDV via the card. We are looking at that right now (to output via the card) The HDV codec that is available via Premiere Pro does not allow us to capture HDV – however we believe that we can playback the HDV clips via the card in Premiere Pro without having to render to our codec – like what we do with DV.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Scott,

The biggest difference with PCI E is how commands are sent over the bus. PCIE replaces the parallel multidrop bus architecture of PCI and PCI-X with a serial, point-to-point connection bus architecture.

PCIE works with a point to point connection known as “lanes” Each lane has 2 differential signal pairs carrying 2.5 Gbps of traffic in opposite directions. One pair is used for transmitting, and the other pair is used for receiving. To make this even faster further pairs can be put in parallel such as x4, x8 and x16 slots.

This makes consumer motherboards such as the Asus P5WD2 Premium and Asus A8N-E a perfect low cost solution for uncompressed SD work. We are still testing how these low cost boards go for HD uncompressed.

The DeckLink Extreme PCIE version is a x1 PCIE card. The Multibridge Extreme is a x4 PCIE interface.

As to your direct question about FCP, the G5’s that are available do not have PCI E slots so it is impossible for us to give you an answer on something that is not available.

If you are planning to use your current G5 for you HD work, I would advise just using the PCIX DeckLink HD series. They start at just $595US, so quite a small investment to get your first HD jobs out the door.

I hope this helps explain things.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Chris,

Sorry for the length of the response but there is a fair bit to cover.

[Chris Tomberlin] “Thank you for addressing these issues, and responding to our posts. I am truly grateful, but why did it take so long to get any word from you guys on this? Most of these issues started showing up here on the forum about a month ago. I mentioned in an earlier post that perhaps the quick response from Blackmagic on past issues has spoiled me, and if that is the case, then you just set a high bar in the early days! That has always been one of the great things about BMD; please don’t forget about us out here in the trenches.”

My apologies for the delayed action. Sometimes we just don’t get the chance to get on the Cow as much as we would like. Please feel free to mail me offline if you are not getting satisfactory answers to your questions or concerns.

[Chris Tomberlin] “When I first read the above, I think I misunderstood, because I removed the 1.2 version of “FCP Uncompressed 422.component” from the QT folder and then installed the Blackmagic (software only) codec. Of course, this gave no video output from FCP or AE. SO, I reinstalled the Blackmagic 5.0 drivers. I was surprised to find that there was now a “FCP Uncompressed 422.component” back in the quicktime folder. Apparently, the version 1.1 of “FCP Uncompressed 422.component” is part of the Blackmagic 5.0 install.”

The Apple codecs have been a part of our installer since 5.0.

[Chris Tomberlin] “Now, this fixes everything in AE (except the issue to be resolved later this week), but how will it affect FCP 5.02? Everything seems to play back and display properly, but is there going to be a problem using the 1.1 version of the FCP Uncompressed 422.component? FCP 5.02 installs the 1.2 version presumably for a good reason, though as we’ve seen, it certainly seems to do more harm than good. Any chance you could just get Apple to ditch their 10-bit codec, license the Blackmagic codec, and call it a day?”

There wont be a problem as both the BMD and Apple codecs have the same fourCC. The 1.2 Apple codec was done to address some Shake issues. We are still discussing with Apple what is the best we can both tackle this issue.

[Chris Tomberlin] “One last thing. A couple of us here on the forum have spent quite a bit of time troubleshooting this stuff, and have provided BMD with detailed info on what we have found. Does that really help you, or are we just wasting a lot of our time?”

ABSOLUTELY NOT a waste of time! Please keep the feedback coming as much as possible – it is vital to us to get your feedback on everything, this contributes greatly to how and what we develop. Thanks for all the detailed feedback to date!

Cheers

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Felix,

Yes, if you go to /library/QuickTime and take the Apple uncompressed codecs out of that folder and put the Blackmagic 10 bit codec in
/library/QuickTime (you can get just the codec from our support page), this will help you guys out until we have discussed further with Apple a suitable solution for the Apple uncompressed codec.

Hope this helps.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Chris,

Hopefully i can clear a bit of this up with you.

[Chris Tomberlin] “1) There is a bug (likely in the desktop video output component) of the current BMD drivers in Tiger. This bug outputs an incorrectly low gamma from After Effects to the NTSC monitor. It does not, however, affect the rendered file. A grayscale ramp that displays an incorrect gamma curve on a scope while viewing in AE, will render correctly and display a proper gamma curve from FCP. This bug makes proper color-corrections in AE difficult, if not nearly impossible. “

We can do something about that and have it planned in the next release which will be sometime this week.

[Chris Tomberlin] “3) After Effects, in Tiger, does not properly recognize the new version (1.2) of the Apple uncompressed 10-bit codec when in 16bit mode. This is what is causing the green lines on the footage when you put AE in 16bit mode.
“

Yeh, we see the same thing. Unfortunately there is nothing we can do about that. We have been discussing this issue with Apple. The only way i can think of, that would get around that is to remove the Apple codec from the system and replace it with the BMD 10 bit codec. If both were left in then QT would randomly choose one or the other to render to which could cause gamma problems in itself. There reason for this is that both codecs are V210 and have the fourcc.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

HI Shane,

We are looking at all the DV support now – not just PAL.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Shane,

I can’t give a 100% answer on that as we havent completed running tests. I believe it will certainly work for SD but as i said – havent finished HD testing.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Mike,

5.1.1 – the PAL DV has not changed. We have come up with a better solution than the current support and will be rolling that into 5.2 which is around 10 days away.

Cheers,

Regards,

Matt
Blackmagic Design

[Matt Dowling]

Hi Shane,

It is still a little early for us to recommend motherboards and system setups. When we have completed our testing with various vendors we will post a full spec.

Cheers,

Regards,

Matt
Blackmagic Design