I am using FCP to create some animated titles - saving them as QT files using the BlackMagic Design 8 bit YUUV codec.
I've installed the Black Magic codecs into my Win 7/Vegas 9.0c machine.
If I view the FCP files in Quicktime on the Win 7 machine, they are fine. However, in Vegas the screen is black, although the audio plays OK.
If I render a QT file from Vegas using camera footage, using the BMD codec, the new rendered file can be viewed in Quicktime, but when I put it into Vegas, I still get a black screen. The audio still comes through.
If I take that QT files created with the BMD codec, put it on my timline, then render it to a second file, there is no video in the output. In other words, it's not just a preview issue in Vegas, I think that Vegas is not recognizing the codec.
I assume the fact the QT see's the files means that the codec is properly installed in the Vegas/win 7 machine, however Vegas just isn't seeing it.
I can use a different format for the animated titles from FCP, but I'd rather have a solution instead of a work around, assuming that someone has already seen and solved this problem.
Thanks....
I've installed the Black Magic codecs into my Win 7/Vegas 9.0c machine.
If I view the FCP files in Quicktime on the Win 7 machine, they are fine. However, in Vegas the screen is black, although the audio plays OK.
If I render a QT file from Vegas using camera footage, using the BMD codec, the new rendered file can be viewed in Quicktime, but when I put it into Vegas, I still get a black screen. The audio still comes through.
If I take that QT files created with the BMD codec, put it on my timline, then render it to a second file, there is no video in the output. In other words, it's not just a preview issue in Vegas, I think that Vegas is not recognizing the codec.
I assume the fact the QT see's the files means that the codec is properly installed in the Vegas/win 7 machine, however Vegas just isn't seeing it.
I can use a different format for the animated titles from FCP, but I'd rather have a solution instead of a work around, assuming that someone has already seen and solved this problem.
Thanks....