View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000932 | DCP-o-matic | Features | public | 2016-08-10 10:56 | 2024-01-03 00:26 |
Reporter | Carsten | Assigned To | carl | ||
Priority | low | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Platform | Mac | OS | OS X | OS Version | 10.6 |
Product Version | 2.9.0 | ||||
Summary | 0000932: Add cursor based X/Y/Z number display in vector scope, giving 'real' 12Bit X/Y/Z numbers | ||||
Description | Add cursor based X/Y/Z number display in vector scope, giving 'real' 12Bit X/Y/Z numbers. So if you move the cursor over the image/vectorscope, you would see the full X/Y/Z triplet for the specific part of the image, based on the actual conversion formula set up in color conversion.
| ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | Average | ||||
|
Basic mouseover in video waveform done in f8a0bc6135a933dcf660bbc46b4b3d29d503690e |
|
Yup, works, but would be nice to beef this up to show all three XYZ values simultaneously. |
|
I'm not sure I follow. The XYZ values would all equal to the "component value" in that window. It's not showing the image, it's showing the frequency of each possible X/Y/Z pixel value in each vertical strip of the image. So if we have one vertical strip of the video waveform at, say, x=42 which looks like this: <pre> it means that that vertical line in the <b>image</b> has lots of high-valued (4096/3584/3072) pixels, lots of low-valued pixels (0-512) and not much in between. What do you need to find out from the waveform? |
|
The idea is to not have to switch the component selector X/Y/Z at the top to see all three XYZ values at the same time for the same mouse position. Maybe need to switch from vectorscope to an image coordinate based display? Would be quite helpful to see the actual XYZ value for a specific image region.
|
|
What you say would make sense for an image coordinate-based display, indeed. With the current display the X, Y or Z values for any particular part of the image would be the same, since the mouse-over numbers just say where the mouse is in the image, not what it contains. |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-08-10 10:56 | Carsten | New Bug | |
2016-08-10 16:04 | carl | Assigned To | => carl |
2016-08-10 16:04 | carl | Status | new => acknowledged |
2016-08-16 14:10 | carl | Note Added: 0001370 | |
2016-08-16 16:04 | carl | Target Version | => 2.11.0 |
2016-08-19 14:18 | Carsten | Note Added: 0001386 | |
2016-08-22 16:31 | carl | Note Added: 0001387 | |
2016-08-22 16:31 | carl | Note Edited: 0001387 | |
2016-08-22 16:32 | carl | Note Edited: 0001387 | |
2016-08-22 16:33 | carl | Note Edited: 0001387 | |
2016-08-22 16:33 | carl | Note Edited: 0001387 | |
2016-08-22 16:33 | carl | Status | acknowledged => feedback |
2016-08-22 19:55 | Carsten | Note Added: 0001388 | |
2016-08-22 19:55 | Carsten | Status | feedback => assigned |
2016-08-22 19:59 | Carsten | Note Edited: 0001388 | |
2016-08-22 21:40 | carl | Note Added: 0001390 | |
2017-04-21 10:13 | carl | Target Version | 2.11.0 => |
2024-01-03 00:26 | carl | Status | assigned => acknowledged |