Subversion Repositories svn.mios

Compare Revisions

Ignore whitespace Rev 1180 → Rev 1181

/trunk/schematics/mbhp_midi_io/mbhp_midi_io.ps
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/trunk/ucapps/mbhp_midi_io.html.gen
2,9 → 2,9
 
<H1>MIDIbox Hardware Platform, MIDI_IO Module</H1>
 
<P><CENTER><IMG SRC="mbhp/mbhp_midi_io.jpg" width=550 height=253></CENTER></P>
<P><CENTER><IMG SRC="mbhp/mbhp_midi_io.jpg" width=550 height=241></CENTER></P>
 
<P CLASS=DESC>MBHP_MIDI_IO has been created as a MIDI breakout module for the <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module.</P>
<P CLASS=DESC>MBHP_MIDI_IO is a MIDI breakout board for the <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module.</P>
 
<P CLASS=DESC>It consists of two MIDI IN/OUT pairs and MIDI Activity LEDs which are connected to monoflops.</P>
 
28,7 → 28,7
<TD CLASS=TABCOLOR2><I>MBHP_MIDI_IO_V1</I></TD>
<TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_midi_io.pdf">mbhp_midi_io.pdf</A></TD>
<TD CLASS=TABCOLOR2 COLSPAN=1>to be published</TD>
<TD CLASS=TABCOLOR2 COLSPAN=1>to be published</TD>
<TD CLASS=TABCOLOR2 COLSPAN=1><A HREF="mbhp/mbhp_midi_io_0.jpg">mbhp_midi_io_0.jpg</A></TD>
</TR>
</TABLE></DD>
 
89,20 → 89,21
<DD>
<DD><TABLE CELLSPACING=2 CELLPADDING=2>
<TR>
<TD><IMG SRC="mbhp/mbhp_midi_io_1.jpg" WIDTH=280 HEIGHT=114 BORDER=0 ALT=""></TD>
<TD><IMG SRC="mbhp/mbhp_midi_io_1.jpg" WIDTH=280 HEIGHT=124 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>It's always a good idea to start with the smallest components to simplify mounting.<BR>
So, start with the resistors:
So, start with the resistors and diodes:
<UL CLASS=CL>
<LI>R1, R3, R5, R6, R8, R10, R11, R13, R15, R17 = 220 Ohm
<LI>R4, R9 = 1k
<LI>R2, R7 = 4.7k
<LI>R12, R14, R16, R18, R19, R20 = 100k
<LI>D1, D2 = 1N4148
<UL>
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_midi_io_2.jpg" WIDTH=280 HEIGHT=131 BORDER=0 ALT=""></TD>
<TD><IMG SRC="mbhp/mbhp_midi_io_2.jpg" WIDTH=280 HEIGHT=124 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>Continue with caps and LEDs:
<UL CLASS=CL>
<LI>C1, C2 = 100 nF
114,19 → 115,19
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_midi_io_3.jpg" WIDTH=280 HEIGHT=140 BORDER=0 ALT=""></TD>
<TD><IMG SRC="mbhp/mbhp_midi_io_3.jpg" WIDTH=280 HEIGHT=123 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>Mount the IC sockets
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_midi_io_4.jpg" WIDTH=280 HEIGHT=128 BORDER=0 ALT=""></TD>
<TD><IMG SRC="mbhp/mbhp_midi_io_4.jpg" WIDTH=280 HEIGHT=131 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>And then the DIL Headers and MIDI Sockets
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_midi_io.jpg" WIDTH=280 BORDER=0 ALT=""></TD>
<TD><IMG SRC="mbhp/mbhp_midi_io_5.jpg" WIDTH=280 HEIGHT=132 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>And finally put the ICs into the sockets:
<UL CLASS=CL>
<LI>IC1, IC2 = 6N138
140,12 → 141,19
 
</DL>
 
<P><CENTER><IMG SRC="mbhp/mbhp_midi_io_chain.jpg" width=550 height=196></CENTER></P>
<P><CENTER><IMG SRC="mbhp/mbhp_midi_io_chain.jpg" width=550 height=174></CENTER></P>
<P CLASS=DESC>
Two MBHP_MIDI_IO modules connected to J11E of the <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module in a chain.
</P>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Board Modification for 3.3V based MIDI outputs </H2></DT>
<DD><P CLASS=DESC>If you are planning to use this module for a microcontroller which outputs MIDI OUT at 3.3V level (such as the <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> module), please change the R3, R5, R8 and R10 resistor values to 47 Ohm, and connect J1:Vd to 3.3V instead of 5V!<BR>
This measure is not required for microcontrollers which output 5V, or where MIDI output (Tx) pins can be configured in open drain mode.</P>
</DD>
</DL>
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Credits </H2></DT>
<DD><P CLASS=DESC>Thanks to Tim aka. SmashTV for the great idea to chain two MBHP_MIDI_IO modules by using a special J1/J2 pin encoding. He also created 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_808.html.gen
347,7 → 347,7
<LI><B>SHIFT+Edit:</B> activates/deactivates "change all" function - changes will take place on all 16 tracks when activated</LI>
<LI><B>Gate:</B> selects gate layer for editing</LI>
<LI><B>Aux:</B> selects auxiliary layer for editing</LI>
<LI><B>Gate+Aux:</B> selects both layers for editing</LI>
<LI><B>Gate+Aux:</B> selects both layers for editing (button will cycle between Gate On, Gate+Aux On, Gate+Aux Off)</LI>
<LI><B>SHIFT+Gate:</B> temporary forces accent on all selected tracks (+the global accent trigger)</LI>
<LI><B>SHIFT+Aux:</B> temporary forces the aux trigger on all selected tracks</LI>
</UL>
/trunk/ucapps/midibox_seq_manual_m.html.gen
5,9 → 5,9
<H1>MIDIbox SEQ V4</H1>
<H1>User Manual --- Menu Pages</H1>
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Edit Screen </H2>
<P CLASS=DESC>This is the main screen which is visible after startup. From any other menu page you can always go back to this screen by pushing the EDIT button.<BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit1.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<H2> <IMG SRC="images/bullet.gif" ALT=""> Edit Page </H2>
<P CLASS=DESC>This is the main page which is visible after startup. From any other menu page you can always go back to this page by pushing the EDIT button.<BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit1.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
The <B>upper line</B> shows following informations:
<UL CLASS=CL>
<LI><B>G1T1:</B> the group/track number (1,2,3,4) which is displayed in most menu pages at upper left corner. If multiple groups and/or tracks are selected, a M is displayed instead of the number.<BR>
26,31 → 26,39
 
<P CLASS=DESC>Alternatively, each track can get an individual name and category which are displayed at the upper display line. In this example, the name "SoloSynthline2" and the category name "Synth" has been choosen. Name/Category can be edited in the Event menu.</P>
 
<CENTER><IMG SRC="midibox_seq/cs4/edit2.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit2.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
 
<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>Pressing the SELECT button will open a special page which allows to select different view modes:
<CENTER><IMG SRC="midibox_seq/cs4/edit13.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<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:
<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 on 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>
<I>Note2: EDIT RECORDING always behaves like a step recording (not like a live recording) regardless of the configuration in the record page. Live recording is only active while you are in the record page!</I><BR>
<I>Note3: EDIT RECORDING is the most simple way to enter chords into the parameter layers!</I><BR>
 
<P CLASS=DESC>Press&amp;hold the EDIT button to open a special page which allows to select different view modes:
<CENTER><IMG SRC="midibox_seq/cs4/edit13.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
<UL CLASS=CL>
<LI> <B>Step View:</B> you already know it;
<CENTER><IMG SRC="midibox_seq/cs4/edit1.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit1.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
<LI> <B>Trigger View:</B> left page allows to select the step, Gate,
Accent, Roll, Glide, Skip, Random Gate and Random Velocity.<BR>
Right Page allows to edit up to 8 parameter layers.
<CENTER><IMG SRC="midibox_seq/cs4/edit14.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit14.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
<LI> <B>Layer View:</B> allows to select the step, Gate and up to 14
parameter layer. Especially nice for custom chord editing.
<CENTER><IMG SRC="midibox_seq/cs4/edit15.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit15.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
<LI> <B>303 View:</B> provides a 303ish interface to select the Step,
Gate, Accent, Glide, Octave, Note, Velocity and up to 9
additional parameter layers
<CENTER><IMG SRC="midibox_seq/cs4/edit16.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
<CENTER><IMG SRC="midibox_seq/cs4/edit16.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
<LI> <B>Step Select:</B> allows to enable/disable the steps which are controlled by the ALL function. E.g., with the pattern below, only steps 1,2,5,6,9,10,13,14 (plus the edited step) will be changed if the ALL function has been activated:
<CENTER><IMG SRC="midibox_seq/cs4/edit12.gif" width=481 height=19 ALT="Edit Screen"></IMG></CENTER><BR>
If the track consists of more than 16 steps, the selection pattern will be applied on each step view.<BR>
Note: since V4.074 the selection pattern will be automatically displayed (and can be changed) when the ALL button is pressed, so that this page is actually obsolete. But I will keep it for future extensions.
<CENTER><IMG SRC="midibox_seq/cs4/edit12.gif" width=481 height=19 ALT="Edit Page"></IMG></CENTER><BR>
If the track consists of more than 16 steps, the selection pattern will be applied on each step view.
<LI> <B>Record Config:</B> enters the Recording configuration page (see detailed menu page description later in this chapter)
<CENTER><IMG SRC="midibox_seq/cs4/record1.gif" width=481 height=19 ALT="Random"></IMG></CENTER><BR>
<LI> <B>Random Generator:</B> enters the Random Generator page (see detailed menu page description later in this chapter)
<CENTER><IMG SRC="midibox_seq/cs4/trkrnd1.gif" width=481 height=19 ALT="Random"></IMG></CENTER><BR>
<LI> <B>Euclid Generator:</B> enters the Euclidean Rhythm Generator page (see detailed menu page description later in this chapter)
86,7 → 94,7
<CENTER><IMG SRC="midibox_seq/cs4/edit_d2.gif" width=481 height=19 ALT=""></IMG></CENTER><BR>
This page shows animated VU meters for each instrument (to give you an overview about the played instruments), and allows you to select the instrument with GP buttons.</P>
 
<P CLASS=DESC>The name of the selected drum instrument is displayed at the right upper corner of the edit screen:
<P CLASS=DESC>The name of the selected drum instrument is displayed at the right upper corner of the edit page:
<CENTER><IMG SRC="midibox_seq/cs4/edit_d3.gif" width=481 height=19 ALT=""></IMG></CENTER></P>
 
 
431,7 → 439,7
</UL>
Audio Example: **MP3**"http://www.ucapps.de/mp3/midibox_seq/mbseqv3_arp.mp3"#ffffff**<BR>
You cannot imagine how easy it is to setup complex arpeggiator textures when you never tried this by yourself :) - the <A HREF="http://www.youtube.com/watch?v=UtnUMpykQLc" TARGET="_blank">Session #4 video</A> gives a nice example of some arpeggios which where created within a few number of minutes<BR>
When you turn the rotary encoder within the Edit Screen to select the "Arp Event" for a step, you may notice events with the format "x*y".<BR>
When you turn the rotary encoder within the Edit Page to select the "Arp Event" for a step, you may notice events with the format "x*y".<BR>
These are Multi-Arp events. They play the appr. step so many times as notes are held on the external keyboard. Each key will be
transposed by the specified octave value (-3..+3). Once all keys have been played, the sequencer continues with the next step of the track.<BR>
This feature has been explained in <A HREF="midibox_seq_tutorial4.html">Tutorial #4</A> for MBSEQ V2, and it is still available in MBSEQ V4<BR>
570,7 → 578,7
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Trigger Assignments Page (Shortcut: MENU+GP Button #9)</H2>
<P CLASS=INFO>There are eight trigger layers A..H which control additional trigger functions. They can be set for each step individually with the 16 GP buttons within the Edit screen. Following triggers can be assigned to the trigger layers:<BR>
<P CLASS=INFO>There are eight trigger layers A..H which control additional trigger functions. They can be set for each step individually with the 16 GP buttons within the Edit page. Following triggers can be assigned to the trigger layers:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/trgasg1.gif" width=481 height=19 ALT="Trigger Assignments"></CENTER></IMG>
<UL CLASS=CL>
<LI><B>Gate:</B> controls if a step should be played or not. If the Gate trigger is not assigned to any layer, all steps will be played, otherwise only the selected steps will be played.</LI>
767,8 → 775,10
 
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Record Page (Shortcut: UTILITY (F1)->Rec)</H2>
<P CLASS=INFO>MIDIbox SEQ V4 provides a realtime (live) and step recording mode. Recording is always active as long as you are in this menu page. In distance to certain other sequencers, it is not required to stop an ongoing sequence in order to start recording.<BR>
<H2> <IMG SRC="images/bullet.gif" ALT=""> Record Page (Shortcut: EDIT->Record Config or UTILITY (F1)->Rec)</H2>
<P CLASS=INFO>MIDIbox SEQ V4 provides a realtime (live) and step recording mode. Recording is always active as long as you are in this menu page. A special "edit recording" is also available in the EDIT page (press GP button in EDIT page to record MIDI events into the selected step).</P>
 
<P CLASS=INFO>In distance to certain other sequencers, it is not required to stop an ongoing sequence in order to start recording.<BR>
Incoming events will be immediately inserted into the selected track. If the current step already holds a note/CC, it will be replaced by the new one. The gatelength of a note will be recorded as well, it can allocate multiple steps. If a new note is played over such a "stretched" step, the previous note will be automatically split.<BR>
<P CLASS=INFO><CENTER><IMG SRC="midibox_seq/cs4/record1.gif" width=481 height=19 ALT="Record"></CENTER></IMG></P>
<P CLASS=DESC>The <B>realtime recording mode</B> supports monophonic note, polyphonic chords (chord 1/2 and note/note/note layer mode), and CC events, which are stored into the currently selected track while the sequencer is playing.</P>
779,6 → 789,8
<P CLASS=DESC><B>Port: </B> the MIDI port to which your MIDI keyboard is connected.</P>
<P CLASS=DESC><B>Chn: </B> the MIDI channel used for recording.</P>
<P CLASS=DESC><B>Forward MIDI:</B> if on (default): events played by an external keyboard were always immediately forwarded to the MIDI output. "off" disables this function for keyboards w/o a "local off" function.</P>
<P CLASS=DESC><B>FTS:</B> enables force-to-scale for the forwarding function</P>
<P CLASS=DESC><B>FX:</B> enables MIDI effects (such as MIDI Echo and Humanizer) for the forwarding function</P>
<P CLASS=DESC><B>Quantize:</B> than lower the percentage value, than lower the quantization (-&gt; events not shifted to the next step)</P>
 
<P><center><object width="400" height="225"> <param name="allowfullscreen" value="true" /> <param name="allowscriptaccess" value="always" /> <param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=1628550&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=1628550&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="225"></embed></object><br /><a href="http://vimeo.com/1628550?pg=embed&amp;sec=1628550" TARGET="_blank">Midibox Sequencer V3 for Live Recording</a> from <a href="http://vimeo.com/user710438?pg=embed&amp;sec=1628550" TARGET="_blank">Stuart Mitchell</a></center></P>
848,7 → 860,7
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Random Generator Page (Shortcut: UTILITY (F1)->Rand)</H2>
<P CLASS=INFO>This menu page allows to randomize the layers based on individual "intensity" parameters. In difference to the "Humanize" function, random values are statically stored in the layers, so that they can be modified (within the EDIT screen, or with Utility functions like Scroll, Move, ...) until a "best matching" line has been found.<BR>
<P CLASS=INFO>This menu page allows to randomize the layers based on individual "intensity" parameters. In difference to the "Humanize" function, random values are statically stored in the layers, so that they can be modified (within the EDIT page, or with Utility functions like Scroll, Move, ...) until a "best matching" line has been found.<BR>
<P CLASS=INFO><CENTER><IMG SRC="midibox_seq/cs4/trkrnd1.gif" width=481 height=19 ALT="Random"></CENTER></IMG></P>
<UL CLASS=CL>
<LI><B>Generate:</B> generates a new pattern based on the constraints given at the right LCD</LI>
901,7 → 913,7
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Options Page (Shortcut: UTIL (F1)->Opt.)</H2>
<P CLASS=INFO>This page has an unusual layout and handling! It is intended for special customizations for which no other place have been found, or which need extended descriptions (whenever a short item name wouldn't describe the parameter sufficiently).</P>
<P CLASS=INFO>The various parameters have to be selected with one of encoders GP1..8 (left screen), and the parameter value has to be selected with one of the encoders GP9..16 (right screen).</P>
<P CLASS=INFO>The various parameters have to be selected with one of encoders GP1..8 (left page), and the parameter value has to be selected with one of the encoders GP9..16 (right page).</P>
<P CLASS=INFO>Here a list of all available options:</P>
<P CLASS=INFO><CENTER><IMG SRC="midibox_seq/cs4/opt1.gif" width=481 height=19 ALT="Options"></CENTER></IMG></P>
<UL CLASS=CL>
997,8 → 1009,8
<P CLASS=DESC>With V4.0 beta43 and higher it's possible to synchronize Mutes and Unmutes to a selectable measure of 1..256 steps. This feature is inspired from the "MIDI Clip Launcher" of Ableton Live and can be enabled in the Utility->Options page! Whenever a GP button is pressed, the Mute won't take place immediately, but synchronized to the measure. A countdown will be displayed under the track name to inform you about an ongoing mute/unmute.</P>
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Pattern Screen </H2>
<P CLASS=DESC>Within the pattern screen you can quickly change the patterns of the four available track groups:<BR>
<H2> <IMG SRC="images/bullet.gif" ALT=""> Pattern Page </H2>
<P CLASS=DESC>Within the pattern page you can quickly change the patterns of the four available track groups:<BR>
<CENTER><IMG SRC="midibox_seq/cs4/pattern1.gif" width=481 height=19 ALT="Pattern"></CENTER></IMG></P>
<P CLASS=DESC>The GP buttons and the track buttons have a special function within this menu page to improve the handling:<BR>
<UL CLASS=CL>
1036,7 → 1048,7
</LI>
</UL>
 
<P CLASS=DESC>For a fast usage the Track and Layer buttons have a special function in this screen: the Track buttons select the pattern group G1..G4, Layer button A sets the cursor to the "Song" item, Layer button B selects the "Position" item, Layer button C selects the "Action" item.</P>
<P CLASS=DESC>For a fast usage the Track and Layer buttons have a special function in this page: the Track buttons select the pattern group G1..G4, Layer button A sets the cursor to the "Song" item, Layer button B selects the "Position" item, Layer button C selects the "Action" item.</P>
 
<P CLASS=DESC>Song mode is demonstrated in the <A HREF="http://www.youtube.com/watch?v=gyffClGnFN4" TARGET="_blank">Session #2 video</A></P>
 
1091,7 → 1103,7
If the imported track contains different velocity or length values for polyphonic played notes, and this characteristic is important, it is recommended to split the track into multiple pieces (e.g. for long and for short notes) and to import them into separate MBSEQ tracks.<BR>
Another hint: if notes of the imported track don't start exactly at the 16th/32th/64th note position (e.g. because they have a "swing" feel), it is recommended to quantize the notes in a DAW before the import.<BR>
The swing feel can be added again after the import (GROOVE page).<BR>
All tracks will be initialized depending on the selected resolution and layers before the import is started. Than higher the resolution, or than more layers are selected, than less bars can be imported (number of bars is displayed on screen).<BR>
All tracks will be initialized depending on the selected resolution and layers before the import is started. Than higher the resolution, or than more layers are selected, than less bars can be imported (number of bars is displayed on page).<BR>
The MIDI port will always be set to DEFAULT during import. The MIDI channel will be set to the channel of the first played note (for each track separately).<BR>
MIDI Files can be imported while the sequencer is running. This allows you to search for a certain file, but also to try different parameters during runtime.<BR>
Here two MP3 examples of patterns that have been imported, and that are played by MBSEQ (and not by a MIDI player...).<BR>
1141,6 → 1153,7
<P CLASS=DESC>This is one of the main new features of MIDIbox SEQ V4 - thanks to the mighty MIDI event scheduler the echo function works very accurate, even on quick parameter or pattern changes:
<CENTER><IMG SRC="midibox_seq/cs4/fx_echo.gif" width=481 height=19 ALT="Fx Echo"></CENTER></IMG></P>
<UL CLASS=CL>
<LI><B>Echo:</B> allows to enable/disable the echo Fx without touching the repeat value (Repeat=0 has the same effect).</LI>
<LI><B>Repeats:</B> selects how many times a played MIDI event should be repeated (0..15).</LI>
<LI><B>Delay:</B> defines the delay between each repeat (64T, 64, 32T, 64d, 32, 16T, 32d, 16, 8T, 16d, 8, 4T, 8d, 4, 2T, 4d, 2, 1T, 2d, 1, Rnd1 and Rnd2)</LI>
<LI><B>Velocity Level:</B> defines the initial velocity level of the first repeating note</LI>
1187,7 → 1200,7
<LI><B>Note:</B> applies the LFO waveform over all Note values of the track (use low amplitudes values!) - especially interesting in conjunction with Force-to-Scale and the Limiter Fx!</LI>
<LI><B>Velocity:</B> applies the LFO waveform over the Velocity value of the track (use high amplitudes values!)</LI>
<LI><B>Length:</B> applies the LFO waveform over the Gatelength (why not...)</LI>
<LI><B>Extra CC#:</B> allows to define an CC number which will directly send the LFO value</LI>
<LI><B>Extra CC#:</B> allows to define an CC number which will directly send the LFO value with GP13, allows to enable/disable the Extra CC with GP14</LI>
<LI><B>Offset:</B> allows to increase/decrease the LFO offset within the range of 0.127</LI>
<LI><B>PPQN:</B> defines the update rate of the CC parameter (3..384 ppqn). Than higher the value, than more MIDI traffic will be produced! A value >= 96 ppqn is only recommended for virtual synths controlled via MIDI USB!</LI>
</UL></P>
1344,7 → 1357,7
Slot 1
Name Def.
####################
+Page 16
+Page EDIT
+Group 1
+Tracks 1000000000000000
+Mutes 0000000000000000
1368,7 → 1381,7
Slot 1
Name AllT
####################
-Page 16
-Page EDIT
-Group 1
+Tracks 1111111111111111
-Mutes 0000000000000000
/trunk/ucapps/midibox_seq_lite.html.gen
144,7 → 144,7
<LI>48 Mini Buttons (e.g. <A HREF="http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/index.html?ACTION=3&GROUPID=3278&ARTICLE=27893&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: TASTER 3301B</A>)
<LI>48 green LEDs (e.g. <A HREF="http://www.reichelt.de/LEDs-standard-hell/LED-3MM-ST-GN/index.html?ACTION=3&GROUPID=3018&ARTICLE=6829&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: LED 3MM ST GN</A>)
<LI>16 red LEDs (e.g. <A HREF="http://www.reichelt.de/LEDs-standard-hell/LED-3MM-ST-RT/index.html?ACTION=3&GROUPID=3018&ARTICLE=6828&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: LED 3MM ST RT</A>)
<LI>64 Diodes (e.g. <A HREF="http://www.reichelt.de/1N-UF-AA-Dioden/1N-4148/index.html?ACTION=3&GROUPID=2987&ARTICLE=1730&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: 1N 4148</A>)
<LI>48 Diodes (e.g. <A HREF="http://www.reichelt.de/1N-UF-AA-Dioden/1N-4148/index.html?ACTION=3&GROUPID=2987&ARTICLE=1730&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: 1N 4148</A>)
<LI>8 BC337 Transistors (e.g. <A HREF="http://www.reichelt.de/BC-Transistoren/BC-337-16/index.html?ACTION=3&GROUPID=2881&ARTICLE=4985&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: BC337</A>)
<LI>8 1k Resistors (e.g. <A HREF="http://www.reichelt.de/1-4W-5-1-0-k-Ohm-9-1-k-Ohm/1-4W-1-0K/index.html?ACTION=3&GROUPID=3065&ARTICLE=1315&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: 1/4W 1,0K</A>)
<LI>8 100 Ohm Resistors (e.g. <A HREF="http://www.reichelt.de/1-4W-5-100-Ohm-910-Ohm/1-4W-100/index.html?ACTION=3&GROUPID=3064&ARTICLE=1336&SHOW=1&START=0&OFFSET=16&;PROVID=2402" TARGET=_blank">Reichelt: 1/4W 100</A>)
/trunk/ucapps/midibox_ng_manual_ngc.html.gen
1309,6 → 1309,41
</TABLE>
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> DIO </H2>
 
<P CLASS=DESC>The DIO command has been added for <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> users who want to start with a very simple MIDIbox NG setup and only need a small number of digital inputs and outputs (e.g. for buttons, encoders and/or LEDs), and don't want to connect serial shift registers (MBHP_DINX4, MBHP_DOUTX4, MBHP_DIO_MATRIX). In this case, J10A and J10B can be used for up to 16 digital pins. Each J10 port can overrule a DIN or DOUT shift register.
 
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
<TR>
<TH WIDTH=150>DIO Parameter</TD>
<TH>Description</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>port=&lt;port-name&gt;</I></TD>
<TD CLASS=TABCOLOR2>Specifies the IO port which should be configured:
<UL CLASS=CL>
<LI><B>STM32F4:</B> <I>port=&lt;J10A or J10B&gt;</I><BR>
<LI><B>LPC17:</B> <I>port=&lt;J10 or J28&gt;
</UL></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>emu_din_sr=&lt;1..32&gt;</I></TD>
<TD CLASS=TABCOLOR2>The selected port will overrule a DIN shift register position, so that 8 inputs are available. Note that internal pull-up devices will be enabled, which means that buttons could be connected directly between J10 pins and ground.<BR>
Note that you can't specify emu_dout_sr in addition for the same port. The entire port is either configured for inputs our outputs!</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2 WIDTH=150><I>emu_dout_sr=&lt;1..32&gt;</I></TD>
<TD CLASS=TABCOLOR2>The selected port will overrule a DOUT shift register position, so that 8 outputs at 3.3V are available.<BR>
Note that you can't specify emu_din_sr in addition for the same port. The entire port is either configured for inputs our outputs!</TD>
</TR>
</TABLE>
 
Configuration examples:
<UL CLASS=CL>
<LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_1.ngc" TARGET="_blank">diocfg_1.ngc</A>: use J10A and J10B for up to 16 buttons
<LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_2.ngc" TARGET="_blank">diocfg_2.ngc</A>: use J10A for 8 buttons, and J10B for 8 LEDs
</UL>
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> KEYBOARD </H2>
 
<P CLASS=DESC>The KEYBOARD command configures (hardware) keyboards. The same driver like for <A HREF="midibox_kb.html">MIDIbox KB</A> is used, but the scan frequency is slower (10 times!). Each row is scanned in 320 uS (instead of 32 uS). This has to be considered in the velocity delay configuration: delay_slowest should be 100 (instead of 1000), and delay_fastest should be 5 (instead of 50)</P>
/trunk/ucapps/mbhp_ainser8.html.gen
116,7 → 116,6
Solder following components:
<UL CLASS=CL>
<LI>R1 = 10 Ohm
<LI>R2 = 470 Ohm
<LI>C4, C6 = 100 nF
<LI>C5 = 10 uF (check the polarity!)
<LI>Red "Supply" LED (polarity! Long leg is + (Anode)), it shows to the 470 Ohm resistor
125,7 → 124,7
<LI>the 3-pin SIL header J4 for chip select
</UL>
Important: the jumper have to be stuffed to get the module working!<BR>
Usually J4 selects Chip Select line 1, and J5 selects the "Dig." option for analog supply.<BR>
Usually J4 selects Chip Select line 1.<BR>
</TD>
</TD>
</TR>
/trunk/ucapps/midibox_seq_manual_fp.html.gen
5,7 → 5,7
<H1>MIDIbox SEQ V4</H1>
<H1>User Manual --- Frontpanel</H1>
 
<p></p><center><a href="midibox_seq/mbseq_panel_v3_with_v4_labels.gif"><img src="midibox_seq/mbseq_panel_v3_with_v4_labels_small.gif" width="575" height=160 align="center">MIDIbox SEQ V2/V3 panel</A></a></center><p></p>
<p></p><center><a href="midibox_seq/mbseq_panel_v3_with_v4_labels.gif"><img src="midibox_seq/mbseq_panel_v3_with_v4_labels_small.gif" width="575" height=160 align="center">MIDIbox SEQ V3/V4 panel</A></a></center><p></p>
 
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Buttons/LEDs of "Traditional" Frontpanel Layout </H2>
17,9 → 17,10
<TD> <SPAN CLASS=BIG>GP #1-16</SPAN></TD>
<TD> <SPAN CLASS=NORM>The 16 "general purpose" buttons, LEDs and rotary encoders are assigned to various functions depending on the menu context.<BR>
<UL CLASS=CL>
<LI><B>Edit screen:</B> the rotary encoders are used to change values of the parameter layers. By default, these layers control the note, velocity and gatelength.<BR>
The GP buttons are used to active/deactivate steps in the trigger layers. The appr. LED will be lit when the function is activated. By default, the trigger layers are assigned to Gate, Accent and Roll.</LI>
<LI><B>In all other menu pages:</B> the GP buttons and rotary encoders can be used to select and change the menu item which is displayed at the same location on the LCD.<BR>The usage is very intuitive and doesn't need further explanation - you will like it! :)</LI>
<LI><B>EDIT page:</B> the rotary encoders are used to change values of the parameter layers. By default, these layers control the note, velocity and gatelength.<BR>
The GP buttons are used to active/deactivate steps in the trigger layers. The appr. LED will be lit when the function is activated. By default, the trigger layers are assigned to Gate, Accent and Roll.<BR>
By pressing&amp;holding a GP button in this page, incoming MIDI events will be recorded into the step (as long as parameter layers are assigned to the appr. MIDI event type, and they are free).</LI>
<LI><B>In all other menu pages:</B> the GP buttons and rotary encoders can be used to select and change the menu item which is displayed at the same location on the LCD (soft functions).<BR>The usage is very intuitive and doesn't need further explanation - you will like it! :)</LI>
</SPAN></TD>
</TR>
 
26,7 → 27,7
<TR>
<TD> <SPAN CLASS=BIG>(Track) 1-4</SPAN></TD>
<TD> <SPAN CLASS=NORM>Use these buttons to select the track(s) which should be edited.<BR>The track buttons behave like "radio buttons" if only one is pressed so that you can quickly change between the tracks views. It's also possible to select multiple tracks by holding one, and pushing the additional track buttons - in this case every parameter change will be applied on all selected tracks.<BR>
Within the pattern and song screen, these buttons are used to select the track group (1-4).</SPAN></TD>
Within the PATTERN and SONG page, these buttons are used to select the track group (1-4).</SPAN></TD>
</TR>
 
<TR>
45,23 → 46,24
 
<TR>
<TD> <SPAN CLASS=BIG>EDIT</SPAN></TD>
<TD> <SPAN CLASS=NORM>Changes to the edit screen.</SPAN></TD>
<TD> <SPAN CLASS=NORM>Changes to the EDIT page.<BR>
This button has a second function - while it is pressed, various edit views and modes can be selected, and there are also shortcut buttons to the Record, Random and Euclid generator page.</SPAN></TD>
</TR>
 
<TR>
<TD> <SPAN CLASS=BIG>MUTE</SPAN></TD>
<TD> <SPAN CLASS=NORM>Changes to the mute screen.<BR>
<TD> <SPAN CLASS=NORM>Changes to the MUTE page.<BR>
This button has a second function - while it is pressed, individual parameter layers or drum instruments of the selected track can be muted/unmuted.</SPAN></TD>
</TR>
 
<TR>
<TD> <SPAN CLASS=BIG>PATTERN</SPAN></TD>
<TD> <SPAN CLASS=NORM>Changes to the pattern screen.</SPAN></TD>
<TD> <SPAN CLASS=NORM>Changes to the PATTERN page.</SPAN></TD>
</TR>
 
<TR>
<TD> <SPAN CLASS=BIG>SONG</SPAN></TD>
<TD> <SPAN CLASS=NORM>Changes to the song screen.</TD>
<TD> <SPAN CLASS=NORM>Changes to the SONG page.</TD>
</TR>
 
<TR>
100,7 → 102,7
<TD> <SPAN CLASS=BIG>F1-F4</SPAN></TD>
<TD> <SPAN CLASS=NORM>These are spare buttons, the function can be changed in the MBSEQ_HW.V4 file.<BR>
Following functions are assigned to the F buttons by default:<BR>
<B>F1:</B> shortcut to the Utility page<BR>
<B>F1:</B> shortcut to the UTILITY page<BR>
<B>F2:</B> selects the Step View<BR>
<B>F3:</B> selects the Trigger Layer<BR>
<B>F4:</B> selects the Track</SPAN></TD>
113,8 → 115,8
 
<TR>
<TD> <SPAN CLASS=BIG>SELECT</SPAN></TD>
<TD> <SPAN CLASS=NORM>in most menu pages this button is used to select the parameter (cursor position).<BR>
Press MENU+SELECT to enter the Bookmarks page.</SPAN></TD>
<TD> <SPAN CLASS=NORM>in most menu pages this button is used to select the parameter (cursor position) or special functions (e.g. in EDIT page it will toggle recording mode).<BR>
Press MENU+SELECT to enter the BOOKMARKS page.</SPAN></TD>
</TR>
 
<TR>
127,8 → 129,8
<TR>
<TD> <SPAN CLASS=BIG>UP/DOWN or Datawheel</SPAN></TD>
<TD> <SPAN CLASS=NORM>used to increment/decrement the selected parameter.<BR>
In edit page the datawheel and these buttons can be used for different purposes: it can scroll the cursor, the step view, can change the value and it can be used to select the parameter/trigger layer.<BR>
The function can be selected by pressing SELECT + GP7/8 in EDIT page.
In EDIT page the datawheel and these buttons can be used for different purposes: it can scroll the cursor, the step view, can change the value and it can be used to select the parameter/trigger layer.<BR>
The function can be selected by pressing EDIT + GP7/8.
</SPAN></TD>
</TR>
 
206,13 → 208,13
</TR>
<TR>
<TD> <SPAN CLASS=BIG>Utility</SPAN></TD>
<TD> <SPAN CLASS=NORM>changes to the Utility page, e.g. to access the Copy/Paste/Clear function.<BR>
With the MBSEQ V2/V3 frontpanel, the Utility page has to be selected with the F1 button.</LI>
<TD> <SPAN CLASS=NORM>changes to the UTILITY page, e.g. to access the Copy/Paste/Clear function.<BR>
With the MBSEQ V2/V3 frontpanel, the UTILITY page has to be selected with the F1 button.</LI>
</SPAN></TD>
</TR>
<TR>
<TD> <SPAN CLASS=BIG>Copy/Paste/Clear buttons</SPAN></TD>
<TD> <SPAN CLASS=NORM>direct access to the Copy/Paste/Clear function (no need to change to the Utility page).</SPAN></TD>
<TD> <SPAN CLASS=NORM>direct access to the Copy/Paste/Clear function (no need to change to the UTILITY page).</SPAN></TD>
</TR>
<TR>
<TD> <SPAN CLASS=BIG>MENU+COPY</SPAN></TD>
256,7 → 258,7
</TR>
<TR>
<TD> <SPAN CLASS=BIG>Record</SPAN></TD>
<TD> <SPAN CLASS=NORM>to enter the live/step recording page directly (alternatively enter Utility page and press GP button for "REC" button)</SPAN></TD>
<TD> <SPAN CLASS=NORM>to enter the live/step RECORDING page directly (alternatively press EDIT+GP11/GP12 or enter the UTILITY page and press GP button for "REC" button)</SPAN></TD>
</TR>
<TR>
<TD> <SPAN CLASS=BIG>Loop</SPAN></TD>
265,7 → 267,7
<TR>
<TD> <SPAN CLASS=BIG>Follow</SPAN></TD>
<TD> <SPAN CLASS=NORM>to enable follow mode (alternatively cam be enabled with MENU+EXIT<BR>
If activated, the step view in EDIT screen will change automatically if the played step of the selected track is outside the page. Within the SONG page, the song pointer follows the current song position while a song is played.</SPAN></TD>
If activated, the step view in EDIT page will change automatically if the played step of the selected track is outside the page. Within the SONG page, the song pointer follows the current song position while a song is played.</SPAN></TD>
</TR>
<TR>
<TD> <SPAN CLASS=BIG>Ext.Restart</SPAN></TD>
273,7 → 275,7
</TR>
<TR>
<TD> <SPAN CLASS=BIG>Tempo Preset</SPAN></TD>
<TD> <SPAN CLASS=NORM>to enter the tempo preset page (can be alternatively entered from the BPM menu)</SPAN></TD>
<TD> <SPAN CLASS=NORM>to enter the TEMPO PRESET page (can be alternatively entered from the BPM menu)</SPAN></TD>
</TR>
</TABLE>
 
/trunk/ucapps/midibox_ng_manual_lcd.html.gen
5,7 → 5,7
<H1>MIDIbox NG</H1>
<H1>User Manual --- LCD</H1>
 
<P CLASS=INFO><A HREF="midibox_ng.html">MIDIbox NG</A> provides so many different LCD hardware options, that this topic deserves a special page!</P>
<P CLASS=INFO><A HREF="midibox_ng.html">MIDIbox NG</A> provides so many different LCD hardware options, that this topic deserves a special page! Choose one of these types for your MIDIbox. Note that it isn't possible to combine different LCDs; means: you can connect multiple character LCDs or multiple graphical LCDs, but the firmware doesn't allow to use both type of LCDs at the same time.</P>
 
<H2> <IMG SRC="images/bullet.gif" ALT=""> Character LCDs (CLCDs) </H2>
 
/trunk/ucapps/mbhp_core_stm32f4.html.gen
2,7 → 2,7
 
<H1>MIDIbox Hardware Platform, CORE_STM32F4 Module</H1>
 
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_proto.jpg" width=550 height=326></CENTER></P>
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4.jpg" width=550 height=324></CENTER></P>
 
<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>
 
17,6 → 17,7
<LI> the enhanced instruction set with DSP operations makes Cortex-M4 very interesting for audio applications (e.g. Synths and Fx)
<LI> MIOS32 applications are typically running more than 2..3 times faster than on STM32F103RE @72 MHz, and ca. 50% faster than on a LPC1769 @120 MHz
<LI> Very useful integrated peripherals for MIDI and Synthesizer applications, such as UART, SPI, I2C, USB, CAN, Timers, ADC, DAC
<LI> The USB OTG (Micro-USB) socket supports MIDI Host, which means that it's possible to connect a USB MIDI Keyboard or Synth (see also <A HREF="http://midibox.org/forums/topic/18906-usb-host-support-for-mbhp-core-stm32f4/" TARGET="_blank">this forum article</A>)
<LI> The on-board Audio DAC predestinates this module for synthesizer projects - it could even be used standalone without the MBHP_CORE_STM32F4 breakout board for this purpose.
<LI> in distance to STM32F103RE, CAN and USB can be used in parallel
<LI> It's easy to interface external components like <A HREF="mbhp_sdcard.html">SD Cards</A> and <A HREF="mbhp_eth.html">MBHP_ETH</A>
71,19 → 72,14
</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
<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>
</TR>
<TR>
<TD><A HREF="mbhp/mbhp_core_stm32f4_prog_win4.png"><IMG SRC="mbhp/mbhp_core_stm32f4_prog_win4.png" WIDTH=280 BORDER=0 ALT=""></A></TD>
<TD CLASS=TABCOLOR2>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>The success message should show up after the programming procedure.
</TD>
</TR>
<TR>
<TD><A HREF="mbhp/mbhp_core_lpc17_program_win6.png"><IMG SRC="mbhp/mbhp_core_lpc17_program_win6.png" WIDTH=280 BORDER=0 ALT=""></A></TD>
<TD CLASS=TABCOLOR2>Click on the "START" button to program the bootloader into the flash. The "Verification...OK" message should be displayed -&gt; success! :-)
</TD>
</TR>
 
<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>
120,9 → 116,6
<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><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_fheaders.jpg" width=550 height=338></CENTER></P>
 
<P CLASS=INFO>As you can see, I'm currently using a breadboard for prototyping, since the MBHP_CORE_STM32F4 PCB isn't finished yet. This approach is only recommended for DIY people who don't flinch from handling the big mess of short wire wraps ;-)<BR>
<P><CENTER><IMG SRC="mbhp/mbhp_core_stm32f4_noodles.jpg" width=550 height=358></CENTER></P>
 
</DD>
</DL>
 
141,7 → 134,7
<TD CLASS=TABCOLOR2><I>MBHP_CORE_STM32F4_V1</I></TD>
<TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_core_stm32f4.pdf">mbhp_core_stm32f4.pdf</A></TD>
<TD CLASS=TABCOLOR2 COLSPAN=1>under construction</TD>
<TD CLASS=TABCOLOR2 COLSPAN=1>under construction</TD>
<TD CLASS=TABCOLOR2 COLSPAN=1><A HREF="mbhp/mbhp_core_stm32f4_0.jpg">mbhp_core_stm32f4_0.jpg</A></TD>
</TR>
</TABLE></DD>
 
273,10 → 266,90
 
 
<DL>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> To be continued...</H2></DT>
<DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Soldering Guide</H2></DT>
<DD>
<P CLASS=DESC>This page will be continued once the MBHP_CORE_STM32F4 PCB is available - stay tuned! :-)</P>
<DD><TABLE CELLSPACING=2 CELLPADDING=2>
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_1.jpg" WIDTH=280 HEIGHT=208 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>It's always a good idea to start with the smallest components to simplify mounting.<BR>
So, start with the resistors and diodes:
<UL CLASS=CL>
<LI>R7a, R7b, R8a, R8b: 2.2k
<LI>R11, R13: 1k
<LI>R12: 10k
<LI>R33: 4x1k resistor array (polarity!)
<LI>D1: 1N4148 (polarity!)
<UL>
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_2.jpg" WIDTH=280 HEIGHT=207 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>Continue with caps, transistor and trimpots:
<UL CLASS=CL>
<LI>C14, C15 = 100 nF ceramic caps
<LI>T1: BC337 transistor
<LI>P1, P2: 10k trimpots
</UL>
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_3.jpg" WIDTH=280 HEIGHT=213 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>Mount the IC sockets and DIL headers:
<UL CLASS=CL>
<LI>IC1: 20 pin socket
<LI>IC2: 16 pin socket
<LI>10 2x5 DIL headers
<LI>2 2x8 DIL headers
</UL>
</TD>
</TR>
 
<TR>
<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>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)
<LI>SD Card socket
</UL>
</TD>
</TR>
 
<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:
<UL CLASS=CL>
<LI>IC1: 74HCT541
<LI>IC2: 74HC595
<LI>STM32F4DISCOVERY
</UL>
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_6.jpg" WIDTH=280 HEIGHT=160 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>The bootloader can be installed on the STM32F4 chip by connecting a Mini-USB cable at the right side of the module (see also description in the "Installing the MIOS32 Bootloader" section of this page) - this only has to be done once, thereafter updates are possible via MIOS Studio. This Mini-USB socket can't be used for USB MIDI based connections!
</TD>
</TR>
 
<TR>
<TD><IMG SRC="mbhp/mbhp_core_stm32f4_7.jpg" WIDTH=280 HEIGHT=152 BORDER=0 ALT=""></TD>
<TD CLASS=TABCOLOR2>Applications (and bootloader updates) can be installed via MIOS Studio by connecting a Micro-USB cable at the left side of the module. This USB port is also used for common USB MIDI connections.
</TD>
</TR>
 
</TABLE></DD>
</DD>
 
<P><CENTER><IMG SRC="mbhp/mbhp_midi_io_chain.jpg" width=550 height=174></CENTER></P>
<P CLASS=DESC>
In order to add up to 4 MIDI IN and OUT ports, you will need one or two MBHP_MIDI_IO modules. Please <A HREF="mbhp_midi_io.html">follow this page</A>.
</P>
 
</DL>
 
<DL>
/trunk/ucapps/mios.html.gen
143,11 → 143,17
<TD CLASS=TABCOLOR2>2 MIDI IN, 2 MIDI OUT, optional third MIDI IO available at J5, optional fourth MIDI IO at J4B</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR1 width="20%"><B>USB Interface:</B></TD>
<TD CLASS=TABCOLOR1 width="20%"><B>USB Device Interface:</B></TD>
<TD CLASS=TABCOLOR2>no</TD>
<TD CLASS=TABCOLOR2 COLSPAN=3>yes</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR1 width="20%"><B>USB Host Interface:</B></TD>
<TD CLASS=TABCOLOR2 COLSPAN=2>no</TD>
<TD CLASS=TABCOLOR2 COLSPAN=1>yes</TD>
<TD CLASS=TABCOLOR2 COLSPAN=1>no</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR1 width="20%"><B>Ethernet Interface:</B></TD>
<TD CLASS=TABCOLOR2>no</TD>
<TD CLASS=TABCOLOR2>only via external HW</TD>
/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: 2014-05-26</H3></CENTER>
<CENTER><H3>Last Release: 2014-09-08</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,89
<UL CLASS=CL>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.086</I>
<UL CLASS=CL>
<LI> MIDI Learn for Drum notes in Track Event configuration page:
on a drum track, press & hold button GP12 to set the drum note
depending on the configured recording port & channel (which has to be
configured in the RECORD page)
 
<LI> Edit page: press&hold a GP button to record directly into the selected step
 
<LI> Edit page: config page which was previously visible by pressing the SELECT
button now displayed by pressing&holding EDIT button.<BR>
SELECT button now toggles step recording mode
 
<LI> Edit page: added shortcut to Recording Config (EDIT+GP11/GP12)
 
<LI> Record page now allows to toggle the FTS and FX flag for MIDI Forwarding
(same flags can be configured in LIVE page)
 
<LI> Step Recording: note length measurements now also working correctly when
the sequencer is clocked in slave mode.
 
<LI> Track Event configuration page: VelN/VelA not displayed if they are
not relevant for the selected configuration.
 
<LI> Clear function will clear all selected tracks
 
<LI> LFO page: Extra CC can now be disabled/enable with a separate switch
 
<LI> Echo page: echo can now be enabled/disabled without touching the repeat value
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.085</I>
<UL CLASS=CL>
<LI> it's now possible to customize the MENU short cut page in MBSEQ_HW.V4
with the new MENU_SHORTCUT parameter.<BR>
See the templates under hwcfg/*/MBSEQ_HW.V4 for further informations.
 
<LI> the bookmark configuration files (MBSEQ_BM.V4) are using the same
page names like MENU_SHORTCUT instead of numbers.<BR>
The old number scheme will be automatically converted to the new names.
 
<LI> improved keypad (SMS-like) entry of names
 
<LI> SysEx device page allows to specify a delay between SysEx messages which is
used when a .syx file contains multiple dumps
 
<LI> each SysEx device page has now a dedicated port/delay configuration which
is stored/restored from the /SYSEX/&lt;device&gt;/DEVCFG.V4 file
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.084</I>
<UL CLASS=CL>
<LI> the STM32F4 variant of the firmware supports USB Host mode!<BR>
See also <A HREF="http://midibox.org/forums/topic/18906-usb-host-support-for-mbhp-core-stm32f4/" TARGET="_blank">this forum article</A>.
 
<LI> If Force-to-Scale is enabled, the edit screen shows the forced keys at the lower line.<BR>
The original value is still displayed at the upper right line.
 
<LI> Live Page: FTS (Force-To-Scale) not applied on drum tracks anymore
 
<LI> Options Page: added new option which enforces Force-To-Scale for
BLM16x16+X Grid Edit mode
 
<LI> Euclid Generator Page: velocities are re-generated automatically whenever
VelN or VelA value is changed
 
<LI> the optional RECORD button now toggles between RECORD and EDIT page (previously it
only switched to the RECORD page)
 
<LI> Song page: new action "Unmute all" will unmute all tracks and parameter layers
 
<LI> Mixer: in the UTIL->Options page it's now possible to define if CC1, CC2, CC3, CC4
should be sent after or before the Program Change event.
 
<LI> NRPN MSB=127 allows to modify parameters of the currently selected track
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4.083</I>
<UL CLASS=CL>
<LI> fixed potential hang-up during pattern change which was introduced with V4.081
/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: 2014-05-31</H3></CENTER>
<CENTER><H3>Last Release: 2014-08-24</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,27
<UL CLASS=CL>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V1.031</I>
<UL CLASS=CL>
<LI>the STM32F4 variant of the firmware supports USB Host mode!<BR>
See also <A HREF="http://midibox.org/forums/topic/18906-usb-host-support-for-mbhp-core-stm32f4/" TARGET="_blank">this forum article</A>.
 
<LI> MIDI clock input ports now disabled by default to avoid feedback loops
in various setups
 
<LI> improved "ain_filter_delay_ms" implementation to support sensors (experimental stage)
 
<LI> Covered new use case which allows to transform velocity values of incoming notes.
See cfg/test/conev_6.ngc<BR>
EVENT_RECEIVER and EVENT_SENDER have to be specified with "key=any", so that any
key will be received and sent.
 
<LI> support for DIN/DOUT emulation on digital IO ports J10A/J10B (LPC17: J10/J28)<BR>
See examples in cfg/test/diocfg_1.ngc and cfg/test/diocfg_2.ngc
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V1.030</I>
<UL CLASS=CL>
<LI> increased event pool size to 64k for MBHP_CORE_STM32F4
/trunk/ucapps/mios32_download.html.gen
13,7 → 13,7
<TD COLSPAN=2 NOWRAP CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Description</STRONG></FONT></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/mios32_bootloader_v1_015.zip">mios32_bootloader_v1_015.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/mios32_bootloader_v1_016.zip">mios32_bootloader_v1_016.zip</A></TD>
<TD COLSPAN=2 CLASS=TABCOLOR2>MIOS32 Bootloader Update Package. Use this to program a virgin STM32, STM32F4 or LPC17xx device or to update/check a preprogrammed bootloader.<BR>
In distance to MIOS8, MIOS32 doesn't require a separate installation since it is integrated in the application binary.<BR>
Please note that commercial use is not allowed without my permission!</TD>
71,7 → 71,7
<TD COLSPAN=3 CLASS=TABCOLOR1><FONT SIZE=3><STRONG>STM32F1 Applications</STRONG></FONT></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_2x2_v1_009.zip">usb_midi_2x2_v1_009.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_2x2_v1_010.zip">usb_midi_2x2_v1_010.zip</A></TD>
<TD CLASS=TABCOLOR2>A 2x2 USB MIDI interface based on the <A HREF="mbhp_core_stm32.html">MBHP_CORE_STM32</A> module with integrated MIDI monitor</TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_2x2%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
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_083.zip">midibox_seq_v4_083.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_086.zip">midibox_seq_v4_086.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>
90,12 → 90,12
<TD COLSPAN=3 CLASS=TABCOLOR1><FONT SIZE=3><STRONG>STM32F4 Applications</STRONG></FONT></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_2x2_v1_009.zip">usb_midi_2x2_v1_009.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_2x2_v1_010.zip">usb_midi_2x2_v1_010.zip</A></TD>
<TD CLASS=TABCOLOR2>A 2x2 USB MIDI interface based on the <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module with integrated MIDI monitor</TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_2x2%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_4x4_v1_009.zip">usb_midi_4x4_v1_009.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_4x4_v1_010.zip">usb_midi_4x4_v1_010.zip</A></TD>
<TD CLASS=TABCOLOR2>A 4x4 USB MIDI interface based on the <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module with integrated MIDI monitor</TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_4x4%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
105,12 → 105,12
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidio128_v3%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_083.zip">midibox_seq_v4_083.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_086.zip">midibox_seq_v4_086.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_030.zip">midibox_ng_v1_030.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_ng_v1_031.zip">midibox_ng_v1_031.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>
120,12 → 120,12
<TD COLSPAN=3 CLASS=TABCOLOR1><FONT SIZE=3><STRONG>LPC17 Applications</STRONG></FONT></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_2x2_v1_009.zip">usb_midi_2x2_v1_009.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_2x2_v1_010.zip">usb_midi_2x2_v1_010.zip</A></TD>
<TD CLASS=TABCOLOR2>A 2x2 USB MIDI interface based on the <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> module with integrated MIDI monitor</TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_2x2%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_4x4_v1_009.zip">usb_midi_4x4_v1_009.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/usb_midi_4x4_v1_010.zip">usb_midi_4x4_v1_010.zip</A></TD>
<TD CLASS=TABCOLOR2>A 4x4 USB MIDI interface based on the <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> module with integrated MIDI monitor</TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_4x4%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
135,12 → 135,12
<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_083.zip">midibox_seq_v4_083.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4_086.zip">midibox_seq_v4_086.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_seq_v4l_082a.zip">midibox_seq_v4l_082a.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_seq_v4l_086.zip">midibox_seq_v4l_086.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="midibox_seq_lite.html">MIDIbox SEQ V4L</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4_lite%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
155,7 → 155,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_030.zip">midibox_ng_v1_030.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/midibox_ng_v1_031.zip">midibox_ng_v1_031.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>
170,7 → 170,7
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftroubleshooting%2Fainser_jitter_mon%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mios32/iic_midi_v1_001.zip">iic_midi_v1_001.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mios32/iic_midi_v1_002.zip">iic_midi_v1_002.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mbhp_iic_midi.html">MBHP_IIC_MIDI</A></TD>
<TD CLASS=TABCOLOR2><A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftroubleshooting%2Fiic_midi%2F" TARGET="_blank">SOURCE</A></TD>
</TR>
/trunk/ucapps/midibox_ng_manual_fs.html.gen
62,6 → 62,8
 
<P CLASS=DESC>The next experiment will work if a DIN shift register (e.g. of a <A HREF="mbhp_din.html">MBHP_DIN</A> or <A HREF="mbhp_dio_matrix.html">MBHP_DIO_MATRIX</A> module is connected to J8/9 of the core module.
 
<P CLASS=DESC><I><B>New:</B> alternatively you could emulate up to 2 DIN shift registers at port J10A and J10B of a <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module by using the DIO command. In this case, please add the two DIO commands like shown in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_1.ngc" TARGET="_blank">the diocfg_1.ngc example</A>, and connect the button(s) to J10.D0..D15</I>
 
<P CLASS=DESC>We want to generate a Note event with a button connected to the D0 pin of the first shift register. The appr. button ID is 1.
 
<P CLASS=DESC>Add following command to your HELLO.NGC file:
133,8 → 135,10
 
<P CLASS=DESC>This experiment requires a DOUT shift register (e.g. of a <A HREF="mbhp_dout.html">MBHP_DOUT</A> or <A HREF="mbhp_dio_matrix.html">MBHP_DIO_MATRIX</A> module connected to J8/9 of the core module) in addition. The anode (long leg) of the LED should be connected at D7 (the first (leftmost) DOUT output pin), the cathode (short leg) to Vs (ground).
 
<P CLASS=DESC><B>Beware:</B> the MBHP_DIO_MATRIX module has no series resistor for the LED! Please use a 220 Ohm resistor between Anode (long leg) and the D7 pin, otherwise the LED will be fried!
<P CLASS=DESC><I><B>New:</B> alternatively you could emulate up to 2 DOUT shift registers at port J10A and J10B of a <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> module by using the DIO command. In this case, please add the two DIO commands like shown in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_2.ngc" TARGET="_blank">the diocfg_2.ngc example</A>, and connect the button(s) to J10A, and the LEDs to J10B</I>
 
<P CLASS=DESC><B>Beware:</B> the J10 ports and the MBHP_DIO_MATRIX module have no series resistor for the LED! Please use a 220 Ohm resistor between Anode (long leg) and the output pin, otherwise the LED will be fried!
 
<P CLASS=DESC>So much about the obligatory disclaimer... don't worry, this resistor should be already stuffed on your <A HREF="mbhp_dout.html">MBHP_DOUT</A> module
 
<P CLASS=DESC>Change the EVENT_BUTTON definition in your HELLO.NGC file as follows:
/trunk/ucapps/midibox_seq_lite_changelog.html.gen
1,7 → 1,7
HEADER 3 ChangeLog of MIDIbox SEQ Lite
 
<CENTER><H1>MIDIbox SEQ V4 Lite Change Log</H1></CENTER>
<CENTER><H3>Last Release: 2014-05-03</H3></CENTER>
<CENTER><H3>Last Release: 2014-09-08</H3></CENTER>
 
<P CLASS=DESC>Current firmware, schematics, additional infos are located at <A HREF="midibox_seq_lite.html">http://www.uCApps.de/midibox_seq_lite.html</A>.</P>
 
10,6 → 10,25
<UL CLASS=CL>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4L.086</I>
<UL CLASS=CL>
<LI> Step Recording: note length measurements now also working correctly when
the sequencer is clocked in slave mode.
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4L.085</I>
<UL CLASS=CL>
<LI> new parameter LiveKeepChannel in MBSEQ_C.V4 file to change the MIDI forwarding function
so that the MIDI channel won't be changed according to the selected sequence, but will
be kept.
 
<LI> clock divider (configured while pressing the Tempo button) handled correctly for PitchBend and CC tracks
</UL>
</LI>
 
<IMG SRC="images/1x1dot.gif" height=20 ALT=""><BR>
<LI><I>V4L.082</I>
<UL CLASS=CL>
<LI> CLEAR button now allows to clear individual tracks with the GP buttons:
/trunk/ucapps/mbhp_mf_ng.html.gen
62,7 → 62,7
<TD NOWRAP CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Description</STRONG></FONT></TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_mf_ng_v1_004.zip">mbhp_mf_ng_v1_004.zip</A></TD>
<TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_mf_ng_v1_005.zip">mbhp_mf_ng_v1_005.zip</A></TD>
<TD CLASS=TABCOLOR2>49k</TD>
<TD CLASS=TABCOLOR2>This package contains the precompiled MIOS application and the source code for PIC18F452<BR>
Please <A HREF="mios_bootstrap_newbies.html">install</A> <A HREF="mios_download.html">MIOS</A> before downloading this app via <A HREF="mios_studio.html">MIOS Studio</A>!</TD>
83,6 → 83,11
<TD CLASS=TABCOLOR2>1k</TD>
<TD CLASS=TABCOLOR2><A HREF="http://www.reichelt.de/" TARGET="_blank">Reichelt</A> orderlist</TD>
</TR>
<TR>
<TD CLASS=TABCOLOR2><A HREF="mbhp/MF_NG_connection_diagram.pdf">MF_NG_connection_diagram.pdf</A></TD>
<TD CLASS=TABCOLOR2>406k</TD>
<TD CLASS=TABCOLOR2>Connection Diagram for ALPS RASON11M9 faders</TD>
</TR>
</TABLE></DD>
</DL>