EsotericLabs

Excellent, it works! Some notes: I set up a 128/8/8 note track with one note, one root, one chord parameter layer. The note layer is apparently necessary to send a trigger, without it, no chord is played. i put c-3 in and it is correctly transposed to d in step 3 by the root note layer and chorded to Dm in the chord layer. When i put a c-4 note in, it is a higher octave root note in the chords. I noticed though that the chord naming in the upper line of the right lcd is a bit 'off' . i have chords A/3 in step 1 and a/3 in step 3, both from the original chord set. They are both displayed as Maj6/2 however and empty steps 2 and 4 say Min10/1. I'd expect Major I and minor I in 1 and 3 and none in 2 and 4. The chord track feature is excellent though! I will play a bit more with it, see what happens when I send this one through a bus into an euclidian bass pattern and/or an arpeggiator track.

Thank you TK for your quick action!! Unfortunately it does not yet do what i expected. I will try to explain what I did and what I expected: I made a very short sequence with par layer A = root and par layer B = Chord. Four steps only; root C and chord A/3 (major) on step 1 and root D and chord a/3 (minor) on step 3. I expected that this would output C-2 E-2 G-2 on step 1 (which it did) and D-2 F-2 A-2 on step 3 (the minor chord with root D). But on step 3 I also get C-2 E-2 -G-2. So apparently, somehow the root info does not affect the chord. Or maybe I havent set it up right?

Yes thank you TK, That might be an excellent solution, I would really like to try that and help testing. If the root note parameter would work as a local transpose for the chord on another parameter layer, that would in fact create a chord track, as in Cubase and other daws. If also the arpeggiator information could make it into a parameter layer, then everything would be bundled into a single track. I guess that would make quite a powerful feature.

<<maybe this post is best here>> Hello guys, I was thinking about the chord handling in the SEQ V4. and have some suggestions for a future version (or for the v4plus). Currently we need a root note track (into a bus) and a chord track (being transposed from the bus) in order to properly play a chord progressions. But we also have multiple parameter layers in many track types, one of which is 'note' and another one of which is 'chord'. We do have 256 step/ 4 parameter / 8 trigger and 128/8/8 chord track already, but are there use cases for the additional parameter layers? Now suppose the note in parameter layer A would transpose the chord in parameter layer B (layers C and D could still hold velocity and length info). Maybe then even parameter layer E could hold arpeggiator information, so that everything would be on one track! We would have a great overview editing such tracks in layer view. I guess not many people make longer-than-256-position chords progressions. I gave it a try of course, set up a 256/4/8 chord track, changed par A to note par B to chord, but then it plays both the note and the chord with root C. Maybe if there is another parameter type 'root' that feeds the chord type? I don't know the implications of such change for the software architecture, and if it is possible at all, but I think this approach might simplify the chords handling in the SEQ V4. 'll be happy to hear your ideas about my suggestions, whether it makes sense, whether it is possible at all etc.

Hello guys, I was thinking about the chord handling in the SEQ V4. and have some suggestions for a future version (or for the v4plus). Currently we need a root note track (into a bus) and a chord track (being transposed from the bus) in order to properly play a chord progressions. But we also have multiple parameter layers in many track types, one of which is 'note' and another one of which is 'chord'. We do have 256 step/ 4 parameter / 8 trigger and 128/8/8 chord track already, but are there use cases for the additional parameter layers? Now suppose the note in parameter layer A would transpose the chord in parameter layer B (layers C and D could still hold velocity and length info). Maybe then even parameter layer E could hold arpeggiator information, so that everything would be on one track! We would have a great overview editing such tracks in layer view. I guess not many people make longer-than-256-position chords progressions. I gave it a try of course, set up a 256/4/8 chord track, changed par A to note par B to chord, but then it plays both the note and the chord with root C. Maybe if there is another parameter type 'root' that feeds the chord type? I don't know the implications of such change for the software architecture, and if it is possible at all, but I think this approach might simplify the chords handling in the SEQ V4. 'll be happy to hear your ideas about my suggestions, whether it makes sense, whether it is possible at all etc.

if user AndroSid is still in the house, try to find him. He's the prime supplier of excellent SID's

Hmm yeah maybe. But anyway, the secret is in the MBSEQ_HW.v4 file. i'd say download one & take a look.

Bump and don't hesitate if you want to send me your best offer.

it is basically a button led matrix. If you look that up on uncaps.de, you'll get the hang (DIO Matrix with configuration examples). you could also use the simpler wiring without matrixing, take a look at www.ucapps.de / seq v4 / manual / hardware options / how many buttons - leds do I need / check link to pinning diagrams) In any case, the seq core and software will take the information what button /led is where (on what shift register) from the hardware configuration file MBSEQ_HW.v4. The schematic is in here somewhere..

Haha maybe yes. Let the seq improvise with the random function. I'd love to hear your tune... But now I come to think about it.. Is there a way to have the random note generator follow the rhythmic patterns in the Jam page? That would probably make seriously cool seqjazz..

Yes, I agree. The 135 system is another way of presenting the 4 and 3 semitones structure, that is true. And I now see your point that notes must be forced down to stay in diatonic harmony instead of up. On the other hand, many songs do not perfectly follow diatonic harmony and that gives them their spice. Twelve bar blues has I IV and V dominant. Not to mention jazz progressions jumping through many ii-IV movements and changing root note every few bars. Tension chords deliberately break diatonic harmony. How to cope with that? But maybe I digress, who plays complex jazz on the seq after all? if there's interest, us theoryheads might think of something to help the programming. Indian and middle eastern music are not very chords progression oriented. Klezmer harmony is strongly harmonic minor oriented (i, iv, V7) with some occasional twists. But that's probably too far out for now.

Diatonics chords are quite tightly linked to the scale being used. A standard major or minor chord has a 1st, 3rd, 5th. in C major (Ionian) C has 1=C 3=E 5=G and becomes major , D has 1=D 3=F and 5=A, so it is minor. An example for 7th: C: 1=C 3=E 5=G 7=B(H) which is major seventh. G: 1=G; 3=B(H); 5=D; 7=F which is dominant; D: 1=D 3=F 5=A 7=C which is minor 7th. This applies for all chords without tensions. 6th, 9th, 11th 13th and all the other jazz stuff. Tension chords have non-diatonic 5th (#5 or b5) and 9th (b9 and #9)./ So a force-chord-to-scale function should look rather at the 1-3-5 principle than per-note settings for up/down forcing. in the code chords are specified in half tone steps, but the 135 principle makes far more evident what is going on in the relation between chords and scales.

Hello guys & gals, i hope this is appropriate here, if not , i ll take it down. For sale from NL is a customized FCB1010 foot controller with the LG_FCB module, the brains of a Gordius controller http://www.lg-fcb.com/. Adds lots & lots of midi functionality, USB and bidirectional DIN-5 Midi. Comes with a fitting SKB case, looking for approx 200 EUR.

isn't there a bit of confusion in the paths? There is /c/midibox/mios32/trunkS / with that extra s. And maybe something gets confused about the mios_base directory. I'm not on windows, so I cannot verify and maybe it's a stupid suggestion, but on the other hand...

did you set the additional environment variables?as in http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core

Awesome, happy to see the images over there, they are Wilba's anyway rather than mine.

I think it is possible - look up snapshots in the manual (in the standard control surface section). But I don't have working experience with them.

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, buttons, encoders & pots with midi commands.

Great! a beer well deserved.

You can make a config file in any editor. Milos studio has a basic one built in. Then upload it to the SD card.

Compatibility info here: and here IIRC 407 are good 411 are bad.

Feedback on 4.091 beta5, the extended chord table function. configured a track for chords, initialized it, then set the parameter layer to Chrd2 and confirmed with GP button switched to edit mode, stepped though all chords while playing them on my sound card. Technically no issues found, only the 13 chords (maj13, dom13, min13) are off - my bad! all '20' in the extended chord table code should be '21'. updated 6 note extended chord table in C code: {{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,21}, '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,21}, '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,21}, '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'},

yes I was thinking about that as well. Thanks for telling me the pinning!

Yes, got it. Switch the box off, keep the blue button pressed, switch on, start Mios studio and it connects in boot loader mode. And then, it uploads the firmware without any issues. Thanks @Latigid On!

Hello, While trying to upload a new firmware to my STM32F4 core, MIOS Studio timed out trying to enable the bootloader mode. How can I repair this?