Bug 419344 - Color Picker work wrong
Summary: Color Picker work wrong
Status: RESOLVED DUPLICATE of bug 405605
Alias: None
Product: kdenlive
Classification: Applications
Component: Effects & Transitions (show other bugs)
Version: 19.12.3
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-28 17:43 UTC by inFlowia Lab.
Modified: 2021-02-14 22:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: timeline_corruption+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description inFlowia Lab. 2020-03-28 17:43:35 UTC
SUMMARY
Effect Chroma-Key: Advanced and Chroma Key: Basic works wrong with color picker. 
I talking about a color picker that is immediately on the effect panel - one that is in the form of a blue drop. If you choose a color using it, then he chooses not the color that is on the video, but more dull. 

SOFTWARE/OS VERSIONS
Linux: UbuntuStudio 19.10 but this happen on other versions too
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
If you click on the rectangle with the selected color and use the "Pick Screen Color" button inside the color selection panel, the color will be chosen a completely different color than the one selected using the button in the form of a blue drop. The color that is selected with the "Pick Screen Color" button is already correct.
Comment 1 emohr 2020-04-04 11:26:52 UTC
Do you get better result if you draw a rectangle while holding down the mouse key, instead of picking?
Comment 2 inFlowia Lab. 2020-04-04 13:46:53 UTC
(In reply to emohr from comment #1)
> Do you get better result if you draw a rectangle while holding down the
> mouse key, instead of picking?

Yes! If if i draw a rectangle then the result is identical, as if I clicked the "Pick Screen Color" button inside the color selection panel.
Comment 3 Vincent PINON 2021-02-14 22:02:38 UTC

*** This bug has been marked as a duplicate of bug 405605 ***