ZynthianOS 2103 Stable Released

rolfdegen · April 7, 2021, 9:13am

Hello Zynthian friends …

I am newbie with Zynthian. Sorry for my question: Do I have to load the new Release version via the SD card or can I use the update function of the Zynthian webpage

rolfdegen · April 7, 2021, 11:02am

A little problem. I made the release 2103 via Webpage Update and reboot. When I load my old snapshot, I can’t edit a synth layer. It always jumps to the MY / generative / Zynscope

rolfdegen · April 7, 2021, 11:20am

I deleted all layers and created new layers. I deleted the old snapshots and created new ones. Zynthian now works without errors

Update: Now… i have same problem. Selecting the layers does not right work with my mouse. But it works with the Softkeys “LAYER” and “SELECT”.

I calibrated my mouse but the problem remains.

My current Zynthian version

I made a short video https://youtu.be/V7PtKectwEY

Thanks for help

Next problem: When I select a different patch, I have no parameters in the main menu and I don’t hear any sound.

Update: Now I clear my new image and install the old version . I hope my system its runnig as previously.

Update: I install new Image and its same problem
what am I doing wrong ?

All Patch parameter zerro ?

Solved:
It was my mistake. I have selected “Wiring Layout: Custom” in the wiring configuration. That was a mistake. With “Wiring Layout: Dummies” it works fine.

I’m learning more every day Thanks for watching. Rolf

MrDham · April 7, 2021, 8:33pm

Hi,

I faced this problem and entered an issue on Github:

github.com/zynthian/zynthian-ui

Test Branch: can't select layers properly.

opened 08:11PM - 07 Apr 21 UTC

closed 03:50AM - 08 Apr 21 UTC

MrDham

bug Hot-fix

**Describe the bug** Testing UI on test branch after fix of zynthian/zynthian-u…i#360. I can't select any other layer than the 1st created one. **To Reproduce** Steps to reproduce the behavior: 1. Create 2 layers 2. **Select** layer 1 -> You are in Layer 1 "control" 3. **Back** until you are in layer list 2. **Select** layer 2 -> You are in Layer 1 "control" 4. Push **Layer** -> You stay in layer 1 "control" **Expected behavior** 2. **Select** layer 2 -> You are in **Layer 2** "control" 4. Push **Layer** -> You change of layer "control" **Screenshots** I can get if required **Setup:** - SD-image Build Date: 2020-09-05 - Hardware Config Raspberry Pi 3 Model B Plus Rev 1.3 Soundcard: HifiBerry DAC+ Display: PiScreen 3.5 (v2) Wiring: MCP23017_EXTRA GPIO Expander: MCP23017 - Software Version zyncoder: testing (d852c8f) zynthian-ui: testing (1894310) zynthian-sys: testing (9b6ead4) zynthian-data: testing (194fd59) zynthian-webconf: testing (33699a7) **Additional context** Test branch.

Then I thought about:

Maybe you are expecting that people differenciate what they find in “Stable” branch from what they find in “testing” branch.

Have you identified any preferred ways of submitting bugs depending on which branch we are in ?

jofemodo · April 7, 2021, 10:54pm

When reporting a bug you always have to specify “the context”, and that includes the branch. The context can be “captured” by simply taking a shot of the webconf’s dashboard.

Both, stable & testing branches can have bugs. Some of them are common, some others can be bugs already solved on testing , but not merged to stable yet (hotfixes). Finally there are new bugs introduced on testing. (@riban, should we add these 3 labels to the triage system?)

BTW, I would like to encourage people to take seriously the task of reporting a bug. Please, don’t forget to include the context and detailed steps to reproduce the bug. If we can’t reproduce the bug, normally we can’t solve it. By reporting correctly, you are saving time of developers, and we can concentrate on code instead of the github’s issue manager

Thanks,