piz midi plugins (windows/linux/mac)
-
- KVRAF
- 5350 posts since 8 Aug, 2003 from Berlin Germany
-
- KVRist
- 443 posts since 13 Feb, 2006
great! thank you
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
http://thepiz.org/xt/midi2qwerty_test.zip
here's a version to test. to get around the problem, i made it so that a noteon will send a keydown, and noteoff will send a keyup. this works pretty well.
i'm not sure of the best way do it with CCs, though.
in this build, in "CC (127)" mode, it will send an instantaneous keydown/keyup when it receives a value of 127 (same as before). "CC (0)" works the same way.
in "CC+ (>64)" or "CC- (<64)" modes, it will send a keydown when it gets a value in the range, and send a keyup for values outside the range. 64 is always a keyup. it might be easier to use with a slider if i increase the size of the "dead zone" to 58-70 or something.
let me know if i should add more CC modes to make it useful with existing midi controllers.
(edit - added "CC (0)" mode and re-uploaded)
(edit2 - there was a rounding problem that made some keys inaccessible. fixed and re-uploaded.)
here's a version to test. to get around the problem, i made it so that a noteon will send a keydown, and noteoff will send a keyup. this works pretty well.
i'm not sure of the best way do it with CCs, though.
in this build, in "CC (127)" mode, it will send an instantaneous keydown/keyup when it receives a value of 127 (same as before). "CC (0)" works the same way.
in "CC+ (>64)" or "CC- (<64)" modes, it will send a keydown when it gets a value in the range, and send a keyup for values outside the range. 64 is always a keyup. it might be easier to use with a slider if i increase the size of the "dead zone" to 58-70 or something.
let me know if i should add more CC modes to make it useful with existing midi controllers.
(edit - added "CC (0)" mode and re-uploaded)
(edit2 - there was a rounding problem that made some keys inaccessible. fixed and re-uploaded.)
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRist
- 443 posts since 13 Feb, 2006
the >64 <64 mode does not work properly with encoders... this has to work the same way it works with 120&0 mode, sending instantaneous keypressed.
it can work with buttons that send cc-on and cc-off, but not with encoders.
noteon=keydown, noteoff=keyup works well with scrollbars controlled with buttons\notes but not with cc's.
regarding analog faders\pots, a deadzone from 27 to 100 could be used for keyup and the two cc ranges 0-27 and 100-127 could be used as keydown triggers for two keys
impossible to insert the value 92... if i try to type 92 the plug recives 117..
it can work with buttons that send cc-on and cc-off, but not with encoders.
noteon=keydown, noteoff=keyup works well with scrollbars controlled with buttons\notes but not with cc's.
regarding analog faders\pots, a deadzone from 27 to 100 could be used for keyup and the two cc ranges 0-27 and 100-127 could be used as keydown triggers for two keys
impossible to insert the value 92... if i try to type 92 the plug recives 117..
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
i guess i'll make 6 settings for CCs:-PIKU- wrote:the >64 <64 mode does not work properly with encoders... this has to work the same way it works with 120&0 mode, sending instantaneous keypressed.
it can work with buttons that send cc-on and cc-off, but not with encoders.
noteon=keydown, noteoff=keyup works well with scrollbars controlled with buttons\notes but not with cc's.
regarding analog faders\pots, a deadzone from 27 to 100 could be used for keyup and the two cc ranges 0-27 and 100-127 could be used as keydown triggers for two keys
CC >64, CC <64: instantaneous keydown/keyup on any value in range
CC 127, CC 0: instantaneous keydown/keyup
CC >100, CC <27: "slider" mode - keydown, with keyup dead zone between
for the sequencer scrolling in XT2, you'll have to use notes or the CC "slider" mode.
http://thepiz.org/xt/midi2qwerty_test.zip
in XT2, there will be 27 missing values, because it only lets you get to 101 values. when you type in a value, you're accessing the range mapped to integers 0-100. i'm hoping jorgen will fix this and at least allow 128 values like in XT1.impossible to insert the value 92... if i try to type 92 the plug recives 117..
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRist
- 443 posts since 13 Feb, 2006
i'll test it soon.
regarding the mouse buttons triggering, do you think it's possible? i need the right muse triggering
regarding the mouse buttons triggering, do you think it's possible? i need the right muse triggering
-
- KVRAF
- 1529 posts since 12 Jun, 2004 from Portland, OR
I tried the midiaudiotocc vst and it shows up in Live/OS X.
I put it on an audio track playing a drum loop, then made a new midi track and was able to select midiaudiotocc as the input, but no midi was being output?
I tried squirreling around with the midiaudiotocc parameters, but no luck...
I put it on an audio track playing a drum loop, then made a new midi track and was able to select midiaudiotocc as the input, but no midi was being output?
I tried squirreling around with the midiaudiotocc parameters, but no luck...
-
- KVRAF
- 2427 posts since 16 Jun, 2005 from Somewhere, NV
Just to be sure, kodama, are you using the latest pizmidi20071031? There are special inst. versions of the plug for use with hosts like Live.kodama wrote:I tried the midiaudiotocc vst and it shows up in Live/OS X.
I put it on an audio track playing a drum loop, then made a new midi track and was able to select midiaudiotocc as the input, but no midi was being output?
I tried squirreling around with the midiaudiotocc parameters, but no luck...
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
i see the problem... i forgot to add audio outputs to the instrument version of midiAudioToCC. Live needs that for some reason. i'll upload a new version in a few minutes.
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
it's possible, but i'll have to use a different method than i use for sending keyboard events, so it'll take some work.-PIKU- wrote:i'll test it soon.
regarding the mouse buttons triggering, do you think it's possible? i need the right muse triggering
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRAF
- Topic Starter
- 2237 posts since 12 Nov, 2002 from swordfish
updated windows and mac builds (linux coming soon) including the fix for midiAudioToCC in Live:
http://thepiz.org/xt/pizmidi20071101.zip
http://thepiz.org/xt/pizmidi20071101.dmg
http://thepiz.org/xt/pizmidi20071101.zip
http://thepiz.org/xt/pizmidi20071101.dmg
wrongtastic, baby
tucson's number one gothic rock band since 1995
tucson's number one gothic rock band since 1995
-
- KVRist
- 443 posts since 13 Feb, 2006
great!it can be very usefull for touchscreen users in some conditions.insertpizhere wrote:it's possible, but i'll have to use a different method than i use for sending keyboard events, so it'll take some work.-PIKU- wrote:i'll test it soon.
regarding the mouse buttons triggering, do you think it's possible? i need the right muse triggering
the mousewheel messages sending is very usefull too
-
- KVRist
- 443 posts since 13 Feb, 2006
you could limit the input values to 100... so there won't be lacking numbers untill the limitinsertpizhere wrote:
in XT2, there will be 27 missing values, because it only lets you get to 101 values. when you type in a value, you're accessing the range mapped to integers 0-100. i'm hoping jorgen will fix this and at least allow 128 values like in XT1.