I can build midi sequences inside zmors and control my vcos, or I can playback midi sequences Ive written on other software.

I have found pitch scaling is not perfect (maybe its called calibration?), but I can get three octaves more or less in unison if Im sending the same notes to a hardware oscilator or to one inside Zmors. Send one oscilator from Zmors out the Es3 to filter and distort with eurorack, send it back into Zmors and apply a nice reverb or whatever. I tend to mix sound sources from the ipad (be it zmors, model 15 or animoog.) and the modular. I am using Zmors with an Es3/es6 combo through the usbstreamer minidsp. But Ive recently started using my ipad instead of my laptop to augment my eurorack setup. UPDATE: Looks like there's a newest thread on Audulus pitch conversion, which features an updated template with a better implementation of pitch conversion. So bottom line: This is feasible for now, but not in a very practical way. So switching between Audulus and midi sequencing app (StepPolyArp) in my case would often cause Audulus to lose its midi connection from StepPolyArp. Workflow wise this is also imperfect, for the reasons already noted in my earlier posts: for this to work, you have to run Audulus in standalone mode (e.g., it can't be loaded in AUM or another AUv3 / IAP / Audiobus host). But it didn't really have any impact on fixing the pitch tracking. In the above link, there's also an ES-8 calibration template, which I used and found simple enough. The pitch cv coming out doesn't track all that well, even within just one octave. You can then open up whatever midi sequencing app you'd like and have it output its midi to Audulus. It was simple enough to just disconnect the turing machine parts and replace it with the basic midi node. The VPO conversion template is pretty much ready to go, and as-is, uses an audulus version of turing machine (sent to a quantizer, of course).

Work has been a bit light lately so I've had a bit more time to dig into this.įollow the link below to go to a post on the audulus forum where a user compiled a number of basic ES-8 templates. Still don't feel like I have a great handle on this issue, but it seems apparent that Audulus isn't quite there yet for accomplishing what we're hoping to. That comment implies to me that they know true support for modular control doesn't really exist at this time in Audulus 3. Here's another comment from biminiroad about support for calibrating VCO pitch in Audulus 4. I'll have to see if I can even get two channels going. So I *think* that means that you could only use two channels of Audulus to convert midi to cv. Both cannot be directly connected to ES-8 at the same time, and when an IAA/AUv3/Audiobus host is running, you're apparently limited to just two inputs and two outputs of audio. If I'm understanding that comment correctly the issue is this: Either Audulus is connected directly to ES-8 (Standalone Mode) or your whatever app you're using to host apps as IAA/AUv3/Audiobus is connected directly to ES-8. This comment explains the problem very thoroughly. The problem is that Audulus acts a certain way when running in standalone mode vs interfacing Audulus with other apps, which require having Audulus be loaded as Inter App Audio / AUv3 / Audiobus. And if it is possible, the functionality is very limited. Upon further reading on the Audulus forum, I don't think this will be possible until Audulus 4 is out, which will allow Audulus to support AUv3 ios apps - meaning, so that it can host AUv3 apps inside Audulus (in the manner that, say, AUM or Beatmaker does currently).

Zmors vs audulus