Make Panels act as containers

+4 votes
asked Jan 7, 2014 in Suggestions by cnurse (580 points)
recategorized Jan 8, 2014 by MIDI Designer Team (Dan)
Yeap I am wishing so much for this too. would be a big time saver.
Thanks guys... we actually had this feature but nixed it before the 1.0 release, because it got a bit too complicated.

While we're here: why do you say, "make similar" instead of "copy?" We've always wanted panels to act as copies (exact same control in a different place, so another instance of the same) rather than clones (similar, but independent)... oh, I see, "tweak the MIDI values"... but then... what if the original changes in size? Placement?

Do you just want a "make similar" for panels that makes similar all the stuff that is fully "on" the panel? That wouldn't be so hard, but kind of misses the point...

Glad for the dialog.

Thanks!
Dan
I "Make Simlar" because I need a distinct new set of controls. I'm copying VG99 Channel A controls to paste them as Channel B controls, same function, but different signal path in the VG99.

So...to exapand a little....

If a Panel was a container and a panel could be visible / invisible according to the value of a super control, we could create some really dynamic templates. Of course, hiding a panel would hide the controls which it contains.

With this feature we could have a pick list which provides a selection of modulation effects. Depending on which modulation effect was selected, we would display a panel with an appropriate set of controls for that effect, and hide other panels.

The VG99 has a MODULATION 1 and MODULATION 2 and you get to pick they are a Chorus, Flanger, etc. So if you pick Chorus for Modulation 1, you need a set of controls to show that are appropriate for Chorus. Same applies if it was a Pitch Shifter, which would need completely different set of controls. This is why panels as containers, and having them go visible and invisible would be a massive benefit and enable very dynamic layouts to exist.
I was kind of hoping your suggestion would be a bit less persuasive ;)

So the panels, once made similar, are completely independent? Because that's simpler, to a certain extent.
My job is all about technology and persuasion haha

Yes totally independent. But the use of a super control means it only takes moments to tweak the midi command on duplicated sub controls to associate them with a different signal path. Truly this is going to elevate midi designer beyond reach of any other product </persuasion> ;-)
Sorry, can you elaborate on " the use of a super control means it only takes moments to tweak the midi command on duplicated sub controls to associate them with a different signal path. "... we're talking about super-subs as we have now, or hiding as you describe above, or...?
Yep - so page 1 has a set of controls with sysex on them. The L value comes from a super control. All this is inside a frame. The super control means when I copy this frame to page 2 I change the newly pasted super control so all my newly pasted sub controls talk to a second signal path on the target. Identical functions but page 1 talks to amplifier A and page 2 now talks to amplifier B. The super control just helps me quickly tweak all the sub control sysex strings - otherwise I'd have to edit 20+ controls to change one sysex byte in each. This links back to my support of page variables. Rather than use a control I'd like a page config section with variables so I could use them in midi vales and sysex strings.
I just realised - when you paste the copied frame you have to maintain a link between the new super control and sub controls, don't create a relationship between the old super control and all the new sub controls.

I know describing this stuff gets complex so also happy to skype.
What's also very close here is the save page, load page. That has helped me duplicate pages of controls for the VG99 channels.

If you had a save frame / load frame, once frames were containers, I think that would get you really close :)
Just a quick note: in 1.6.2 you'll get to select the OTHER page (on iPad) from a control. This is way less interesting than the feature you're suggesting, of course, but shares some of the advantages and doesn't require much in the way of changes to MD.

At some point, though, selectable panels would be very nice to have.
And I'm reading through this thread again: fascinating!
Just talking about panels with controls, forgetting whether they can be hidden or not:

Initially, panels contained controls in MIDI Designer.... this was amazing because you have COPIES of panels. But I digress.

So if you had save, load, and change channel in design mode for panels you'd be happier?

Then: I have to think of how to deal with panels in MIDI Designer. I might not touch panels at all, but rather add a concept of GROUPS in MIDI Designer (like in design programs). That would be VERY simple. Groups are what you call containers, I think...?
Glad that this would be simple!!!

Containers, groups, macros..........

Call'em whatever you like!!! Would make life easier for a lot of people.

For example i keep using the same of diferent sets of objects that comprise a preset group for other controls(preset knob/slider, store/recall buttons and increment/decrement buttons). It would be so much easier to save these objects as a groups and insert them somewhere in a project.

Important thing is to be able to move them together as a group, because otherwise it would not be soo helpful, since the same result can be accomplished by using saved pages but the hassle is huge when you have to move the objects one by one.
Understood, thanks!
Plus one from me too...the ability to group controls is something I am desperate for! Particularly being able to move things as a group, like you said, just like I can do in my graphic design software. Hope to see it soon.
Working on this right now! Should be out soon... it's part of a larger push, but this is an important piece.
...