393
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + Line 28:
Line 30: − '''Note:''' Auto-connector have changed recently. Your MIDI keyboards/controllers are not connected directly to synth engines anymore. All the MIDI messages are routed thru the MIDI router/filter (zyncoder). No extra latency is added. Everything is done in the same jack processing frame.+ + Line 38:
Line 41: + + + + + + + + + + + + + + + + + + + +
no edit summary
This is just a partial list of features and it's probably outdated:
This is just a partial list of features and it's probably outdated:
RBPi2 is not longer supported by the latest zynthian SD images, so you need a RBPi3 or rebuild your own SD image.
* List of [[Zynthian_Supported_Synth_Engines]]
* List of [[Zynthian_Supported_Synth_Engines]]
* '''MIDI auto-connection''': You don't need to do nothing. Simply plug your controller and it will work as expected.
* '''MIDI auto-connection''': You don't need to do nothing. Simply plug your controller and it will work as expected.
* '''MIDI filter/router''': All input MIDI messages are routed thru the MIDI router/filter (zyncoder), that can be configured using simple rules from the webconf tool. The output MIDI stream is sent to synth engines and to the desired MIDI outs. No extra latency is added. Everything is done in the same jack processing frame.
* '''MOD-UI audio routing''': Route audio from standalone engines to MOD-UI, allowing to use MOD-UI as a Real-Time Audio Proccesssor for the standalone engines. Zynthian UI's layer options menu allows route/unroute any synth engine to MOD-UI (using mod-monitor or system output).
* '''MOD-UI audio routing''': Route audio from standalone engines to MOD-UI, allowing to use MOD-UI as a Real-Time Audio Proccesssor for the standalone engines. Zynthian UI's layer options menu allows route/unroute any synth engine to MOD-UI (using mod-monitor or system output).
** MIDI configuration & profiles
** MIDI configuration & profiles
** etc.
** etc.
* New '''Pianoteq Engine''', including the Pianoteq 6.0.3 Demo version, upgradable to 6.1 or licensed version from the webconf tool.
* '''Global MIDI-learning'''. See the wiki documentation: http://wiki.zynthian.org/index.php/Zynthian_UI_Users_Guide 20
* '''Improved Security'''. SSH keys and webconf cookie secret will be generated on first boot, avoiding that anybody accessing your local network can hijack your Zynthian box.
* '''PANIC functions''': All notes/sounds Off
* '''Supports the new RBPi 3 B+''': It includes a recent version of firmware (rpi-update), as required by the new RBPi3 B+.
* '''MIDI over network''': It can be enabled from the Webconf or the UI’s Admin menu. It uses QmidiNet, that implements UDP/IP multicast and it’s fully compatible with IP-Midi 2 for Windows & Mac.
* '''Improved controller scheme for setBfree''', integrating latest changes from @x42
* '''Channel Clone''': it’s the new method for “layering” sounds while allowing to change volume and other controllers independently. Any MIDI channel can be bond to other channels, what it means that all the note on/off + pitch bending + channel presure (aftertouch) messages received by the source channel will be cloned to the bond channels.
* '''Multi-port Architecture''': the new MIDI router allows having several input and output ports, that can be configured and routed easily (by code). This will allow to adapt the Zynthian MIDI Router to the new features as we develop it.
* '''Active Channel''': this feature, that can be enabled/disabled from the webconf tool, allows to forward all MIDI input to the active layer’s channel. This is very useful when your master keyboard can’t change its MIDI channel easily. You can rotate the active layer by clicking the “layer” knob, or selecting from the layer list.
* '''Improve Filter Rule System''':
** Fix IGNORE rules. Now it should work as expected!
** Add new events types: NOTE_ON, NOTE_OFF
** Program Change event name has changed from PG to PC!!!
** Allow specifying PC number in rules, so you can set rules for specific Prog.Nums.