View Full Version : Burn-in problems
Nick Shaw
12-17-2007, 10:00 AM
Is anybody else seeing the same issue I am when adding a timecode burn-in in Redcine? It looks fine in the GUI, but the rendered frames have what looks like a massive gamma shift in the image, making them look burned out. Possibly an alpha pre-multiplication error when overlaying the text?
The issue is obvious in the attached JPEGs. They are two Redcine snapshots, with no settings changed, except changing the snapshot mode from 'View' to 'Image'.
For reference, my machine is an 8-core Mac Pro with 4GB of RAM, and an ATI 1900 graphics card.
Rob Lohman
12-17-2007, 10:19 AM
Thanks for letting us know
Hi Nick,
can you provide exact steps on how to reproduce the problem?
thanks
leo
Nick Shaw
12-17-2007, 02:45 PM
can you provide exact steps on how to reproduce the problem?
Just turn on any burn ins.
It's not a question of how to reproduce it. On my system it always happens.
Hi Nick, we could reproduce the problem. it is only happening on the OSX version.
working on it.
thanks for the feedback
leo
Mark L. Pederson
12-19-2007, 04:41 AM
Hi Nick, we could reproduce the problem. it is only happening on the OSX version.
working on it.
thanks for the feedback
leo
Great to see you here Leo!!! You need an avatar!!
Epyx2000
12-27-2007, 07:33 AM
Is anybody else seeing the same issue I am when adding a timecode burn-in in Redcine? It looks fine in the GUI, but the rendered frames have what looks like a massive gamma shift in the image, making them look burned out. Possibly an alpha pre-multiplication error when overlaying the text?
The issue is obvious in the attached JPEGs. They are two Redcine snapshots, with no settings changed, except changing the snapshot mode from 'View' to 'Image'.
For reference, my machine is an 8-core Mac Pro with 4GB of RAM, and an ATI 1900 graphics card.
Ah, yes, this is what I was trying to ask in my post http://www.reduser.net/forum/showthread.php?t=6883. You did a much better job of asking!
Thanks for the heads up.