Novation SL-MK3 Extension

GP Extensions
82

Good evening. Your extension to SLMK3 is a great job. I have to thank you again. At the same time, I want to ask if it would be possible to expand Momentary touch _m to 16 buttons in addition to 16 pads. Simply, when selecting any function, instead of 2x (on off), I have to press 4x. Thank you

83

I think that should not be a problem. Although I’m not following why you have to press 4x to toggle something.

I can’t make any promises about timing. Probably at least a week before I’ll have a chance to look at it.

1 Like
84

Because when I map buttons for different software synths, I have to turn on a function, then it stays on when I press it again and only turns off the function when I press it a third time. It would be great if the buttons could behave like pads in your MK3 extension. Thank you very much.

85

Ok. Just to make sure this is going to do what you want, have you tried assigning the same widgets to pads and seeing how it works?

The point of the momentary function is so that when you are holding a button down the widget will be on, and as soon as you release it the widget will turn off.

From you description it sounds like you are doing two different things with one widget. You’re not talking about using a “learn” kind of thing to map widgets to parameters in a plugin, are you? Because that’s not going to work properly.

86

Yes, I know what I want. exactly how pads should behave buttons. It is possible to do this in the SL MK3 setup application and this feature is quite missing in your extension. Otherwise your extension is brilliant and gives many, many possibilities without limitations. Thank you very much

87

Try downloading a beta version from this link down at the bottom of the page: WidnerM/GP-SL-MK3@81cf644

The buttons should work like the pads now using the “_m” on the parameter widget. I can’t test it myself currently because my SL-MK3 is in storage for a while.

1 Like
89

Yes, I had something like that in mind. However, they can’t change the color yet . I know you’re saying it’s a beta version. But otherwise, great work, and I think I won’t be the only one who appreciates this. Thank you very much

90

And actually all buttons now work like this and it’s impossible to decide which button will do it and which won’t.

92

I’m not sure what you mean by that. The colors should still work same as they did before. Just that the “on” color will only be visible while holding the button/pad down and the “off” color will be visible the rest of the time.

93

Buttons are colored. Only when pressed or held does the color not change. But otherwise everything works perfectly. The color is not important. Thank you very much again

94

After some testing and modifications this is now the updated Current Release on the GP-SL-MK3 Github page.

Colors and behavior should be working properly now using the “_m” momentary flag for both pads and buttons.

3 Likes
95

Thanks again for your work. I’m sure you’ll like this, and not just me. Now all I need is a lot of imagination and time and I can work on it.

96

DobrĂœ deƈ. Je eĆĄte jedna vec, s ktorou potrebujem pomĂŽcĆ„. Chcem poprosiĆ„ o nejakĂœ prĂ­klad v GP, ako viem vyuĆŸiĆ„ prĂĄcu s Bankami. mc_f_mix1_[0..7] mc_k_mix1_[0..7] mc_p_mix1_[0..15] mc_b_mix1_[0..15]. KonkrĂ©tne by som chcel pomocou nejakĂ©ho widgetu prepnĂșĆ„ na konkrĂ©tny panel.. naprĂ­klad pomenovanĂœ sl_f_panel0_i Ďakujem

1 Like
97

Hello. There is one more thing I need help with. I would like to ask for an example in GP, ​​how I can use the work with Banks. mc_f_mix1_[0..7] mc_k_mix1_[0..7] mc_p_mix1_[0..15] mc_b_mix1_[0..15]. Specifically, I would like to use a widget to switch to a specific panel..for example, named sl_f_panel0_i Thank you

98

It looks like a made an error in the documentation (because I copied and pasted that paragraph from a different extension).

Everywhere you see “mc_” in that, change it to “sl_”. I will correct the documentation and re-upload it. I’ll also make a version update to fix a couple of minor unrelated errors.

The “indicator widgets” (the ones ending _i) are for display only. You can’t click on them to change banks. You have to change banks using the assigned bank switching keys. I’ll edit the documentation file to make it more clear which buttons on the SL-MK3 control bank switching and other things.

1 Like
99

805

now it’s clear to me. “mc” confused me and I thought that there was something else that I already know. In any case, it would be great if you could use any widget to jump to a specific Bank and switch the group, for example “sl_k_polysix_i + sl_p_polysix_i + sl_f_polysix_i”. I know that you can step this way using the buttons for the knobs bank, but it would be better to jump to a specific bank, for example, using a widget, to which I would then assign some button on my SL MK3. Then it would look like I would have mapped the controllers to, for example, “korg polysix vst plugin” and by switching any button I would switch to a differently mapped panel, for example, to “roland Jupiter 8 vst plugin”. But that is not a condition at all. Your extension is already perfect and gives a lot of options. Thank you very much

100

That’s an interesting use case I hadn’t considered. I’ll have to think about how to implement that in a way that behaves as expected and doesn’t have potential to cause problems.

When two widgets have the ability to activate each other you can end up with loops that will cause the system to hang. I’ve been down that road and run into scenarios I didn’t think possible.

101

I just updated the Github Release to v1.0.5. This includes some corrections and updates to the documentation, a newer demo Gigfile, and a few small bugfixes.

For anyone using the “momentary” function for buttons or pads, please note that in the prior versions the code was looking for the “_m” in the wrong place. The correct format for the Caption of the parameter widget was always supposed to be “Display name_Off text_On text_m”. Prior versions were looking for it in the “On text” slot. If you were using this function you’ll need to move your _m over one place.

1 Like
102

SLMk would then behave like any hardware synthesizer, for example, where clicking a button opens a menu. Your extension can already do this, but it has to be laboriously stepped through.

103

thank you very much