@Taylor

I was speculating on the possibility of being able to compile external code modules into code that can be run as "Audulus code" on iOS. Or ran as if it belonged to a patch.

It's the same idea as in compiling code in any source to binary and then "it's compatible with everything".

And then the iOS version could be reduced "embedded" Audulus that disables the modification of such external modules.

See this from the libpd site, which is doing similar things as Audulus:
https://github.com/libpd/pd-for-ios/wiki/ios#using-compiled-c-language-externals-on-ios

Buchla-style modules!

( but I'll absolutely +1 for this; "folders in the patch browser -- @thinds, @Elektroshnik" )


Cheers!

@biminiroad - my bad, that was mighty vague! Don Buchla was not a fan of playing traditional music on synths and his instruments were not created toward that end - more about "events" than "notes" so most of his modules supported complexities that could be downright non-musical. As I get more into Audulus I think I'll be able to cobble some stuff together to float my boat in this style, if I find some really legible graphics I'll send them by way of example, also (if you never have) check out Morton Subotnick, "Sidewinder" or "Touch" being good examples of Buchla-based output. and hey thanks for all you do in this community - cheers!

A way to pan midi based on note just like a piano. That would be amazing

Just wanted to drop a +1 in for Midi IO. I see this is currently in the works - awesome.

Not sure if this is possible at the moment or a feature request.. I was considering tanh distortion/wave-shaping and how 'expr' could be a great sandpit for DSP and building custom sub-patches. But I assume aliasing is currently an issue as there is no up/down-sampling. Would you consider adding that to the backlog?

granular, wavetable synthesis

@Scoridd upsampling is a great idea. I've been wanting to add that for a while :)

I know I won't be able to add much to the debate but +1 for midi out (clock, CC and PC) :) Well a least Clock and CCs
Then Ableton link
Then Audio Units as it is a (great) thing on iOS now

Any news from any of these things ?
I hope everything is going well, good luck !!

A save/load preset utility for patches.
For example, the possibility to save and load different values on each parameter in "Phat Pad Thai" patch (a biminiroad's patch, one of my favourites). Is it possible? would be great!
Many thanks!

@diego898 there is a text via available in the modules that you can use to add text to a wire.

After a good session on my iPad mini2, I determined at this time, with this build, it would help to have...
-the ability to multitouch the keyboard and knob/s of modules at the same time(not sure if full multitouch is a problem to add, but at least keyboard and one other control?)
-the lock icon displayed on the main canvas (as opposed to in the hideaway menu. Maybe where the cup reading is now. Idea to move cpu reading follows;)
-the hide/show menu double arrow icon remain in same spot(corner) when menu is both opened and closed
-the cpu display somewhere that it is not hidden by the opened menu(perhaps next to the double arrow icon)
-a second lock function that allows panning, zooming, knob and other module controls manipulation and nothing else(no pop menu when touching module either)
-and perhaps some time in the future a hold function for the keyboard.

These represent the frustrations I continue to have when using on the iPad, sans midi keyboard at least. Sorry if I've mentioned some before. Just wanted to get a fresh complete list here.

Like uv777bk I would like to see a slider control, some persistant read/write storage (perhaps an array that could be indexed). Also a lock for the Mac and iPad that allows you to manipulate the user controls and pan/zoom but freezes the rest of the layout.

@ohmslice - you can do this with a slew limiter after the envelope node! Also, it can probably be built with a z-1 configuration, but @macromachines would know more about that since he made an envelope follower for his Omnimod Eurorack module

Surprise no one has said OSC (open sound control). Having OSC capabilities would be pretty rad imo.

comprehensive midi I/O (multiple ports/channels are a must here) both between programs and with external devices +42

would also love to see some OSC and Link happening, but please let us route the midi first

I can`t wait, midi out finally! I`m going to continue with my patches. I wish a multitouch audulus for ipad/iphone and i`ll jerk off in the screen, This are the only things that i need for my ideas... Do you know if it is coming soon?
Oh, I forgot it, but a way for saving values in sample and hold nodes could break my balls in happyness (i dont know english so i invent my own exptessions)

Simple request, may have been asked before - I haven't read whole thread.

How about being able to set a 'background colour' for patches - perhaps even just from a selection of preset colours that don't interfere too much with the reset of the UI. I think this would really help with being able to visually group sections of the patch together, so that when zoomed out you can instantly see an overview of all the patches that are closely related.

Don't get me wrong - I like the way Audulus looks (it's definitely a step up from max/PD!) - but it does all have the tendency to get lost in a sea of blue and yellow. An option to add colours to patches/modules would make our designs more memorable and visually appealing.

Of course, we'd need to be able to do this also by selecting a number of patches and setting the bg colour for them all at once.

@SteveX - I'd love it if we could have access to all sorts of data-as-nodes, like even GPS coordinates and the 3d touch and whatnot :) It's all a matter of time and implementation

Here's an Idea I had regarding one of the pile of inputs and outputs and knobs and whatever that is created when you create a sub-patch. When exposing elements of a sub-patch, rather than stack them on top of each other they are encased in a little bubble that pops when you drag it around. I am envisioning something like an item drop in a video game. A bubble popping up automatically unlocks the the UI for editing and (like bubbles do) bubbles would be spaced around the spawn point based on the perimeter of their size.

@diego898 - you can use the vias to make patches have right angles in them - check out the inside of the analog delay!

@RobertSyrett - look inside the patch I just posted - the vias are the little tab things that allow me to route the signal backwards at right angles - the > > things

@RobertSyrett - yup! It comes from vias in electronics, where a trace will plunge through a board to another layer through a hole. I didn't come up with them, I think @jdraoul did?

I would like to be able to ping midi triggers with other midi triggers the way you can modulate knobs with other knobs. Currently when I have an input more than one subpatch deep that is tuned to trigger gate input it is least complicated to make that input a knob and then attach a trigger to that and expose it, which is just kind of clumsy to me. I understand that it's kind of nice to be able to attach an LFO to the knob and have the LFO send trigger data and that wouldn't go away. But stringing together triggers makes the most sense to me and has the added advantage that triggers could also be flipflops (toggle mode) if this change were made.

@biminiroad Happy Thanksgiving! Thank you for that bit of Auduknoledge and the Thru Trigger template. What I am describing is a little different, the Thru Trigger sums the trigger object's state with the one in the subpatch above it so if both were in toggle mode, you would get 0, 1, or 2 depending on their configuration. I was thinking of a way to cascade triggers AND build chains of flipflops, but until then the Thru Trigger and the flipflop module will do nicely. Hope you have a great holiday.

Ok, reverse comicbook time. If I want to chain knobs together through levels of subpatches or assign a midi cc to a knob on a module it is (k)no problem. But the midi trigger right next to it is basically just a clickable object only. If I want to assign a midi trigger I have to use another trigger, which is kind of the opposite of a clean interface. If I want to automate toggling, I either have to use a knob and imagine it's a button or I embed a flip flop, which works alright, except it doesn't toggle the trigger on the display. I just think it would be better if the midi trigger were more like the knob.