[Felix Mack]

HI –

the DV10 codec is to give legacy support for Digital Voodoo files. There is a difference in quality, but it doesn’t seem to be huge. In theory you should be using the Black Magic 10bit codec, as DV10 is only meant to allow you to deal with older files that are in the voodoo codec, so there are probably some limitations with them in FCP.

After installing the new drivers, I get Blackmagic 10bit as an option. Maybe you should try uninstalling first. The problem I am getting is that BM10bit renders too brightly from AE.

Let me know if that helps.

-Felix

[Felix Mack]

I’m still having the gamma issues with AE renders.
The image below shows the FCP scopes’ display of 3 different files rendered in AE from a simple black to white ramp made in AE.

The top left one is a black magic 10bit file rendered using the old codec/fcp4.5 setup. The black to white ramp shows a straight line, which is what one would hope for.

The next image is of the same file rendered with the new Black Magic 10bit codec/FCP5.0.2. There is a gamma shift, indicated by the curved line. This is the same thing that is happening when rendering to Apple’s 10bit codec.

The last scope is of the same file rendered in BM DV10/FCP5.0.2 This also shows the correct gamma.

All I want is to be able to render BM10bit or Apple 10bit quicktimes in AE, that will keep the correct gamma in FCP5.0.2 Is anybody else getting these results or is it just my setup?

[Felix Mack]

Try downloading with another browser, like firefox.

[Felix Mack]

Thanks – that seems to work. However, this also seems to remove all RT funcitons from FCP5.02. Is that correct?

Thanks for the help.

[Felix Mack]

O.k. I spoke too soon. I hadn’t tried it with an external monitor – just by looking at FCPs internal scope that now looked correct. I had the same issue as Chris – there was no more output with the FCPUncompressed422.component removed.

Reinstalling BM 5.0 seems to replace version 1.2 with 1.1, but for me the results are still the same. . . Since I can’t render to the BM10bit codec from AE, I am still getting a gamma boost. What am I supposed to remove exactly to fix things? How can I render to the BM10 codec from AE?

Thanks,
Felix

[Felix Mack]

Great – so far this seems to fix all my gamma issues, including that previously rendred BM10bit files (10.3.9/FCP4.5) from AE appear at the correct brightness level in QtPlayer again.

Thanks.

[Felix Mack]

So, does that mean that in Tiger is it possible to remove the Apple 10bit and replace it with Black Magic 10bit? That would make me very very happy . . .

-Felix

[Felix Mack]

yep –

check this out:

https://forums.creativecow.net/cgi-bin/new_read_post.cgi?univpostid=856611&forumid=2&postid=856611&pview=t

[Felix Mack]

i have tried both 8 and 16bits when going to 10bit uncompressed, and the results have been the same for me. I think there’s something whack with the rgb to yuv conversion with the apple codecs. All other codecs seem to work fine for me.

https://www.kenstone.net/fcp_homepage/video_levels_nattress.html

If you check here in the article, towards the end he mentions that FCP adds a gamma increase to all still brought in. He says to fix it you have to apply a 0.8 gamma setting with the levels filter in PS. I have tried doing the same in AE with the levels filter, and it does indeed compensate for the FCP gamma increase to fix it.

https://www.highend2d.com/boards/showflat.php?Cat=1,6,7,8,9&Board=shakeforum&Number=192693&page=20&view=collapsed&sb=5&o=&fpart=

I think people are having a lot of issues with this. . .

https://docs.info.apple.com/article.html?artnum=93794

The above is also interesting to read. Maybe there are some clues in there. Why can’t we just have a preference to turn off ‘gamma assumptions’?

Cheers,
Felix

[Felix Mack]

yes –

try downloading with safari instead.