Looking through the Module Reference Guide. Lots of cool stuff here.
Some random stuff:
You can play the grid buttons like a keyboard.
There is a CV out you can configure.
There is a diffuser audio module
It’s got a ton of CV functions – as for instance a quantizer.
There is an envelope follower.
References:
From the Zoia Module Reference Guide:
Keyboard – Turns grid buttons into a keyboard you can connect to an oscillator and play. No external MIDI controller necessary! Tune each keyboard button using the knob to have it play your desired note.
CV Port Out – This module interprets internal CV and sends it down the ring of a 1/4" TRS connector in the control port as a standard CV signal of 0-5 volts. Remember to set CPort to cv in the Config Menu.
Diffuser – Diffuser spreads your signal across the galaxy like so many shimmering little stars. On it’s own it sounds like a modulated slapback delay with no dry signal, but it can be used to construct many a tonal/atonal masterpiece.
Quantizer – Quantizer will interpret incoming CV and send its nearest equivalent note as a CV output.
Envelope Follower – Envelope Follower will interpret an incoming audio signal as a CV signal based on its signal strength. Use this to trigger filter sweeps, audio effects parameters, LFO rates, etc. The connection strength can act as a sensitivity control.
I’m looking in the RG to see if there might be a way to use the Zoia as a midi event processor – i’m thinking of ways to do it through the CV processor modules. Also thinking about refining the quantizer to select chordal notes only and making an arpeggiator. (You can also set the grid up as a keyboard to only play chordal or scale notes only if you want.)
I also have been thinking of all my various midi controllers as now integral part of some sort of musical patch with something cooked up in the Zoia.
Like some of you, after watching the Cuckoo video, I was surprised to see the CPU usage so high.
I remember way back someone asking Steve about this issue and he stated that RAM would be enough for whatever. Coupling that with then over 6 available pages of modules, I had anticipated that one could do a whole lot with this thing.
But as someone has said, I was not blown away by the complexity of Cuckoos patch and it being at 70something%. This gives me pause. I am definitely going to have to give it a go now , as opposed to ordering immediately, to see at which point I can break it.
I keep having to remind myself: this is a guitar pedal made for guitarists by a prestigious guitar pedal manufacturer.
I do admit that if you just need to “set and forget” your fx, and doubly so if you’ve already tweaked your patches to perfection for a specific use, UI-less approach is completely valid. But for me, I sold my H9 as soon as I found out just how much more fitting to me even a lowly TC electronic Alter Ego pedal was… no menu diving, knob per function, I just love that when it comes to fx I guess.
I’m constantly hitting the CPU limit when going particularly elaborate. However depending on what modules you’re using, the CPU load will be different. Basically, ready made Effects take a lot of CPU. Reverb take the most. The heaviest of all modules is called Ghost reverb and is an eerie and lovely smooth long reverb.
Last time I checked, a few firmwares ago (I think it has actually been optimised slightly since):
Most I/O modules take roughly 0.1-0.4% per module.
Stereo output module with gain takes 2.7%
OSC w FM input takes 3.4%
Most Audio Out modules take between 1-3%, some a little more
Most CV modules take 0.1-0.3%, some a little more.
One stereo reverb takes 23%
The mighty Ghostverb takes 40%
Cabinet simulator 7.9%
Vibrato stereo in out 4.9
Chorus stereo in out 19.8%
… so it’s not as powerful as say the Nord Modular G2 in terms of CPU power. I wouldn’t use it to replace a Eurorack, but rather as specifically crafting something unique.
In my tutorial I didn’t do anything musically wonderful. But the other guys’ videos all sound magical, because they made art with it. It’s a great open tool.
Great info, @cuckoomusic! thank you! Like any tool, it’s going to take some planning and experimentation to work within the limitations. Personally, limitations force certain approaches. I think it speaks to this forum’s love of hardware: yeah, most of us use a DAW, but constraints and character lead to inspiration when you can feel like option overload in a modern DAW.
It’ll go glitchy over 100%, but not the cool bzzpttp glitch, more like a nasty aliasing.
Edit. One way of saving CPU on reverb could be to run a mono reverb, and use a stereo spread, if you still want a stereo image. Perhaps that’d be enough stereo for most cases.
Finding ways to do the same sort of thing with less CPU usage will be part of the trick then.
Like i suggested earlier perhaps since the program change/patch change is relatively quick, you can break stuff up into smaller patches and switch between them for different effects, rather than trying to build that all into one Mega Patch.
Perhaps one day a Mega Zoia with a faster processor. This is not a question, in that i doubt there is an answer.
I’m really thinking about using an expression pedal with this too. (Particular with a sax, but in general too.) Either one pedal plugged in directly through the Control Port, or more likely using the Audiofront Expression IO expresssion pedal to midi interface (added: which i already have) with multiple expression pedals.
That’s on my “experiment list” for this thing. I also have a Morningstar MC6 that allows for two EXPs that can be configured per bank. Since I got the MC6, I rarely use exp pedals, depending on the band I’m playing with. That midi IO looks very cool! Thanks for sharing!
You’ve got at least two sax players on this thread. Cuckoo’s video is made with a drum machine running through it… I’m pretty sure it’s for anyone who’s ever purchased more than one patch cable for any reason.
Well concerning CPU usage i guess the same kind of patch would have maxed my Nord Modular G2 CPU if i was using a custom quality reverb (not the included one ).
If the Ghost Reverb is the same algo as their reverb pedal 40 % cpu usage is ok for me. It really depend of the quality of the included FX.
I guess many of their reverbs from their reverb pedal can be recreated to some degree with clever use of the modules. But they are pretty funny though, so some might require specific algorithms. The different ZOIA reverbs are very nice starting points. The Ghost Reverb is super nice, but sometimes the Room works better, or the Plate in other cases. There’s also a low cpu Reverb that is a bit dithered, but will work nice for some type of sounds (perhaps not percussive sounds).
Lots of useful information to mull over today, with especial thanks to @cuckoomusic for the cpu usage insight. I can definitely see ways that this could be super-useful and awesome for me but not one for the immediate future as I’ve other musical fish to aurally fry if you’ll forgive the torturing of that particular metaphor.
That’s how i’ve used my H9 too - try to get the patches gig-ready, then just load and play my instruments with as little param tweaking as possible. I paired it with an EHX Deluxe Memory Man as my live-tweakable friendly delay pedal. I did however learn and practice using the H9 in Expert Mode for emergency tweaks as part of my gig prep.
Lately however, I’ve gotten into trying freeze-inspired patching with an expression pedal for dynamic control. After I feel like I’ve explored what I could of this stuff, I might look more seriously into the Zoia.