Slider for showing desired-level Components

stefan · 15 Sept 2005

But some modules I would consider "high level" might have lesser sub-levels than modules I'd consider "low level" 🙂

Tom7777 · 15 Sept 2005

Yes i must agree with Stefan, I have some structures that have much more complex things than some with much lower levels. Maybe have a module that just recognizes how complex the module its added to is in that it would count the connections and modules it has inside reading the lower levels also or something.

oddson · 15 Sept 2005

I like the intent but it's not about the complexity of the module or its depth but the simplicity of it's use that makes it high level.

(EDIT - OK - it's the level in a project that make them high-level not the simplicity)

I could make a 'high level' module 1 level deep with a handful of primitive components that still has a simple interface - a poly-to-mono with some scaling math to prevent clipping for example.

The in is poly the out is mono and the end user can tie together their poly synth components and then use this to connect to connect to the outside.

It's high-level in it's intent so it should show up in musician mode (if that's what it ends up being called) but it's only one level deep and it's not very complex so neither proposed scheme is going to classify it correctly.

I think component authors would have to decide what the intended use level is. So you'd need a scheme to rank them on that basis.

I hope I haven't misread what everyone is saying too badly

(EDIT - when I wrote this I didn't yet understand the developer object. Seems to me if there were to be multiple levels for users to work at each would need its own similar object to mark it as being at that level.)