Both sides previous revisionPrevious revisionNext revision | Previous revision |
mididocs:seq:hardwareconfig [2014/09/18 01:46] – [The MBSEQ_HW.V4 File] borfo | mididocs:seq:hardwareconfig [2014/09/18 20:33] (current) – borfo |
---|
====Config File for the Wilba Frontpanel==== | ====Config File for the Wilba Frontpanel==== |
If you've just built a MIDIbox and all you want is for your Wilba Frontpanel to work, then you really don't need to understand this file. [[http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fhwcfg%2Fwilba%2FMBSEQ_HW.V4|Here is a standard MBSEQ_HW.V4 file]] for the Wilba Frontpanel. Just make sure that file exists in your SD Card root. | If you've just built a MIDIbox and all you want is for your Wilba Frontpanel to work, then you really don't need to understand this file. [[http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fhwcfg%2Fwilba%2FMBSEQ_HW.V4|Here is a standard MBSEQ_HW.V4 file]] for the Wilba Frontpanel. Just make sure that file exists in your SD Card root. |
| |
| ====Reassigning Buttons==== |
| If you like, you can completely reconfigure your button assignments. If you read through the MBSEQ_HW.V4 file, you'll see that there are a few button assignments available that are not used on the Wilba Frontpanel... If you're interested in having any of those buttons available on your control surface, you can replace a button assignment that you don't need. How to do this should be fairly obvious to you as you read through the MBSEQ_HW.V4 file. If you screw it up somehow, you can just revert to the original MBSEQ_HW.V4 file, no harm done. |
| |
| |
====Example MBSEQ_HW.V4 files==== | ====Example MBSEQ_HW.V4 files==== |
====Adding Modules to Your SEQ==== | ====Adding Modules to Your SEQ==== |
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 [[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. |
| |
| |