As you probably realize, zynthian developers have not every display in the webconf list, so we can’t fix this kind of issues without user’s active collaboration. We totally rely in users for updating the configuration for their specific displays and soundcards. User’s having hardware configuration issues with specific devices should try reading the manufacturer specs & docs or searching the network to find the configuration that works. Then report here the curated configuration options so we can fix in the webconf tool. Yet better, send a PR to the zynthian-webconf repository!
I don’t have the exactly same model, but I solved my problems when applying the profile WaveShare 7 HDMI+GPIO 1024x600 as mentioned above, despite the fact I have a HDMI+USB display version, too. Finally it seemed that of all the options defined by that profile, only the option dtoverlay=vc4-kms-v3d is really necessary, but after installing the latest image, I had to return most of the options again to get rid of some strange issues:
So, the only one I can surely do WITHOUT is the last line with dtoverlay=ads7846,.... Of course, with these options, I can also use the Generic HDMI/DSI Display profile.
Thank you for your fast response.
I must declare that I did not think to access via webconf, but after reading you I did it, and then was able to set up and run my hardware setup. I attach a screenshot previous to properly configure my audio BEHRINGER card nor wiring EXTRA.
However I had the (bad?) idea of update the software and since then I have no access to webconfig though my Zynthian seems to work…
May I put a new image without software update?
Regards,
Hi,
Did something change from accessing zynthian.local?
I cannot get to webconfig anymore. Last ORAM update I did was in June/July and I had no issues. Did not have a chance to play since and I did a fresh install from the latest and now I can’t access that anymore. Did I miss something?
Thanks
@wanthalf thanks for the advice, deleting the line with dtoverlay=vc4-kms-v3d helped.
for the combination of 2024-09-14-oram and WaveShare 7 HDMI+GPIO 1024x600 the working setting for the size of the layout on the display is now the following
@jofemodo, it’s clear to me that you can’t contain all the obscure devices we find on the table and connect with the zynthian. According to me, the biggest problem is with bookworm updates, or rather some of its components, which throw off the tuned configurations.
Unfortunately I have the exact same problem. Webconf is working on the fresh 2024-09-14-oram. After software update is webconf out of connection. But net connection to zynthian is working, zynthian is plaing over the rtp-midi.
Ok so it’s definitely not my setup and something to do with the latest 9-11 or 9-14 update.
I have a ReTerminal with the last stable release and I can connect to and use webconf with no issues so something definitely changed. @jofemodo
I suppose these changes in behaviour are caused by the Linux kernel changes. Personally, I would prefer a kernel as new as possible, even if I have to find a new configuration method again. This configuration we use is still obsolete, but the new one does not work for me.
Anyway, the display starts with wrong resolution and it gets fixed only in the middle of the boot process. The older system worked better and we should find out how to use the new kernel properly. Maybe it will improve again with some even newer kernel…?
I just came here to say I figured out what the issue was. It’s raspberry pi imager. For some reason it doesn’t like using these unzip images. Never had that issue before.
I used Balena etcher with the same zipped image and webconf works and I can access zythian.local again using the same method I was using before.
So it looks like with raspberry pi imager, even though it wrote it and verified it without any issues it somehow messed things up. I was able to successfully do this with both the cm4 and pi400. Also the rebooting issue I had with both is also no longer an issue.
Moral of the story is: UNZIP the image before using raspberry pi imager to avoid some weird things happening
@ToFF if you used raspberry pi imager to write the image without unzipping, I would suggest you either unzip and burn again or use Balena etcher. That fixed my issue with both Pi’s I was having. Looks like raspberry pi imager does not like zipped images.
Good news, I manage to get the waveshare https://www.waveshare.com/wiki/CM4-DISP-BASE-5A display working with Bookworm. I downloaded and installed everything mentioned for Buster in the wiki, then instead of adding dtoverlay=vc4-kms-dsi-7inch which did not work by itself. I did some digging and combined a few things:
Bingo, screen came on and touch works. Unlike what waveshare support said and what they got in that wiki.
This combo seems to work. Now I just have to select the correct display in webconf but it’s late and I’m calling it done for today.
Glad I don’t have a useless cm4 kit with 5 inch screen anymore.
Hello I have installed Oram because @jofemodo said.
I’m now confussed how i can use the Salamander /Grnad Piano in the Sifzz dir.
The Sfizz SFZ engine is enabled but where can i select this ?
I go to Add instrument Chain and i could not find Sfizz.
In Oram, when you add an instrument chain (Midi channel) from the MAIN page, you are shown a list of available synthesis engines organised in categories (synths, samplers, pianos, drums, generators, etc.).
Turn the relevant knob on the right side of the official V5 kit, swipe your finger diagonally on the right side of a touchscreen or scroll the mouse, and you will see Sfizz in the sampler section.
Is anyone having trouble getting touch to work as expected with the latest ORAM. I Can scroll via touch, I can highlight an option but that’s it, nothing else happens. I tried short, long or bold touch and nothing. I can’t access admin, I can’t add chain, I can’t to anything besides scrolling and when touching main or mixer to go there. When I touch “back”, nothing happened as well.
I started reading the latest user guide to see if maybe things have changed regarding touch but I don’t see any difference from last stable to now.
I fired up my stable zynthian ReTerminal and touch works as expected.
Someone please tell me what I’m doing wrong I’ve updated both my pi 400 with a 7 inch usb touch and cm4 with 5 inch kit mentioned in my previous posts. For the 7inch I’ve selected 7 inch with hdmi in webconf and also generic hdmi. No difference.
Adding or removing dtoverlay=vc4-kms-V3d doesn’t do anything.
,