Hi ,
Zynthian OS in the step sequencer causes the system to flicker wildly through all the menus when I start the track. The encoders are not connected.
grettings
Hi ,
Zynthian OS in the step sequencer causes the system to flicker wildly through all the menus when I start the track. The encoders are not connected.
grettings
Greetings @D64FAN63 - We need more information to help you, like what kind of Zynthian youāre running (V5, V4, DIY, etc), what version of software youāre running, how you āstart the trackā, and whatās in the track, perhaps the saved sequence file, etc. A screenshot from the top level or ādashboardā of webconf will provide a lot of info, and in this case a video of what you do and the flickering result might help also. If you use the āReport Issueā button at the bottom of the dashboard it will automatically capture a lot of the info. Help us help you!
Thank you for considering my request. Iāve solved the problem my own way for now.
I used my SD card backup, and the flickering disappeared. Then, after accessing the VNC server via the web configuration, I navigated through the menus a bit with the mouse, and everything was fine. After that, I reconnected the encoders, and everything was normal at first, but then the slight menu hopping started again. Then, I overclocked the CPU to its maximum (Raspberry Pi 3B+) via the web configuration, and everything is working normally without the menu hopping.
Iāll do further testing tomorrow.
Iām using your encoder board from the V2 kit, but Iāve plugged in different encoders with a board that only has pull-up resistors and no capacitors.
I wonāt receive those until next week.
In any case, everything seems to be okay for now.
Greetings from Hamburg, Peter
That sounds like the MIDI had events on the āMaster Channelā, triggering CUIA. I thought we had resolved this. What version of zynthianOS are you running?
Hi,
Iām using the latest stable version of Oram.
If there are sequences that send notes on the āMaster Channelā, CUIA may be triggered. There are some safeguards against this happening, e.g. we disable āMaster Channelā by default and do not allow chains to be set to the āMaster Channelā but this situation can sitll occur, e.g. if an older snapshot has such configuration or if you change the āMaster Channelā to an already assigned MIDI channel.
It may be advantageous to avoid notes on the āMaster Channelā reaching CUIA from the sequencer or SMF player. It may be worth raising a ticket about this in the issue tracker. I am sure this is likely to be the cause of the problem you had.
Sorry for the odd question: How do I create a ticket in the issue tracker? Thanks.
You can press the big red Report Issue button at the bottom of the home screen AKA the Dashboard in webconf.
If you canāt or donāt want to access webconf you can use this link to github:
See the wiki if any of these terms are new to you:
Okay, thank you.
Uploading via GitHub isnāt working; an error report has been sent. The video and WBconfig screenshot are in this thread.
OK, did @riban ās explanation and suggestions above make sense to you?
Thank you very much, yes I partially understand, the master channel is now at 0 and now everything seems to be normal.
Far out! Were you able to make a trouble report in the issue tracker? If not, let us know here please.
I sent something but didnāt write anything about it.