Input for visible parameter
There might be good technical reasons for not doing this, but..: Would it be possible for all interface modules with a "Visible" parameter to have an input for that?
With that parameter open for manipulation on more modules, especially the interface builder could be more flexible, with only the relevant faders etc showing at any given time, much like the sequencer live mode. One could even create some karaoke-like text output - handy if you keep forgetting the lyrics or chords...
With that parameter open for manipulation on more modules, especially the interface builder could be more flexible, with only the relevant faders etc showing at any given time, much like the sequencer live mode. One could even create some karaoke-like text output - handy if you keep forgetting the lyrics or chords...
Bjørn S
Hello
I can add an inlet, no problem.
But don't forget, setting visible on/off for a control can cost a lot in term of CPU. Because Usine has to redraw the control panel, and move remaining controls...
I can add an inlet, no problem.
But don't forget, setting visible on/off for a control can cost a lot in term of CPU. Because Usine has to redraw the control panel, and move remaining controls...
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Brrr, I think it's a bad idea.
An alternative : add an inlet on sub-patches to show patches controls.
An alternative : add an inlet on sub-patches to show patches controls.
Well, well, an alternative to have an inlet would be have the parameter stored by the preset manager just like those with a parameter. What do you think?
Bjørn S
I've tried to add the visible inlet but it makes patches very heavy (the faders and other controls have a double size).
I'm not sure it's a good solution.
For your last (good) suggestion I need to test it before the definitive implementation. I have noticed that preset recall is actually very slow and I'm not sure of the consequences of such implementation.
I'm not sure it's a good solution.
For your last (good) suggestion I need to test it before the definitive implementation. I have noticed that preset recall is actually very slow and I'm not sure of the consequences of such implementation.
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Please keep Usine stable and quick... there must be a lightest solution.
You know my name (look up the number)
It's not a big deal for me, but I thought it was a good idea, expanding the possibilities for the interface builder.
I can't really say I've noticed that recalling presets is slow, and I've been testing with the modules that have the inlet - like the array, step etc. All of them I assume more complex to create/destroy than a simple fader or button.
I can't really say I've noticed that recalling presets is slow, and I've been testing with the modules that have the inlet - like the array, step etc. All of them I assume more complex to create/destroy than a simple fader or button.
Bjørn S
I second that.stanlea wrote:Please keep Usine stable and quick... there must be a lightest solution.
Who is online
Users browsing this forum: No registered users and 75 guests
