Xinput coordinate transformation matrix
Clash Royale CLAN TAG#URR8PPP
I am trying to calibrate a 3.5" pitft
touchscreen on a Raspberry Pi 3 using xinput
.
I have the display rotated so it uses a landscape orientation, with the power connector facing "up" so it can rest on my desk - this means a 270 degree rotation from default. The first challenge was rotating the input to match the screen orientation, which I acheived with:
xinput --set-prop 'stmpe-ts' 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0 1
Now I need to match my touch area to the screen area - currently it uses only the inner 80% or so, so as touches move out from center they become increasingly inaccurate, and things like a scrollbar on the screen edge are completely unreachable.
How can I adjust the command above to calibrate touch area size and offset, without losing my rotation or introducing shear, and without going back to school for a linear algebra degree?
update
I found this:
https://wiki.archlinux.org/index.php/Talk:Calibrating_Touchscreen
which talks about using xinput_calibrator
to generate a transformation matrix. Unfortunately none of the scripts referenced there actually work - they don't appear to take rotation into consideration. The calibrator tool on it's own generates something like this:
Section "InputClass"
Identifier "calibration"
MatchProduct "stmpe-ts"
Option "MinX" "24507"
Option "MaxX" "24507"
Option "MinY" "43599"
Option "MaxY" "43599"
Option "SwapXY" "1" # unless it was already set to 1
Option "InvertX" "0" # unless it was already set
Option "InvertY" "0" # unless it was already set
EndSection
The scripts on that wiki are able to get me a matrix like this:
-144.03296703296703296703 0 52.63736263736263736263
0 -49.08988764044943820224 33.53333333333333333333
0 0 1
But that seems to still be a bit off, and comparing to the "simple" rotation above seems to be conspicuously missing some values.
raspberry-pi xinput
add a comment |
I am trying to calibrate a 3.5" pitft
touchscreen on a Raspberry Pi 3 using xinput
.
I have the display rotated so it uses a landscape orientation, with the power connector facing "up" so it can rest on my desk - this means a 270 degree rotation from default. The first challenge was rotating the input to match the screen orientation, which I acheived with:
xinput --set-prop 'stmpe-ts' 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0 1
Now I need to match my touch area to the screen area - currently it uses only the inner 80% or so, so as touches move out from center they become increasingly inaccurate, and things like a scrollbar on the screen edge are completely unreachable.
How can I adjust the command above to calibrate touch area size and offset, without losing my rotation or introducing shear, and without going back to school for a linear algebra degree?
update
I found this:
https://wiki.archlinux.org/index.php/Talk:Calibrating_Touchscreen
which talks about using xinput_calibrator
to generate a transformation matrix. Unfortunately none of the scripts referenced there actually work - they don't appear to take rotation into consideration. The calibrator tool on it's own generates something like this:
Section "InputClass"
Identifier "calibration"
MatchProduct "stmpe-ts"
Option "MinX" "24507"
Option "MaxX" "24507"
Option "MinY" "43599"
Option "MaxY" "43599"
Option "SwapXY" "1" # unless it was already set to 1
Option "InvertX" "0" # unless it was already set
Option "InvertY" "0" # unless it was already set
EndSection
The scripts on that wiki are able to get me a matrix like this:
-144.03296703296703296703 0 52.63736263736263736263
0 -49.08988764044943820224 33.53333333333333333333
0 0 1
But that seems to still be a bit off, and comparing to the "simple" rotation above seems to be conspicuously missing some values.
raspberry-pi xinput
add a comment |
I am trying to calibrate a 3.5" pitft
touchscreen on a Raspberry Pi 3 using xinput
.
I have the display rotated so it uses a landscape orientation, with the power connector facing "up" so it can rest on my desk - this means a 270 degree rotation from default. The first challenge was rotating the input to match the screen orientation, which I acheived with:
xinput --set-prop 'stmpe-ts' 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0 1
Now I need to match my touch area to the screen area - currently it uses only the inner 80% or so, so as touches move out from center they become increasingly inaccurate, and things like a scrollbar on the screen edge are completely unreachable.
How can I adjust the command above to calibrate touch area size and offset, without losing my rotation or introducing shear, and without going back to school for a linear algebra degree?
update
I found this:
https://wiki.archlinux.org/index.php/Talk:Calibrating_Touchscreen
which talks about using xinput_calibrator
to generate a transformation matrix. Unfortunately none of the scripts referenced there actually work - they don't appear to take rotation into consideration. The calibrator tool on it's own generates something like this:
Section "InputClass"
Identifier "calibration"
MatchProduct "stmpe-ts"
Option "MinX" "24507"
Option "MaxX" "24507"
Option "MinY" "43599"
Option "MaxY" "43599"
Option "SwapXY" "1" # unless it was already set to 1
Option "InvertX" "0" # unless it was already set
Option "InvertY" "0" # unless it was already set
EndSection
The scripts on that wiki are able to get me a matrix like this:
-144.03296703296703296703 0 52.63736263736263736263
0 -49.08988764044943820224 33.53333333333333333333
0 0 1
But that seems to still be a bit off, and comparing to the "simple" rotation above seems to be conspicuously missing some values.
raspberry-pi xinput
I am trying to calibrate a 3.5" pitft
touchscreen on a Raspberry Pi 3 using xinput
.
I have the display rotated so it uses a landscape orientation, with the power connector facing "up" so it can rest on my desk - this means a 270 degree rotation from default. The first challenge was rotating the input to match the screen orientation, which I acheived with:
xinput --set-prop 'stmpe-ts' 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0 1
Now I need to match my touch area to the screen area - currently it uses only the inner 80% or so, so as touches move out from center they become increasingly inaccurate, and things like a scrollbar on the screen edge are completely unreachable.
How can I adjust the command above to calibrate touch area size and offset, without losing my rotation or introducing shear, and without going back to school for a linear algebra degree?
update
I found this:
https://wiki.archlinux.org/index.php/Talk:Calibrating_Touchscreen
which talks about using xinput_calibrator
to generate a transformation matrix. Unfortunately none of the scripts referenced there actually work - they don't appear to take rotation into consideration. The calibrator tool on it's own generates something like this:
Section "InputClass"
Identifier "calibration"
MatchProduct "stmpe-ts"
Option "MinX" "24507"
Option "MaxX" "24507"
Option "MinY" "43599"
Option "MaxY" "43599"
Option "SwapXY" "1" # unless it was already set to 1
Option "InvertX" "0" # unless it was already set
Option "InvertY" "0" # unless it was already set
EndSection
The scripts on that wiki are able to get me a matrix like this:
-144.03296703296703296703 0 52.63736263736263736263
0 -49.08988764044943820224 33.53333333333333333333
0 0 1
But that seems to still be a bit off, and comparing to the "simple" rotation above seems to be conspicuously missing some values.
raspberry-pi xinput
raspberry-pi xinput
edited Mar 7 at 17:58
superstator
asked Mar 2 at 0:12
superstatorsuperstator
17117
17117
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503897%2fxinput-coordinate-transformation-matrix%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503897%2fxinput-coordinate-transformation-matrix%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown