![]() ![]() Its close to the granularity and operation of classic analog modular synthesizers. For example, the “Generator” module is roughly the equivalent of a couple Audulus nodes wired together.Īudulus gives you smaller, simpler modules that offer fine-grained control of your sound. I think SunVox and Audulus are fairly different beasts actually, with different use cases. I’m actually a big fan of SunVox - really dig its UI aesthetic and the way its timeline works. Geo would have shipped 9 months earlier (as “Pythagoras”) if I could have just said “Audulus is your sound engine”. A lot of great ideas get sunk while half-built on iOS due to the current monolithic model of including an obscene amount of similar stuff in each app, and users don’t help this situation at all with the insistence that infinite sales volume be used to make up for infinitesimal prices. It’s kind of inescapable that things have to be organized this way. But even if I did that, I would still need a way to build patches and effects units on the iPad (with a Pd / Max type of interface). But that would have you *inject* the synth patch into the controller rather than have the controller talk to the synth. I tried to use libpd at one point, but performance wasn’t quite there at the time on iPad1. It will take almost no memory at all, and I just name the synths that it can control really well in my description. If Audulus’s MIDI support is sufficient to handle fretless polyphony cases (like the synths I mentioned above), then I could go back to what I really wanted to do all along… just strip out the sound engine entirely and be 100% controller. This is what I mean when I say “Controllers should not (ever) generate audio”, beyond the reasons of keeping things simple. Then I am back to latency so high that I can barely play the instrument. And even with AudioBus… if Geo is generating a 256 buffer of audio, passing through an effects chain (also 256 samples), and into a DAW…then you have to add the latency up. ![]() i will surely try to add audiobus support when the API is public because it really does solve this problem, apparently without creating headaches to go with it. most people will try to record 5 minute noodles with Geo and we would get reports about stability issues, etc. iOS simply crashes an app when you don’t have enough memory, multi-tasking makes it hard to know when you might go over the limit, and we use a lot of memory for echo buffers, etc. I have a way of doing it that works with ThumbJam, Arctic, and SampleWiz (because these guys put in special message support), but can make it mostly work for multi-timbral synths (Korg Karma, Nord, etc), especially if they can change bend width.Īs for never adding basic ACP support into either Mugician or Geo (it is in Cantor btw, and it doesn’t get used) had a lot to do with reliability and memory constraints. (Controllers should not be generating audio.)ītw Kenny, I’m not saying that there isn’t a way to implement MIDI such that it solves almost all of the problem (95%) of MIDI. AudioBus can be used to let devs focus on effects units and mixers, and something like Audulus can let controllers focus on being controllers. If that’s the way it is, then apps need to be more modular and focused. People want all apps to be in the $5 range and support a huge number of scenarios. OSC trivially fixes this problem in theory, but almost nothing implements it, and the things that do are so generic that there aren’t enough out-of-the-box semantics that you can just plug a controller into a synth and know that pitches come out. But MIDI can’t represent the most trivial pitch handling first-day situations that come up on a touch screen, because it assumes that notes are keys that go up and down and there is 1 pitch wheel for bending on the whole instrument, that bend widths are limited to some number of semitones known in advanced, etc. In theory, MIDI is exactly what is required. the problem that MIDI was supposed to let you focus on writing a controller and get out of the business of writing synths and effects units. ![]() audiobus solves a lot of problems (ie: long jams), but audiobus doesn’t solve the controller problem. □ actually, acp doesn’t solve this problem in the slightest.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |