189
edits
Changes
mLine 1:
Line 1: − + Line 8:
Line 8: − + Line 15:
Line 15: + + + + + + + + + + + Line 26:
Line 37: − + − + + + Line 38:
Line 51: − 1.If you are using ACTI mode for your input device+ − + − + − + − * Enable “Active MIDI chanel” in the admin menu. With this enabled, all chains in the same MIDI channel will receive the MIDI stream from the input when some of them is selected (active).+ − * Setup your “cloned” chains in the same MIDI channel.+ − + − + − + − * Disable “Active MIDI chanel” in the admin menu. With this disabled, only the selected (active) chain will receive MIDI from the input, not matter the MIDI channel.+ − * Setup your “cloned” chains in the same MIDI channel.+ − * Create a MIDI+Audio chain in the same MIDI channel. We call this chain the “GROUP” chain. You don’t need to add any processor, so you can select None from the list.+ − * From the GROUP chain options, access “MIDI out” and select your “cloned” chains. This will route MIDI from the GROIUP chain to the cloned chains.+ − * Finally, access “Audio Out” submenu on each cloned chain: uncheck the Main Bus and check the “GROUP chain”. With this you are routing audio from your cloned chains to the GROUP chain, so you can control de mixed audio with the GROUP’s fader. − * Nice, true? I really love this way, but there is a little problem with it. Latency. When you route-back audio from chain’s output to the GROUP chain, you add latency. This is a general rule in digital audio processing: If you feed-back the signal, you add 1-period delay. The MIDI stream is not delayed because there is no real feed-back and it’s processed linearly. − − 2.If you are using MULTI mode for your input device − − * Simply setup your “cloned” chains in the same MIDI channel. That’s all. Line 73:
Line 80: − ===Improvements to VNC=== − Good news for those with headless/barebones setups, there are noticeable improvements to the speed and quality of the VNC connection to Zynthian. − Riban: The fixes were in later versions of VNC libraries that we benefit from by moving to Debian 12 Bookworm. The previous versions were horrible with screen tearing, etc. − − ===Wifi Setup & Accessing Webconf=== − − As of writing, it is not possible to set wifi directly in Webconf. It must be set from within the ADMIN > Wi-Fi Config menu. − − The password for access (Webconf, VNC UI & Engines) is now: '''opensynth'''
no edit summary
==Introduction==
==Introduction==
This is a guide to the x64 Oram testing image version of Zynthian. Based on 64-bit Debian 12 (Bookworm), it will eventually become the new stable version. There are numerous changes to the UI and lots of refactoring under the hood according to the devs. This guide will aim to summarise the important changes or things to note about the testing version from forum discussions. As ever, this guide will be wrong in places or fall out of date so check the [discourse.zynthian.org | forum] if the guidance here isn't working for you. Feel free to contribute if you've found something relevant to add here, if you don't have an account, ask in the forum.
This is a guide to the x64 Oram testing image version of Zynthian. Based on 64-bit Debian 12 (Bookworm), it will eventually become the new stable version. There are numerous changes to the UI and lots of refactoring under the hood according to the devs. This guide will aim to summarise the important changes or things to note about the testing version from forum discussions. As ever, this guide will be wrong in places or fall out of date so check the [https://discourse.zynthian.org forum] if the guidance here isn't working for you. Feel free to contribute if you've found something relevant to add here, if you don't have an account, ask in the forum.
==Getting started==
==Getting started==
===Compatibility===
===Compatibility===
So far, Raspberry Pi3, Pi4 and Pi5 are compatible. Pi5 have some issues to solve, but it's mostly working OK.
So far, Raspberry Pi3, Pi4 and Pi5 are compatible. Pi5 has some issues to solve, but it's mostly working OK.
===Installing Oram===
===Installing Oram===
https://os.zynthian.org/test/2024-03-01-zynthianos-bookworm-aarch64-oram-2403.zip
https://os.zynthian.org/test/2024-03-01-zynthianos-bookworm-aarch64-oram-2403.zip
===Updating the Software===
When new updates are available, the green heart is replaced by the '''green recycle symbol''' and the update entry is shown (see image below). Please note that the update entry is not shown in the admin menu if no updates are available (aka you are updated to the last).
===Improvements to VNC===
Good news for those with headless/barebones setups, there are noticeable improvements to the speed and quality of the VNC connection to Zynthian.
===Wifi Setup & Accessing Webconf===
As of writing, it is not possible to set wifi directly in Webconf. It must be set from within the ADMIN > Wi-Fi Config menu.
The password for access (Webconf, VNC UI & Engines) is now: '''opensynth'''
==The Zynthian UI Workflow==
==The Zynthian UI Workflow==
==Chains==
==Chains==
*Or you could try a midi device and assign the UI navigation to buttons you have available See [[Zynthian_UI_User_Guide_-_V1/V4#CUIA:_Callable_UI_Actions | the CUIA page of the user guide]] for more on this.
*Or you could try a midi device and assign the UI navigation to buttons you have available See [[Zynthian_UI_User_Guide_-_V1/V4#CUIA:_Callable_UI_Actions | the CUIA page of the user guide]] for more on this.
Note also a '''circular green arrow''' in the top right corner of the screen to indicate that an update is available to download.
Note also a '''green recycle symbol''' in the top right corner of the screen to indicate that an update is available to download.
<br clear=all>
<br clear=all>
==Midi Input==
==Midi Input==
There are some changes to the midi options. Currently the ACTI (Active) mode is used to accept midi input to the currently selected chain. The MULTI (Multitimbral) mode is used to select the individual chains you wish to accept midi from the given device. This can be one chain or multiple. E.g. mimi-d synth can be assigned to accept midi from both a keyboard and sequencer at once. More to come....
There are some changes to the midi options, now there are only two 'modes':
* '''ACTI''' (Active) mode is used to accept midi input to the currently selected chain.
* '''MULTI''' (Multitimbral) mode is used to select the individual chains you wish to accept midi from the given device. This can be one chain or multiple. E.g. mimi-d synth can be assigned to accept midi from both a keyboard and sequencer at once.
<blockquote>
<blockquote>
First, you may note that the “clone” option does not exist anymore. We have better mechanisms in oram because several chains can use the same MIDI channel.
First, you may note that the “clone” option does not exist anymore. We have better mechanisms in oram because several chains can use the same MIDI channel.
#If you are using ACTI mode for your input device
#*A. THE EASY WAY
A. THE EASY WAY
#**Enable “Active MIDI chanel” in the admin menu. With this enabled, all chains in the same MIDI channel will receive the MIDI stream from the input when some of them is selected (active).
#**Setup your “cloned” chains in the same MIDI channel.
#*B. THE COOL WAY
#**Disable “Active MIDI chanel” in the admin menu. With this disabled, only the selected (active) chain will receive MIDI from the input, not matter the MIDI channel.
#**Setup your “cloned” chains in the same MIDI channel.
B. THE COOL WAY
#**Create a MIDI+Audio chain in the same MIDI channel. We call this chain the “GROUP” chain. You don’t need to add any processor, so you can select None from the list.
#**From the GROUP chain options, access “MIDI out” and select your “cloned” chains. This will route MIDI from the GROIUP chain to the cloned chains.
#**Finally, access “Audio Out” submenu on each cloned chain: uncheck the Main Bus and check the “GROUP chain”. With this you are routing audio from your cloned chains to the GROUP chain, so you can control de mixed audio with the GROUP’s fader.
#**Nice, true? I really love this way, but there is a little problem with it. Latency. When you route-back audio from chain’s output to the GROUP chain, you add latency. This is a general rule in digital audio processing: If you feed-back the signal, you add 1-period delay. The MIDI stream is not delayed because there is no real feed-back and it’s processed linearly.
#If you are using MULTI mode for your input device
#*Simply setup your “cloned” chains in the same MIDI channel. That’s all.
==Main Menu==
==Main Menu==
==Webconf Changes==
==Webconf Changes==