msq-cc-bcr
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
msq-cc-bcr [2018/02/17 02:36] – phatline | msq-cc-bcr [2018/02/17 02:52] (current) – phatline | ||
---|---|---|---|
Line 7: | Line 7: | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | i have the need to control | + | Controls |
- | So i connect a BlackBox between Sequencer & Synthesizers...\\ | + | Realized by connect a BlackBox between Sequencer & Synthesizer\\ |
This Box is called MSQ_CC_BCR: **M**otion **S**equencer for Midi**C**ontrol**C**hange controlled via a **BCR**2000 Midicontroller\\ | This Box is called MSQ_CC_BCR: **M**otion **S**equencer for Midi**C**ontrol**C**hange controlled via a **BCR**2000 Midicontroller\\ | ||
**__It acts as:__**\\ | **__It acts as:__**\\ | ||
- | - **Midi Merger** NTE,CLK,PC merge with CC... & CCinput is a thing between MSQ_CC_BCR and BCR only since we have intelligent UI with Pages..\\ | + | - **Midi Merger** NTE,CLK,PC merge with CC... & CCinput is a thing between MSQ_CC_BCR and BCR only since we have intelligent UI with Pages\\ |
- | - **Patch Manager** it replaces the Synths internal Patch Storage, | + | - **Patch Manager** it replaces the Synths internal Patch Storage, |
- | - **Motion Sequencer** Record your Controller Movements in a Sequence in 32th Resultion @ maximal 256 Steps length\\ | + | - **Motion Sequencer** Record your Controller Movements in a Sequence in 32th Resultion @ maximal 256 Steps length\\ |
==== Features ==== | ==== Features ==== | ||
- **Remote your Synths** by: 8x Midichannels with up to 32x Control Change (CC)\\ | - **Remote your Synths** by: 8x Midichannels with up to 32x Control Change (CC)\\ | ||
- | For the BCR i only can provide 8x29, because i need some controlls to control the MB Program itself... | + | For the BCR i only can provide 8x29, because i need some controlls to control the MB Program itself\\ |
- | - **Save the Patches** and dump it the Synth\\ | + | - **Save the Patches** and dump it to Synth\\ |
- **Load hundrets of Patches** via received Program Change + the Bank-CC (CC32)\\ | - **Load hundrets of Patches** via received Program Change + the Bank-CC (CC32)\\ | ||
- | - **Save Patches** vie CC24 + CC value 0-127... when sending before a BankCC32 you can expand that..\\ | + | - **Save Patches** vie CC24 + CC value 0-127... when sending before a BankCC32 you can expand that to 128x128 patches\\ |
- **Record CC-Motion-Sequences** use a footpedal connected to FSW1 on the backside of the BCR, to ARM/Disarm it... so you can tweedle 2 ore more CC @ once... but you dont have to, BCR-onboard is also a Button for it\\ | - **Record CC-Motion-Sequences** use a footpedal connected to FSW1 on the backside of the BCR, to ARM/Disarm it... so you can tweedle 2 ore more CC @ once... but you dont have to, BCR-onboard is also a Button for it\\ | ||
- | - **PLAY Motions-Sequences,** up to 256 steps @ 32th rate... this steps of course are only right when you have choosen 4/4 in your Patch... elswhere of course will differ a bit...but 256 is max.\\ | + | - **PLAY Motions-Sequences** up to 256 steps @ 32th rate |
- | - **VELOCITY MORPH** Add Velocity-Ammount to CCs \\ | + | - **VELOCITY MORPH** Add Velocity-Ammount to CCs\\ |
- | - **MERGE** incoming Midi-Notes/ | + | - **MERGE** incoming Midi-Notes/ |
- | - **Set Sequencer Beatstructure** - how to interprete Clock-ticks (4/4, 5/4, 6/4, 7/4...)\\ | + | - **Set Sequencer Beatstructure** - how to interprete Clock-ticks (4/4, 5/4, 6/4, 7/ |
- **Global Page**: for example you use 8 simular Drum-Voices, | - **Global Page**: for example you use 8 simular Drum-Voices, | ||
8xVolume, 8xTone/ | 8xVolume, 8xTone/ | ||
- | if you have one Synth over 2 MSQ_CC_BCR | + | if you have one Synth over 2xMSQ_CC_BCR |
- | - Many of this features, especially the **System Settings would need a UI**, but that would it make bigger, more expensiv, and maybe more complex to use... | + | - Many of this features, especially the **System Settings** would need a UI, but that would it make bigger, more expensiv, and maybe more complex to use... it is set once, for one multipart-synth+bcr2000, |
====== Hardware Requirements ====== | ====== Hardware Requirements ====== | ||
Line 36: | Line 36: | ||
* Melody/ | * Melody/ | ||
* Melody/ | * Melody/ | ||
- | * Midicontroller: | + | * Midicontroller: |
**Midibox: | **Midibox: | ||
Line 49: | Line 49: | ||
The LEDs show via Gestic (Patterns) if something is wrong, done, busy, & show the Rythm structure: | The LEDs show via Gestic (Patterns) if something is wrong, done, busy, & show the Rythm structure: | ||
The Switch switches as Radio-Button thru the Rythm Structures (4/4, 5/4...), the LED-Indicating this. | The Switch switches as Radio-Button thru the Rythm Structures (4/4, 5/4...), the LED-Indicating this. | ||
- | By Holding the Switch and Powering the Core, it will Dump Out a Sysex Template to your BCR. | + | By Holding the Switch and Powering the Core, it will Dump Out a Sysex Template to your BCR.\\ |
{{: | {{: | ||
Line 57: | Line 57: | ||
==== Setting up a BCR2000 ==== | ==== Setting up a BCR2000 ==== | ||
+ | |||
== Cabeling == | == Cabeling == | ||
MidiIO PortA Out >>> | MidiIO PortA Out >>> | ||
AFTER Uploading the Sysex, and restarting the BCR connect:\\ | AFTER Uploading the Sysex, and restarting the BCR connect:\\ | ||
MidiIO PortA In >>> | MidiIO PortA In >>> | ||
- | \\ | + | |
== Upload the Sysex-Template == | == Upload the Sysex-Template == | ||
- | 1. unpack {{: | + | 1. unpack {{: |
2. Put SD-Card into CORE32\\ | 2. Put SD-Card into CORE32\\ | ||
3. bridge J5A Pin0 to ground, or connect a switch to it, that you will need if you want to sequence other song structures then 4/4 (which is default)!\\ | 3. bridge J5A Pin0 to ground, or connect a switch to it, that you will need if you want to sequence other song structures then 4/4 (which is default)!\\ | ||
Line 69: | Line 70: | ||
...if the filestructure (patches) are already existent...then it takes less then half a minute to dump the BCR-2000 Layout Data...\\ | ...if the filestructure (patches) are already existent...then it takes less then half a minute to dump the BCR-2000 Layout Data...\\ | ||
You dont have to save the preset, it will make it automatic\\ | You dont have to save the preset, it will make it automatic\\ | ||
- | ...when no filestructure... then it will take about 16minutes... the core has to make 4000Patches*32KB=139MB!!!!... so better:\\ | + | ...when no filestructure... then it will take a minute or so... the core has to make 256 Patches, since i dont need more ( i can only access on my 16x16BLM 16x16 Patches |
- | * Faking a filestructure: | + | * Faking a filestructure: |
==== Frontpanels ==== | ==== Frontpanels ==== | ||
=== BCR2000 Stickers === | === BCR2000 Stickers === | ||
The Blue Elements are the MBHP Remotes... the Rest is for the Synth\\ | The Blue Elements are the MBHP Remotes... the Rest is for the Synth\\ | ||
- | {{: | + | {{: |
UNTESTET, NOT SCALED!!!!\\ | UNTESTET, NOT SCALED!!!!\\ | ||
In Order to better understand the Routing of the Internal CCs to externals: | In Order to better understand the Routing of the Internal CCs to externals: | ||
- | {{ : | + | {{ : |
==== MBHP ==== | ==== MBHP ==== | ||
Line 84: | Line 86: | ||
====== Software ====== | ====== Software ====== | ||
- | ===== Firmware ==== | + | ===== Firmware |
V1. from 17.02.2018{{: | V1. from 17.02.2018{{: | ||
hardcodet for a NordDrum2 (also newest sysex for the BCR includet) \\ | hardcodet for a NordDrum2 (also newest sysex for the BCR includet) \\ |
msq-cc-bcr.1518834994.txt.gz · Last modified: 2018/02/17 02:36 by phatline