home:project:midi_mapper
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
home:project:midi_mapper [2008/12/15 17:19] – this | home: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' | 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' | ||
Line 11: | Line 12: | ||
- | =====Features===== | + | ====== Features |
* One MIDI hardware-input | * One MIDI hardware-input | ||
Line 26: | Line 27: | ||
{{: | {{: | ||
- | ====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 (" | 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 (" | ||
Line 35: | Line 36: | ||
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/ | 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/ | ||
- | ====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 44: | Line 45: | ||
Also refer/print the {{: | Also refer/print the {{: | ||
- | ====Additional Lookup Functions==== | + | ===== Additional Lookup Functions |
There are additional " | There are additional " | ||
\\ | \\ | ||
Line 64: | Line 65: | ||
The value LED's will show the information as long you hold the screen buttons.\\ | The value LED's will show the information as long you hold the screen buttons.\\ | ||
- | =====Skills / Equipment Required===== | + | ====== Skills / Equipment Required |
- | * [[: | + | * [[: |
* [[: | * [[: | ||
Line 72: | Line 73: | ||
- | =====Harware===== | + | ====== Hardware ====== |
- | ====What modules do I need?==== | + | ===== What modules do I need? ===== |
* [[: | * [[: | ||
Line 81: | Line 82: | ||
* [[: | * [[: | ||
- | ====List of parts==== | + | ===== List of parts ===== |
* 1x MBHP Core Module | * 1x MBHP Core Module | ||
Line 98: | Line 99: | ||
[[: | [[: | ||
- | ====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 147: | Line 148: | ||
| | ||
- | ==== Enclosure / Case ==== | + | ===== Enclosure / Case ===== |
The Case used is a standard case from a local case manufacturer (http:// | The Case used is a standard case from a local case manufacturer (http:// | ||
Line 157: | Line 158: | ||
- | === Enclosure References === | + | ==== Enclosure References |
[[: | [[: | ||
Line 163: | 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 175: | Line 176: | ||
* [[: | * [[: | ||
- | ==== Download ==== | + | ===== Download |
{{: | {{: | ||
- | ==== Setup Instructions ==== | + | ===== Setup Instructions |
* Upload the project.hex file from the zip-package with [[http:// | * Upload the project.hex file from the zip-package with [[http:// | ||
Line 185: | Line 186: | ||
- | =====Extra===== | + | ====== Extra ====== |
{{: | {{: | ||
home/project/midi_mapper.1229361596.txt.gz · Last modified: 2008/12/15 17:19 by this