macgregor
Veteran
I´ve spent +4 hours dealing with the following issue: Sony Vegas does not use more than 8bits from QT files. I´m not sure this is a QT issue or a Vegas issue but in any case, it's bad for us.
After noticing how prores files looked really bad in Vegas (compression artifacts, banding...), I started playing with different formats in the timeline and applying contrast to see where the gradients break.
These is what I've found out so far:
- QT prores files show artifacts and banding in Vegas (8bit or 32b don´t affect this issue).
- Opening that same file in AE CS6 shows no problem. It looks perfect.
- Converting the prores file in AE to a high quality codec like blackmagic 10bit RGB as AVI and then importing it in Vegas --> shows no issues. It looks perfect.
- Converting the same prores file in AE to the same blackmagic 10bit RGB codec as MOV, and then importing that file in Vegas --> shows compression artifacts and color banding.
Then I tried a couple more formats and the results are consistent. QT files in Vegas look like crap even when the format and original source were 10bits.
After noticing how prores files looked really bad in Vegas (compression artifacts, banding...), I started playing with different formats in the timeline and applying contrast to see where the gradients break.
These is what I've found out so far:
- QT prores files show artifacts and banding in Vegas (8bit or 32b don´t affect this issue).
- Opening that same file in AE CS6 shows no problem. It looks perfect.
- Converting the prores file in AE to a high quality codec like blackmagic 10bit RGB as AVI and then importing it in Vegas --> shows no issues. It looks perfect.
- Converting the same prores file in AE to the same blackmagic 10bit RGB codec as MOV, and then importing that file in Vegas --> shows compression artifacts and color banding.
Then I tried a couple more formats and the results are consistent. QT files in Vegas look like crap even when the format and original source were 10bits.
Last edited: