piz midi plugins (windows/linux/mac)

[insertpizhere]

Thanks a lot, I'll try the updated version. The Thru mode for notes not converted to CC might just be it.

So this preliminary Thru mode you just added, what does it let thru if not the notes not converted to CC?

well, i just added the other mode.
http://thepiz.org/xt/midiNotesToCC.zip

now the current thru modes are:
Off - doesn't send through anything, only sends out converted CCs
Unconverted - only blocks notes that are being used as CCs
Yes - sends through everything in addition to converted CCs


let me know if you can't get it to do what you want.

[glObalist]

Thanks a lot, I'll try the updated version. The Thru mode for notes not converted to CC might just be it.

So this preliminary Thru mode you just added, what does it let thru if not the notes not converted to CC?

well, i just added the other mode.
http://thepiz.org/xt/midiNotesToCC.zip

now the current thru modes are:
Off - doesn't send through anything, only sends out converted CCs
Unconverted - only blocks notes that are being used as CCs
Yes - sends through everything in addition to converted CCs


let me know if you can't get it to do what you want.

It seems to be working now, good job man, I can finally hear the sounds. But

1)it seems to be polling for the note-on event at too long intervals, which results in me pressing the hat pedal and it only some times converting the note to the CC message. Seems quite random to be honest.

2)it would be nice if it also included a note-off setting of sorts. What I'm trying to do is to convert note 44 (hat pedal; stupid Yamaha made this a note instead of a Note AND CC event) from my Edrum to act as CC 64 for this other plugin, which then takes a CC message and alternates between the hat pad sound (open/closed)accordingly:



And here my current "semi-working" settings for your plugin:



I tell you I'm never buyig another Yamaha product again, ever

[insertpizhere]

1)it seems to be polling for the note-on event at too long intervals, which results in me pressing the hat pedal and it only some times converting the note to the CC message. Seems quite random to be honest.

that's weird...

2)it would be nice if it also included a note-off setting of sorts. What I'm trying to do is to convert note 44 (hat pedal; stupid Yamaha made this a note instead of a Note AND CC event) from my Edrum to act as CC 64 for this other plugin, which then takes a CC message and alternates between the hat pad sound (open/closed)accordingly:

there are note-off settings, they're the "rest" values. but hmmm... you might want to only convert the velocity to a CC. maybe you could send me a midi file of a few hits on the hi-hat with the pedal open and closed...


edit: i gave this some thought. i think these are the settings you want:



this will convert all note-ons at note 44 to CC 64 at 127, and all note-off 44 to CC64 0. this should work, assuming the "dynamic hat" plugin works right.

[glObalist]

I believe you've done all you could to help me and it's really appreciated.

But I just can't get this to work the way I need it. I'm gonna call Yamaha to see if they have a solution, then return the kit if they don't.

Cheers man!

[insertpizhere]

I'm uploading a version of midiProbability:

http://thepiz.org/xt/midiProbability_0.zip

It has two slots which can affect different step values. Each slot has the following parameters:

Step - Like the quantization grid in a midi sequencer... for example, "16" means notes starting on the 16th note gridlines will be affected by this slot. Go up past "64" and you get "All Notes" which means the grid isn't used (all notes have a chance to be affected).

StepShift - Shifts the grid set by "Step" from 0 up to 100% (the following gridline).

Mode - What to do with the selected notes. Choices: Off, Skip, OctaveUp, OctaveDown, RandTransp, RandVeloc, Channelize, Multi.

Prob - Overall probability for the slot, or how often notes at the selected step will be affected, from 0% (never) to 100% (always). When Mode is set to Multi, the separate effect probabilities are scaled by this overall setting.

The slots are processed from top to bottom. If an effect from the first slot is applied to a note, the second slot will be skipped for that note.

Following the per-slot parameters are the settings for the "Multi" effect probabilities. When "Multi" is selected, these will determine how often each effect is applied. Multiple effects can apply to each note.

For Channelize, there is another setting which determines what channel to use. This can be set to 1-16, or "Random" which will randomly choose a channel for each affected note.


Future possibilities: more effects, more slots, channel per slot, useful presets...

[Optomadic]

WOW! Yes piz this is cool! Can't wait to take for a test run.

Will let you know

[Optomadic]

Everything makes sense! Correct me if I'm wrong, if I set either one of the probabilities to Multi I get all controls in one (or 2 )?

[insertpizhere]

Everything makes sense! Correct me if I'm wrong, if I set either one of the probabilities to Multi I get all controls in one (or 2 )?

that's correct. but if you set them both to Multi, you lose the ability to separately control what each slot does.

[Z3R0T0N1N]

Hi, Piz,

sorry it took so long for me to reply.

you asked what the LFO was doing before the crash - running on free-run mode if I recall correctly, and controlling the phase mod depth of the xt synth.

Interesting, about the asio4all/realtek + crash = bluescreen! I had no idea. But it did that again since my message, and this time I wasn't using a PizMidi, so I think you are on to something there. I think I'm going to drop my Delta44 into this computer.

If you still want that file, just for curiousity's sake, i can send it. Just PM me where to send it to.

Anyway, cheers, and thanks for the info on my setup. Good to know.

-g

[Optomadic]

piz I'm trying to get Midiprobability to make a CC envelope skip with no success. Sorry I should have asked before, does this works with CCs also?

Thanks

[insertpizhere]

you asked what the LFO was doing before the crash - running on free-run mode if I recall correctly, and controlling the phase mod depth of the xt synth.

with what LFO waveform? Tempo or Hz? i'm trying this now...

okay, i just got a crash when i switched from tempo to hz with the frequency turned all the way up. looks like i need more protection with fast waveforms...

before i click "close" on the error message and get a blue screen, i'd better send this.

p.s. sometimes when the crash message comes up (energyXT2 has encountered a problem...), it's still possible to close XT2 and save the project, and then close the error message. sometimes this stops the blue screen as well.

[insertpizhere]

piz I'm trying to get Midiprobability to make a CC envelope skip with no success. Sorry I should have asked before, does this works with CCs also?

Thanks

it only affects notes so far. i did that first because they're more tricky, since it has to remember what it did to each note and then handle the note-off the same way. i'll add a switch to affect CCs as well, and one for all midi events. obviously "octave up" and "velocity" etc. won't have the same meaning, so i'll have some decisions to make...

[sinkmusic]

I'm uploading a version of midiProbability:

http://thepiz.org/xt/midiProbability_0.zip

It has two slots which can affect different step values. Each slot has the following parameters:

Step - Like the quantization grid in a midi sequencer... for example, "16" means notes starting on the 16th note gridlines will be affected by this slot. Go up past "64" and you get "All Notes" which means the grid isn't used (all notes have a chance to be affected).

StepShift - Shifts the grid set by "Step" from 0 up to 100% (the following gridline).

Mode - What to do with the selected notes. Choices: Off, Skip, OctaveUp, OctaveDown, RandTransp, RandVeloc, Channelize, Multi.

Prob - Overall probability for the slot, or how often notes at the selected step will be affected, from 0% (never) to 100% (always). When Mode is set to Multi, the separate effect probabilities are scaled by this overall setting.

The slots are processed from top to bottom. If an effect from the first slot is applied to a note, the second slot will be skipped for that note.

Following the per-slot parameters are the settings for the "Multi" effect probabilities. When "Multi" is selected, these will determine how often each effect is applied. Multiple effects can apply to each note.

For Channelize, there is another setting which determines what channel to use. This can be set to 1-16, or "Random" which will randomly choose a channel for each affected note.


Future possibilities: more effects, more slots, channel per slot, useful presets...

WOw , seems to be a cool little pluggie.
THanks, Senor Piz !

[Optomadic]

it only affects notes so far. i did that first because they're more tricky, since it has to remember what it did to each note and then handle the note-off the same way. i'll add a switch to affect CCs as well, and one for all midi events. obviously "octave up" and "velocity" etc. won't have the same meaning, so i'll have some decisions to make...

Ok wheww thought I was loosing it for a sec there.. Don't rush, take your time if you have other things to deal with !

[insertpizhere]

i'm actually working on a number of things. i've updated midiProbability with CC support, along with some new plugins, including:

midiPolyphony - Mainly for spreading polyphony across midi channels, i.e. if you play 4 notes, each one will go to a different channel. Polyphony per channel can be set from 1 to 16 notes for more flexibility. You can also use it to convert polyphonic input to monophonic output.

midiModulator - Use one CC to modulate another CC (or note velocity) in various ways: add/subtract/multiply/etc, plus logic gates (AND, NAND, XNOR, etc).

midiCCToggle - For changing momentary CC buttons into toggles.

once i get these finished and compiled for all platforms, i'll do an "official release" of the package.