midi-cc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
midi-cc [2024/01/17 00:19] steve.wangmidi-cc [2024/03/18 19:55] (current) steve.wang
Line 1: Line 1:
 ====== Create CC Changes For A Player to Follow ====== ====== Create CC Changes For A Player to Follow ======
 **Overview: ** This tutorial will teach you how to use Konduktiva to send MIDI Control Change(CC) messages. **Overview: ** This tutorial will teach you how to use Konduktiva to send MIDI Control Change(CC) messages.
 +**Things To Note:** This tutorial assumes you have already installed Konduktiva successfully using the [[https://github.com/renickbell/konduktiva|Konduktiva installation]] instructions and have read through and understood the [[:first_steps|first steps tutorial]]. The tutorial also assumes 2 things. One, Konduktiva has been assigned to the //K// variable. Two, user created a Musical Environment using the //setUpMusicalEnvironment// function using //K.defaultConfigurationObject// as the first argument and //'exampleMidiPlayer'// as the third argument then, assigned the output to the //e// variable.
 +<code javascript>
 +const K = require('konduktiva')
 +let e = K.setUpMusicalEnvironment(K.defaultConfigurationObject,4,'exampleMidiPlayer')
 +</code>
  
-Ensure you have 4 sessions of a music synthesizer that supports MIDI control change messages. Yoshimi recommend for Linux and Surge is recommended for MacOS.+The example below is based on YoshimiClick [[https://yoshimi.github.io/docs/user-guide/mlearn/mlearn.html|here]] to read more about MIDI CC in Yoshimi.
  
-**Things To Note:** This tutorial assumes you have already installed Konduktiva successfully using the [[https://github.com/renickbell/konduktiva|Konduktiva installation]] instructions and have read through and understood the [[:first_steps|first steps tutorial]]. The tutorial also assumes that you have imported Konduktiva to the //K// variable and assigned any of the example MusicalEnvironments to the //e// variable. 
  
-The example below is based on YoshimiClick [[https://yoshimi.github.io/docs/user-guide/mlearn/mlearn.html|here]] to read more about MIDI CC in Yoshimi.+A player that sends controlChange messages will not send other MIDI messages anymoreAfter configured, it will only send MIDI control change messages and nothing more. 
 +To configure a player to ONLY send MIDI CC messages change the action function and define the controlChangeMap variable in the player. 
 +<code javascript> 
 +//Changing action function: 
 +e.players.exampleMidiPlayer1.action = 'sendMidiCCMessages' 
 +</code>
  
 The key to making Konduktiva send control change messages is the //controlChangeMap// variable in the //MusicalEnvironment//. //QuantizedMaps// stored in //controlChangeMap// variable.  The key to making Konduktiva send control change messages is the //controlChangeMap// variable in the //MusicalEnvironment//. //QuantizedMaps// stored in //controlChangeMap// variable. 
  
-First create a controlChange map and add it to //e.controlChangeMaps//. I will call this one //p1//+Create a controlChange map and add it to //e.controlChangeMaps//. I will call this one //p1//
 <code javascript> <code javascript>
 e.controlChangeMaps.p1 = new K.QuantizedMap(10, e.controlChangeMaps.p1 = new K.QuantizedMap(10,
Line 23: Line 32:
 In Yoshimi, this will change whatever you assign 37 to. In Yoshimi, this will change whatever you assign 37 to.
  
 + 
 Next I will ensure the exampleMidiPlayer1 uses it: Next I will ensure the exampleMidiPlayer1 uses it:
 <code javascript> <code javascript>
  • midi-cc.1705479553.txt.gz
  • Last modified: 2024/01/17 00:19
  • by steve.wang