Subversion Repositories svn.mios

Compare Revisions

Ignore whitespace Rev 927 → Rev 931

/trunk/ucapps/midibox_seq_v3_manual.html.gen
142,7 → 142,7
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Additional Buttons/LEDs for MIDIbox SEQ V3 </H2></DT>
 
<P CLASS=INFO>If you are planning to create your own frontpanel, following additional buttons and LEDs are recommented, which are new for MIDIbox SEQ V3, and therefore haven't been considered in the MBSEQ V2 layout. The buttons can be connected to any free DIN (button) and DOUT (LED) pin, and they have to be enabled in the setup_mbseq_v3.asm file:<BR>
<P CLASS=INFO>If you are planning to create your own frontpanel, following additional buttons and LEDs are recommended, which are new for MIDIbox SEQ V3, and therefore haven't been considered in the MBSEQ V2 layout. The buttons can be connected to any free DIN (button) and DOUT (LED) pin, and they have to be enabled in the setup_mbseq_v3.asm file:<BR>
 
<DD>
<TABLE CLASS=BOX WIDTH=550 ALIGN=CENTER BORDER CELLSPACING=2 CELLPADDING=3 >
742,7 → 742,7
<LI><B>Keyboard Channel:</B> the MIDI channel over which the arpeggiator/transpose can be controlled, and CCs will be received (e.g. for the morph function)</LI>
<LI><B>T/A Split:</B> optionally, the transpose and arpeggiator function can be controlled from two different keyboard zones</LI>
<LI><B>Middle Note:</B> separates between the transpose and arpeggiator function. The transpose function is controlled from the lower keys</LI>
<LI><B>Merger:</B> incoming MIDI events will be directly forwarded to the default MIDI out port. <I>not recommented, as control events - e.g. for the transpose function, will be forwarded as well! Only useful if SysEx data should be temporary forwarded, in all other cases use the router instead!</I></LI>
<LI><B>Merger:</B> incoming MIDI events will be directly forwarded to the default MIDI out port. <I>not recommended, as control events - e.g. for the transpose function, will be forwarded as well! Only useful if SysEx data should be temporary forwarded, in all other cases use the router instead!</I></LI>
<LI><B>MIDI Router</B> provides a simple possibility to route incoming MIDI events to synthesizers which are connected to the MIDI Out ports (which means: also to the AOUT port - MBSEQ replaces a CV interface!)
<UL CLASS=CL>
<LI><B>IN:</B> selects the MIDI IN port (Internal/IIC1) - for both ports an individual output mapping is available.<BR>