Reggie

in the meantime I thought I'd try compiling the app. to see whether my toolchain is setup correctly (looks like it, I get errors when compiling \o/) and I've answered my own question, as the app. currently stands in the repo, it won't just work, giving me this error message: this MIOS32_BOARD hasn't been prepared yet! Looking in the mios32_config.h file I see this #if: // Dedicated SpeakJet pin assignments #if defined(MIOS32_BOARD_MBHP_CORE_STM32) # error "TODO!" #elif defined(MIOS32_BOARD_MBHP_CORE_LPC17) || defined(MIOS32_BOARD_LPCXPRESSO) # define SPEAKJET_PORT_RST_N 2 # define SPEAKJET_PIN_RST_N 2 # define SPEAKJET_PORT_M1 2 # define SPEAKJET_PIN_M1 3 # define SPEAKJET_PORT_M0 2 # define SPEAKJET_PIN_M0 4 # define SPEAKJET_PORT_D2 2 # define SPEAKJET_PIN_D2 5 #else # error "this MIOS32_BOARD hasn't been prepared yet!" #endif

Hi All, I've got an stm32F4 and a speakjet chip knocking around, so I thought I'd try out the speakjet synth for mios32 in mios32\trunk\apps\synthesizers\midibox_sj_v2. . Unfortunately, the schematic in the svn repo for the app. is for the lpc core module, looking at the schematic compared to the lpc module pinout, if I've got this right, the speakjet chip connects d2,m0,m1,rst to J10.d3, .d2, d1 and .d0 and the speakjet rcx pin connects to J5b.A7, will the midibox_sj2_v2 app. work if I connect the respective pins as they're laid out on an stm32F4 (pe8,9,10,11 for the J10 pins and pb1 for the j5b.a7-rcx connection)?

HI Norbim, I checked the forum right after I asked the question :-)

Thank you Norbim, that's a really cool port, I wonder does it absolutely need the LCD screen or are there windows editors that can be used?

Hi Yogi, thanks :-) It's a great little synth, I thought it would go really nice with midibox, the random stuff does produce a lot of pure noise, the magicPatch and magicFX functions are pretty savage, they leave no stone unturned :D I've made some alterations I think are useful, I'll list a few of them: encoder support for filter 1 and 2 frequency, 80hz-8000hz in 1hz increments (the encoders on the arturia minilab have acceleration) encoder support for tempo, 20bpm to 520bpm in 1bpm increments (can be set to any resolution you like) split MagicFX randomiser into magicDelay, MagicPhaser, MagicChorus, makes the randomness a lot more manageable, easy to get very interesting variation over sounds Added straight 16 step sequence playback support, the sequencer was really just randomly picking notes from a scale over an octave spread with the existing patterns, now it will play hardcoded 16 step sequences you can still set the octave spread if you want. I'd really like to get the midi control formalised on it, it seems a little bit clunky in the assignment of CCs and slightly wasteful of them in some areas, it's been built really for any keyboard with an assignable fader(s) or pots and some pads, so 0-127 7bit values, complimenting anything that could do with finer control (I'm thinking anything with a frequency control or time control etc.) with inc/dec via encoders instantly becomes even better, the difference it's made to the filters is fantastic. There is some tradeoff with the encoders and fine control, you can't do large sweeps in 1hz/step resolution, this can be mitigated though, I have put code in for multipliers and I've left the original code intact. I don't want to add too much more code to the control side until I've had time to think about how I should go about formalising it. There are quite a few functions like the filter type selection where it's using 0-127 on a control that only has 5 settings, or pairs of CCs used for inc/dec of a setting, both types of setting could do with encoder support or altering so that their range matches the control.

Hi Digineural, I am reasonably familiar with C/C++ and gcc mainly on linux and I setup a toolchain in windows last week for the stm32F4-Discovery board, it was a bit of a pain to get there though but I have it set up with eclipse or the console + context (text editor) now. I already own the board btw. I currently have it running an open source synth firmware that I'm editing to make it a bit more useable/useful, it's a great little synth, got lots of randomisers on it though, so I'm adding functions in to split them off into more manageable sections, also adding higher resolution controls, 7bit midi is not so great with the amount of resolution the synth has got under the hood so I'm adding support for encoders on some functions. https://github.com/MrBlueXav/Dekrispator I don't want to do the author (MrBlueXav) any injustice, it's a fantastic sounding synth in it's own right but it was built to be more of a random noise/pattern maker as it stands. I'm just adding functions where necessary.. just making sure things were ok with the instructions before I dive down another rabbit hole..... I had thoughts about an LCD but I'm not so keen on using a 2x20 display, nothing wrong with them as such, I just have other options I could probably use. a couple of arm quad core dev boards, one with a 7" cap touchscreen, both with linux and android support and hdmi out, networking, + access to gpio, uart, USB etc. I'm figuring a control surface done with ctrlr + mouse and keyboard would be reasonable.

Hi All, I have an stm32F4 discovery board and I'd like to start developing for it using midibox. I had a look through the wiki and by the looks of it, as I'm using windows this is what I need: http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core However, the tutorial is for windows XP so I wonder if it's still relevant to me as I'm using windows 7? I'm also unsure as to exactly what I'll need for particular projects, I envisage having the core stm32F4 board as a midi engine connected to a PC and with an external usb control surface (keyboard, mixer, dj controller), I know there is usb-midi host mode support, so is it possible to build a midibox project with just that setup? Obviously ignoring things like the FM synth which requires external parts. I have 4 programmable midi controllers (2 keyboards, 1 with 16 pots, 1 with 16 encoders + 16 programmable pads , custom midi controller with 32buttons notes or CCs and 8pots and lastly a peavey pc1600x, so I figure I'm pretty much covered for control via midi.

Hi all, so I've decided that an lpc1769 would be the way forwards but it will have to wait until I get some more money. In the meantime, I found a midi usb firmware for the arduino leonardo which is the same atmega32u2 as a little breakout board that I've got, which gets me where I want to be with simple usb to midi commands and my current controller. it gives me options for experiments while I wait for an lpc board. I also managed to harvest some 4051 chips, they're soic but I have some tssop-28 breakouts that can take the chips if you're very careful about MISplacing the chip, the 4 corner pins all connect to a single pad, the other 12 connect to 2 pads, it should be ok. there's also a handy little breakout for the lpc board too, lots of pads for different smt stuff, very useful I think.

I've already got quite a few boards and chips here, just not an lpc1769. However, the entry price of an lpc1769 is very cheap, I'm not sure I'd even need a din socket, if midibox talks serial and i2c/spi then i can possible use those interfaces. I've got shift registers, 8bit atmega chips so I have lots of options. I've got some other boards coming that will give me most of what I want immediately, the controller box I've already built is just throwing out midi via serial 5v, once those projects are out of the way, I can then think about an lpc based board to hook these other units into.

Hi John, thanks for the reply, that's not what I was hoping to hear. Especially considering the 100 exposed pins on the stm32F4-Discovery board. Whilst I appreciate that not all of those pins will be available (there are 10 or so that are for 3/5v, vdd and ground) I had expected there to be access to quite a few of them. To start off with I just need be able to use it as a general controller sending midi via usb, it feels like complete overkill right now to start mashing other ICs together when the disco board has everything onboard already. Then again, just using it as a controller with a ton of buttons seems underkill :D It's a shame as I'd hoped the modules were software style plugins, setup the number of pins, which pins you want to use, add functions to go with them and away you go. Reggie.

Thanks Hawkeye, I had a look at a lot of projects and they seem to contain a lot of dead links :-( As you can appreciate, midibox is no small thing, I don't really fully understand all of the concepts yet, perhaps I need to start with that? I understand that I need a core, which would be my stm32F4-discovery board. I also see that there are other modules such as AIN etc. which seem to be units (another mcu?) that are attached to the core? Which is where my understanding breaks down, with the stm32F4 board, I can't see me actually needing any extra add-on modules, the board should cope with everything already in it's own right, is that possible? To start with I really just need to be able to use digital pins connected to buttons/rotary encoders to send note on/off and cc data via USB, perhaps something like 16-20 buttons, 8 encoders. I'd like to be able to offline edit the button/encoder messages, in the future I'd like to add multiple messages per button (which shouldn't be difficult at all). If I have to add external modules I have various atmega chips that that can send midi data over serial if necessary. Is it worth trying to message TK at all, to see what the state of play is with his code or whether he can give me any pointers as he ultimately knows more than anyone on the subject?

Hi all, I found this forum last night while searching for information on usb-midi for an stm32F4-Discovery board, it appears that someone awesome (TK I think?) has started a port to the stm32F4-discovery boards :-) I understand that midibox isn't really just one thing, it appears to be a collection of things from synths and sequencers to controllers and manglers, I've just built myself a simple midi controller using an arduino mega1280 that's using serial and a serial to midi bridge, however, I have some teensy 2.0 boards on their way which will give me straight usb-midi, this will be entirely adequate for some smaller controllers that I want to build but midibox seems like an interesting path to wander down too :-) I'd like to build a better controller with the stm32F4-Discovery board if that's possible, I mainly want to be able to design a sensible controller with the usual controls, buttons, sliders, pots, rotary encoders, I appreciate that at this time the stm32F4-disco support is limited to digital only so the pots/sliders will have to wait for analog support to be written. I would also like to be able to manipulate the messages to a tempo when I hit certain buttons,so essentially providing midi controller based effects. For instance, I might want to press a controller button and have it repeat every 8th note etc. Bearing all that in mind, can any of you knowledgeable people suggest where I might start? Reggie.