AUDULUS 3 TUTORIAL IPAD SOFTWARE

I'm just looking at what might be more easily achieved (I suspect) as a 'Minimum Viable Product' UI for exported app developers. I prefer my published ports in one place, but I'm not speaking against any of the ideas to have them in on the editor canvas itself, it could be awesome to have that too. I think as a minimum for UI in Vuo Editor and development process, the same published input port UI window that gets used for the exported app could be present as real time controls for the Editor though? A lot of coding overlap with the exported app. I'm just focusing on exported apps at this point, because some of the good ideas expressed in the last couple of days are for the interface of the Vuo app itself, and there's overlap with exported apps UI and developer space UI but also differences to the Vuo Editor and how it may offer enhanced for UI design which might be unique to the Vuo and not easily translate to the current automatic app build routine of Vuo. enumerated list, not a Vuo type I don't think would need making (think indexed list in QC)Ī user choice of horizontal or vertical arrangement would be the easiest to implement but it's conceivable more advanced arrangements as discussed above would be possible.

is gradient a native type? if not make it a Vuo type.

I'd have a preference that for a subset of published input ports that represent some of the simple native types could be arranged in a window in horizontal or vertical fashion as a kind of minimum feature set for exported apps. I like that the dev for Audulus is committed to strong visuals all for UX - he just introduced a shader node for GLSL, and already has for the current beta other clever ways for supporting custom visuals, SVG and PNG support, using demux to animate PNGs specifically for knob UI's, etc.Īudulus screenshot, users create/customize modules: (Can also cable directly to the knobs to modulate, which makes a lot of sense for modular audio world.) Then in the editor (root view) key command an 'edit UI' mode to drag knobs around. In Audulus users create modules (which would be subcomps in Vuo) for sound stuff then 'expose' knobs and other elements from inside the module.

AUDULUS 3 TUTORIAL IPAD SOFTWARE

Since we're using examples of other software - there is a modular audio app called Audulus (currently in beta for version 4) that uses an effective approach with knobs.Īudulus was originally directed towards iOS for iPad, then to macOS + AU plugin version. Like being able to see (and edit, wow!) an audio waveform on a computer - imagine that before and after! Yeah, George, I agree, I think there is a strong use case for seeing GUI objects. c node opens up in a text editor when I double click on it from inside the Vuo editor (in my case BB Edit). Pretty sure these concepts have been hashed out a kajillion times by now from various directions.

In lieu of this, it would be great to have some solution that considers these basics. Some think all parameters in modular software should be normalized. The knob could be assigned to an external source via either OSC or MIDI.The knob could simultaneously be published (for creating comps to load in other software, VDMX, CoGe, Resolume) and still be used in a running Vuo comp.Don't need to consider event flow because it will just work.The more parameters a module has, the more difficult it is to use as an expressive object. Two things get in the way - event flow and parameter ranges on modules. This idea applies to a majority of Vuo scenarios, here's a simple example: say I want to play with thin line widths on a 3D Object, say a Make Grid Lines Object - I wish I could load a knob and quickly type an expression into Calculate, knob * knob *. Then I could quickly refine it with Calculate to set up an expressive range. To this end I wish I could load a simple 'knob' - a Share Value in the form of a knob UI element, could just be a float value normalized to 0 to 1 range. Like having a sketchbook close by, I want to be able to set up and explore possibilities ASAP. Say I have a creative thread I wish to follow, a sketch, a seed. In one sense this is a UX/UI issue - modular software is particularly difficult when it can cover so many use cases - how do you decide what to highlight? Vuo lacks tools for working quickly - it can be difficult to set something up and see expressive results right now. This is about supporting creativity and expression.

Audulus 3 tutorial ipad