manenbu
I did some tests.
First one is trying each of the curves. I pressed middle A on the A300, and pressed down as hard as I could.
Obviously, 4 is totally useless. 1 is crappy as well. I almost maxed out on 3.
Also notice how the initial velocity increases - probably the result of me getting pissed.
Next I was trying to play something (some random notes) with a "real world" attempt of aftertouch. Curve is set to 3.
Well, it's possible. Very hard to control the level, but I guess we are ****ed anyway. So better practice this instead of ****ing about Roland's support.
I must say that I also own an EV-5 pedal, so whatever vibrato I need goes there. AT could be sort of an "on-off" switch for me.
Good goin',
Manenbu - Thanks for doing the screen shots and posts.
Curve 3 is the most sensitive, as shown in the manual's curve chart, which you've also posted. When I try that, if I stand up and push so hard I think I'll break something, then I'll get an intermittent swoop of AT data, like in your picture, but I mean, really intermittently - just on a few scattered notes, not all of them. But for me it's literally impossible to have any kind of reliable consistency with it. It was less hassle just drawing it in the PRV as I did forever before this.
You've mapped AT to a pedal, good solution. What I've done is have a special map with AT mapped to the modulation stick:
--This works for me because my primary instruments are Garritan, and most of those use CC1, or alternately, CC11 for volume. I have a pedal for doing volume via CC11 with those instruments, leaving the mod stick handy for adding good, finely nuanced AT. It works great, and I use it sometimes for non-Garritan instruments also.
Trying to use the spring-action mod stick for volume control with Garritan instruments doesn't work exactly for the reason that it's a spring-loaded thing. My ancient keyboard before Apro, a $50 used generic controller beat the pants off the Apro with its mod wheel because it was free wheeling, no center detent, no spring action. And it could be instantly programmed for any CC controller needed - a much more straightforward proposition than having to make all these various maps for the Apro. BUT - it only had the one assignable control, the wheel.
AT shouldn't be an off/off switch, because there's a big difference between suddenly having full vibrato, and having it go in and out in degrees. The extra spice in Garritan instruments is then to also control the speed of the vibrato, via CC17 which I have mapped to an Apro knob in my special Garritan control map. Having various levels of AT and, if available, degrees of speed - that's what makes samples of real-world instruments come to life.
But, back to the point - AT doesn't work right in the Apro with the default connection to key pressure. It's spotty at best. Happily though, AT doesn't have to be only on the keys. To me there's no problem making another sweep through a MIDI track to add AT data, or any other data, via controls on the Apro or by just digging in and drawing them in the PRV view.
Sadicus, you asked what "Sonar patch" could be used as a test - We've already proven that AT in the Apro doesn't work right, it wouldn't really be a good use of time to discover the same thing all over again. But it shouldn't matter what patch you use anyway. AT is commonly used in a lot of synths and their patches - In theory it should work with anything you want.
Randy B.