MIDI Kinetics Forum

Dear all,

i am building a Diva Template and want to select a tab from a menu item. Could someone help me here, i'm quite a script noob.

What i'm trying is this action from withing a menu object:

decl ind=(Menu.selection);
selecttab(Container,ind);

It changes the tab to the first one, but cant select any other tab.

thanks!

For anyone interested, here is the file. Very much Work In Progress! If you have any additions please share. It's very much based on Chris Malikoff's voyager controller (thanks Chris).
PS i figured out how to work with the octave and fine tune in Diva. You should map with different settings in diva itself (octave settings and normal settings, or integer and normal, can't remember which). Let me know if you're interested and i will figure it out again and explain in detail.

you probably want to change modules in Diva, isn't it? My approach was to show/hide non-tabbed containers. I started with tabbed containers but found it not suitable. And the tab-bar is taking too much space.

But I think you have the solution already, maybe you didn't use indexes for the menu. I'll have a look at it tonight. Oh and the tune-knobs work alright now in my template. I don't directly control Diva with MIDI-learn, I use a method that gives me parameter feedback. Unfortunately this works only in Cubase. Do you have Cubase?

Hi Phil, thanks for your reply.

yes right, changing modules of course . I found the show hide way (but don't know how it works in detail) but think the tabbed container with hidden tabs (agree the tab bar takes too much space) but controlled from a menu object could be a nice way that resembles how it works in Diva.

No, i used Cubase 1 (yes on the atari) through Cubase 3, but use Ableton Live these days. I read Cubase can do bidirectional with lemur via some Cubase trick. My Live workaround is mapping the parameters in live and then midi map the live parameters with the lemur cc's. That way i can send out paramter changes from the daw. Only concern is there are two streams of information going into the Diva which might cause conflicts. I'll see.

I would really appreciate if you could look into it and point me in the right direction. I tried to address the index numbers in the menu, but get stuck in my limited scripting knowledge. I am also curious about your Diva template, are you willing to share?

I resolved the issue while fiddling around.
The script was correct, but execution was set on "Message sent when value goes from positive to 0" because i copied this trick from working with pad buttons. I set it back to "any" and now it works fine. I put the menu it above the containers so it is always visible.
see new version attached.
Any way any comment or help is welcome and would like to see other user's diva templates.

good work!

Yes the Menu objects must be set quite high. It has already been requested to the developer team that the menu should go up if there's not enough space below, or make this behavior freely customizable. But in the end we can build customized menu-like elements with other objects from the creation palette.

In my template I actually don't know yet what kind of menu I will use to change Diva modules. Now I have simple switches. A menu would reflect the plugin GUI better, but with switches you must tap only once.

In the attachment is the current state of my approach. It is quite empty, but what is there is functional with parameter feedback. When I change presets in Diva, the VCO modules change, also the modulation source "menus", etc. except VCO tune. This is in another test template that is not entirely functional yet. Going to work on it right after this post.

Great, thanks for sharing. I am also one step further in creating the template and will share the new version somehwere next week.

Just had a quick look. Very instructive. Love the values layered over the knob. Nice space saver.