|
Type:
|
Wish List
|
|
Priority:
|
High
|
|
Severity:
|
Minor
|
|
Status:
|
Unassigned
|
|
Resolution:
|
Unresolved
|
|
Resources:
|
Nobody
|
|
Reported By:
|
Bob Denny
|
|
Component:
|
Whole Product
|
|
Versions Affected:
|
5.0
|
|
Start Date:
|
?
|
| Created: |
9/25/2009 8:47:16 AM |
| Revised: |
4/9/2015 8:00:27 AM
|
|
Implement these in PinPoint, allowing it to handle "overscan" regions found on professional imagers. From John Farrell:
BIASSEC = '[1058:1121,1:1024]'
TRIMSEC = '[18:1041,1:1024]'
DATASEC = '[18:1041,1:1024]'
The values are for my chip. BIASSEC defined the region to be used for the
overscan correction, not necessarily the entire overscan region. TRIMSEC is
the region to be retained after trimming. DATASEC is the region containing
the actual data. For my and most others, TRIMSEC and DATASEC are the same
but they don't have to be.
|
|
|
Links |
|
ACP-1130
|
|
Handle images with overscan regions and extend subframing
|
Related
|
|
PINPOINT-163
|
|
Handle negative pixel values
|
Related
|
|
|
|
|
|
|
|
|
Are you sure that you want to reset the votes?
