ok, cool thanx.
Since jofemodo said to burn a new image, I suppose that I have to write down all my settings since it’s a custom Zynthian or can I save my prefs ?
There is a backup option in webconf.
1 Like
Be warned that restoring “config” files could not work. A lot of things have changed in the core and I wouldn’t recommend to do it, but you could try. Data backups (snapshots, etc.) should be restored without problems.
Regards!
1 Like
Ok, I’ll just make some screen captures of the webconf.
It’s a good idea to copy off the my-data folder
1 Like
Hi,
I was somewhat away from zynthian for a while …
I love very much this new version. The mixer is the feature I was expecting to really make of Zynthian the companion of my keyboard and theremin…
I simply updated to staging version for a while, it looked to work fine on my V2.1 kit.
Then I burned another SD with stable as advised. It ended with an error. I changed kit to V2 in conf, the error disappeared. But I had to
1- change repositories to staging
2- update
3- change repository to stable
4- update
To have the encoder and switch working.
Best
I think that it would be wise to first make a copy of my existing SD before making. I saw that with Etcher there is a clone option, I suppose that the backup function? Unless I simply buy a new SD.
1 Like
It is best practice and our advice to use a separate SD card for upgrades. It is wise to keep a spare card in case of issues with the main one.
2 Likes
I’ve been testing the new release and there are still some wrinkles to iron out, I’m not sure whether I should comment them here, open a new thread or just open a new issue in github.
Until I’m educated in the best practices, let me explain the most noticeable one.
When you have multiple chains, you can get to the control view of each one in different ways:
- from the mixer, move to a chain and select it
- from the control view, go to the next chain using the layer button (short click)
- using a Program Change
1 and 2 work fine, you get the control view with the proper controls and values
Number 3, using Program Change to select a chain via a ZS3 does not work properly when you are in the control view. The ZS3 subsnapshot is loaded with the right values, you can use the chain and everything sounds fine. But the ui controls are not updated for the new chain and you see the controls of the former chain. If you go back, you still navigate in the former engine. Seems like the screen params are not updated. If you go to the mixer and come back, then you can see the right params, so it’s only a matter of a missing update somewhere.
Hope it helps!
I am not keen on program change messages changing the selected chain. I raised this during development but don’t remember it being changed but maybe it was. I can see workflows that would benefit from the feature and others that wouldn’t. Maybe we could consider an option to enable this feature.
fix_zs3_control_refresh.diff (519 Bytes)
I’ve taken a little time to understand a small part of the code and I’ve come up with this two-liner fix for the control screen refresh.
Hope it is right!
1 Like
It can be simpler than that:
fix_zs3_control_refresh_1.diff (520 Bytes)
but we need to see what happens under other conditions, e.g. when in multitimbral mode.
2 Likes
But @riban, ZS3 Program Change actually DOES CHANGE the selected chain, and the GUI should reflect the change. It already does when you are in the mixer view, and it should do when you are in Control View.
-
In stage mode, it simply MUST be like this. Active chain recives all MIDI input. It can’t be done in a different way. There is no discussion here.
-
In Multitimbral mode we could keep the active chain unchanged, ignoring the “active chain setting” stored in the ZS3. It’s not going to make a big difference. We could discuss this
Regards,
Any chance this will make it into the testing/stable branch? I don’t know if it fixes the multitimbral mode, but it certainly solves the problem in stage mode.
Hello everybody.
I had just installed the 2210 version and from webconf I did the update to have the 2211 which seems to have been successful, but in webconf I see that the firmware is still 2210. Is this normal? Thank you
No, you have to select, “Stable” then update.
Well done to the team here. A fantastic achievement.
The new Main FX feature seems like a handy way to have your favourite FX available across different Chains. Is there a way to control each Master FX level? Like the same way you would have a Bus send level in a DAW where the FX is on the Bus.
Thanks again for making such a joyful device
1 Like