I was able to get the “Onset Trigger - Bassdrum Detection Mono” working well (triggering a kick sample from an audio input), but I could only configure the routing via VNC-Engines and the routing doesn’t get saved in a snapshot.
This setup uses two chains. The first is a MIDI+Audio chain that has a gain plugin after input 1 (Wazinator) that feeds the Onset Trigger. The second is an instrument chain with a drum kit. In order to connect the Onset Trigger audio input to the gain and its MIDI output to the instrument chain, I had to use the VNC-Engines Patchage UI. When I save as a snapshot and then reload, however, these two connections are gone.
Is this a bug or should I be doing something differently?
Hi @jofemodo , thanks for your response! In the Zynthian UI I can select sending MIDI to chain 2, but I can see in patchage that while it connects ZynMidiRouter ch0_out to chain 2, the MidiOut of Onset Trigger is not connected to anything.
Fixed! Oram & vangelis branches. Please, update and test!
Note that you should place post-fader the Onset Trigger processor. It’s recommended in Oram and mandatory in Zynbleton.
BTW, i’ve been testing with the Onset Trigger + Fabla and i must say it works quite nicely! Latency is not so bad! And it’s super fun!
I think i will build a KickPad with a simple piece of wood and a piezo.
Indeed, we could conceive a kind of poor-man electronic drumset using just zynthian, piezos and some imagination.
A quick demo recorded with Onset Trigger + Fabla + SooperLooper. As input i used a SM58 connected to the zynthian audio input and my fingers tapping on it
It’s not perfect, but it was a first try, just to test latency is not a big issue.
Haha amazing and totally agree, it is super fun! Used subtly for “4 on the floor” it can fill out a performance nicely. It’s good to focus on the musical benefits of all this tinkering Many thanks!
