 |
Mixed up with 0000657 so closing this one. |
|
|
Mods suggested to change/improve Chromakey (mixed up with BT 0000657). |
 |
@IgorBeg +1 And possibly change the name: Threshold --> Hue range |
 |
@Andrea_Paz @ALL I tested your values for Threshold and Slope in ChromaKey plugin. It seems good to me. I agree with you for the change. I think would be better to swap the position of the Threshold and Slope items in the GUI: from top to bottom, first Threshold and then Slope, because Threshold is the master, I think. I would like to have the GUI improvement like for the ChromaKey-HSV plugin, if possible. |
|
|
In chromakey.C we have as default settings (Reset): ChromaKeyConfig::ChromaKeyConfig() { reset(); } void ChromaKeyConfig::reset() { red = 0.0; green = 0.0; blue = 0.0; threshold = 60.0; use_value = 0; slope = 100; } I propose the following changes: threshold = 10.0; slope = 0; Above all, the Slope at 0 is important because otherwise we will have too much "transparency" that makes it impossible to recognize the key color. Finally, the plugin works fine for me. What are the problems that have been encountered? |
|
|
The ChromaKey HSV plugin works reasonably well, it is only the "Min Saturation" slider that works improperly. Overall, the plugin allows you to extract keys of sufficient quality. The "Min Saturation" problem has been solved in CinHV: the plugin has been rewritten and improved, bringing it even closer to the original plugin that inspired Jerome, namely Avid's SpectraMatte. https://github.com/heroineworshiper/hvirtual/tree/master/plugins/chromakeyhsv |
- Anonymous
