midibox_sequencer_vx
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| midibox_sequencer_vx [2006/04/06 15:15] – In C not ASM. Some typos fixed stryd_one | midibox_sequencer_vx [2007/04/18 09:45] – Added forum links stryd_one | ||
|---|---|---|---|
| Line 162: | Line 162: | ||
| Despite all of the differences, | Despite all of the differences, | ||
| + | |||
| + | |||
| + | |||
| Line 171: | Line 174: | ||
| I hope that eventually the grid of buttons for the steps will be arranged in an 8 row x 12 column grid. This will allow for two modes of operation. The first would be one that we are already familiar with, where each row is a pattern and each button within that row representing a step in the sequence. In this mode, there would be left/right buttons which would control which 8 of the 16 steps are displayed, and you can freely select which pattern will be displayed on each row. Pressing a button selects that step, and then you set the parameters for the step using the controls mentioned above. | I hope that eventually the grid of buttons for the steps will be arranged in an 8 row x 12 column grid. This will allow for two modes of operation. The first would be one that we are already familiar with, where each row is a pattern and each button within that row representing a step in the sequence. In this mode, there would be left/right buttons which would control which 8 of the 16 steps are displayed, and you can freely select which pattern will be displayed on each row. Pressing a button selects that step, and then you set the parameters for the step using the controls mentioned above. | ||
| + | |||
| + | |||
| + | | Pattern 1 ^ Step 1 ^ Step 2 ^ Step 3 ^ Step 4 ^ Step 5 ^ Step 6 ^ Step 7 ^ Step 8 ^ | ||
| + | ^ Track 1 | | ||
| + | ^ Track 2 | | | | | | | | X | ||
| + | ^ Track 5 | | ||
| + | ^ Track 16 | ||
| + | ^ Track 15 | ||
| + | ^ Track 8 | | | | ||
| + | ^ Track 3 | | | ||
| + | ^ Track 6 | | ||
| + | ^ Track 13 | ||
| + | ^ Track 12 | ||
| + | ^ Track 7 | | | | | | | | X | ||
| + | ^ Track 9 | | ||
| + | |||
| The second mode would be Grid Edit, where all of the buttons are used to set parameter values for a single pattern. In this mode, each column of buttons represents a single step, and each button in that vertical column represents a separate value for the selected parameter, so the 12 rows become, for example, an octave worth of notes. This is basically like a piano roll, but of course you can only edit one pattern at a time in this manner. When you press a button, it sets the selected parameter (eg Parameter 1, which is used for MIDI Note Number in the 'Send MIDI Note' Function) according to the row. In this mode, there would be left/right buttons which would control which 8 of the (up to) 16 steps are displayed, and pitch up/down buttons to ' | The second mode would be Grid Edit, where all of the buttons are used to set parameter values for a single pattern. In this mode, each column of buttons represents a single step, and each button in that vertical column represents a separate value for the selected parameter, so the 12 rows become, for example, an octave worth of notes. This is basically like a piano roll, but of course you can only edit one pattern at a time in this manner. When you press a button, it sets the selected parameter (eg Parameter 1, which is used for MIDI Note Number in the 'Send MIDI Note' Function) according to the row. In this mode, there would be left/right buttons which would control which 8 of the (up to) 16 steps are displayed, and pitch up/down buttons to ' | ||
| + | |||
| + | |||
| + | | Track 1 ^ Step 1 ^ Step 2 ^ Step 3 ^ Step 4 ^ Step 5 ^ Step 6 ^ Step 7 ^ Step 8 ^ | ||
| + | ^ G | ||
| + | ^ F# | | | | | | | | | | ||
| + | ^ F | ||
| + | ^ E | ||
| + | ^ D# | | | | | | | | | | ||
| + | ^ D | ||
| + | ^ C# | | | | | | | | | | ||
| + | ^ C | ||
| + | ^ B | ||
| + | ^ A# | | | | | | | | | | ||
| + | ^ A | ||
| In the meantime, the User Interface will be driven by PC software… This is just until the core features are all done. I strongly suspect that a UI such as this may require a second core module, which would pass data to the second core, to drive the LCD and DOUTs. This has been discussed previously on the forum, and I am keen to implement it, as moving the control surface onto a second core will relieve the primary core of extra load driving IO, increasing performance of the sequencer. | In the meantime, the User Interface will be driven by PC software… This is just until the core features are all done. I strongly suspect that a UI such as this may require a second core module, which would pass data to the second core, to drive the LCD and DOUTs. This has been discussed previously on the forum, and I am keen to implement it, as moving the control surface onto a second core will relieve the primary core of extra load driving IO, increasing performance of the sequencer. | ||
| Line 196: | Line 229: | ||
| **Please share any thoughts or ideas or concerns or criticism or whatever!! :)** | **Please share any thoughts or ideas or concerns or criticism or whatever!! :)** | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ===== Forum Links ===== | ||
| + | |||
| + | These are links to forum posts which discuss the vx or matters related to the development of the seq. Just in case you're really bored, or maybe writing your own seq and want to learn from my mistakes ;) | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | [[http:// | ||
| + | |||
| + | |||
| + | |||