midiStep bug found on sequencer

[insertpizhere]

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)

actually, i noticed that while i was adding per-pattern output channel selection yesterday... so it should be fixed in the next update. just need to change the GUI before uploading it. you'll still be able to set the output channel to "no change" to use the recorded channel.

[MaliceX]

actually, i noticed that while i was adding per-pattern output channel selection yesterday... so it should be fixed in the next update. just need to change the GUI before uploading it. you'll still be able to set the output channel to "no change" to use the recorded channel.

Sick! Will certainly be looking forward to the next version for sure!

[insertpizhere]

updated:
- out channel works now and is per-pattern
- saves and recalls patterns
- reads timebase of imported midi files

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

[MaliceX]

Yep, workin great on this end. Found one little GUI bug:

At least I've only ever had this happen under Hemann-seib VSTHost, sometimes when changing to pattern 2 (or other patterns, dunno) after having notes loaded between them, sometimes display glitches up. (ie: At that point I'd be clicking pattern 2, it's still highlighted to pattern 1 and the note display is blank, or something)

Pattern saving/project recall confirmed working great! (except on VSTHost but it's most likely a bug on the program itself.)

Per-pattern channels working great too. Sick stuff, kinda feels like cheating playing a single note to scan through what could be a full song. xD

Again thank you for the update on this. I really should send a donation your way but man, it sucks not having a prepaid credit card anymore...

[MaliceX]

Okay, found a few more bugs.

Unticking ACTIVE has no effect. (ie: patterns are always enabled)
Unticking ACTIVE then selecting a different pattern does not highlight selected pattern in blue (but the red highlights.)
THRU notes blocked when using trigger notes that output to other channels. (may be related to ACTIVE bug)
Sometimes when deleting notes, it leaves a very very micro-sized note left behind that's unselectable.

[insertpizhere]

Okay, found a few more bugs.

Unticking ACTIVE has no effect. (ie: patterns are always enabled)
Unticking ACTIVE then selecting a different pattern does not highlight selected pattern in blue (but the red highlights.)

not a bug, just confusing... "active" means that clicking on a pattern number automatically arms the active (aka displayed in piano roll) pattern for recording. otherwise you have to ctrl-click to arm patterns for recording. the blue highlight means it's armed for recording; the red number means it's showing in the piano roll.

THRU notes blocked when using trigger notes that output to other channels. (may be related to ACTIVE bug)

i'm not sure i understand what you mean but i will check it out later.

Sometimes when deleting notes, it leaves a very very micro-sized note left behind that's unselectable.

if i can reproduce this i'll fix it...

thanks for testing!

[MaliceX]

i'm not sure i understand what you mean but i will check it out later.

For example, deactivate the pattern, enable thru mode. Attempting to press the trigger note will result in silence, while every other note is audible. (It still responds in record mode however.)

Record mode bug (tested with REAPER 64-bit version):
When recording in midiStep, notes are placed randomly on the screen rather than along the cursor.

[Mr.Duck]

Sometimes when deleting notes, it leaves a very very micro-sized note left behind that's unselectable.

if i can reproduce this i'll fix it...

This is a really annoying one for me. Having to start all over from the beginning because I didn't save it for like 15 mins.

You hold Alt and click to drag a selection from the beginning of a little box, but instead of dragging to the right, you drag to the left and it leaves behind a note you cant delete. Very fiddly and frustrating.

[Mr.Duck]

Just wanted to say midiStep is pretty great so thanks for that! And a couple of quick requests...

Can you make and option in midiStep so that it plays each note in the sequence while only having to hold down the trigger key instead of pressing it over and over? Tempo could be controlled by host and/or a tempo setting. Maybe an option to play the whole sequence from just one key press too?

Make an option to always start the sequence from the beginning instead of where it left off.

Make the default trigger key = zero on all banks because it blocks that key when you try and play and takes a while to go though all banks you are not using to put the triggers to 0.

Ok thanks and thanks for other little midi tools they can come in very handy!

[insertpizhere]

i'm not sure i understand what you mean but i will check it out later.

For example, deactivate the pattern, enable thru mode. Attempting to press the trigger note will result in silence, while every other note is audible. (It still responds in record mode however.)

well, there is no way to deactivate a pattern so that is probably part of the problem. that part of the GUI is confusing.

Record mode bug (tested with REAPER 64-bit version):
When recording in midiStep, notes are placed randomly on the screen rather than along the cursor.

i've seen that happen as well...

[insertpizhere]

Sometimes when deleting notes, it leaves a very very micro-sized note left behind that's unselectable.

if i can reproduce this i'll fix it...

This is a really annoying one for me. Having to start all over from the beginning because I didn't save it for like 15 mins.

You hold Alt and click to drag a selection from the beginning of a little box, but instead of dragging to the right, you drag to the left and it leaves behind a note you cant delete. Very fiddly and frustrating.

ok, i see what you mean. hopefully i will have time to fix this soon.

Just wanted to say midiStep is pretty great so thanks for that! And a couple of quick requests...

Can you make and option in midiStep so that it plays each note in the sequence while only having to hold down the trigger key instead of pressing it over and over? Tempo could be controlled by host and/or a tempo setting. Maybe an option to play the whole sequence from just one key press too?

Make an option to always start the sequence from the beginning instead of where it left off.

of course, that is part of the plan. if you've ever used the "MIDI Part" of energyXT 1.x, this should eventually have a lot of the same functionality.

Make the default trigger key = zero on all banks because it blocks that key when you try and play and takes a while to go though all banks you are not using to put the triggers to 0.

ok. you could also make a default bank ("midiStep/default.fxb") that has all the triggers at 0.

Ok thanks and thanks for other little midi tools they can come in very handy!

you're welcome.

[insertpizhere]

I just read this thread again and realized I never uploaded a version with all triggers defaulted to 0. I changed that just now and added midi learn for the triggers (set to -1). Also put some info on my website: http://thepiz.org/plugins/?p=midiStep

Soon I'll put in the piano roll from midiLooper, which I originally copied from midiStep but have improved it since.