midiStep bug found on sequencer

[MaliceX]

Hi. I managed to hook up a miniature VST setup on my laptop with VSTHost, routing midiStep to Oatmeal.

Issue: There seems to be instances where deleting notes after active chord scanning would kill the ability to trigger chords completely.

I'm currently unable to predict how this happens but it seems to happen to me on cases with 3+ note chords then deleting, and perhaps if it were the current or next chord to be triggered which the deleted note(s) reside.

Other than that this thing is looking fantastic. Most certainly will be useful when jamming with keyboard drums and controlling chords in realtime.

Questions:
---Any possibility for a switch to block normal note output other than the trigger note?
---What's the current/planned implementation of switching patterns?

Again, big thanks for making this thing.

EDIT: Here's a MIDI to import that somehow 'breaks' the ability to trigger by the end.

http://djtbmx.soulbreakers.com/junkpile ... dintro.mid

[insertpizhere]

thanks for the bug report and midi file. i'll try to check it out tomorrow.

---Any possibility for a switch to block normal note output other than the trigger note?

sure, no problem

---What's the current/planned implementation of switching patterns?

currently:
clicking on a pattern number selects it for editing. when "active" is checked, clicking on a pattern number also arms it for recording. you can ctrl-click to arm more than one pattern for recording. i'll probably change the way the buttons look (i.e. i guess record arm should be red instead of blue).

i don't have anything else planned in that area but suggestions are welcome.

[MaliceX]

Oh okay, though clicking to change patterns while playing triggers could be a slight issue for those not using a touchscreen, heh. A next/previous trigger key/controller/program change event to reflect the selected pattern perhaps may be a little more convenient (whatever's easier to implement, could always use one of your other plugins to change the behaviour.)

[yellukhan]

hi
i hope im not hijacking the thread


i want to thank you for this great tool.
i think some kind of bug in FL9.0.3
after 3th or 4 th midi dragging ( replacing ) to midistep its freezing.
+
one suggestion for now
is it posible: select different midi out channel for per pattern ?

[insertpizhere]

there was a stupid mistake causing problems after the 99th note in a pattern. fixed that, added a "thru" switch, program change for switching active pattern, named the parameters...

http://thepiz.org/pizmidi/midiStep.zip

i'll try to get midi out channel per pattern for next time...

[yellukhan]

hi
thanks for the fast fix (as always)
now no crash anymore
but
i think something changed because interface doenst refresh itself when i drag the new midi its still showing old midi data ..
( if i open close interface its ok or if i click to other pattern then click again fist pattern its ok ..refreshing )
but it doest show which notes im playing.

[MaliceX]

hi
thanks for the fast fix (as always)
now no crash anymore
but
i think something changed because interface doenst refresh itself when i drag the new midi its still showing old midi data ..
( if i open close interface its ok or if i click to other pattern then click again fist pattern its ok ..refreshing )
but it doest show which notes im playing.

Bug confirmed under VSTHost. Screen refresh seems to be broken (ie: will only refresh after 'wiping' over the window or scrolling.)

EDIT: Another bug, loading two different MIDI's on different patterns, the selected pattern would trigger simultaneously with another pattern.

[insertpizhere]

Bug confirmed under VSTHost. Screen refresh seems to be broken (ie: will only refresh after 'wiping' over the window or scrolling.)

i just uploaded a new version that should fix this. same link...

EDIT: Another bug, loading two different MIDI's on different patterns, the selected pattern would trigger simultaneously with another pattern.

if they have the same trigger note, that's what's supposed to happen. "selected" just means it is the one showing on the piano roll. is that ok, or does it need a mode to play only the active pattern?

[MaliceX]

if they have the same trigger note, that's what's supposed to happen. "selected" just means it is the one showing on the piano roll. is that ok, or does it need a mode to play only the active pattern?

AH. I did not realise that. Thank you very much for clarifying that. :O Will test now.

EDIT: File is the exact same one. (Dated 29th March with identical file size) No change to the screen refresh bug on trigger.

Suggestion on Record mode: Looking at the behaviour of your other plugin, midiHold, I was wondering if the Record mode would be possible to record chords in step sequence in a similar manner? At the moment it seems like it records like any MIDI sequencer would, and so far slightly unusable without editing the timings of the recorded notes since triggering them would tend to miss notes. )At least when recording on-tempo)

Unimportant edit: A little MIDI I made in about 10-15 minutes after toying around with pre-made chords in midiStep, re-recording the output to my MIDI sequencer and adding my own drums on top. Instant gratification for 80's Jazz fusion solo wankery. WOOOOO
http://djtbmx.soulbreakers.com/muzik/me ... 20test.mid

[yellukhan]

file not the same
because when the dragging midi its refreshing but triggered notes still dont
(actually its no big problem to me )

[insertpizhere]

fixed, i think... download again

Suggestion on Record mode: Looking at the behaviour of your other plugin, midiHold, I was wondering if the Record mode would be possible to record chords in step sequence in a similar manner? At the moment it seems like it records like any MIDI sequencer would, and so far slightly unusable without editing the timings of the recorded notes since triggering them would tend to miss notes. )At least when recording on-tempo)

hmmm... there is a certain time between notes under which the plugin will consider them a chord. this could be made adjustable. a step record mode would be nice too though.

Unimportant edit: A little MIDI I made in about 10-15 minutes after toying around with pre-made chords in midiStep, re-recording the output to my MIDI sequencer and adding my own drums on top. Instant gratification for 80's Jazz fusion solo wankery. WOOOOO
http://djtbmx.soulbreakers.com/muzik/me ... 20test.mid

i can't listen right now but it looks cool.

[MaliceX]

fixed, i think... download again

Checked, tested, confirmed fixed. Thanks very much for that.

hmmm... there is a certain time between notes under which the plugin will consider them a chord. this could be made adjustable. a step record mode would be nice too though.

Yeah I sort of noticed that when I first imported one of my own barebones MIDI's in (I usually have a timebase of 120 which somehow made all the notes ultra-tiny in length. Hahaha) instead of a single chord it played every note within what was supposed to be a bar or two of chords all at once. (All I had to do was re-save my MIDI with the 960 timebase as your thing exports, to workaround that.) At the moment I'm not in front of my MIDI keyboard at home so it's pretty easy to notice notes being missed when trying to record on-tempo with a typing keyboard. Heh.

Thanks very much again, there's perhaps a dozen uses for a handy tool like this if one knows how to get it working in their rig. From breaking composers block to a live performance partner (whether it be cheating or if you're a drummer wanting to play "chords" or "melodies" too. )

[MaliceX]

Benching this in Jeskola Buzz, seemingly quite fun to toy around with hahaha.

FR: Saving loaded patterns to project? (Recalling patterns on project load, current empty.)

That's all I can think of right now, No actual bugs otherwise.

[insertpizhere]

the next update will read the timebase of imported midi files. will hopefully recall patterns too.

[MaliceX]

Alright, found a recording bug.

Given the settings:
REC CH: ANY (Recording from Channel 10)
TRIG KEY: 51
TRANSP: 0
OUT CH: 1

After recording, when triggering the recorded notes, output passes to Channel 10 instead of the Output Channel (which is 1). (ie: Recorded notes ignore Output Channel setting).

EDIT: However I must say I think this could be seen as a "workaround/accidental feature" to obtaining independent outout channels for each pattern. Very handy. (Currently 'attempting' to jam with ELP's "Tarkus" with midiStep on keyboard drums)