MIDI CC and SysEx "learn"

[Sanderxpander]

Is it possible to have Lemur "learn" the basic SysEx strings or midi CC's from moving a slider or altering a parameter on my synth?
Could someone point me in the right direction for this? Could I do it from the app or would I need the editor?
Failing that, is there a way to have a midi monitor in the app so that I can see the incoming strings? I know this is possible on the PC/Mac but doing it in app would be a lot more useful for me.

[Softcore]

NOT sure and NOT tested, but maybe this can help you!

[Sanderxpander]

Hey cool, thanks! I'll check that out when I have some time later this week, and let you know what I find!

[Sanderxpander]

Ok so this is working great but I ran into the next hurdle.
I'm trying to build a lemur template to edit a synth by monitoring the output of the synth (and/or the pc version of the editor, which sucks). I can see the SysEx string fine, but now I need to have a menu object that sends a sysex string with a variable in it. I tried searching for others with this issue but the solution doesn't seem to apply to my case.

Basically I have a SysEx string like this;
66, 48, 104, 67, 11, 19, 0, 0, 0, 0, 0, MyVariable(0 to 7), 127

I created a menu object with 8 options. It took me a while to figure out I can apparently not assign SysEx as output using the in-app editor. Got past that hurdle. But how do I make it so that each of my options sends out a different sysex string? I thought I would be able to simply create a string for each new option I made, but that doesn't seem to be the case. The other solutions I googled said I could use a fader to set the variable. But I want my menu itself to create the variable.... how would I go about that?

[Softcore]

Try this one....I think it should work!

[Sanderxpander]

I bow to your skillz. That's great, and helps me understand how it works. So it's not actually the Menu sending the thing (in fact, it seems to send a note on currently), it's the script that's reading the menu setting upon change.

I'm having a hard time figuring out the available lemur scripting commands from the manual. Maybe I'm looking in the wrong place. I just googled and found a partial list.
It's been ages since I did any real programming but I'm familiar enough with object oriented language in general. Just can't find the commands I need. So thanks again!

[Softcore]

Exactly that! At first, I tried to enter the "data" in the menu MIDI mapping (when set to send Sysex midi commands) but I realized the "data" field could not be populated with anything other than static numerical values (and not the "selection" expression). I may have forgotten to untick the "selection" expression from the project window in my above example - so yeah, it may also be sending a note-on message - unticking it from the project window OR leaving it without a target setting makes sure you dont have any output as far as the midi-OSC settings go so that you can freely do what you want with scripting alone.

So yeah, the scripts always help in these cases! As far as the available commands and things....I always have two references:

1. the final pages of Lemur manual where all the attributes of the objects are referenced - therefore, you can easily see the commands when you want to script an action that affects another object of Lemur

2. INSIDE the desktop editor, right at the project window, there is a blue folder named "internal". There you will find all the available commands as reference!

note: as good and handy as the in-app editor may be, I think especially when learning Lemur and discovering its capabilities, you MUST use the desktop editor, so keep that in mind!

[Sanderxpander]

I also tried entering the variable straight into the menu's sysex box at first. Then I looked if perhaps each menu item had its own box. Neither worked. To be honest it seems strange to make a menu item and always need a separate script to output what you need - even if it were just a different midi note for each option I see no way of doing it without a script. I wonder if perhaps the menu object could be updated to include a separate send for each item. The multiball has an x, y and z for each ball after all.

I'm also starting to see your point about the desktop editor vs the in app editor. To be honest since I got to the iPad and lemur only recently I didn't realize at first I would even need a desktop editor. I only found out this week that there are substiantial differences between the two, such as no sysex programming from the in-app editor. I thought the differences were just cosmetic and it appeals to me a lot more to sit on the couch or on the bus or wherever with my iPad, programming, rather than hook up my laptop or studio computer. So I hope perhaps the editor will be updated to include full functionality. My friend used the lemur a long time ago and was surprised you could now edit from the app itself - something I took for granted. Well, I'm getting there step by step, with much thanks to you!

[Softcore]

The menu object has "selection" as its "native" expression variable. How it can be used though depends on the selected MIDI mapping....

Try for example note on - "selection" then, becomes the velocity of the note on message, or try Control Change - "selection" becomes the CC value. Indeed, for Sysex the "selection" becomes just a "trigger" so it's not so usable.

As for the in-app editor, besides being a relatively new feature, I took it from the start as a "last change on the fly" solution, on a template which has been already designed in the desktop editor therefore the more complex things have been already sorted-out. Frankly, I dont know if I could ever use it alone even if it did have all the functionality that the desktop editor provides just because I dont feel particularly comfortable or fast when working with the in-app editor.