User Tools

Site Tools


mididocs:seq:hardwareconfig

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
Last revision Both sides next revision
mididocs:seq:hardwareconfig [2014/09/18 01:32]
borfo [Example MBSEQ_HW.V4 files]
mididocs:seq:hardwareconfig [2014/09/18 05:59]
borfo [Adding Modules to Your SEQ]
Line 1: Line 1:
 **[[mididocs:​index|MIDIdocs]]** **[[mididocs:​index|MIDIdocs]]**
 ======The MBSEQ_HW.V4 File====== ======The MBSEQ_HW.V4 File======
-[[|Forum Discussion Thread]] - for comments, corrections,​ or questions about this article+[[http://​midibox.org/​forums/​topic/​19043-mididocs-seqv4-the-mbseq-hwv4-file-discussion-thread/​|Forum Discussion Thread]] - for comments, corrections,​ or questions about this article
  
 This file contains configuration information about your SEQ's hardware - button, LED, and encoder assignments,​ some low level settings, etc. This file has to be in the root of your SD Card in order for the Wilba Frontpanel to work, because without this file, the SEQ core won't know anything about the buttons and LEDS on your frontpanel. ​ This file contains configuration information about your SEQ's hardware - button, LED, and encoder assignments,​ some low level settings, etc. This file has to be in the root of your SD Card in order for the Wilba Frontpanel to work, because without this file, the SEQ core won't know anything about the buttons and LEDS on your frontpanel. ​
Line 21: Line 21:
  
 ====Adding Modules to Your SEQ==== ====Adding Modules to Your SEQ====
-Some modules, like the TPD (Track Position Display) module, the AOUT_NG module (provides CV outs), and hardware Button LED Matrices ​(BLMs) require amendments to the MBSEQ_HW.V4 file.  ​See, for example, the configuration documentation on [[http://​www.midibox.org/​dokuwiki/​doku.php?​id=tpd_pcb&​s[]=mbseq&​s[]=hw&​s[]=v4#​config|this page]] about the [[http://​www.midibox.org/​dokuwiki/​doku.php?​id=tpd_pcb&​s[]=mbseq&​s[]=hw&​s[]=v4|TPD module]].+Some modules, like the [[http://​www.midibox.org/​dokuwiki/​doku.php?​id=tpd_pcb&​s[]=mbseq&​s[]=hw&​s[]=v4|TPD (Track Position Display) module]], the [[http://​www.midibox.org/​dokuwiki/​doku.php?​id=aout_ng|AOUT_NG module]] (provides CV outs), and the hardware ​[[http://​www.ucapps.de/​midibox_seq_manual_blm.html|Button LED Matrix ​(BLM)]] require amendments to the MBSEQ_HW.V4 file.  ​To learn a bit about how this works, see, for example, the configuration documentation on [[http://​www.midibox.org/​dokuwiki/​doku.php?​id=tpd_pcb&​s[]=mbseq&​s[]=hw&​s[]=v4#​config|this page]] about the [[http://​www.midibox.org/​dokuwiki/​doku.php?​id=tpd_pcb&​s[]=mbseq&​s[]=hw&​s[]=v4|TPD module]]
 + 
 +Some modules, like the QUAD_MIDI_IIC,​ are pretty much "plug and play" and don't require any editing of the MBSEQ_HW.V4 file.  Generally speaking, you'll need to edit the MBSEQ_HW.V4 whenever you're adding a module that has buttons, encoders, or LEDs that you want to assign
  
    
mididocs/seq/hardwareconfig.txt · Last modified: 2014/09/18 20:33 by borfo