MIDIbox

User Tools

Site Tools

Trace:
home:project:midi_mapper

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
home:project:midi_mapper [2008/12/15 14:16] – thishome:project:midi_mapper [2011/07/22 14:53] (current) – removed spam digineural
Line 1: Line 1:
-** THIS PAGE IS UNDER CONSTRUCTION ! **+====== MIDI Mapper ======
  
-=====Intro=====+ 
 +====== Intro ======
  
 This page describes the MIDI-Channel-Mapper device, which can route input channels of a single hardware input to output channels of a single hardware output in any way you want. The device's user interface is designed to allow switching the routing of some channels while performing, leaving other routings untouched. This page describes the MIDI-Channel-Mapper device, which can route input channels of a single hardware input to output channels of a single hardware output in any way you want. The device's user interface is designed to allow switching the routing of some channels while performing, leaving other routings untouched.
Line 11: Line 12:
  
  
-=====Features=====+====== Features ======
  
   * One MIDI hardware-input   * One MIDI hardware-input
Line 26: Line 27:
 {{:home:project:midi_mapper:routing_example.jpg|}} {{:home:project:midi_mapper:routing_example.jpg|}}
  
-====Buses====+===== Buses =====
 The routing is oranized with buses. To each of the 16 buses, input and output channels can be assigned. The events from the input channels of a bus will be routed to it's output channels. There will be no redundant routing, this means if you route channel 2 -> 7 on more than one bus, a incoming event on channel 2 will just be sent once to the output 7. The goal of all this is to have some routings fixed, while you can play arround on the currently selected bus without affecting the routings on the other buses. The routing is oranized with buses. To each of the 16 buses, input and output channels can be assigned. The events from the input channels of a bus will be routed to it's output channels. There will be no redundant routing, this means if you route channel 2 -> 7 on more than one bus, a incoming event on channel 2 will just be sent once to the output 7. The goal of all this is to have some routings fixed, while you can play arround on the currently selected bus without affecting the routings on the other buses.
  
-====User Interface Screens====+===== User Interface Screens =====
 The user interface is organized in four screens. If you switch to a screen by pushing the screen button, the value button LED's reflect the setup for this screen, with pushing the buttons, you manipulate the setup.\\ The user interface is organized in four screens. If you switch to a screen by pushing the screen button, the value button LED's reflect the setup for this screen, with pushing the buttons, you manipulate the setup.\\
 The **preset screen** is the top-level-screen. Pushing a value button loads a preset (1-16). Pushing [preset]+[X] saves the current setup to the preset X. Holding [preset] for > 3 sec clears all presets ("factory reset"). After the reset, the first preset has a "straight" setup: in 1 -> out 1, in 2 -> out 2 etc., all other presets will be empty (no forwarding).\\ The **preset screen** is the top-level-screen. Pushing a value button loads a preset (1-16). Pushing [preset]+[X] saves the current setup to the preset X. Holding [preset] for > 3 sec clears all presets ("factory reset"). After the reset, the first preset has a "straight" setup: in 1 -> out 1, in 2 -> out 2 etc., all other presets will be empty (no forwarding).\\
 On the **bus screen**, you select the bus. This does not affect the routing, but you will "work" on this bus then, that means if you switch to input or output screen, you will assign input/output channels to the bus that is currently selected. To reset (clear) the currently selected preset, just hold the bus-screen button for > 3 sec.\\ On the **bus screen**, you select the bus. This does not affect the routing, but you will "work" on this bus then, that means if you switch to input or output screen, you will assign input/output channels to the bus that is currently selected. To reset (clear) the currently selected preset, just hold the bus-screen button for > 3 sec.\\
 On the **input and output screens**, you assign in/out channels to the currently selected bus. Multiple values can be selected by using the screen button as shift key: [input]+[1]+[7]+[3]. This way channels can be added/removed from a bus. Pushing a single value button again will switch off the other values, and switch the state of the pushed value.\\ On the **input and output screens**, you assign in/out channels to the currently selected bus. Multiple values can be selected by using the screen button as shift key: [input]+[1]+[7]+[3]. This way channels can be added/removed from a bus. Pushing a single value button again will switch off the other values, and switch the state of the pushed value.\\
-====Additional Lookup Functions==== 
-There are some additional "lookup" functions. They just show information about the current setup:\\ 
-"which buses have (any)input channels assigned?": [bus]+[input]\\ 
-"which buses have input channel 6 assigned?": [bus]+[input]+[6]\\ 
-"which buses have (any)output channels assigned?": [bus]+[output]\\ 
-"which buses have output channel 3 assigned?": [bus]+[output]+[3]\\ 
-"which outputs are assigned to a(any) bus?": [output]+[bus]\\ 
-"which outputs are assigned to bus 2 ?": [output]+[bus]+[2]\\ 
-"which inputs are assigned to a(any) bus ?": [input]+[bus]\\ 
-"which inputs are assigned to bus 7?": [input]+[bus]+[7]\\ 
-The value LED's will show the information as long you hold the screen buttons.\\ 
  
-====Usage Example====+===== Usage Example =====
  To give you an idea of the use of all this, have a look at this simple example:  To give you an idea of the use of all this, have a look at this simple example:
  
Line 53: Line 43:
 The reasons why I built the device: on my masterkeyboard I can switch the output channel of the keyboard section (keys/pitch wheel/mod wheel), but this can only be done by performing shift+channel -> choose channel by encoder -> push ok. But I rather like to just push one button to route the events to my target instrument. For all the faders/rotaries I can assign individual channels/events, but these channels will not be affected by changing the output channel of the keys section. With the MIDI-Mapper I can do for example this: have some faders routed to a fixed target (instrument/sequencer etc.), and others on the same bus with the keyboard section channel to a target instrument that I can change quickly while playing on the keyboard. 1000's of other possibilities can be imagined.\\ The reasons why I built the device: on my masterkeyboard I can switch the output channel of the keyboard section (keys/pitch wheel/mod wheel), but this can only be done by performing shift+channel -> choose channel by encoder -> push ok. But I rather like to just push one button to route the events to my target instrument. For all the faders/rotaries I can assign individual channels/events, but these channels will not be affected by changing the output channel of the keys section. With the MIDI-Mapper I can do for example this: have some faders routed to a fixed target (instrument/sequencer etc.), and others on the same bus with the keyboard section channel to a target instrument that I can change quickly while playing on the keyboard. 1000's of other possibilities can be imagined.\\
 \\ \\
-Also refer/print the usage manual in the extra-section at the bottom of the page for information about how to handle the device.+Also refer/print the {{:home:project:midi_mapper:midi_mapper_usage.pdf|usage manual}} in the extra-section at the bottom of the page for information about how to handle the device.
  
 +===== Additional Lookup Functions =====
 +There are additional "lookup" functions. They just show information about the current setup:\\
 +\\
 +"which buses have (any)input channels assigned?": [bus]+[input]\\
 +"which buses have input channel X assigned?": [bus]+[input]+[value X]\\
 +"which buses have (any)output channels assigned?": [bus]+[output]\\
 +"which buses have output channel X assigned?": [bus]+[output]+[value X]\\
 +\\
 +"which inputs are assigned to a(any) bus ?": [input]+[bus]\\
 +"which inputs are assigned to bus X?": [input]+[bus]+[value X]\\
 +"which inputs are routed to (any) output:": [input]+[output]\\
 +"which inputs are routed to output X:": [input]+[output]+[value X]\\
 +\\
 +"which outputs are assigned to a(any) bus?": [output]+[bus]\\
 +"which outputs are assigned to bus X ?": [output]+[bus]+[value X]\\
 +"which outputs are fed by (any) input:": [output]+[input]\\
 +"which outputs are fed by input X:": [output]+[input]+[value X]\\
 +\\
 +The value LED's will show the information as long you hold the screen buttons.\\
  
-=====Skills / Equipment Required=====+====== Skills / Equipment Required ======
  
-  * [[:home:skills:preparation | Preparation]]+  * [[:home:skills:tools| Tools]]
   * [[:home:skills:soldering | Soldering]]   * [[:home:skills:soldering | Soldering]]
  
Line 64: Line 73:
  
  
-=====Harware=====+====== Hardware ======
  
-====What modules do I need?====+===== What modules do I need? =====
  
   * [[:home:mbhp:module:core | Core Module]]   * [[:home:mbhp:module:core | Core Module]]
Line 73: Line 82:
   * [[:home:mbhp:module:dout | DOUT Module]]   * [[:home:mbhp:module:dout | DOUT Module]]
  
-====List of parts====+===== List of parts =====
  
   * 1x MBHP Core Module   * 1x MBHP Core Module
Line 90: Line 99:
 [[:home:mbhp:parts | Where to buy Parts]] [[:home:mbhp:parts | Where to buy Parts]]
  
-====Connections====+===== Connections =====
  
 Connect the buttons / LED's to DIN and DOUT module like shown in the following table: Connect the buttons / LED's to DIN and DOUT module like shown in the following table:
Line 139: Line 148:
  
      
-==== Enclosure / Case ====+===== Enclosure / Case =====
 The Case used is a standard case from a local case manufacturer (http://www.jaegerag.ch). The bottom plate is metal, the top metal plate is just a thin cover, which is layed over the plastic top.  The Case used is a standard case from a local case manufacturer (http://www.jaegerag.ch). The bottom plate is metal, the top metal plate is just a thin cover, which is layed over the plastic top. 
  
Line 149: Line 158:
  
  
-=== Enclosure References ===+==== Enclosure References ====
 [[:home:skills:constructing_enclosures]] [[:home:skills:constructing_enclosures]]
  
Line 155: Line 164:
  
  
-=====Software===== +====== Software ====== 
-==== Setting Up ====+===== Setting Up =====
  
 PIC's must be setup with MIOS bootstrap Loader and MIOS before an application can be uploaded. \\  PIC's must be setup with MIOS bootstrap Loader and MIOS before an application can be uploaded. \\ 
Line 167: Line 176:
     * [[:home:mios:software_tools | Additional tools]]     * [[:home:mios:software_tools | Additional tools]]
  
-==== Download ====+===== Download =====
  
 {{:home:project:midi_mapper:midi_mapper_dist.zip|MIDI Mapper Source Code and Binary (.zip)}} {{:home:project:midi_mapper:midi_mapper_dist.zip|MIDI Mapper Source Code and Binary (.zip)}}
  
-==== Setup Instructions ====+===== Setup Instructions =====
  
   * Upload the project.hex file from the zip-package with [[http://miosstudio.midibox.org/|MIOS-studio]] to your MIDIBox - core   * Upload the project.hex file from the zip-package with [[http://miosstudio.midibox.org/|MIOS-studio]] to your MIDIBox - core
Line 177: Line 186:
  
  
-=====Extra===== +====== Extra ====== 
- +{{:home:project:midi_mapper:midi_mapper_usage.pdf|MIDI-Mapper usage manual (.pdf)}}
-[[usage manual]]+
  
-  + anything else 
home/project/midi_mapper.1229350585.txt.gz · Last modified: 2008/12/15 14:16 by this