Works fine! Many thanks
I have raised issue 1028 describing this bug and @Klangschmiedās suggested solution which also fixed it for me. I had not noticed the issue until today so it must be a recent regression. Ironically, the display profile called, āMIPI DSI 800x480 (inverted)ā is actually inverted 
.
1 Like
Thank you very much, it works perfectly now
First time I can contribute to solving an issue, otherwise I am always asking for help
1 Like
Raising an issue is better than keeping quiet. Giving descriptive information about the issue is better than saying, āIt doesnāt workā. Talking about the issue is better than ignoring it. I donāt think everyone appreciates how useful they are to projects. It is all too common for users to sit silently waiting for a developer to chance upon some issue that is bugging the user. This rarely happens. Developers like to be told of issues with their products. They also appreciate the praise when it comes too! So thank you @Klangschmied and everyone who talks about their problems. It is good to talk! 
3 Likes
The display should be reconfigured. This part:
dtoverlay=rpi-ft5406,touchscreen ā¦
must be deleted and zynthian rebooted.
Regards,
1 Like
@jofemodo thanks.
For me understandig: we do not need the line ādtoverlayā¦ā anymore?
Exactly! And choose āinvertedā in the selectbox, down in the form
Regards!
@jofemodo will there be a fix in a Zynthian update for this?
It works ok in my V5 units and AFAIK, nobody complained except @Klangschmied . I will check the update procedure anyway.
Regards
1 Like
I am complaining. I went to my V5 today and found the touch was inverted. Something changed recently which broke this. There should be an update to fix the regression.
1 Like
I installed ORAM 3 days ago and ran into the inverted touchscreen issue too. Found the same solution in webconf. Works fine. If an update will fix this some day, it would be nice. For now IĀ“m happy with the features .
1 Like
Itās fixed. An update should fix things now.
Regards!
4 Likes
GENIUS! Thanks
Perfect, thanks!
It seems that when you load a track with fluidsynth and switch to the fullgrand preset, the preset names change, but the sound remains the same. Essentially, the preset doesnāt actually change. Does it behave the same way to you too? Thanks for your help
These are not essential things, but I communicate these problems:
The calibrate touchscreen function does not work even if the display works normally.
I use Pi 7 Touchscreen Display 800x480.
lcd_rotate=0
dtoverlay=rpi-ft5406
At startup I get this message:
Failed to start backlight.service ā Turn on/off Display backlight
For the rest everything seems to work (now I check the problem encountered by @mnovaro).
Thanks
I have done some tests and I confirm to you that, in addition to not loading the flud grand presets, it gives me the same errors as yours, including the display calibration not working.
But putting : lcd_rotate=0 on the driver settings, the touchscreen works fineā¦
@Lanfranco Calibrate screen works on a standard V4 with resistive touch screen. Maybe there is an issue with non-standard displays.
@mnovaro I confirm that Fluidsynth, Full Grands soundfont does not seem to change sound when some presets are selected but does for others, e.g. selecting āPiano Vib Pad 1ā adds vibrato.
[Edit] I think the instruments are just too subtle. As I try each one there are differences but some concsecutive pianos sound very similar. I donāt think there is a fault.
1 Like