Differences

This shows you the differences between two versions of the page.

--- lucem [2009/01/03 00:46]
lucem
+++ lucem [2009/07/06 17:37] (current)
80.144.110.200
@@ Line 27: / Line 27: @@
 I built an MB-6582 in 2008.
-NOTE: Insert photos here!
+Photos are available under [[http://users.sr-iserlohn.de/mb6582/]]
 ===== Projects =====
@@ Line 51: / Line 51: @@
 ==== 4x4 / 8x8 MIDI hardware router ====
-This will be using basically the same hardware as the Keyboard, so this is mainly a programming task -
+<del>This will be using basically the same hardware as the Keyboard, so this is mainly a programming task -
 and it's in fact the elder project of the two. First stage is developing a 4x4 hardware router using only
 a single microcontroller, if that works to satisfaction, I plan on expanding to using two, interconnected
@@ Line 57: / Line 57: @@
 The routing table will be easily set up by using a matrix very similar to the one on the mbsid.
 nILS suggested use of a touch screen, which I think is pretty interchangeable since there is no
-real difference between switches and phototransistors.
+real difference between switches and phototransistors.</del>
+<del>Since the introduction of the gm5, in conjunction with MIDI-Ox, this seems less urgent than
+ever, so I will put this on a hold.</del>
+==== 16x16 programmable MIDI patch bay ====
+This evolved from the MIDI router idea above.
+A whitepaper describing the device and the use cases is in preparation.
 ==== MIDI Sequencer ====
-This is in early concept stage, and atm just an idea I tinker with.
+<del>This is in early concept stage, and atm just an idea I tinker with.
 I like the idea and concept of the midibox sequencer, so maybe I'll decide to abandon this
 and build a proven solution instead...
@@ Line 66: / Line 73: @@
 As I said, I like the concept of the MBSEQv3, but I find it quite hard to use from what I've seen and
 read by now, so I started doodling in aim of a more entry-level friendly UI.
+Update January 2009:
+I've worked on the Sequencer concept over the last few weeks and fleshed it out to a great deal.
+Currently, I'm aiming for mega128 instead of mega2560, as this one won't need too many I/Os.
+The hardware concept is somewhat similar to the CORE32 regarding peripherals and such, and there's
+a chance I might switch to STM32 after all, but I'm not sure about that right now.
+So far, my plan includes the use of several modules to do the job.
+There are six microcontrollers currently involved, all the same hardware design, but for different tasks.
+One is acting as a MIDI master clock, which outputs MIDI clock data on a dedicated MIDI output, plus
+a clock gate signal, which will be used internally for synchronization.
+One controller will act as a master sequencer controlling all other modules, handling the UI and
+doing file operations on an SD card.
+The other four controller modules will be the actual MIDI sending "sub"sequencers, each one playing
+four tracks.
+Several sequencer devices can be chained together to allow for (theoretically infinite) expansion;
+such chained seq's will not require a master clock module present, but still do require a master
+controller module present.
+Everything, from the UI, displays, internal communication, file system access etc. will be based on
+SPI. Therefore, each module will have 3 SPI interfaces, each one capable of adressing 9 different
+SPI busses; one using the hardware SPI, two using software SPI.
+I chose the subsequencer-approach with several independent, gate-synchronized seq's because this
+offers very interesting opportunities to work with polyrhythmic sequences (i.e. one sequence consisting of 12 16th-notes,
+one sequence consisting of 8 16th notes, one of 3 8th notes etc.) which I find rather funny and worth exploring.</del>
+Update February 2009:
+Joined forces with stryd_one, as his vx32 Sequencer and mine were very similar in approach.
+As of this, target is now core32 / mios32 (plus a PC application using the same code).
+I'm responsible for the UI and the PC port of the app, and development is already underway.
+For the PC port, I use Qt4, so it's gonna be portable to Windows, OSX and Linux. Whee!
+Update July 2009:
+The library used for GUI is now JUCE, which eases the overall work a lot, since
+with the introduction of the MIOSJUCE port, we can work directly with MIOS
+calls on the PC, too. The GUI is optimized to be used on a PC with a small
+touchscreen.
 ===== Research =====
@@ Line 71: / Line 115: @@
 Some random sketches exist.
 I'm opting for a computer multitouch screen and use that for some musical applications.
+(This will have to wait for a long time)
 ==== Multitouch pad ====
@@ Line 86: / Line 131: @@
 The function principle of the sensing portion is described here: [[http://files.tachilab.org/intconf1900/tanie198410RVSC.pdf]]

MIDIbox

User Tools

Site Tools

Differences

Page Tools