MIDI Kinetics Forum

Thank you Hodari! Good idea... unfortunately, the project has reached a complexity that I find very difficult to handle given the current state of the Lemur desktop editor. (It's a pain in the ass tbh, having to deal with code all painted red because of an error without being given a hint what the ...

Thank you!

New and improved in Version 2.0 - Chord Matrix for managing chord notes and chord progressions - FatMo Midi input monitor displaying incoming chords and melody notes/intervals - Rewritten Chordbank and Progressionsequencer now allowing for 16 progressions * 10 Chords triggered in up to 20 sequences ...

Thanks alot for letting me know! I've fixed the file, had difficulties uploading a screenshot and messed it all up

Changes in this version: Contacting the author: - you can now contact me directly, see the email adress mentioned in the manual Redesigned Interface: - scale pads are now located at the bottom of the screen for a more traditional layout and easier jamming - scale change buttons removed, chord ...

I have a variable defined: t1 = floor(time/minutes*bpm*quarters) t2 = empty I have an onframe Event where I do if (t1 != t2) { t2 = t1; ... do the sequencing stuff } The resolution of the timing depends on the bpm and quarters settings. I don't think that omitting t1 and calculating the complete ...

I'd suggest using 6 horizontal rows of multipads, simulating 6 strings with each pad representing a fret or note. Add some extra controls for articulations and you're done :). Damn it, if I had more time I'd do it myself, I've had Vir2's Electri6ity installed for quite some time without using it ...

[...] However, the capability to be reasonably accurate should be there, 60FPS means a frame every 16.7ms, 30FPS means 33.4ms, so I guess you could run an onFrame Script that said "if time is greater than the expected time that this note should fire, fire the note and reset its expected firing time ...

It doesn't work without external clock, just tried it using a Monitor attached to midi_clocks, it gives you a vector of zeroes that don't change at all. Would be a nice feature though to have a single clock source both running free on its own and beeing syncable if required.

Probably yes, my mistake, I had thought that the midi clock only works when it's fed with an external clock signal. I'll try that, thanks for the tip. Yet I'd like to understand the difference between assigning a time calculation at designtime vs assigning it at runtime (in a script) and why the ...