sneakthief

What about encoders with switches? The LRE8x2 boards support them and you go enter a mode which disables the encoders so you don't accidentally turn them and change a setting.

latigid on: it's the high speed SD card port that can't be used because of the audio dac using the same pin. AFAIK the SD card is accessed via a slower SPI port and the audio dac is available.

chriss - sorry, looks like all 9 PCB pairs are accounted for. However, if anybody changes their mind, you're next in line.

Do you mean something like this? http://www.ebay.com/sch/i.html?_nkw=5v%203.3v%20level%20converter&clk_rvr_id=764133331262&mfe=search

The diagonal screens are a little bit strange (for my tastes). What about 128x32 OLEDs instead?

[status: order closed] I'm ordering 10 pairs of Transmitter/Receiver boards and selling 9 pairs. I'll ship them out at the end of January and will only take payment at that time. Update as of 01.30.2015 @ 11.00 - all boards shipped: mfk: 1 pair- shipped borfo: 1 pair - shipped rowan: 1 pair - shipped CJ55: 1 pair - shipped jojjelito: 1 pair - shipped monokinetic: 2 pairs - shipped Ungleichklang: 1 pair - shipped grizz: 1 pair - shipped (Notes: This is just a one-off run, I won't be doing any more. If anyone else needs more, I suggest simply uploading the .brd files to OSHPark.com or following this thread for other possible groupbuys)

IIRC according to TK, there isn't enough resources to drive all the MIDIbox CV2's cv's and run more than 4 OLEDs and 1 CLCD

latigid on: MIDIbox CV2 only supports 4 SSD1306 OLEDs

Looks like MIDIbox CV2 supports LPC: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv_v2%2Fsrc%2Fmios32_config.h

For those MIDIbox-ers wanting to experiment, you can compile this for the STM32F4 Discovery like so: https://raw.githubusercontent.com/JohannesTaelman/axoloti/master/doc/for%20stm32f4discovery.html Compiling info: https://github.com/JohannesTaelman/axoloti/blob/master/doc/compiling%20from%20source%20on%20osx.html https://github.com/JohannesTaelman/axoloti/blob/master/doc/compiling%20from%20source%20on%20windows.html Notes: You lose audio in and SD card (meaning you can only save one preset on board). MIDI I/O gpio pins are documented at the end of this file: https://github.com/JohannesTaelman/axoloti/blob/master/firmware/midi.c MIDI In/Out

Like this? http://www.rapidonline.com/electrical-power/antenna-terminal-pcb-mount-90-degree-scrtm4ra-43-0786

Thanks so much, Tim!Mike. Very much appreciated.

Thanks TK - I'll consider my question in this thread "closed" and see if Tim answers in my

[edit] my question was answered here: [/edit]

Is there any layout data for the mounting holes on the CORE_STM32F4 or the MIDI_I/O boards? I'm back to working on my MIDIbox CV2 case and the coordinates for the holes would be very helpful.

Hugo106 - I think you're confused. The AL-88c does 8x midi in and 8x midi out hardware ports - whereas ilmenator's has up to 56x ins and 56x outs. No contest. MIDIbox wins again! :D

kristal= how about nootropics and beer? http://www.engadget.com/2014/12/22/the-problem-solver-beer-creativity/

4 beers from me! Alles jut, Herr Klose.

If I'm not mistaken, you need to use bash instead of sh: http://unix.stackexchange.com/questions/17727/why-does-my-shell-script-give-the-error-declare-not-found http://ubuntuforums.org/showthread.php?t=1658965 I find Googling compiler error output often very helpful.

[edit] I was considering midifying a Yamaha CS70m keyboard but instead will use MIDIO128 [/edit]

Thanks for confirming this. I'd fix it (and also finish my MIDIbox CV 2) but I'm sick as a dog all year and recovering from throat surgery - beware of solder fumes!

I can't seem to get loop points over 16 steps to work! - Loop points 17-31 as well as 33 to 63 don't reset on those respective steps For example, if I set ALL Instruments to loop steps 1 to 17, A+B won't combine automatically. If I select A+B manually, it plays 32 steps instead of 17. However: - Setting loop points to 16 and under works correctly - Setting loop point to 32 combines A+B as well as C+D and works correctly - Setting loop point to 64 combines A+B+C+D and works correctly

I assume that STM32F407 was being overclocked as the standard maximum speed is 168MHz. Seems plausible based on these test results: http://blog.stm32f4.eu/overclock-stm32f4-controllers/ http://sigalrm.blogspot.de/2014/01/overclocking-stm32f4.html

What's the explanation for this behaviour? I would have only expected polyphony to be limited by card speed. Does it have to do with the filesystem?