[mb47]

sounds nice having a toolbar, especially for new users, as was pointed out.
I would anyway try to keep the toolbar as well, as it’s nice to access, for example, the Save button (or other things) with just one click.

[mb47]

I could imagine there MIGHT be issues with having functions that are used to dynamically create modulators when the panel is running.
As an alternative to having a Lua function to create modulators, one way could be to have a GUI function "Create Modulator Array" or "Copy Modulator to Array" (to get not just one copy, but several instances, in one single shot).
Editing the .panel text file is defintely an option, but it would just be great to have GUI functions for simplicity.
Just a thought….

[mb47]

hello,

yes, creating them manually and then setting their position with Lua is what I’ve done so far.
However it can be quite time consuming when you have to create hundreds of modulators by hand.

Here’s an example with a panel for the Kawai -5:
[attachment=0:3i8ruluu]KitScreenshot.png[/attachment:3i8ruluu]
In a "kit" program each key is assigned a "single" sound plus few other settings. In this case there are 528 modulators that need to be manually created.
Being able to programmatically create by copying a modulator from another would also do.

[mb47]

hi,

I don’t know what those settings in the CTRLR preferences are for.
Anyway, for example configured like this works for me (in Live on a Mac)
[attachment=0:2krd68kh]SettingsForShruthi-1.png[/attachment:2krd68kh]
Note that I changed the MIDI input and output device in the Shruthi-1 panel to select my MIDI interface.

It also seems that not all VST parameters can be exported into Ableton (in the attached image I exported the resonance and few others): only those whose VST index (in the panel) is <64 (at least with the CTRLR version I’m using: see post in this forum). However changing the index of the parameters I wanted to export to values <64 works (just make sure those indexes are unique, or CTRLR will change their values next time you load the panel).

Hope this helps.
Best,
Marco

[mb47]

I’m using version 5.0.3, revision 1089.

[mb47]

Hi,

I think I just found out where the problem is.
I just realized that the problem showed when I renamed the tab modulator.

Apparently (?) its children refer to it by its name, so when rename it the children modulators can’t find it and are placed on the top panel, instead of inside the tab.
So I guess I cannot rename the tab anymore. Not too bad, I will stay with it current name, so far.

Same thing was happening with groups, when I rename one, its children loose the link to it.

I can still share the panel if you want to replicate that: in case please just let me know.

Best,
Marco

[mb47]

…so I tried again….

I created the tabs, moved the groups into it and saved the panel.
When I reopened it, all was in place and working fine.
So, I proceeded editing the panel, like changing some colors and adding a function (to change the currently selected tab, upon MIDI message of a certain patch/program received).

However after several editings and savings of the the panel, the problem showed up again, and the panel is messed up again:
[attachment=0:17uqj9r4]BugMovingGroupsIntoTabs2.png[/attachment:17uqj9r4]
The function I use to change the tab is:
[code:17uqj9r4]function selectTab(tabname)
if tabname == "single" then
panel:getModulatorByName("TABS"):getComponent():setPropertyString("uiTabsCurrentTab", "0")
elseif tabname == "kit" then
panel:getModulatorByName("TABS"):getComponent():setPropertyString("uiTabsCurrentTab", "1")
elseif tabname == "kit" then
panel:getModulatorByName("TABS"):getComponent():setPropertyString("uiTabsCurrentTab", "2")
end[/code:17uqj9r4]
I doubt that this is the cause of the problem since this was happening also before creating that function, but who knows?

The -5 has certain patch programs (0 to 63) which are called "single", and others (64-127 IIRC) which are called "kit".
Since "Singles" and "Kits" require different sets of modulators, and they hardly would fit in a panel, being able to use tabs here would really help here.
However i am kind of stuck, because the panel can just get completely messed after some editing/saving.

Helps or hints are appreciated.

Best ,
Marco

[mb47]

Hi all,

I need to send from a modulator SysEx formula like this one:
f0 40 09 10 00 06 15 02|MS LS f7
where with | I mean an OR operation on the bits.

It actually seems to accept it, as well as writing:
f0 40 09 10 00 06 15 02+MS LS f7

but both will only send
f0 40 09 10 00 06 15 02 LS f7
whatever the valus of MS is.

"atom":ud9lamkv wrote:

You can do it 3 ways

1) use a FixedImageSlider and fill the list of values in a way that it will fit your formula perfectly
2) use the expression fields to add/subtract/divide/multiply the modulator value to get the actual value you want
3) use LUA to create/send those messages[/quote:ud9lamkv]

Is method 3) the only possible in this case, or there also other ways?
I am not sure that method 1 could be used here.
Method number 2) sounds like the most straightforward, and wanted to try it out, but could not make it work.

Does anybody know how to do it?

Thanks!
Marco

[Author]

Posts