![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: sustainBy with Wacom KBD control | |
Phi Curtis Member |
![]() ![]() ![]()
I'm having a minor issue with the Keyboard mode of the Wacom tablet. Attached you'll find a small variation of the AhhReverb sound, in which I am trying to add a sustain pedal mode (here a !Damper hot value toggled by the !PenDown end of the pen). However, when I toggle the !Damper and attempt to play with the eraser end, it is not damped. I can however play on my keyboard and the sound is in fact damped. Please point out my error... thanks, IP: Logged | |
SSC Administrator |
![]() ![]() ![]() Is it possible that !PenDown is not toggling the damper pedal state? You could accomplish this with: !PenDown asToggle IP: Logged | |
Phi Curtis Member |
![]() ![]() ![]() I just realized what the problem is. I was mistaken when I said that the damper wasn't engaged for the Wacom. It was - but the sustain was very low in volume. I needed to adjust my eraser's sensitivity and click threshold. I had been double triggering, and I guess the second trigger was sending a much lower velocity. Thanks for the new syntax for setting event values as toggles - that'll come in handy. I also realized this morning that !KeyNumber (and presumably !Pitch as well) are not being sent by the tablet. That is a little strange, but I guess potentially useful if you want to do different things with the keyboard than you are with the tablet (though I guess different channels could be used to distinguish them as well). IP: Logged | |
SSC Administrator |
![]() ![]() ![]() Hi Phil, I just checked !KeyNumber nn and !Pitch with the Oscillator+DutyCycle KBD prototype and it is working in my setup so something must be different in the way we have things configured. Do you have the eraser end sending the KBD events? (I wonder whether it might be another instance of sensitivity of the pen settings?) IP: Logged | |
Phi Curtis Member |
![]() ![]() ![]() I'm using the eraser end. What test were you using to check that !KeyNumber is being sent? I'll try duplicating it. I just now opened the Oscillator+DutyCycle KBD prototype, and since !KeyNumber wasn't being used in any of the green parameter fields, I put this in the gate field of the AR: !KeyDown gateWhen: (!KeyNumber eq: 60) Sure enough, now it only triggers when I play 4 c on my keyboard, but not the Wacom tablet. If I play the 4 c on the key and then tap on the Wacom tablet, I do get the new note briefly just before the release envelope goes to 0, so I know I'm sending notes (!KeyPitch messages rather than !KeyNumber, presumably) thanks, IP: Logged | |
SSC Administrator |
![]() ![]() ![]() The test I did was to put !KeyNumber nn into the Frequency field of the Oscillator. Maybe you have to round the pitch? That could explain the difference between the keyboard and the tablet: !KeyDown gateWhen: (!KeyNumber rounded eq: 60) [This message has been edited by SSC (edited 28 September 2005).] IP: Logged | |
Phi Curtis Member |
![]() ![]() ![]() Ah, that works! So let me see if I'm understanding what's going on: if I have "intial pitch" as the setting for pitch rounding in the Wacom preferences, Kyma is still seeing the unrounded pitch as the !KeyNumber value? That makes sense. I just realized why in your Wacom template the F is blue (the G would make more sense to me, being the dominant of C): you're being harp-centric! IP: Logged | |
SSC Administrator |
![]() ![]() ![]() "you're being harp-centric!" Or perhaps we just like to root for the subdominant? IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.