Macros / Grouped Contraptions / Abstractions

4 posts / 0 new
Last post
Curvespace
Curvespace's picture
Joined: March 12, 2012

As discussed elsewhere in the forums, some more ideas pertaining to macros:

1) The ability to save groups of contraptions as an abstraction with inputs/outputs (as per Max/Reaktor etc.). This would allow people to create their own custom FX chains/systems, bundle them up and drop them into future projects.

2) The ability for these chains to then store preset files within them. This would allow users to dial-up previously stored settings for their own macros.

3) Multiple metasurface instances. This would require some serious UI and event handling cleverness I imagine, but is potentially very powerful (I'm thinking two x/y joystick controllers routed to ...).

I realise that moving over to a heavily modular system like this might be a logistical nightmare from an IA point-of-view... sorry about that ;)

Cheers,

Ross B.
Ross B.'s picture
Joined: April 11, 2009

> logistical nightmare from an IA point-of-view

Indeed. This is the main reason why it hasn't happened. Although there are a number of interesting ideas that have accumulated over the course of discussing the issues.

Item (1) on your list is most likely to get addressed first. The others are very much unformed ideas at this stage.

Curvespace
Curvespace's picture
Joined: March 12, 2012

Yeah, for a programmer it's pretty boring stuff to work on, but I think it adds a whole lot of power. I remember playing around with Audiomulch a 'long' time ago. At that point the ceiling in terms of ambition was CPU (at least it was on the machine I was using), but now it's probably more UI/organisation.

I think if the macro idea were to happen then it will in turn throw-up the requirement for UI optimisation elsewhere - for instance separate plugin windows for each macro or something similar.

Ross B.
Ross B.'s picture
Joined: April 11, 2009

> Yeah, for a programmer it's pretty boring stuff to work on, but I think it adds a whole lot of power.

I don't think it's boring to program. I do think there are higher priorities right now though -- some of these priorities really are boring, some aren't.

But yes, it's not exactly a "closed" feature with limited scope. The number of things people assume are part of the feature indicates that it's rather open ended.