first_steps

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
first_steps [2024/02/15 19:55] – steve.wangfirst_steps [2024/11/03 23:04] (current) – steve.wang
Line 1: Line 1:
-====== First Steps ====== +====== First Steps with Konduktiva====== 
-**Overview: ** This tutorial will act as a guide about how to get started after installating Konduktiva. See how to [[https://github.com/renickbell/konduktiva/blob/main/README.md#installation|install Konduktiva on the Konduktiva Github page]]+**Overview: ** This tutorial will act as a guide about how to get started after installating Konduktiva. See how to [[https://github.com/renickbell/konduktiva/blob/main/README.md|install Konduktiva on the Konduktiva Github page]]
  
 **Things To Note: ** Only follow this tutorial after you have correctly followed the installation instructions.  **Things To Note: ** Only follow this tutorial after you have correctly followed the installation instructions. 
Line 7: Line 7:
 <code bash> node</code> <code bash> node</code>
  
-Run the following line of code in the REPL which will load the Konduktiva library if you have installed it throught npm. For loading using other methods go to [[|https://github.com/renickbell/konduktiva/blob/main/README.md#running-the-code|the Running The Code part of the Konduktiva Github page]]. :+Run the following line of code in the REPL which will load the Konduktiva library if you have installed it throught npm:
 <code javascript> <code javascript>
 const K = require('konduktiva') const K = require('konduktiva')
 </code> </code>
 +
 +NOTE: await import is not supported
  
 After this is loaded, you will need to open one instance of MIDI output. Next, setup a default/example MusicalEnvironment with After this is loaded, you will need to open one instance of MIDI output. Next, setup a default/example MusicalEnvironment with
  
 <code javascript> <code javascript>
-let e = K.setUpMusicalEnvironment(0)+let e = K.setUpMusicalEnvironment(K.defaultConfigurationObject, 1,'exampleMidiPlayer')
 </code> </code>
  
Line 31: Line 33:
 </code> </code>
  
-Before you can start playing music, you have to connect Konduktiva to your music synthesizer of choice. On Linux, I will be using [[https://kx.studio//Applications:Carla|Carla]]. I can use Carla to easily connect midi inputs and outputs. To do this open Carla and click the "Configure Carla" button and ensure it is using the right engine. If configure it to use the right engine: 
-{{ :configure-carla-button-circled.png?400 |}} 
  
 +Before you can start playing music, you have to connect Konduktiva to your music synthesizer of choice. [[connecting-konduktiva-to-music-synthesizer-using-carla|Click here to learn how to do so]] 
  
-If you did change the settings remember to restart the Carla engine. You can restart the Carla engine by clicking "Engine" on the top left and click the "stop" button. Next, click the "Engine" button again and click the "start" button. 
  
-<html> +Now you can start playing some beats. Ensure you music synthesizer is listening to channel 1. Try this command to allow one player to start playing.
-<img src='http://konduktiva.org/lib/exe/fetch.php?media=restarting-carla-engine.gif'></img> +
-</html> +
- +
-Next click the "Patchbay" button. It is located towards the upper left part of your screen. It is on the same line as and between two other buttons, "Rack" and "Logs": +
- +
- +
-IMG +
- +
-Scroll around the Patchbay and look for the midi bridges, the should have red tags in them indicating they are midi. +
- +
-IMG +
- +
-In one of the midi bridges, you should see "Midi Through:(capture_0) Midi Through Port-0". Ensure that it says capture not playback. The pointy part of the red tag should also be facing left: +
- +
-IMG +
- +
-If you use your mouse to hold down in the "Midi Through:(capture_0) Midi Through Port-0" red tag, then move your mouse. You should see a line coming out. Use that line to connect to the input of the your music synthesizer. In this example I am using a music synthesizer called Yoshimi: +
- +
-GIF  +
- +
-Next configure you music synthesizer to listen to the correct channel. These are the correct channels for the these players. exampleMidiPlayer1: 1, exampleMidiPlayer2: 2, exampleMidiPlayer3: 3, exampleMidiPlayer4, 4. If you do not understand what player are don't worry right now. They will be explained in due time and you will also be reminded to change the channel later. For now just know how to do it. This is an example of changing it in Yoshimi: +
- +
-{{ :yoshimi-changing-channels-circled.png?400 |}} +
-Now you can start playing some beats. Try this command to allow one player to start playing.+
  
 <code javascript> <code javascript>
 e.play('exampleMidiPlayer1') e.play('exampleMidiPlayer1')
 </code> </code>
-You should here something like this: 
-{{ :setupverysimplemusicalenvironment-audio.mp3 |}} 
-You can also restart the node session by cressing CTRL + D in the terminal and typing node again. Then you might want to try some of these other functions: 
  
-<code> +Stop it by doing this: 
-let e = K.setUpMusicalEnvironment(0) +<code javascript> 
-e.play('exampleMidiPlayer1') +e.stop('exampleMidiPlayer1')
-//OR +
-let e = K.setUpMusicalEnvironment(1) +
-e.play('exampleMidiPlayer1') +
-//OR +
-let e = K.setUpMusicalEnvironment(3) +
-e.play('exampleMidiPlayer1')+
 </code> </code>
-REMEMBER to restart nodejs everytime you run one of those functions. As you learn more about Konduktiva, you will learn other ways to do this so you do not have to restart node every single time. +You should here something like this:
  
-Konduktiva can send MIDI messages to more than one music synthesizer session. Try opening another session of your music synthesizer then try this function: +{{ :default-config-obj-audio.mp3 |}}
  
-<code> +You can also restart the node session by pressing CTRL + D in the terminal and typing node again. Then you might want to try some of these other functions:
-let e = K.setUpMusicalEnvironment(2) +
-e.play('exampleMidiPlayer1') +
-e.play('exampleMidiPlayer2')+
  
-</code>+The configuration object (first argument controls the type of sound you hear. Try passing in a different configuration object and some extra configurations (last argument).
  
-You should here both your music synthesizer sessions playing different things. It should sound something like this: 
- 
-{{ :setuptwoplayermusicalenvironment-audio.mp3 |}} 
-Next open 2 more music synthesizer session. 4 in total and run the code below: 
-<code> 
-let e = K.setUpMusicalEnvironment(4) 
-e.play('exampleMidiPlayer1') 
-e.play('exampleMidiPlayer2') 
-e.play('exampleMidiPlayer3') 
-e.play('exampleMidiPlayer4') 
-</code> 
- 
- 
-This might sound something like this: 
-{{ :l-system-session-1-player.mp3 |}} 
- 
-You can allow multiple players to play simultaneously: 
 <code javascript> <code javascript>
-e.play('exampleMidiPlayer3') +let e = K.setUpMusicalEnvironment(K.lsystemData,1,'exampleMidiPlayer', K.exampleMusicalEnvironmentsExtraConfig)
-e.play('exampleMidiPlayer4') +
-e.play('exampleMidiPlayer2')+
 </code> </code>
  
-All the exampleMidiPlayers should be playing now.+{{ :yoshimi-10_lsystem_session_2024-03-12.mp3 |}}
  
-After each line you should here an extra layer of sound.+Konduktiva can send MIDI messages to more than one music synthesizer session. Try opening another session of your music synthesizer and configure the new one to listen to channel 2. To hear a more obvious difference configure the second music synthesizer to use a different voice. Then, try this function: 
  
-It might sound something like this:+<code> 
 +let e = K.setUpMusicalEnvironment(K.defaultConfigurationObject,2,'exampleMidiPlayer')
  
-{{ :all-sessions-audio.mp3 |}}+e.play('exampleMidiPlayer1') 
 +e.play('exampleMidiPlayer2')
  
-To stop a specific session. This will stop exampleMidiPlayer3 player: 
-<code javascript> 
-e.stop('exampleMidiPlayer3') 
 </code> </code>
  
Line 132: Line 76:
 </code> </code>
  
-Explanation of K.setUpMusicalEnvironment function:+You should here both your music synthesizer sessions playing the same thing but with different voices. It should sound something like this:
  
-Argument 0 is for the most basic. +ADD AUDIO HERE
-Argument 1 is for slightly more complex than the most basic +
-Argument 2 is for two players. +
-Argument 3 is for more complex and longer single player +
-Argument 4 is for 4 players+
  
- +To here different sounds try these function calls. Remember to restart nodejs and Konduktiva everytime you run one of these funcitons. As you learn more about Konduktiva, you will learn other ways to do this so you do not have to restart node every single time. 
-All the variables that control the music can be set by using the beginner friendly musicalEnvironment configuration objects. Example configuration objects can be found in the file [[https://github.com/renickbell/konduktiva/blob/main/example-melodies-data.js|example-melodies-data.js]] and documentation on the musicalEnvironment configuration objects can be found in the file [[https://github.com/renickbell/konduktiva/blob/main/konduktiva-documentation.md|Konduktiva-documentation.md]]. +
- +
-Recommended reading [[https://github.com/renickbell/konduktiva/blob/main/konduktiva-documentation.md#conceptual-overviewz|Conceptual Overview]] +
- +
-====== Changing Things Played With Existing QuantizedMaps ====== +
-The sound output can be easily changed by simply switching the data the player looks at without creating any new data. +
-====== Changing notes played ===== +
-This will cause the notes to loop between 0 to 3. +
 <code javascript> <code javascript>
-e.players.exampleMidiPlayer1.noteMap = 'default' +let e = K.setUpMusicalEnvironment(K.circleOfFifthChords,1,'exampleMidiPlayer', K.exampleMusicalEnvironmentsExtraConfig)
-//To look at the information being used: +
-console.log(e.noteMaps.default) +
-</code> +
-====== Changing modeMap used ===== +
-This will cause the chord progression form ionian, to phrygian, then to mixolydian. +
-<code javascript> +
-e.players.exampleMidiPlayer1.modeMap = 'default' +
-//To look at the information being used: +
-console.log(e.modeMaps.default) +
-</code> +
-====== Changing melody used ===== +
-This will cause the player to cycle between the notes 0 to 3. +
-<code javascript> +
-e.players.exampleMidiPlayer1.noteMap = 'default' +
-//To look at the information being used: +
-console.log(e.noteMaps.default) +
-</code>+
  
-====== Playing Chords ===== +let e = K.setUpMusicalEnvironment(K.circleOfFifthMelody,1,'exampleMidiPlayer', K.exampleMusicalEnvironmentsExtraConfig)
-To play chords another action function will have to be used. To switch action functions do this: +
-<code javascript> +
-e.players.exampleMidiPlayer1.action = 'sendChordMidiInfo'+
 </code> </code>
-Or click here to learn more about action functions. 
  
-====== Next Steps ====== +circleOfFifthChords: 
-The recommended way to change specific variables in the MusicalEnvironment is to use the addMap method because it checks for many different types of errors and common mistakes when coding quickly. However, if you are confident and need more speed you can choose to directly interact with the MusicalEnvironment object. Here are some examples +{{ :yoshimi-10_circleoffifthchords_session_2024-03-12.mp3 |}}
-===== Changing Octaves =====+
  
-For example, if I wanted to change the octaves of exampleMidiPlayer4 without changing timing I would do this: +circleOfFifthMelody: 
-<code javascript> +{{ :yoshimi-10_circleoffifthmelody_session_2024-03-12.mp3 |}}
-//Identify which octave map exampleMidiPlayer4 is looking at: +
-e.players.exampleMidiPlayer4.octaveMap +
-//Next (the safer way): +
- e.addMap('octaveMaps',  +
-    e.players.exampleMidiPlayer4.octaveMap,  +
-    e.octaveMaps[e.players.exampleMidiPlayer4.octaveMap].keyspan, +
-    e.octaveMaps[e.players.exampleMidiPlayer4.octaveMap].keys,  +
-    [[ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ]] +
-) +
-//to see the changes: +
-console.log(e.octaveMaps[e.players.exampleMidiPlayer4.octaveMap].values)+
  
-//OR do this the less safe way but potentially faster with more control: 
-e.octaveMaps[e.players.exampleMidiPlayer4.octaveMap].values =[[ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ], [ 6 ]] 
  
-//to see the changes: +All the variables that control the music can be set by using the beginner friendly musicalEnvironment configuration objects. Example configuration objects can be found in the file [[https://github.com/renickbell/konduktiva/blob/main/example-melodies-data.js|example-melodies-data.js]] and documentation on the musicalEnvironment configuration objects can be found in the file [[https://github.com/renickbell/konduktiva/blob/main/konduktiva-documentation.md|Konduktiva-documentation.md]].
-console.log(e.octaveMaps[e.players.exampleMidiPlayer4.octaveMap].values) +
-</code> +
-===== Changing RhythmMap ===== +
-Example changing rhythmMap for exampleMidiPlayer4 without changing timing. Similar to [[http://konduktiva.org/doku.php?id=first_steps#changing_octaves|changing octave]]. +
-<code javascript> +
-//Recommended safe way: +
-e.addMap('rhythmMaps',  +
-    e.players.exampleMidiPlayer4.rhythmMap,  +
-    e.rhythmMaps[e.players.exampleMidiPlayer4.rhythmMap].values[0].keyspan,  +
-    e.rhythmMaps[e.players.exampleMidiPlayer4.rhythmMap].values[0].keys,  +
-    [2, 4, 6] +
-) +
-//other potentially faster way: +
-e.rhythmMaps[e.players.exampleMidiPlayer4.rhythmMap].values[0].values = [2, 4, 6] +
-</code>+
  
-===== Changing Melody, Notes or Chords ==== +Recommended reading [[https://github.com/renickbell/konduktiva/blob/main/konduktiva-documentation.md#conceptual-overviewz|Conceptual Overview]]
-Example of changing notes played for exampleMidiPlayer4 Similar to [[http://konduktiva.org/doku.php?id=first_steps#changing_octaves|changing octave]].: +
-<code javascript> +
-//Recommended way +
-e.addMap('noteMaps',  +
-    e.players.exampleMidiPlayer4.noteMap,  +
-    5,  +
-    [0, 1, 2, 3, 4],  +
-    [ [40],[50], [60], [70], [80]] +
-) +
-//OR +
-e.noteMaps[e.players.exampleMidiPlayer4.noteMap] = new QuantizedMap(5, [0, 1, 2, 3, 4], [ [40],[50], [60], [70], [80]]) +
-</code> +
- +
-===== Changing The MusicalEnvironment In General ===== +
- +
-To change things in the MusicalEnviornment, one should use the addMap method. The documentation is in [[https://github.com/renickbell/konduktiva/blob/main/konduktiva-documentation.md|konduktiva-documentation.md]]+
  
-Or read about the different ways to generate music [[http://konduktiva.org/doku.php?id=music_generation|here]]+[[quantizedmaps-tutorial|Click to learn about QuantizedMaps and how they are used in Konduktiva]]
  • first_steps.1708055738.txt.gz
  • Last modified: 2024/02/15 19:55
  • by steve.wang