EsotericLabs

yes use a STM32F4 core if you can still lay your hands on a discovery board. Even if you hate encoders, they will make your project easier as you will only need DIN and DOUT modules. These will also support buttons & leds . Or if you really hate encoders, use the AINSER64 . A standard control surface with general purpose buttons and a 2x20 LCD is also very practical. iirc Ilmenator has a pcb for that..

I guess Midibox NG is the right direction to look into for your purpose. You don't need to program, ' only' to make a configuration file, once the firmware is installed on the processor core. You will have to know the midi implementation of your future sent very well though. The best place to start is the user manual of Midibox NG http://www.ucapps.de/midibox_ng_manual_fs.html That will give you a starting point how to link up leds and buttons and encoders (why pots??) with midi commands.

Me too, once i properly get what we're after.

This is the design that went to formulor. For documentation & download.. 2xSEQV14_17inch2xBackQuadIIC.zip NOTE: the back panel design is NOT perfect: the 2 midio sections are too close together by approx 6-8 mm.

Yes it does. It takes some experimenting, but once you get it, it is really powerful. In a personal use case, I have bass, pads and arps in group 1., drums in group 4. Three patterns for group1 (1:A1; 1:A2; 1:A3) hold chord changes for verse, chorus and bridge of my song (all three instruments follow the chords) The drum group has a normal time ) and half time drum patterns in 4:A1 and 4:A2. Just switching patterns gives a lot of flexibility. I can imagine some lead and melody lines in group 2, with an empty pattern to start with.

Ok here are four note versions, approved of by the jazz police. {{0,7,-1,-1}, 'Pwr5'}, {{0,7,12,-1}, 'Pwr8'}, {{0,4,-1,-1}, 'R+mj3'}, {{0,3,-1,-1}, 'R+min3'}, {{0,4,7,-1}, 'Maj '}, {{0,5,7,-1}, 'Sus4'}, {{0,4,8,-1}, 'Maj+'}, {{0,4,7,9}, 'Maj6'}, {{0,4,7,11}, 'Maj7'}, {{0,4,7,14}, 'add9'}, {{0,4,11,14}, 'Maj9'}, {{0,4,11,17}, 'Maj11'}, {{0,4,14,20}, 'Maj13'}, {{0,3,7,-1}, 'Min'}, {{0,3,7,9}, 'Min6'}, {{0,3,7,10}, 'Min7'}, {{0,3,7,14}, 'Minad9'}, {{0,3,10,14}, 'Min9'}, {{0,3,10,14}, 'Min11'}, {{0,3,14,20}, 'Min13'}, {{0,4,7,10}, 'Dom7'}, {{0,5,7,10}, '7Sus4'}, {{0,4,10,14}, 'Dom9'}, {{0,4,10,17}, 'Dom11'}, {{0,4,10,20}, 'Dom13'}, {{0,4,6,10}, '7b5'}, {{0,4,8,10}, '7#5'}, {{0,4,10,13}, '7b9'}, {{0,4,10,15}, '7#9'}, {{0,3,6,-1}, 'DimTri'}, {{0,3,6,9}, 'Dim'}, {{0,3,6,10}, 'm7b5'}, But if the arpeggiator is not at risk, here are max 6 note versions with minor 6th added. I forgot that one. {{0,7,-1,-1,-1,-1}, 'Pwr5'}, {{0,7,12,-1,-1,-1}, 'Pwr8'}, {{0,4,-1,-1,-1,-1}, 'R+mj3'}, {{0,3,-1,-1,-1,-1}, 'R+min3'}, {{0,4,7,-1,-1,-1}, 'Maj '}, {{0,5,7,-1,-1,-1}, 'Sus4'}, {{0,4,8,-1,-1,-1}, 'Maj+'}, {{0,4,7,9,-1,-1}, 'Maj6'}, {{0,4,7,11,-1,-1}, 'Maj7'}, {{0,4,7,14,-1,-1}, 'add9'}, {{0,4,7,11,14,-1}, 'Maj9'}, {{0,4,7,11,14,17}, 'Maj11'}, {{0,4,7,11,14,20}, 'Maj13'}, {{0,3,7,-1,-1,-1}, 'Min'}, {{0,3,7,9,-1,-1}, 'Min6'}, {{0,3,7,10,-1,-1}, 'Min7'}, {{0,3,7,14,-1,-1}, 'Minad9'}, {{0,3,7,10,14,-1}, 'Min9'}, {{0,3,7,10,14,17}, 'Min11'}, {{0,3,7,10,14,20}, 'Min13'}, {{0,4,7,10,-1,-1}, 'Dom7'}, {{0,5,7,10,-1,-1}, '7Sus4'}, {{0,4,7,10,14,-1}, 'Dom9'}, {{0,4,7,10,14,17}, 'Dom11'}, {{0,4,7,10,14,20}, 'Dom13'}, {{0,4,6,10,-1,-1}, '7b5'}, {{0,4,8,10,-1,-1}, '7#5'}, {{0,4,7,10,13,-1}, '7b9'}, {{0,4,7,10,15,-1}, '7#9'}, {{0,3,6,-1,-1,-1}, 'DimTri'}, {{0,3,6,9,-1,-1}, 'Dim'}, {{0,3,6,10,-1,-1}, 'm7b5'}, And if i may digress a bit, I'd suggest a chord track with one parameter layer holding the root note and another holding the chord type, if that is technically possible. This might be easier to set up than through the loopback function.

If its helpful to redefine the extended chord table to a four note per chord maximum, please say so, that is not too hard. Many chords can do without a fifth, if that helps to preserve the arpeggiator function (i'd want to add the minor 6 after all..)

any cheap kingston - i've got one now with a micro SD in it . also good experience with SanDisk. but sometimes formatting a couple of times does the trick. Don't know why tho.

sometimes it helps to format your card on a computer (FAT32), then on the midi box. I have good experiences with Kingston though.

why to try formatting the card first? type sdcard_format in the MIOS Studio command line.

Yes I have comparable results. I run a 16 step 16th based drum (G4TM) track against a 16 step 8th based baseline (G1T1) In phase mode i hear no issues. In song mode, with any of these as a guide track, only half of the baseline is played. Without a guide track, things play as expected, only if i want to play the bassline 2x, i have to repeat the pattern 4x. I expected that with a 16 step 8th based guide track, I'd need to set the appropriate pattern only 2x to hear the bassline 2x. The drum track can repeat ad nauseam, though its cool to have an extra Nth layer with an occasional crash or a snare fill. It's quite an abstract issue, i'd say the divider value is not taken into account for the guide tracks somehow. Maybe @TK will tune in and enlighten us?

Thank you for adding that so quickly. Your tekst suggests that it is possible to jam with my keayboard first on one track (lets say G1T1) and then switch over to another one (maybe G1T2). With or without recording. That would be an interesting usecase, I will test that tonight. Glad you mentioned the guide track! While testing, I had an issue with a short 16th based drum pattern (with Nths for fills & stuff) and a longer and slower (8th) bassline. Song mode made me enter 8x if I'd want the bassline to play twice! I guess i should designate the bassline as the guide track. If so, that's a powerful feature indeed! And if you'd want the chords table for the chords2 layer in 4.091: A, B: power chords (root 5th; root 5th octave) C, D root with major 3rd, root with minor 3rd E, F major triad, augmented trias G-M maj6, maj7, add9 (no 7th), maj9, maj11, maj13 N-c: minor triad, min7, minadd9, min11, min13 d-h: dominants: 7, 7sus4, 9, 11, 13 i-l: tensions: 7b5, 7#5, 7b9, 7#9 m,n: diminished triad, diminished chord o: half diminished m7b5 p: polychord (stacked 4th). PS: i forgot minor6! Maybe we should forget about the polychord and add minor6. Polychords are weird enough for multiple note parameter layer tracks.

A small comment to ch4 though. I first did not get it to work. But then I found out that the recording bus was still set to its default T&A mode. When I selected Jam, it worked as expected. It might make sense to add that. In terms of buttons& encoders: UTIL->GP10 to go to Jam page, there press midi GP7; then turn ENC14 or press GP14 to select Jam instead of T&A. But nonetheless: Excellent job & Many kudos for writing this up! May the Force bless you with happy sequencing!

I use the cc to enter remote control mode - I set up cc80 in MBSEQHW. And then tap tempo could be added to the remote function - some notes are still free. But depending on the foot controller, it might also make sense to bypass remote function activation and have a CC to directly tap in the tempo. For me it does not really matter which cc number on which channel. Best is possibly to make a configurable cc tap tempo number, but that requires more code i expect.

Hello, another feature request is remote tap tempo, for those working with a foot controller. If I understand correctly, it will take only a small modification to the code:

Excellent! this is SO helpful. Can't wait to have my displays and test all the steps for you..

I think it is only cheap within the eurozone. no costs involved in euro to euro transfers.

I think it is only cheap within the eurozone. no costs involved in euro to euro transfers.

Is it not cheaper if European guys use the SEPA / IBAN system?

Hello Midiboxers, as I'm currently making a formulor front panel design, I am looking for confirmation about the exact dimensions of the front panel for a SEQ V4 in the Heidenreich enclosure. I found: 17 inch x 3U for the inner panel (w431.8mm x h133.35mm) . 1.8mm should be added on all sides for the thinner 'slabs' to click it into the corner profiles of the case. Am I correct? And - if I want to make a Formulor front panel - should I enlarge the front panel for the 'slab' and dremel it? Or is it better to stick to exactly 17"x3U and glue on a thin all profile for the slabs? Or is the formulor route failure bound altogether and do you strongly recommend to go for a premade aluminium panel? Please enlighten me!

Methinks - through MIOS studio, the file browser utility?

I'm currently working on a design for a back plate in the heidenreich format. It will contain: holes for 2xMIDIO; AOUT (if required) and a type B connector. For me the sd card can stay inside as long as it is accessible through USB. I want to throw in a USB panel mount extension cable like this one. http://www.miniinthebox.com/nl/0-5m-1-5ft-micro-usb-5pin-male-naar-usb-b-female-panel-mount-het-type-kabel-50cm-met-schroeven-gratis-verzending_p2114390.html I still need to think about the routed edge required for fitting the heidenreich enclosure and find a proper power connector and switch and draw them into the back panel. here is a formulor based design, two pieces in the large formulor size. Suggestions warmly welcomed of course.. 2xSEQHeidenreich.eps.zip PS: I'm a bit confused by the dimensions: the STM32F4 pcb length is 118mm ; the bottom plate of the heidenreich case is 125.2mm width. Why doesn't the core fit? Do the corner profiles get in the way or is it a height issue? And what would be the exact size of the front panel - w435,50mm x h133.65mm (3U) ? or slightly higher

PMed

Well OK, I'm in. Heidenreich cases are pretty solid and way cool. Thanks for organizing Doc007.