Home | News | Products | Support | Download | Sales | library | Guests | Contact | WebCam | Links
CDS Logo LanBox-Talk mail archive
 

By date: Prev | Next | Index By thread: Prev | Next | Index

SubjectRe: [LCtalk] Midi-controller
FromP. Koelman
DateWed, 9 Jan 2008 23:32:52 +0100


Well for MIDI search Google for MIDI notes and controller messages.

I find a lot of information about keyboards, but this is not a keyboard is it...



The midi-part in LCplus reference is to me like reading Norwegian, I can see the logic, but have no idea what they mean.

For setting channels look at page 7 of the LC+ Reference v2.0a1.pdf; you only need to send NoteOns. Keep in mind that MIDI messages are written often as hex values.

Let's be more specific: The reference says:

EngineSetTransparencyDepth
The EngineSetTransparencyDepth command is implemented for MIDI as Controller message number 99. The MIDI channel determines which engine should process the command (depending on the MIDI mapping). The value of the controller should be the transparency depth.


If I want a fader to controll the transparency of layer P, what would that look like?


For all other actions you need to use controller messages. If you have a MAX (http://www.cycling74.com) runtime, you can also have a look at our LC+ MIDI Example.pat

No I do not have MAX, do I need it?


For "Go" ing to cues you can use controller, as well as bank select + program change messages, see page 30 of the LC+ Reference v2.0a1.pdf.

Please don't just throw in words assuming I would understand them... What has bank select got to do with "Go"ing a cue? And what program do I need to change?
Is a program a cuelist? or is bank select a cuelist?


By the way, the O1V has motorised faders, does that automatically mean that the faders will be set to values in the lanbox? (e.g. if I change something in LCedit, will the fader jump to the right spot)


That's it for a start anyway, when I better manage the midi "language" I'm sure that there are more posibilities.

All of above is possible with simple MIDI messages, but you can go wild with MIDI SysEx messages.

I will keep the SysEx for the future, but as with everything on the lanbox, it sounds good!


Sorry for the lack of understanding. If I would just have an exampled start somewhere so I can see how it works that would make understanding a lot easier!

The little video-like tutorials for the Lassie are an example for clear explanations.
I would like to be free to use the full potential of the lanbox and the O1V, so i'd rather program it myself. (heck, the learning-curve for lcedit+ was worth it as wel!)


And for the use of the Wiki, if there is anyone using a midi-mixer (in a more advanced way than just setting channels), can somebody start a topic on midi there? The wiki is a potential great help for all beginners, as long as knowledge is shared.

By date: Prev | Next | Index By thread: Prev | Next | Index