Subversion Repositories svn.mios

Compare Revisions

Ignore whitespace Rev 1227 → Rev 1228

/trunk/ucapps/midibox_seq_manual_tut4.html.gen
41,7 → 41,7
 
You could play a plucked synth with this track. The synth should vary the cut-off frequency with the velocity value. Add a lot of reverb, and maybe also an additional audio delay.<BR>
Example:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
So: with only two notes, and the MIDI delay we create a sequence which plays 16 notes over 4 bars. If you like to experiment a bit more with this configuration, enter additional notes at various positions.
</SPAN></TD></TR>
 
55,7 → 55,7
<LI><B>Length:</B> 4 steps (only)
</UL>
 
And now you will learn a new trick to "stretch" such a sequence: change to the Divider page, and set the "Repeat" value to 1, and the Interval (Itv.) to 7:
And now you will learn a new trick to "stretch" such a sequence: change to the Direction page, and set the "Repeat" value to 1, and the Interval (Itv.) to 7:
<CENTER><IMG SRC="midibox_seq/cs4/tut4_3b.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
 
With this configuration, after 7 steps the last step will be repeated. Accordingly we add a note each 2 iterations of this 4-step sequence: each measure will start with a different note!<BR>
73,7 → 73,7
</UL>
 
So: now we have a sequence which changes it's starting note with each measure, and concurrently apply a velocity scheme which repeats each 6 steps. This is the result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
 
Hard to imagine, that we actually only entered 4 notes, no? :-)<BR>
The step repeat function in conjunction with a groove pattern is a great field for experiments. E.g. if you try different notes, but also track lengths, you will get very different variants on each change.
92,7 → 92,7
Change back to the EDIT page, and press the Trigger Layer C button. It will display a menu page for all 8 trigger layers. Select Trigger Layer E (Skip).<BR>
With the GP buttons, enable the skip function for step 4, 6, 8, 12 and 14 (note: an uneven number of disabled steps).<BR>
So, we reduced the sequence to 11 steps - and this is the result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
While the sequence is playing, you could enable/disable Skip also for some other steps to vary it even more.
</SPAN></TD></TR>
 
105,7 → 105,7
<LI><B>Divider:</B> set to 32 (8th notes). You could also push GP12 for the quick selection of this divider value.
</UL>
The result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
116,7 → 116,7
<LI><B>Divider:</B> set to 64 (4th notes). You could also push GP11 for the quick selection of this divider value.
</UL>
Since the track length is still 16, the reduced resolution means that the chord will be played over 4 measures:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
125,13 → 125,13
I'm too lazy to describe you all the details how I created this pattern, therefore just upload this <A HREF="midibox_seq/TUTOR4_D.zip" TARGET="_blank">TUTOR4_D.V4T</A> file into the PRESETS folder of the SD Card (you could use the <A HREF="mios_studio.html">MIOS Studio based filebrowser</A> for this purpose).<BR>
Thereafter import the preset into G2T3 with the MENU-&gt;EVENT-&gt;PRESETS function.<BR>
An audio sample of the drum track:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_6.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_6.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
<TR><TD COLSPAN=2>
Finally the complete sequence where all tracks are played together with some (sample loop based) drums:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
I recommend you to change some track notes and configurations while the sequence is playing, mute tracks, add more tracks - a typical Berlin School song must take at least 20 minutes! ;-)
</SPAN></TD></TR>
 
139,7 → 139,7
Addendum: you could also play another synth line live, but unfortunately I can only give you a poor example for this, because I'm a lousy keyboard player (that's the reason why I created MIDIbox SEQ! ;-).<BR>
In order to ensure, that I don't play wrong notes which are out of scale during this recording, I played the synth via the Live function with Force-to-Scale enabled. This function can be activated with UTILITY-&gt;LIVE. Activate Force-to-Scale with the FTS option, select Bus2 (and not Bus1, because it's used by the transposer), adjust the MIDI IN port, and set the Bus mode to "Play" instead of T&A:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut4_8a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut4_with_keys.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut4_with_keys.mp3"#ffffff**<BR><SPAN CLASS=NORM>
Sorry again for the bad performance!<BR>
And yes, I'm a big fan of <A HREF="http://www.klaus-schulze.com" TARGET="_blank">Klaus Schulze</A>! :-)
</SPAN></TD></TR>
/trunk/ucapps/midibox_seq_manual_m.html.gen
31,7 → 31,7
<P CLASS=DESC>The <B>lower line</B> shows the values of 16 steps within the selected track view and parameter layer. They can be directly modified with the 16 GP rotary encoders below these items. The displayed parameter of the step changes with the active layer. E.g. in layer C the gatelength is controlled, which is visualised with vertical bars:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit3.gif" width=481 height=19 ALT="Edit Length"></IMG></CENTER></P>
 
<P CLASS=DESC>Press&amp;hold a GP button to change into <B>EDIT RECORDING</B> mode. Incoming MIDI events will be recorded into the selected step as long as the parameter layer configuration is matching, and layers are free. E.g. it's possible to record MIDI Notes, CCs, PitchBender, Program Change values. The step will be framed by curly brackets to indicate the mode:
<P CLASS=DESC>Press&amp;hold a GP button to change into <B>EDIT RECORDING</B> mode. Incoming MIDI events will be recorded into the selected step as long as the parameter layer configuration is matching, and layers are free. E.g. it's possible to record MIDI Notes, CCs, PitchBender, Poly Pressure (Aftertouch), Program Change values. The step will be framed by curly brackets to indicate the mode:
<CENTER><IMG SRC="midibox_seq/cs4/editrec.gif" width=481 height=19 ALT="Edit Record"></IMG></CENTER></P>
<P CLASS=DESC>EDIT recording can also be toggled on/off with the SELECT button. This allows you to keep this recording mode enabled while no GP button is pressed (useful if you want to enter chords with two hands). Select the step into which the events should be recorded with the datawheel.<BR>
<I>Note1: if recording isn't working as expected, check the recording configuration by pressing EDIT+GP12. At the right side of the page the MIDI port and channel to which the recording function will listen has to be selected.</I><BR>
147,6 → 147,7
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>128</TD> <TD CLASS=TABCOLOR2>2 (32 steps only)</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>16</TD> </TR>
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>128</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>2</TD> <TD CLASS=TABCOLOR2>8</TD> </TR>
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>256</TD> <TD CLASS=TABCOLOR2>2 (64 steps only)</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>8</TD> </TR>
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>64</TD> <TD CLASS=TABCOLOR2>2</TD> <TD CLASS=TABCOLOR2>2</TD> <TD CLASS=TABCOLOR2>8</TD> </TR>
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>64</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>16</TD> </TR>
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>128</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>8</TD> </TR>
<TR> <TD CLASS=TABCOLOR2>Drum</TD> <TD CLASS=TABCOLOR2>256</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>1</TD> <TD CLASS=TABCOLOR2>4</TD> </TR>
169,10 → 170,13
<LI><B>i-n:</B> Min6, Min7, Min8, Min9, Min10, Min12 (4-note chords)</LI>
<LI><B>o-p:</B> Co7 and Min+</LI>
</UL></LI>
<LI><B>Chord2:</B> enhanced chords</LI>
<LI><B>Chord3:</B> our secrent weapon with >100 chords provided by EsotericLabs! **MP3**"http://www.ucapps.de/mp3/midibox_seq/20170623.mp3"#ffffff**</LI>
<LI><B>Velolcity:</B> controls the velocity value for all notes/chords of the instrument.
<LI><B>Length:</B> controls the gatelength of all notes of the instrument
<LI><B>CC:</B> plays a selectable CC number.<BR>
CC#128 (displayed as "off") is initialized by default for each layers. With this CC assignment, no events will be sent, which means in other words, that a valid CC number has to be selected with one of the GP encoders 11..13 to send something. Note also, that after the CC has been selected, one of the GP buttons 11..13 has to be pressed to confirm the CC number change. This handling ensures, that no unintended CCs will be sent while the CC number is changed.
<LI><B>PrgCh:</B> sends a program change event.
<LI><B>Pitch:</B> sends a PitchWheel event
<LI><B>Prob:</B> sets the probability that the step will be played (1..100%)
<LI><B>Delay:</B> delays the step for 1..96 microticks
218,6 → 222,11
<LI> <B>Fx:</B> enable Fx each nth bar
<LI> <B>Nx:</B> don't enable Fx each nth bar
</UL></LI>
<LI><B>Root:</B> if Root is assigned to any parameter layer of a track, the layer can either select the global root selection ("Glb") or set the root note for each step explicitely.<BR>
The global root selection is configured in the FX->Scale page, it's either "Keyb" (for MIDI keyboard entry) or C, C#, ... B
The local root selection is C, C#, ... B<BR>
Notes and Chords will be transposed accordingly if the track is in Normal mode (and not in Transpose or Arpeggiator mode)
<LI><B>Scale:</B> overrides the globally configured scale of the FX->Scale page for each step.
</UL></LI>
<LI>The <B>MIDI Channel</B> can be selected from 1-16.</LI>
<LI>Following <B>MIDI Ports</B> are available:<BR>
495,10 → 504,14
</UL>
<LI><B>Bus:</B> selects Bus1..Bus4 over which the Transposer/Arpeggiator should be controlled. Each bus provides a separate MIDI port/channel/keyboard zone that can be configured in the MIDI page. Alternatively busses can transfer the output of loopback tracks as described earlier.<BR>
Since each track has an own bus assignment, it's possible to transpose tracks individually.</LI>
<LI><B>Hold:</B> the last key or chord is held until a new key/chord is played on the keyboard (only relevant for Tranpose/Arpeggiator mode)</LI>
<LI><B>Note:</B> Allows to specify, if the transposer should take the last or first played note</LI>
<LI><B>Hold:</B> the last or first key or chord is held until a new key/chord is played on the keyboard (only relevant for Tranpose/Arpeggiator mode)</LI>
<LI><B>Sort:</B> only relevant for arpeggiator mode: the note stack will be sorted when this function is active (default); arpeggios will be played with notes "as played" when this functions is deactivated.</LI>
<LI><B>Restart:</B> the track is restarted when a new key/chord is played</LI>
<LI><B>Force Scale:</B> played notes are mapped to the global scale, which can be selected in the Fx-Scale menu page, accordingly only notes are played which match with the selected harmony. This is especially useful when the track consists of randomly generated notes! 127 predefined scales are available!<BR>
<LI><B>ReSt. (Restart):</B> the track is restarted when a new key/chord is played</LI>
<LI><B>STrg. (Step Trigger):</B> if activated, the step progression will be controlled from the transposer
bus, hence it can either be triggered from a loopback track or from an external MIDI device (MIDI keyboard, sequencer, etc.)<BR>
Note that each track can be assigned to a dedicated transpose bus (4 busses are available), this allows to control 4 independent step progressions for all 16 tracks.</LI>
<LI><B>FTS (Force to Scale):</B> played notes are mapped to the global scale, which can be selected in the Fx-Scale menu page, accordingly only notes are played which match with the selected harmony. This is especially useful when the track consists of randomly generated notes! 127 predefined scales are available!<BR>
<A HREF="midibox_seq/scalesMidiboxSeqv4.pdf" TARGET="_blank">Nuke created some nice graphics for all scales - thank you!!!</A></LI>
<LI><B>Sustain:</B> omits the "Note Off" event - notes are played endless, independent from the gatelength. Especially useful for strings and pads!</LI>
</UL>
612,6 → 625,7
</LI>
<LI><B>Intensity:</B> available as VPOS/VNEG parameter to vary the style without creating a new groove template. Also nice for live tweaks to find "best matching" grooves!
<LI><B>Global:</B> By default, groove configuration changes are applied on all tracks. By turning Global "off" the selected groove will only be used for the edited track. This way it's possible to select individual grooves for certain tracks, but also to keep the groove selection for the remaining tracks global.
<LI><B>Sync:</B> allows to sync the groove to the global reference step (RefS) or to the local track step
</UL></P>
 
<P CLASS=DESC>Custom #1..#16 global groove styles can be freely edited. They are stored on SD Card (MBSEQ_G.V4 file) and available for all patterns of a session:
1053,7 → 1067,7
</LI>
<LI><B>Initial CC value for Clear and Init is: X</B>: allows to specify the default value which will be used for CCs whenever the Clear button is pressed, or the Init function in the MENU-&gt;EVENT page is used. It's normally 64, but some people prefer 0 instead. Just define it here.</LI>
<LI><B>If Live function, matching received MIDI events will ...</B>: this experimental function works in conjunction with Live mode or the MIDI Router in "Track" or "Sel.Trk" mode.<BR>
Whenever Note, CC, PitchBender, Program Change events are received on the selected IN Port, the corresponding track layer (or LFO CC) will be muted completely, or temporary for a given number of steps. This allows to temporary overrule events generated by the sequencer from an external MIDI keyboard or controller.<BR>
Whenever Note, CC, PitchBender, Poly Pressure (Aftertouch), Program Change events are received on the selected IN Port, the corresponding track layer (or LFO CC) will be muted completely, or temporary for a given number of steps. This allows to temporary overrule events generated by the sequencer from an external MIDI keyboard or controller.<BR>
Supported settings:
<UL CLASS=CL>
<LI><B>do nothing</B>: function disabled
1145,7 → 1159,7
<LI><B>Pos:</B> the song position - 128 positions are available, they are enumerated from A1..P8</LI>
<LI><B>Action:</B> defines what should be done when this song position is reached:
<UL CLASS=CL>
<LI><B>Stop:</B> sequencer will be stopped.</LI>
<LI><B>End:</B> sequencer will loop this position endless.</LI>
<LI><B>x1..x16:</B> specified Pattern set will be played the given number of cycles (x1..x16). The pattern for each group (G1..G4) can be specified at the right side of the "action" item. If "-:--" is selected instead of the pattern number, the pattern won't be changed for this song step.</LI>
<LI><B>Jump Pos:</B> sequencer jumps to the specified position - allows to set loop points</LI>
<LI><B>Jump Song:</B> sequencer jumps to the specified song</LI>
1326,7 → 1340,7
<LI><B>First Channel:</B> specifies the first channel to which additional note events should be forwarded.<BR>
E.g. with 3 channels starting at Channel 2, Notes will be forwarded to the original MIDI channel configured in the Track Event page + Channel 2, 3 and 4.</LI>
<LI><B>Port:</B> selects the MIDI port to which the additional notes should be forwarded. With "Same" the events will be sent to the MIDI port configured in the Track Event page, with the remaining port settings the MIDI notes will be sent to the selected MIDI port.</LI>
<LI><B>Non-Notes:</B> specifies what should happen with Non-Note events (such as CCs, PitchBender, Channel Pressure, Program Change): they can be filtered, or forwarded to all additional MIDI channels.</LI>
<LI><B>Non-Notes:</B> specifies what should happen with Non-Note events (such as CCs, PitchBender, Aftertouch, Program Change): they can be filtered, or forwarded to all additional MIDI channels.</LI>
<LI><B>Mode:</B> selects the behaviour of this Fx:
<UL CLASS=CL>
<LI><B>Forward to all Channels:</B> notes will be directly forwarded to all MIDI channels
1388,7 → 1402,8
<UL CLASS=CL>
<LI><B>CV:</B> selects the CV channel (1..8)
<LI><B>Curve:</B> selects the output curve: V/Oct, Hz/V, Inverted
<LI><B>Slew Rate:</B> allows to configure a slew rate (slack) in the range of 0..255 mS
<LI><B>SlewR(ate):</B> allows to configure a slew rate (slack) in the range of 0..255 mS
<LI><B>SusK:</B> activates the "SusKey" function (also known as "fingered portamento"): the slew rate will only be activated if at least two notes are played. This allows to use the glide function to enable slew only on demand.
<LI><B>PRng:</B> sets the pitch range for pitch bender events (normally 2, use 12 or 24 to sweep over one, resp. two octaves)
<LI><B>Gate:</B> sets the gate polarity (positive or negative)
<LI><B>Calibr.:</B> allows to force different output voltages for calibration (Min/Middle/Max/1V, 2V, 4V, 8V)
/trunk/ucapps/midibox_seq_manual_tut5.html.gen
44,7 → 44,7
<LI><B>Length:</B> 8 steps (available as quick selection at the right side)
</UL>
Push the PLAY button, and change the note length in Layer C until it sounds nice (ca. 83%).<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut5_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut5_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
Sidenote: <A HREF="midibox_sid.html">MIDIbox SID</A> in poly mode is used as sound source for this track!
</SPAN></TD></TR>
 
52,7 → 52,7
Change to the FX-&gt;ECHO page, and select following configuration:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut5_3a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Now it should sound like in this example:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut5_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut5_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
For the case that you don't already know this tune, here a hint: it's the beginning of the <A HREF="http://www.c64.org/HVSC/MUSICIANS/G/Galway_Martin/Miami_Vice.sid" TARGET="_blank">"Miami Vice" ingame music</A>, composed by Martin Galway - master of the SIDs! :-)<BR>
You can use <A HREF="http://sidplay2.sourceforge.net" TARGET="_blank">SIDPLAY2</A> to playback the .sid file. Mac Users: use <A HREF="http://www.sidmusic.org/sidplay/mac/" TARGET="_blank">SIDPLAY</A>.
</SPAN></TD></TR>
61,7 → 61,7
We add an 8-step bassline which gets use of the Arpeggiator as well:
<CENTER><IMG SRC="midibox_seq/cs4/tut5_4a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Audio example:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut5_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut5_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
68,13 → 68,13
And an additional 8-step line, where we also vary the velocity (in Parameter Layer B):<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut5_5a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Audio example:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut5_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut5_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
<TR><TD COLSPAN=2>
Finally let's play all 3 tracks together with some (sample loop based) drums:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
After 0:29 I started to play the chords manually from an external keyboard to vary the sequences.
</SPAN></TD></TR>
 
/trunk/ucapps/midibox_ng_manual_ngc.html.gen
562,7 → 562,7
<LI><I>RetrieveAinValues</I>: the values of AIN EVENTs will be updated according to the current analog values (pot positions)
<LI><I>RetrieveAinserValues</I>: the values of AINSER EVENTs will be updated according to the current analog values (pot positions)
 
<LI><I>EncFast</I>: speeds up encoder movements according to the EVENT value. E.g. if <I>meta=EncFast range=0:5</I> is assigned to a BUTTON_EVENT, encoders will increment 5 times faster if the button is pressed.
<LI><I>EncFast</I>: speeds up encoder movements according to the EVENT value. E.g. if <I>meta=EncFast:1 range=0:5</I> is assigned to a BUTTON_EVENT, encoder #1 will increment 5 times faster if the button is pressed.
 
<LI><I>MidiLearn</I>: can be used to enable MIDI Learn mode from a dedicated button (instead of the <A HREF="midibox_ng_manual_scs.html">SCS</A>).<BR>
E.g. if <I>meta=MidiLearn range=0:1</I> is assigned to a BUTTON_EVENT, Learn Mode will be enabled when the button is pressed, and disabled once it has been released.<BR>
949,13 → 949,16
<LI>the first 4 digits enable/disable USB1..USB4
<LI>the next 4 digits enable/disable MIDI1..MIDI4
<LI>the next 4 digits are reserved, don't use!
<LI>the last 4 digits enable/disable OSC1..OSC4
<LI>the next 4 digits enable/disable OSC1..OSC4
<LI>the last 4 digits enable/disable SPI1..SPI4 (requires that the spi_midi flag has been enabled in the <A HREF="mios32_bootstrap_newbies.html">MIOS32 Bootloader configuration</A>.
</UL>
Example: following binary value (which is the default value)
<TT><PRE style="margin-left:50px; font-size:8pt">ports=1000100000001000</PRE></TT>
<TT><PRE style="margin-left:50px; font-size:8pt">ports=10001000000010000000</PRE></TT>
will enable USB1, MIDI1 (IN1 and OUT1) and OSC1, and following binary:
<TT><PRE style="margin-left:50px; font-size:8pt">ports=0000110000000000</PRE></TT>
<TT><PRE style="margin-left:50px; font-size:8pt">ports=00001100000000000000</PRE></TT>
will only enable MIDI1 and MIDI2
<TT><PRE style="margin-left:50px; font-size:8pt">ports=00000000000000001000</PRE></TT>
will enable SPI1
</TD>
</TR>
 
1052,8 → 1055,57
type=CC chn= 1 cc= 16 range=map1 lcd_pos=1:1:1 label="^std_enc"
</PRE></TT>
 
<P CLASS=DESC>Up to 255 maps can be defined (<I>MAP1</I> .. <I>MAP255</I>), each map can specify up to 128 values, the value range is 0..255 (8bit)
<P CLASS=DESC>Up to 255 maps can be defined (<I>MAP1</I> .. <I>MAP255</I>).
 
Four different types are available:
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
<TR>
<TH WIDTH=150>MAP</TD>
<TH>Description</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt; or MAP&lt;n&gt;/BYTE</I></TD>
<TD CLASS=TABCOLOR2>Up to 128 values can be specified, the value range is 0..255 (8bit)<BR>
Example:
<TT><PRE style="margin-left:50px; font-size:8pt">
MAP1/BYTE 1 2 4 8 32 64
</PRE></TT>
</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt;/HWORD</I></TD>
<TD CLASS=TABCOLOR2>Up to 64 values can be specified, the value range is 0..16383 (16bit)<BR>
Example:
<TT><PRE style="margin-left:50px; font-size:8pt">
MAP1/HWORD 1 2 4 8 32 64 128 256 512 1024 4096 8192
</PRE></TT>
</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt;/BYTEI</I></TD>
<TD CLASS=TABCOLOR2>Applies linear interpolation between data points. This allows to quickly define curves without the need to enter the values for the complete range. E.g. with MAP/BYTE it is required to enter 128 values to create a curve for a CC controller, with MAP/BYTEI it's mostly sufficient to define the same with 3..4 data points. MBNG will interpolate the values between these points. Up to 64 datapoints can be specified, the value range is 0..255 (8bit).<BR>
Example:
<TT><PRE style="margin-left:50px; font-size:8pt">
# using an interpolation map to define the velocity curve
MAP1/BYTEI 0:0 64:30 96:80 127:127
</PRE></TT>
</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt;/HWORDI</I></TD>
<TD CLASS=TABCOLOR2>Applies linear interpolation between data points. Up to 32 datapoints can be specified, the value range is 0..65535 (16bit).<BR>
Example:
<TT><PRE style="margin-left:50px; font-size:8pt">
# pot is working at 12bit resolution (0..4095)
# 0..2048 should send CC value 127..0 downwards,
# and 2049..4095 (the second half) should send 0..127 upwards.
MAP1/HWORDI 0:127 2048:0 4095:127
</PRE></TT>
</TD>
</TR>
</TABLE>
 
 
<P CLASS=DESC>The various control elements use maps the following way:
<UL CLASS=CL>
<LI><I>EVENT_ENC</I>: send a mapped value with <I>enc_mode=Absolute</I> - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapenc.ngc" TARGET="_blank">configuration example</A>
1063,9 → 1115,7
<LI><I>EVENT_SENDER</I> and <I>EVENT_RECEIVER</I>: the sent/received value will be mapped - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapmidi.ngc" TARGET="_blank">configuration example</A>
</UL>
 
<P CLASS=DESC>Other EVENTs don't support mapped ranges yet. It could make sense for EVENT_CV to map output voltages (problem: maps only work at 8bit resolution), or for EVENT_BUTTON_MATRIX to map a Note key - this could be provided in future versions.</P>
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> SYSEX_VAR </H2>
 
<P CLASS=DESC>This command specifies the default values of various SysEx variables, which are available for <I>EVENT_* stream="..."</I>:
1392,7 → 1442,7
With (for example) <I>SRIO sr_num=8</I> only up to 8 DIN and 8 DOUT SRs will be scanned anymore, but the update rate is reduced to ca. 110..120 uS (a little bit more than a quarter due to SR handling overhead).</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>debounce_cycles=&lt;0..255&gt;</I></TD>
<TD CLASS=TABCOLOR2 WIDTH=150><I>debounce_cycles=&lt;0..65535&gt;</I></TD>
<TD CLASS=TABCOLOR2>This command allows to enable a debouncing mechanism for digital inputs (buttons). The number specifies the dead time in SRIO cycles at which button events will be rejected.<BR>
The time of a SRIO cycle depends on the num_sr configuration, typically it's around 420 uS for 32 SRs, which means that with debounce_cycles=20 the debouncing dead time is 8.4 mS.</TD>
</TR>
/trunk/ucapps/midibox_seq_manual_up.html.gen
16,9 → 16,9
<LI>new ribbon cables for the LCDs + two new 16 pin Female IDC Connectors</LI>
<LI>new ribbon cable for the DIN/DOUT modules + 10 pin Female IDC Connectors</LI>
<LI>ribbon cable for the DIN/DOUT modules + 10 pin Female IDC Connectors</LI>
<LI>a Micro SD card with adapter socket + ribbon cable + a 10 pin Female IDC Connector (see also <A HREF="mbhp_sdcard.html">see also this page</A><BR>
Recommented speed factor: at least 60x - than higher than better!.<BR>
Recommented size: 256MB..4GB</LI>
<LI>A SD card (see also <A HREF="mbhp_sdcard.html">see also this page</A><BR>
Recommended speed factor: at least 60x - than higher than better!.<BR>
Recommended size: 256MB..4GB</LI>
</UL>
 
<P CLASS=DESC>The upgrade will cost you ca. US $50..$60 (+ shipping)</P>
52,10 → 52,6
<TD><IMG SRC="midibox_seq/mbseqv3_v4_upgrade3.jpg" WIDTH=280 HEIGHT=116 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>DIN/DOUT modules and the LCD should be connected to the MBHP_CORE_STM32F4 module now. Power-on the core to check if they are working (download the firmware if this hasn't been done yet!)</TD>
</TR>
<TR>
<TD><IMG SRC="mbhp/mbhp_sdcard_lowcost_12.jpg" WIDTH=280 HEIGHT=187 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>The final step: connect a SD Card to J16 of the core module. The picture shows a least-cost SD card adapter as explained on the <A HREF="mbhp_sdcard.html">MBHP_SDCARD page</A>.</TD>
</TR>
</TABLE>
 
<P CLASS=DESC>Feel free to send me pictures of your upgraded MIDIbox, which will be published here!</P>
/trunk/ucapps/midibox_seq_manual_tut6.html.gen
35,7 → 35,7
<LI>if C-3, D#3 and G-3 are pressed, the sequencer plays C-2, D#2, G-2, C-3, D#3 and G-3
</UL>
Audio Example:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut6_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut6_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
49,7 → 49,7
<LI>Step #4: plays the second note of the chord, not transposed (+0)
</UL>
Audio Example (sounds a bit like music from Jean Michel Jarre...):<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut6_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut6_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
58,7 → 58,7
Thereafter enter following pattern:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut6_3a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Select a bellish sound on your synth with some delay and reverb. Play some chords:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut6_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut6_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
As you can hear in the audio example, the arpeggio is really "organic"! Depending on the number of notes which are played, and the order of changes, the resulting sequence is sometimes inpredictable, but still "rhythmic" and "melodic". Remind that 14 additional tracks are still unused here! ;-)
</SPAN></TD></TR>
 
71,7 → 71,7
A second track should play a simple bassline. Change to G1T2, select length 4, change the MIDI channel back to 2 in the MENU-&gt;Event page. Enter following pattern in the EDIT page:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut6_4b.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Finally start the sequencer, and play only single notes on your MIDI keyboard. The result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut6_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut6_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
(drums are based on sample loops)<BR>
Sidenote: in the second half of the MP3 you will hear the difference of a 100% gate length compared to ca. 50% gate length at the beginning.
</SPAN></TD></TR>
81,7 → 81,7
Change the track length of G1T1 to 4 steps, and then enter following pattern in the EDIT page:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut6_5a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Play some chords and have fun! :-)<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut6_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut6_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
</TABLE>
/trunk/ucapps/midibox_ng_manual_lcd.html.gen
66,11 → 66,11
 
<P CLASS=DESC>After this application has been uploaded, enter following commands to configure 6 2x20 LCDs:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type CLCD
lcd_num_x 6
lcd_num_y 1
lcd_width 20
lcd_height 2
set lcd_type CLCD
set lcd_num_x 6
set lcd_num_y 1
set lcd_width 20
set lcd_height 2
store
</PRE></TT>
 
92,11 → 92,11
 
With following configuration:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type CLCD
lcd_num_x 3
lcd_num_y 2
lcd_width 20
lcd_height 2
set lcd_type CLCD
set lcd_num_x 3
set lcd_num_y 2
set lcd_width 20
set lcd_height 2
store
</PRE></TT>
 
176,21 → 176,21
 
<P CLASS=DESC>Following configuration is required in the <A HREF="mios32_bootstrap_newbies.html">Bootloader Update Application</A> for a 128x64 GLCD (2 CS lines):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_KS0108
lcd_num_x 1
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_KS0108
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>If the CS lines of your GLCD are inverted (=low-active), then enter following configuration:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_KS0108_INVCS
lcd_num_x 1
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_KS0108_INVCS
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
197,11 → 197,11
 
<P CLASS=DESC>For a 240x64 GLCD (with 4 CS lines) like used for the original <A HREF="midibox_lc/midibox_lc_1.jpg">MIDIbox LC</A> enter:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_KS0108
lcd_num_x 1
lcd_num_y 1
lcd_width 240
lcd_height 64
set lcd_type GLCD_KS0108
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 240
set lcd_height 64
store
</PRE></TT>
 
224,21 → 224,21
 
<P CLASS=DESC>Following configuration is required in the <A HREF="mios32_bootstrap_newbies.html">Bootloader Update Application</A> for a 122x32 GLCD (2 CS lines):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SED1520
lcd_num_x 1
lcd_num_y 1
lcd_width 122
lcd_height 32
set lcd_type GLCD_SED1520
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 122
set lcd_height 32
store
</PRE></TT>
 
<P CLASS=DESC>It's possible to combine two SED1520 LCDs by connecting all signals (beside of CS) in parallel to J15A. The two CS lines of the second display have to be connected to the CS3 and CS4 output at J28. Configuration:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SED1520
lcd_num_x 1
lcd_num_y 1
lcd_width 244
lcd_height 32
set lcd_type GLCD_SED1520
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 244
set lcd_height 32
store
</PRE></TT>
 
249,11 → 249,11
</UL>
Configuration:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SED1520
lcd_num_x 2
lcd_num_y 1
lcd_width 244
lcd_height 32
set lcd_type GLCD_SED1520
set lcd_num_x 2
set lcd_num_y 1
set lcd_width 244
set lcd_height 32
store
</PRE></TT>
 
269,11 → 269,11
 
<P CLASS=DESC>Following configuration is required in the <A HREF="mios32_bootstrap_newbies.html">Bootloader Update Application</A> for a single DOGM GLCD:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_DOG
lcd_num_x 1
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_DOG
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
280,41 → 280,41
 
<P CLASS=DESC>Following configuration for 8 DOGM GLCDs:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_DOG
lcd_num_x 8
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_DOG
set lcd_num_x 8
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 12 DOGM GLCDs (remaining CS pins connected to J28):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_DOG
lcd_num_x 12
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_DOG
set lcd_num_x 12
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 16 DOGM GLCDs (remaining CS pins connected to a 74HC595 based shift register at J28):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_DOG
lcd_num_x 16
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_DOG
set lcd_num_x 16
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 64 DOGM GLCDs (remaining CS pins connected to seven chained 74HC595 based shift register at J28):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_DOG
lcd_num_x 64
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_DOG
set lcd_num_x 64
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
332,51 → 332,51
 
<P CLASS=DESC>Following configuration is required in the <A HREF="mios32_bootstrap_newbies.html">Bootloader Update Application</A> for a single SSD1306 GLCD:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SSD1306
lcd_num_x 1
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_SSD1306
set lcd_num_x 1
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 8 SSD1306 GLCDs:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SSD1306
lcd_num_x 8
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_SSD1306
set lcd_num_x 8
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 12 SSD1306 GLCDs (remaining CS pins connected to J28):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SSD1306
lcd_num_x 12
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_SSD1306
set lcd_num_x 12
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 16 SSD1306 GLCDs (remaining CS pins connected to a 74HC595 based shift register at J28):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SSD1306
lcd_num_x 16
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_SSD1306
set lcd_num_x 16
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
<P CLASS=DESC>Following configuration for 64 SSD1306 GLCDs (remaining CS pins connected to seven chained 74HC595 based shift register at J28):
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SSD1306
lcd_num_x 64
lcd_num_y 1
lcd_width 128
lcd_height 64
set lcd_type GLCD_SSD1306
set lcd_num_x 64
set lcd_num_y 1
set lcd_width 128
set lcd_height 64
store
</PRE></TT>
 
383,7 → 383,7
 
<P CLASS=DESC>Alternatively the SSD1306 screen can be rotated by 180 degrees, which might be useful in some cases (e.g. if it has been mounted the wrong way). In this case, please enter following lcd_type into the bootloader:
<TT><PRE style="margin-left:50px; font-size:8pt">
lcd_type GLCD_SSD1306_ROTATED
set lcd_type GLCD_SSD1306_ROTATED
store
</PRE></TT>
resp. "lcd_type 0x85" if you are using Bootloader V1.010 (V1.011 hasn't been released yet...)
/trunk/ucapps/mbhp_sdcard.html.gen
109,6 → 109,13
</DL>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Alternative Adapter for <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module </H2></DT>
<DD><P CLASS=CL>See this <A HREF="http://midibox.org/forums/topic/19761-sd-card-reader-3m-alternative/#comment-172182" TARGET="_blank">forum posting</A>. Many thanks to Tashikoma for the great idea!</P>
<CENTER><IMG SRC="mbhp/mbhp_sdcard_lowcost_pcbmount.jpg" WIDTH=550 BORDER=0 ALT=""></CENTER>
</DD>
</DL>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> IMPORTANT for MBHP_CORE_STM32</H2></DT>
<DD><P CLASS=CL>The resistor array R30 of the <A HREF="mbhp_core_stm32.html">MBHP_CORE_STM32</A> module shouldn't be connected when a SD Card is used, because pads are configured in Push-Pull mode at 3.3V.<BR>
SD Card transfers could work unstable with these Pull-Up resistors!</P>
/trunk/ucapps/mbhp_core_stm32f4.html.gen
6,10 → 6,10
 
<P CLASS=INFO>MBHP_CORE_STM32F4 is the successor of the <A HREF="mbhp_core_stm32.html">MBHP_CORE_STM32</A> module, and an alternative solution to the <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> module.</P>
 
<P CLASS=DESC>Main features of the <A HREF="http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419" TARGET="_blank">STM32F4DISCOVERY</A> based MBHP_CORE_STM32F4 module:
<P CLASS=DESC>Main features of the <A HREF="http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419" TARGET="_blank">STM32F407G-DISC1</A> based MBHP_CORE_STM32F4 module:
<UL CLASS=CL>
<LI> 1MB Flash and 192k RAM (significantly more than previous core modules)
<LI> The STM32F4DISCOVERY evaluation board is available for 15 EUR at <A HREF="http://mouser.com/Search/Refine.aspx?Keyword=STM32F4DISCOVERY" TARGET="_blank">Mouser</A>, 17 EUR at <A HREF="http://www.watterott.com/de/STM32F4Discovery" TARGET="_blank">Watterott</A> (Germany), 11 GBP at <A HREF="http://uk.farnell.com/jsp/search/browse.jsp?N=2031+203908&Ntk=gensearch&Ntt=stm32f4discovery&Ntx=mode+matchallpartial" TARGET="_blank">Farnell</A> (GB) - an meanwhile even at <A HREF="http://www.amazon.de/STM32F4-DISCOVERY-STM32F407VGT6-Cortex-M4-Development/dp/B00GGCNBAC/ref=sr_1_1?s=ce-de&ie=UTF8&qid=1442176910&sr=1-1&keywords=stm32f4+discovery" TARGET="_blank">Amazon</A>!<BR>
<LI> The STM32F407G-DISC1 evaluation board is available for 15 EUR at <A HREF="http://mouser.com/Search/Refine.aspx?Keyword=STM32F407G-DISC" TARGET="_blank">Mouser</A>, 17 EUR at <A HREF="http://www.watterott.com/de/STM32F4Discovery" TARGET="_blank">Watterott</A> (Germany), 11 GBP at <A HREF="http://uk.farnell.com/stmicroelectronics/stm32f407g-disc1/dev-brd-stm32f407vg-foundation/dp/2506840?ost=stm32f407g-disc&selectedCategoryId=&categoryName=All+Categories&categoryNameResp=All%2BCategories" TARGET="_blank">Farnell</A> (GB) - an meanwhile even at <A HREF="https://www.amazon.de/s/ref=nb_sb_noss_1?__mk_de_DE=ÅMÅŽÕÑ&url=search-alias%3Daps&field-keywords=stm32f407g-disc1" TARGET="_blank">Amazon</A>!<BR>
It will be attached on the MBHP_CORE_STM32F4 PCB, but can also be used standalone for mini applications which only require USB MIDI and a small number of IOs or the Audio DAC.
<LI> Easily available for private persons in small quantities and no SMD soldering skills required
<LI> ARM Cortex-M4 CPU is widely supported by the GNU toolchain, accordingly source code can be compiled under Windows/Linux/MacOS w/o spending money for an expensive ARM compiler
24,13 → 24,13
<LI> STM32F4xx is supplied at 3V, but 5V tolerant inputs allow to access all existing MBHP modules without additional hardware.
<LI> Performance boost by using the DMA for background operations, such as scanning DIN/DOUT modules, analog inputs but also I2S transfers (Audio Output) w/o loading the CPU
<LI> Supported by a free available Realtime Operating System: <A HREF="http://www.freertos.org" TARGET="_blank">FreeRTOS</A>
<LI> no external flash programmer required, ST-LINK/V2 is part of the STM32F4DISCOVERY board to program the MIOS32 bootloader into a "virgin" device
<LI> no external flash programmer required, ST-LINK/V2 is part of the STM32F407G-DISC1 board to program the MIOS32 bootloader into a "virgin" device
<LI> Fast upload of application code via USB MIDI (ca. 50kb/s) - thanks to the <A HREF="mios32_bootstrap_newbies.html">MIOS32 Bootloader</A>
</UL>
 
<P CLASS=DESC>Ok, enough praises for this nice toy. Here a list of issues/imperfections that I don't really like:
<UL CLASS=CL>
<LI> ADCs cannot be supplied at 5V, 3.3V is the limit, and the STM32F4DISCOVERY board uses an even lower voltage (3V). This decreases the signal/noise ratio. The <A HREF="mbhp_ainser64.html">MBHP_AINSER64</A> and <A HREF="mbhp_ainser8.html">MBHP_AINSER8</A> module helps to overcome this by using an external 5V ADC.
<LI> ADCs cannot be supplied at 5V, 3.3V is the limit, and the STM32F407G-DISC1 board uses an even lower voltage (3V). This decreases the signal/noise ratio. The <A HREF="mbhp_ainser64.html">MBHP_AINSER64</A> and <A HREF="mbhp_ainser8.html">MBHP_AINSER8</A> module helps to overcome this by using an external 5V ADC.
<LI> Pin mapping suboptimal in some cases. E.g., the outputs of the integrated DAC (not the on-board Audio-DAC) overlay SPI1 pins. However, one DAC channel has been freed up with the small drawback that SPI1 can't be used in slave mode.<BR>
The IO pins of the SDIO peripheral (high speed SD Card access) conflicts with the on-board Audio DAC, so that it can't be used.<BR>
Although the chip contains 6 UARTs, only 4 RX and TX pins could be found for MIDI IN/OUT. IN3/OUT3 even have to use two different UARTs.
47,7 → 47,7
<DD><TABLE CELLSPACING=2 CELLPADDING=2 WIDTH=640>
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_prog.jpg" WIDTH=280 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>The STM32F4DISCOVERY board is equipped with an on-board debugger (right side) which is called ST-LINK/V2. It has to be connected via a Mini-USB cable to your PC, and allows to program the flash of the target device (the STM32F407VE chip).<BR>
<TD CLASS=TABCOLOR2>The STM32F407G-DISC1 board is equipped with an on-board debugger (right side) which is called ST-LINK/V2. It has to be connected via a Mini-USB cable to your PC, and allows to program the flash of the target device (the STM32F407VE chip).<BR>
We use ST-LINK to install the MIOS32 Bootloader, so that a MIOS32 application can be flashed via USB-MIDI later with the Micro-USB connector at the left side. This approach will allow you to update an application on-the-fly without the need for a second USB port on your MIDIbox, it's even faster than via ST-LINK, and it will work under MacOS and Linux as well by using <A HREF="mios_studio.html">MIOS Studio</A> instead of the Windows propritary ST-LINK utility.! :-)
</TD>
</TR>
62,7 → 62,7
 
<TR>
<TD><A HREF="mbhp/mbhp_core_stm32f4_prog_win1.png"><IMG SRC="mbhp/mbhp_core_stm32f4_prog_win1.png" WIDTH=280 BORDER=0 ALT=""></A></TD>
<TD CLASS=TABCOLOR2>After the STM32F4DISCOVERY board has been connected to your PC, the driver has been installed, and the ST-LINK utility has been opened, try to connect to the ST-LINK by pushing the appr. button.
<TD CLASS=TABCOLOR2>After the STM32F407G-DISC1 board has been connected to your PC, the driver has been installed, and the ST-LINK utility has been opened, try to connect to the ST-LINK by pushing the appr. button.
</TD>
</TR>
<TR>
72,7 → 72,7
</TR>
<TR>
<TD><A HREF="mbhp/mbhp_core_stm32f4_prog_win3.png"><IMG SRC="mbhp/mbhp_core_stm32f4_prog_win3.png" WIDTH=280 BORDER=0 ALT=""></A></TD>
<TD CLASS=TABCOLOR2>Click on the small "Program and Verify" icon. Click on the "Browse" button and search for the project.hex binary of the STM32F4DISCOVERY directory which comes with the <A HREF="mios32_download.html">MIOS32 Bootloader</A> application.
<TD CLASS=TABCOLOR2>Click on the small "Program and Verify" icon. Click on the "Browse" button and search for the project.hex binary of the STM32F407G-DISC1 directory which comes with the <A HREF="mios32_download.html">MIOS32 Bootloader</A> application.
</TD>
</TR>
<TR>
83,7 → 83,7
 
<TR>
<TD><A HREF="mbhp/mbhp_core_stm32f4_prog_led.jpg"><IMG SRC="mbhp/mbhp_core_stm32f4_prog_led.jpg" WIDTH=280 BORDER=0 ALT=""></A></TD>
<TD CLASS=TABCOLOR2>Finally press the (black) Reset button on the STM32F4DISCOVERY board. The green status LED should flash two times (effect via PWM modulation) - the MIOS32 bootloader is up and running!
<TD CLASS=TABCOLOR2>Finally press the (black) Reset button on the STM32F407G-DISC1 board. The green status LED should flash two times (effect via PWM modulation) - the MIOS32 bootloader is up and running!
</TD>
</TR>
 
106,7 → 106,15
</DL>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Using the STM32F4DISCOVERY Board standalone </H2></DT>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Required Firmware Update for newer board version </H2></DT>
<P CLASS=INFO>Newer board versions marked with <B>MB997D</B> require a firmware update for STM Link, so that the microcontroller can boot with Micro USB power supply instead of the ST-Link connector. This update can be done with the ST Link Utility:</P>
<P><CENTER><A HREF=""><IMG SRC="mbhp/st_link_firmware_update.png" width=347 height=112></A></CENTER></P>
</DD>
</DL>
 
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Using the STM32F407G-DISC1 Board standalone </H2></DT>
<P CLASS=INFO>You've probably already noticed, that the board is powered via the ST-LINK connector CN1, and not via the USB connector CN5 which is used for USB-MIDI. This can be changed by bridging the PA9 pin to the 5V input with a short cable:<BR>
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_standalone.jpg" width=550 height=382></CENTER></P>
 
113,7 → 121,7
<P CLASS=INFO>In addition, it makes sense to mount dual row pin headers at the bottom of the PCB for P1 and P2:<BR>
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_headers.jpg" width=550 height=327></CENTER></P>
 
<P CLASS=INFO>Two 2x25 SIL headers are required (e.g. Reichelt order number: <A HREF="http://www.reichelt.de/index.html?ACTION=3;ARTICLE=19494;SEARCH=SL%202X25G%202,54" TARGET="_blank">SL 2X25G 2,54</A>). The usage of such headers has the advantage, that later you can plug the STM32F4DISCOVERY board on the MBHP_CORE_STM32F4 module into the corresponding female sockets - and that you can remove it, e.g. to plug it into another MBHP_CORE_STM32F4 module.
<P CLASS=INFO>Two 2x25 SIL headers are required (e.g. Reichelt order number: <A HREF="http://www.reichelt.de/index.html?ACTION=3;ARTICLE=19494;SEARCH=SL%202X25G%202,54" TARGET="_blank">SL 2X25G 2,54</A>). The usage of such headers has the advantage, that later you can plug the STM32F407G-DISC1 board on the MBHP_CORE_STM32F4 module into the corresponding female sockets - and that you can remove it, e.g. to plug it into another MBHP_CORE_STM32F4 module.
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_fheaders.jpg" width=550 height=338></CENTER></P>
 
</DD>
214,7 → 222,8
<TR>
<TD CLASS=TABCOLOR2>J11E</TD>
<TD CLASS=TABCOLOR2>10</TD>
<TD CLASS=TABCOLOR2>This port provides four MIDI IOs at 3V level, interface to the <A HREF="mbhp_midi_io.html">MBHP_MIDI_IO</A> breakout board.</TD>
<TD CLASS=TABCOLOR2>This port provides four MIDI IOs at ca. 5V level (the pin is configured in open-drain mode, so that a resistor connected between the MOx pins and 5V can pull the output level to 3V or 5V. Normally this pull-up resistor is not required if an opto coupler is used at the receiver side)<BR>
Interface to the <A HREF="mbhp_midi_io.html">MBHP_MIDI_IO</A> breakout board.</TD>
</TR>
 
<TR>
310,7 → 319,7
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_4.jpg" WIDTH=280 HEIGHT=211 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>And then the remaining headers:
<UL CLASS=CL>
<LI>2 2x25 female SIL headers for the STM32F4DISCOVERY module
<LI>2 2x25 female SIL headers for the STM32F407G-DISC1 module
<LI>3 1x2 male SIL header
<LI>1 1x3 male SIL header
<LI>2 jumpers stuffed on J17 (USB PWR) and J15_S to select the LCD voltage (5V or 3.3V)
321,11 → 330,11
 
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_5.jpg" WIDTH=280 HEIGHT=196 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>And finally put the ICs, and then the STM32F4DISCOVERY module into the sockets:
<TD CLASS=TABCOLOR2>And finally put the ICs, and then the STM32F407G-DISC1 module into the sockets:
<UL CLASS=CL>
<LI>IC1: 74HCT541
<LI>IC2: 74HC595
<LI>STM32F4DISCOVERY
<LI>STM32F407G-DISC1
</UL>
</TD>
</TR>
353,6 → 362,18
</DL>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Special Guide: Connecting a 2x40 (or 2x20) LCD</H2></DT>
<DD>
<P CLASS=INFO>The pinning of the 2x8 LCD connectors J15A and J15B is mirrored to simplify the cabling of common 2x20 and 2x40 displays (and partly due to historical reasons - it's originated from the so called "UltraPCB").<BR>
J15 Pin 1 (labeled with Vs) goes to Pin 1 of the LCD (normaly named "Vss").<BR>
Following picture illustrates the orientation of the IDC connectors:
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_lcd_connection.jpg" width=550 height=412></CENTER></P>
<P CLASS=DESC>See also <A HREF="mbhp/mbhp_lcd_2x20_mios32.pdf">this schematic</A>.
<P CLASS=DESC>You should be able to change the contrast of the LCD with the contrast pot. If the lumination pot changes the contrast instead, the orientation of the IDC connectors is not correct (rotated by 180 degrees).
</DD>
</DL>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Credits </H2></DT>
<DD><P CLASS=DESC>Thanks to Tim aka. SmashTV for creating the PCB layout. PCBs and kits are available in his <A HREF="http://www.midibox-shop.com" TARGET="_blank">MIDIbox Shop</A>.<P>
</DD>
/trunk/ucapps/midibox_seq_manual_blm.html.gen
5,13 → 5,14
<H1>MIDIbox SEQ V4</H1>
<H1>User Manual --- 16x16+X Button/LED Matrix</H1>
 
<center>
<object width="400" height="300"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=11768389&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=11768389&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="300"></embed></object>
</center>
<center><iframe width="560" height="315" src="https://www.youtube.com/embed/tSkaGWImzII" frameborder="0" allowfullscreen></iframe></center>
 
<center><iframe width="560" height="315" src="https://www.youtube.com/embed/i-ClNqM_2eE" frameborder="0" allowfullscreen></iframe></center>
 
<H2>General informations and discussions about this project</H2>
 
<P CLASS=INFO><A HREF="http://midibox.org/forums/index.php?/forum/43-midibox-blm/" TARGET="_blank">Link to special "MIDIbox BLM" forum section</A></P>
<P CLASS=INFO><A HREF="http://wiki.midibox.org/doku.php?id=mididocs:seq:blm16x16_x" TARGET="_blank">Link to special Wiki Page, maintained by the user community</A></P>
 
<H2>Supported features by MIDIbox SEQ V4</H2>
 
96,6 → 97,7
<LI><A HREF="midibox_blm/blm_connector_mbseq.pdf" TARGET="_blank">schematic for BLM connector (MBSEQ Side)</A>
<LI><A HREF="midibox_blm/blm_connector_core.pdf" TARGET="_blank">schematic for BLM connector (MBHP_CORE Side)</A>
<LI><A HREF="midibox_blm/blm_connector_minicore.pdf" TARGET="_blank">schematic for BLM connector (Latigid On's MINICORE Side)</A>
<LI><A HREF="http://midibox.org/forums/gallery/album/51-tk-blm16x16-x/" TARGET="_blank">Pictures of the prototype</A>
</UL>
 
<P CLASS=DESC>No special configuration has to be done in the MBSEQ_HW.V4 file. Please don't be confused about BLM_* and BLM8x8_* parameters. BLM_* parameters configure the (expired) 4x16 BLM which was provided by MBSEQ V3 but isn't so powerful as BLM16x16+X. BLM8x8_* parameters configure a special matrix for Wilba's Frontpanel to save some shift registers.</P>
/trunk/ucapps/midibox_seq_manual_tut.html.gen
17,7 → 17,21
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/TEdI6lOf0wc" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/eAz_MgX5cWg" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/xD7S5pNdoMU" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/M70q4cqMXsI" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/IjY_TUKvM4I" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/4U_l4cTz_8U" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/3I5ivgdDPlo" frameborder="0" allowfullscreen></iframe></P>
 
<P CLASS=INFO><iframe width="560" height="315" src="https://www.youtube.com/embed/rHESaRhfULs" frameborder="0" allowfullscreen></iframe></P>
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Step-by-Step Tutorials </H2>
 
<P CLASS=INFO>Provided by TK:</P>
/trunk/ucapps/midibox_seq_manual.html.gen
11,12 → 11,12
<LI><A HREF="midibox_seq_manual_hw.html">Hardware Options</A></LI>
<LI><A HREF="midibox_seq_manual_fp.html">Frontpanel</A></LI>
<LI><A HREF="midibox_seq_manual_in.html">Installation</A></LI>
<LI><A HREF="midibox_seq_manual_tut.html">Tutorials</A></LI>
<LI><A HREF="midibox_seq_manual_m.html">Menu Pages</A> (the huge one with many additonal sound samples)</LI>
<LI><A HREF="midibox_seq_manual_sessions.html">Sessions</A></LI>
<LI><A HREF="midibox_seq_manual_blm.html">BLM16x16+X Extension</A></LI>
<LI><A HREF="midibox_seq_manual_up.html">V3-&gt;V4 Upgrade</A></LI>
<LI><A HREF="midibox_seq_manual_ki.html">Known Issues and Troubleshooting Tips</A></LI>
<LI><A HREF="midibox_seq_manual_tut.html">Tutorials</A></LI>
<LI><A HREF="midibox_seq_changelog.html">Changelog</A></LI>
</UL>
</P>
24,7 → 24,9
<H2> <IMG SRC="images/bullet.gif" ALT=""> User Documentation </H2>
<P CLASS=INFO>
<UL CLASS=CL>
<LI><A HREF="http://www.midibox.org/dokuwiki/doku.php?id=mididocs:index">Wiki page maintained by the MIDIbox community</A></LI>
<LI><A HREF="http://wiki.midibox.org/doku.php?id=mididocs:seq:beginners_guide:start" TARGET="_blank">The MIDIbox SEQ V4 Beginner's Guide</A><BR>
A *must read* for all beginners (print it out!)</LI>
<LI><A HREF="http://www.midibox.org/dokuwiki/doku.php?id=mididocs:midibox_seq_v4" TARGET=_blank">Additional wiki pages</A> maintained by the MIDIbox community</LI>
</UL>
</P>
 
/trunk/ucapps/midibox_seq_changelog.html.gen
1,7 → 1,7
HEADER 3 ChangeLog of MIDIbox SEQ
 
<CENTER><H1>MIDIbox SEQ V4 Change Log</H1></CENTER>
<CENTER><H3>Last Release: 2015-12-22</H3></CENTER>
<CENTER><H3>Last Release: 2017-11-05</H3></CENTER>
 
<P CLASS=DESC>Current firmware, schematics, additional infos are located at <A HREF="midibox_seq.html">http://www.uCApps.de/midibox_seq.html</A>.</P>
 
10,6 → 10,177
<UL CLASS=CL>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.094</I>
<UL CLASS=CL>
<LI> support for Antilog Frontpanel.<BR>
The appr. HW configuration file can be found under hwcfg/antilog/MBSEQ_HW.V4
 
<LI> enhanced COPY/PASTE/CLEAR functions for following pages:
<UL CLASS=CL>
<LI> PATTERN page: copy/paste/clears all patterns.<BR>
Special function: by pressing COPY+PASTE the patterns will be pasted into the next slots
<LI> PARSEL page: copy/paste/clears the currently selected parameter layer only
<LI> TRGSEL page: copy/paste/clears the currently selected trigger layer only
<LI> INSSEL page: copy/paste/clears the currently selected instrument only
(useful for drums: corresponding trigger any parameter layers are cleared)
</UL>
<LI> improved ALL button behaviour
 
<LI> New worflow for PATTERN page: GP 1/2, 5/6, 9/10, 13/14 allow to select group as well<BR>
(especially interesting for Antilog Frontpanel: Selection buttons can be used for mutes)
 
<LI> New worflow for MUTE page: whenever a track or parameter layer is unmuted, it will be automatically selected
 
<LI> EDIT page: improved handling for chord layers
 
<LI> moved some configuration settings which were previously part of the
MBSEQ_HW.V4 file to the Options page, so that they can be changed without
a file editor:
<UL CLASS=CL>
<LI> MIDI remote key (or CC)
<LI> Track Selection CC
<LI> MIDI OUT Runtime Status Optimisation
<LI> MENU button assignments
</UL>
 
<LI> support for "Shadow Out", which will forward the MIDI events of the currently selected
track to a specified MIDI port and channel (e.g. can be used to visualize played notes
with an external device). Select the port/channel in the OPTIONS page.
 
<LI> Metronome page removed. Please configure the metronome function in the Options page.
 
<LI> Pattern banks can't be modified by default anymore, because they are typically
assigned to group 1/2/3/4, changed bank assignments can confused users
to much. If somebody still finds this feature useful: it can be enabled in the
Options page
 
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.093</I>
<UL CLASS=CL>
<LI> new parameter type "Chord3" provides an alternative set of 108 chords.<BR>
Thanks to EsotericLabs for providing the chord table!
 
<LI> notes in edit screen are displayed transposed now
 
<LI> drum tracks: random probability layer now working as intended
 
<LI> layers are now initialized for 6 notes polyphony by default (8 layers, 128 steps)
 
<LI> optionally pattern changes don't re-send the PC/bank settings.<BR>
This option can be configured in the UTILITY->Options menu (item #4/18)
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.092</I>
<UL CLASS=CL>
<LI>new parameter layers for track specific root note and scale<BR>
Root selection strategy: if Root is assigned to any parameter
layer of a track, the layer can either select the global root
selection ("Glb") or set the root note for each step explicitely.<BR>
The global root selection is configured in the FX->Scale page,
it's either "Keyb" (for MIDI keyboard entry) or C, C#, ... B<BR>
The local root selection is C, C#, ... B<BR>
Notes and Chords will be transposed accordingly if the track is in
Normal mode (and not in Transpose or Arpeggiator mode)<BR>
Similar for Scale: it can override the globally configured scale
of the FX->Scale page for each step.
<LI> new drum configurations: 4*16/2*64, 4*16/2*128, 4*16/1*256
 
<LI> new configuration option in Track Mode page: "Note Last/First"<BR>
Allows to specify, if the transposer should take the last or first
played note (previously it always played the last note)
 
<LI> new configuration option in Track Mode page: "STrg" (Step Trigger).<BR>
If activated, the step progression will be controlled from the transposer
bus, hence it can either be triggered from a loopback track or from an
external MIDI device (MIDI keyboard, sequencer, etc.)<BR>
Note that each track can be assigned to a dedicated transpose bus
(4 busses are available), this allows to control 4 independent step progressions
for all 16 tracks.
 
<LI> individual steps of CC, PitchBender, Program Change and Aftertouch
layers can now be disabled so that they won't play.<BR>
Turn the encoder to the rightmost position (value 128)<BR>
Also the init value has been changed: for these layers, the steps
are now disabled by default.<BR>
For CCs please change the init value by yourself in the UTIL->OPT
page (option #12: Initial CC value)
 
<LI> new behaviour of CLEAR button in recording mode:<BR>
it clears only the selected step (instead of the entire pattern).
During live recording it will clear the "played" steps while the
button is pressed.
 
<LI> new CC functions which can be configured in MIDI->ExtCtrl. page:
<UL CLASS=CL>
<LI>Play/Stop: allows to assign the PLAY button to a CC
<LI>Record: allows to assign the RECORD button to a CC
</UL>
 
<LI> new option in Groove page: Sync<BR>
Allows to sync the groove to the global reference step (RefS)
or to the local track step
 
<LI> fixed G# transpose
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.091</I>
<UL CLASS=CL>
<LI> new parameter type "Chord2" provides an alternative set of 32 chords
 
<LI> new parameter type "Aftertouch" allows to send and record channel pressure events
 
<LI> CPU load display has been re-adjusted for LPC17 and STM32F4
 
<LI> hwcfg/wilba*/MBSEQ_HW.V4: default F1-F4 assignments changed to:<BR>
F1: Track Select, F2: Live Forwarding, F3: Recording, F4: Save All
 
<LI> MBSEQ_HW.V4: added new button/LED functions: FX, MOVE, SCROLL
 
<LI> MBSEQ_HW.V4: added new LED_MEASURE function which will activate a LED
when the first step of the measure is played.
 
<LI> CC Parameter layer label now prints "#<number>" instead of "CC"
 
<LI> Jam page: AStart now starts to record into first step in
live recording mode (as intended), it starts on the selected step
in step recording mode
 
<LI> Purpose of Record and Live Button & LED change:<BR>
they switch between record (and live) mode w/o changing to the Jam page
 
<LI> new button/LED combo: JAM_LIVE and JAM_STEP: they switch to the JAM
page and select Live resp. Step recording mode
 
<LI> BLM16x16+X keyboard can now record into any track
 
<LI> Transpose page now allows selection based on Scale
 
<LI> New option page item #10 "Initial Gate Trigger Layer"
(empty or trigger on each 4th step)
 
<LI> Event configuration page: new drum track configuration 2*64/2*128
 
<LI> AOUT: added suskey function (AKA fingered portamento: slew rate only
enabled if more than 2 keys are played)<BR>
This function can be enabled in the CV Configuration page
 
<LI> removed obsolete (non-working) pattern based scale control
 
<LI> fixed LED behaviour in Step View page (corrected display if page is deselected)
 
<LI> various minor bugfixes & improvements
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.090</I>
<UL CLASS=CL>
<LI> Fx-&gt;Scale page: the configured scale is now displayed at the right
/trunk/ucapps/midibox_seq_manual_tut2.html.gen
30,7 → 30,7
with following note lengths:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut2_1l.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
The track should be assigned to a bass sound. Here an audio example:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2><BR><SPAN CLASS=NORM>
48,7 → 48,7
<TR><TD COLSPAN=2>
Continue to work on the sequence, fill some steps:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut2_3.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
If you don't like the changes, you can revert them in the PATTERN page by loading the previouly saved pattern: ensure that group 1 is selected, then press GP9 to load A1 again.
<CENTER><IMG SRC="midibox_seq/cs4/tut2_3p.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
</SPAN></TD></TR>
65,7 → 65,7
<CENTER><IMG SRC="midibox_seq/cs4/tut2_4ch.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut2_4co.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
Here an audio example (I'm using the "Gruesome Kit" of <A HREF="http://www.spectrasonics.net/products/stylusrmx.php" TARGET="_blank">Stylus RMX</A>):<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
74,7 → 74,7
<CENTER><IMG SRC="midibox_seq/cs4/tut2_5.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
You are now able to define the probability under which a step will be played from 0..100% for each step of each instrument. Go back to the EDIT screen, press parameter layer B button and enter the probability values with the GP rotary encoders. It also make sense to enter additional drum triggers with lower velocity values (can be changed in parameter layer A) and a very low probability.<BR>
The resulting sequences randomly vary based on your constraints! :-)<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
91,7 → 91,7
And now a new trick to add more variance: enter the MENU-&gt;FX-&gtHumanizer page, and set the random intensity to 7. Then enable Notes:
<CENTER><IMG SRC="midibox_seq/cs4/tut2_6h.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
The result: the track will randomly pick up chords with each cycle:
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
Than higher the intensity value, than more different chords will be played.
</SPAN></TD></TR>
 
102,13 → 102,13
Enter the EDIT page again, press parameter layer C button which gives you a selection menu. Push GP4 button to get layer D. Thereafter entere following sequence:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut2_7e.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
The result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_6.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_6.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
<TR><TD COLSPAN=2>
Bass, Pad and Drums played together:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_7.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_7.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
115,7 → 115,7
Now we come to another nice trick which works in conjunction with a Sample Player like <A HREF="http://www.spectrasonics.net/products/stylusrmx.php" TARGET="_blank">Stylus RMX</A>. In distance to the previously used "kit" mode, where each drum instrument is seperately triggered by note events, in the so called "Multi" mode we play parts of a drumloop sample instead. The drumloop is chopped into multiple pieces (resp. slices), and each piece can be played with individual notes. If we play notes in an ascending order:<BR>
<center><img src="midibox_seq/cs4/tut2_pianoroll_d1.png" width="434" height=263></center><BR>
...we will get back the original sample:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_8.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_8.mp3"#ffffff**<BR><SPAN CLASS=NORM>
But if we play the notes in a different order, we will get very different - but interesting - results!
</SPAN></TD></TR>
 
128,12 → 128,12
<center><img src="midibox_seq/cs4/tut2_pianoroll_d2.png" width="486" height=200></center><BR>
So: we've still notes in ascending order, but they are interlaced with other "lines", and they are starting from different positions. The track has been configured for 64 steps, so that the sequence will be varied over 16 bars.<BR>
The audible result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_9.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_9.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
And here the final result with Bass, Pad, Drums played traditionally with a drum kit, but also with sample slices:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut2_10.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut2_10.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
</TABLE>
/trunk/ucapps/midibox_ng_changelog.html.gen
1,7 → 1,7
HEADER 3 ChangeLog of MIDIbox NG
 
<CENTER><H1>MIDIbox NG Change Log</H1></CENTER>
<CENTER><H3>Last Release: 2015-11-24</H3></CENTER>
<CENTER><H3>Last Release: 2016-02-08</H3></CENTER>
 
<P CLASS=DESC>Current firmware, schematics, additional infos are located at <A HREF="midibox_ng.html">http://www.uCApps.de/midibox_ng.html</A>.</P>
 
10,6 → 10,45
<UL CLASS=CL>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V1.035</I>
<UL CLASS=CL>
<LI> Support for secure keyboard handling if patch is switched: keep original
MIDI port, note, channel when playing Note Off
(this feature is not supported for LPC17 due to high memory consumption)
 
<LI> Fixed encoder incrementer in absolute mode
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V1.034</I>
<UL CLASS=CL>
<LI> Support for interpolation tables:<BR>
MAPs can now apply linear interpolation between data points.<BR>
This allows to quickly define curves without the need to enter the values for the complete range.
E.g. previously it was required to enter 128 values to create a curve for a CC controller,
now it's mostly sufficient to define the same with 3..4 data points. MBNG will interpolate
the values between these points.<BR>
 
Interpolation tables can be defined with following commands:
MAP&lt;n&gt;/BYTEI and MAP&lt;n&gt;/HWORDI<BR>
 
A BYTEI map can define up to 64 datapoints with 8bit resultion,
and a HWORDI map can define up to 32 datapoints with 16bit resolution.<BR>
 
Usage examples can be found under cfg/test/map* and cfg/test/kb_2.ngc<BR>
 
See the user manual for further explanations.
 
<LI> Support for 16bit maps: with MAP&lt;n&gt;/HWORD 16bit values can be mapped.
 
<LI> label "std_rgbled" renamed to "std_rgb" to avoid error message
 
<LI> Cursor handling on SysEx based GLCD output should now work correctly if the big font is activated
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V1.033</I>
<UL CLASS=CL>
<LI> with this release, .NGR scripts running on a STM32F4 are directly executed from RAM in a compressed
/trunk/ucapps/mios_download.html.gen
194,7 → 194,7
<TD CLASS=TABCOLOR2>MIDIbox based firmware for the <A HREF="http://www.stribe.org" TARGET="_blank">Stribe</A> project (see also <A HREF="http://www.midibox.org/forum/index.php/topic,11130.0.html" TARGET="_blank">this forum article</A>)</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios/blm_scalar_v1_0a.zip">blm_scalar_v1_0a.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios/blm_scalar_v1_1.zip">blm_scalar_v1_1.zip</A></TD>
<TD CLASS=TABCOLOR2>Firmware for <A HREF="http://www.ucapps.de/midibox_seq_manual_blm.html" TARGET="_blank">BLM16x16+X</A>. The BLM driver can also used for other purposes, it scans 5 8x8 matrices for up to 320 buttons and 320 Duo-LEDs (=640 outputs)</TD>
</TR>
<TR>
/trunk/ucapps/mios32_download.html.gen
81,7 → 81,7
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_mass_storage_device%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_090.zip">midibox_seq_v4_090.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_094.zip">midibox_seq_v4_094.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="midibox_seq.html">MIDIbox SEQ V4</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
110,12 → 110,12
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_kb_v1%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_090.zip">midibox_seq_v4_090.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_094.zip">midibox_seq_v4_094.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="midibox_seq.html">MIDIbox SEQ V4</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_ng_v1_033.zip">midibox_ng_v1_033.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_ng_v1_035.zip">midibox_ng_v1_035.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="midibox_ng.html">MIDIbox NG</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
140,7 → 140,7
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_mass_storage_device%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_090.zip">midibox_seq_v4_090.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_094.zip">midibox_seq_v4_094.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="midibox_seq.html">MIDIbox SEQ V4</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
160,7 → 160,7
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_kb_v1%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_ng_v1_033.zip">midibox_ng_v1_033.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_ng_v1_035.zip">midibox_ng_v1_035.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="midibox_ng.html">MIDIbox NG</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
/trunk/ucapps/midibox_ng_manual_fs.html.gen
22,7 → 22,7
 
<P CLASS=DESC>After transfering your changes back to the SD Card (press the SAVE button), the new file can be loaded from the MIOS Terminal with the "load" command:
<CENTER><A HREF="mios_studio/mios_studio_mbng3.png"><IMG SRC="mios_studio/mios_studio_mbng3.png" width=401 height=350></A></CENTER>
<B>UPDATE:</B> since V1.019 the file will be loaded automatically whenever it has been uploaded. There is no need to enter the "load" command into the MIOS Terminal after the upload anymore! :-)
<B>UPDATE:</B> since MIDIbox NG V1.019 the file will be loaded automatically whenever it has been uploaded. There is no need to enter the "load" command into the MIOS Terminal after the upload anymore! :-)
 
<P CLASS=DESC>The filename has to be specified without the .NGC extension.
 
/trunk/ucapps/midibox_seq_manual_tut3.html.gen
20,7 → 20,7
<CENTER><IMG SRC="midibox_seq/cs4/tut3_1a.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut3_1b.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
The resulting tune, played with a Piano:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut3_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut3_1.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
37,7 → 37,7
Finally enter the base notes:
<CENTER><IMG SRC="midibox_seq/cs4/tut3_2e.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
and listen to the result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut3_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut3_2.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
49,7 → 49,7
Once the Force-to-Scale function has been configured, it also has to be enabled for the track. Please do this in the MENU-&gt;MODE page:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/tut3_3b.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
and then listen to the result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut3_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut3_3.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
58,18 → 58,18
and enable Transpose + Force-to-Scale in the MENU-&gt;Mode page:
<CENTER><IMG SRC="midibox_seq/cs4/tut3_4b.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
The result:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut3_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut3_4.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
<TR><TD COLSPAN=2>
Finally let's also add some drums with a typical rock pattern. The track should neither be transposed, nor forced to scale (of course...):<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut3_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut3_5.mp3"#ffffff**<BR><SPAN CLASS=NORM>
</SPAN></TD></TR>
 
 
<TR><TD COLSPAN=2>
This pattern works well with Guitar instead of Piano samples:<BR>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4l_tut3_6.mp3"#ffffff**<BR><SPAN CLASS=NORM>
**MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv4_tut3_6.mp3"#ffffff**<BR><SPAN CLASS=NORM>
After the 8th measure the Guitar starts to play a nice glissando! This has been achieved by using the (beloved) echo function with 3 repeats and 8d delays. In addition I'm interactively changing the note increase value from +1..+12 notes. The Force-to-Scale function ensures, that the echos are still "valid" notes in the C scale! :-)
</SPAN></TD></TR>
 
/trunk/ucapps/midibox_seq_manual_in.html.gen
12,7 → 12,7
 
<UL CLASS=CL>
<LI>it's assumed that you already tested the USB MIDI communication by pressing the Query button in <A HREF="mios_studio.html">MIOS Studio</A> as explained in the <A HREF="mios32_bootstrap_newbies.html">Bootloader page</A> - you should get some informations about the chip and the running application.<BR>
If this procedure sounds unfamiliar to you, please follow the hardware test procedure first as explained in the <A HREF="mbhp_core_stm32.html">MBHP_CORE_STM32</A> resp. <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> page.</LI>
If this procedure sounds unfamiliar to you, please follow the hardware test procedure first as explained in the <A HREF="mbhp_core_stm32.html">MBHP_CORE_STM32</A>, <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> resp. <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> page.</LI>
<LI>download the latest midibox_seq_v4_* release package from the <A HREF="mios32_download.html">MIOS32 Download Page</A>.
<LI>unzip the .zip archive.
<LI>load the project.hex file with the "Hex Upload" window of MIOS Studio and press the Start button.