and last point (promised) : i also tried the calibration function in the ADMIN UI from Zynthian… I see a cross in the middle of the display, touch it… becomes red…. and nothing… so after 15sec, it disappears… unless i made something wrong, this method seems not working for me.
I am using a 16” Waveshare HDMI+USB touchscreen display with the same pixel resolution of your model, on one of my custom Zynths.
I didn’t experience any touch calibration or reception issues, except the notorious bug of having to briefly disconnect and reconnect the USB touch cable at startup.
At home I will check my display settings and overlay in webconf > hardware, but I seem to remember that I simply tailored the resolution of an existing Waveshare 7” screen driver.
noted, thanks Aethermind. will check the unplug/plug solution also….
I will also try a bash script that i found in the forum to calculate transformation matrix… let’s see this solution.
By the way, as i use a UR12 Rolnad USB sound interface, i also experienced issue with start-up when the interface and the akai APC keyboard are plugged at same time. I used to unplugged the keyboard to let the interface be correctly detected.. I did not think it could also be the same with the touch display. Let’s try this tonight…
The USB disonnect/reconnect solved the concern !!!
I presume the USB problem i have with the sound interface is also the same with the touch display… But when Akai APC is connected, the boot of UI is stopped by red ERROR audio/midi message…. And… (my bad), i did not think this problem could also affect the use of the touch functionnality for the display…
Thanks for the tip !! → issue can be considered as SOLVED
This solved the booting issue when the AKAI APC is already plugged…. but the touch display remains unsuable : the solution in this case is to unplug and plug again .. probably this re-initialize the drive ?? this is far beyond my technical capabilities…
They are seperate issues. The system won’t start unless jack (sound subsystem) is running. Jack won’t start if it doesn’t have a valid soundcard. Using a numeric index of a soundcard is bad because if you have multile devices plugged in that the OS identifies as soundcards, then they may be detected in different orders on each boot and hence the wrong one may be used by jack and, if that isn’t a real soundcard then it will fail. This is why you should use a named device for the soundcard.
The touch interface is a flaw in the touch device and its linux driver (module). It is not being properly reset at boot, e.g. the driver loads but the device is not yet operational. Replugging after boot allows the device driver to react to the device becoming available. This shouldn’t be required but without a real device in our hands, we are unlikely to be able to resolve this. (There are some touchscreens that are simply broken and will never work properly without such work-arounds.)
I have used the information from the forum to run a script automatically after Zynthian is launched which fixes my calibration issues (a few minutes after start up). Perhaps this might be useful to you?
Hello ! and best wishes to all zynthian people there !
I read this discussion recently, but transformation matrix does not seem to be a solution to the waveshare…
As said, if i start zynthian without the USB connected to the waveshare, and then i connect it after the boot, everything works like a charm !
I contacted waveshare to get a support, they replied and suggested me to test the same with a brand new raspberry pi OS… hence i did it … and it works also like a charm ! If i start the pi 5 with Rasp pi OS (debian), waveshare being connected (hdmi and USB) before the boot, it works !
Which let me think there is probably something in the boot sequence (x server ? zynthian GUI ?)…
Comparing the way rasp pi OS and zytnhian OS are booting the different services could give some ideas… but this is far above my modest knoweldges…
I wonder if have you tried tapping in the top left corner of the screen before unplug and replug? There have been a few reports of folks having non-responsive touch screens until unplug/replug, while others have had scaling issues (myself included in the latter). I ask only because it could be helpful to categorize the issues.
Good tip, always thought that touch was not working, but no i understand that i belong to the scaling problem group. Now i have a new lead, and will pick up on solving that issue. Thx
touch is working in a sense that when i tap the left top corner, something happens… it is always different. it looks like the input area is located on top left, but the area is so small that it is impossible to predict anything.
i tried different way to calculate a transofrmation matrix (several tips are given in the forum).
But impossible to have any data from the scripts : no transofrmation matrix given in output of the scripts…
do you mean that i shoudl try to make a X98 config file with a random transformation matrix just to see what would happen ?? i do not exactly understand what are the meaning of the figures of this matrix, i am little afraid about making a matrix with figures i do not know what they do….
