MIDI Kinetics Forum

Hey,

I use Mainstage for my live performance. I want to control the volumes of the different plugins by using lemur. Setting up the faders is pretty easy and not a problem. But I have a lot of different patches with a lot of different sounds. I want to add a SurfaceLCD, which shows me the the tracknames. Mainstage does not support sysex and / or mackie protocol so I need to use a third party plugin called plogue bidule, which is able to do so. I just need to know, how the sysex or text has to be formatted to appear on my SurfaceLCD on my iPad. I would then create a midi file which contains the sysex information and playback on patch change. If you know a solution, that is more simple, I would be happy to hear it. Thanks!

I really appreciate your help.

//edit: It seems, that the surfaceLCD doesn't react on mackie-control-sysex messages. I have a sysexfile, which contains
F0 00 00 66 10 12 00 48 65 6C 6C 6F F7
If I open a mackie-control-app on my iPad, it prints "Hello" into the display, while the surfaceLCD stays dark...

//edit2: Got it: It seems, that the normal network connection, which comes with OSX filters Sysex. I need to use Lemur Daemon, to make it work.

Thanks,
Chris

I'm interested in that feature. I wasn't able to make practical use of SurfaceLCD yet.

I can help you out, but at first I need more informations about the SurfaceLCD. I don't know, how to position the text in the LCD. How many digits does the SurfaceLCD support? It seems, that it's different from the mackie-display. I found an implementation chart, which shows the sysex msg which has to be sent to the display in order to show text. But it's not working correctly.

Its interesting, that there are nearly no informations out there about this object...

//edit: Ok, got it too. I forgott, that a 10 in dez is not a 10 in hex

iPad_User wrote:Its interesting, that there are nearly no informations out there about this object...

yeah, you say it. Feedback to the controller (Lemur) is almost as important than sending values, I think. Sometimes I don't even touch the controller, but observe what the software on the computer is currently doing. I see the iPad as an analyser and controller at the same time.

Okay, I don't know if you need this informations, but this is how I use the SurfaceLCD:

As I said, Mainstage is not supporting sysex or mackie protocol. I now use Mainstage in combination with sysex librarian. I create a sysex-file for every patch, that I have in my setlist. This file contains the patch- and channelnames. That means, the content is static (no meters, volume-displays, and so on), but in this case that is enough for me. I create a channelstrip in every patch, which sends a programm change to sysex librarian. Every programm change is linked to a sysex file. So, on patch change, sysex librarian sends a sysex to my iPad.
Yesterday I created a little menu in lemur. Now it goes like this:

- Choose patch from menu in lemur
- Lemur sends programm change to Mainstage
- Mainstage changes patch
- Mainstage sends programm change to Sysex Librarian
- Sysex Librarian sends sysex to Lemur
- Lemur shows patchname and channelstrip

Now, I think I could save one step. I will change sysex librarian to listen to the output of the iPad so I don't need Mainstage to send another programm change to sysex librarian.

By the sounds of it all your info is hard coded in the sysex. Sysex is ideal if you are doing live requests etc
You could probably use text objects and simply store and send what you need within Lemur itself
Just a thought . . .

Macciza wrote:You could probably use text objects and simply store and send what you need within Lemur itself
Just a thought . . .

yes I was thinking the same thing.