NathanShirley wrote:

..is the nanoKontrol 2 sending out an automated modulation ...

No it has sliders, knobs and buttons and I just 'ride' one of the sliders and send out CC#1 data to control AfterTouch. Other buttons are set as toggles to put down the 4th pedal or turn on the metronome or set PianoTeq to record... Basic stuff really.

By-the-way - great books for budding students - nice intro to the piano and interesting progression. A great addition to any existing teaching programme !

Oh I see, that makes sense.

And many thanks about the books. That project took a LOT of time away from my regular composition work, but it was a great challenge and I think helped hone my skills for writing very simple yet appealing music. Well hopefully anyway!

..is the nanoKontrol 2 sending out an automated modulation ...

No it has sliders, knobs and buttons and I just 'ride' one of the sliders and send out CC#1 data to control AfterTouch. Other buttons are set as toggles to put down the 4th pedal or turn on the metronome or set PianoTeq to record... Basic stuff really.

By-the-way - great books for budding students - nice intro to the piano and interesting progression. A great addition to any existing teaching programme !

...I do have a KORG nanoKONTROL 2 and used it to transmit control channel data which I then converted in PianoTeq to Aftertouch and with a bit of care got the effect you can hear below...

Very interesting, thanks for taking the time to explain that. So is the nanoKontrol 2 sending out an automated modulation on a per-note basis to control aftertouch? A modulation that you predefined somehow?

In Bitwig I am able to connect an automated modulator to Pianoteq's aftertouch parameter, and it does work, except even when setting Pianoteq to "highest note" it resets aftertouch with each new note played. I think Bitwig's modulator is missing something from Pianoteq perhaps. I'm sure I could assign it to an expression pedal if need be, rather than an automation. But I'll have to save that for another day.

Thanks again.

Bitwig can't use Pianoteq's specific type of polyphony?

I don't have Bitwig and I don't have a keyboard that transmits any kind of Aftertouch...

..But I do have a KORG nanoKONTROL 2 and used it to transmit control channel data which I then converted in PianoTeq to Aftertouch and with a bit of care got the effect you can hear below... Maybe you can do the same in Bitwig? You can assign almost anything to Aftertouch (Pitchbend, Channel mesages, have a look-see)

I include screen shots:

1. PianoTeq mapping (make sure both aftertouch channel and keyboard channel match - ie 16 in this case):
   .
   
   .
   

2. PianoTeq sensitivity altered to suit (you may not have to do this)
   .
   
   .
   

3. Mono Aftertouch set to highest note to separate out effect from sustained notes...
   .
   

   .

..and a sound file:

Poor Bach's "In dem Stück [sehr] bebung" (JOKE !)

So in Bitwig I've just tried connecting the same vibrato LFO to Pianoteq's aftertouch parameter. I hoped this could provide polyphonic control of aftertouch, but in Bitwig's interface 'poly' is still grayed out. Perhaps since Pianoteq's polyphonic aftertouch isn't MPE, Bitwig can't use Pianoteq's specific type of polyphony?

So is MPE a compromise because it would be much more CPU intensive for Pianoteq?

Nothing to do with PianoTeq - it's a compromise based on the current MIDI implementation to allow individual note data to be sent. Note data that would normally be sent on the existing channel, but it is split over several channels - it's main use/conception was initially for guitar string bending I believe ???

By having each string on a separate channel you can bend one string and not affect the others? Polyphonic Aftertouch is much more data intensive and PianoTeq handles that beautifully !!!

Hope that helps.

I was told something along the lines of Pianoteq not supporting full MPE.

That's true !

MPE and Polyphonic Aftertouch are not the same thing...

Here's how you can test Polyphonic Aftertouch in Pianoteq ... by using the onboard keyboard (at the bottom) click the sustain pedal and play a series of notes and while they are still sounding, bend others over the top by clicking them and moving the mouse up and down vertically whilst holding the left-mouse button down (like you do for dragging) only this note will bend (the one highlighted in red) the other will not - that's polyphonic aftertouch.

Monophonic aftertouch would make all notes bend at the same time.

MPE is a compromise where individual note data is sent out on different channels and needs the receiver to recognise this and respond appropriately to it - PianoTeq doesn't.

NathanShirley wrote:

And it would be nice if Pianoteq supported polyphonic aftertouch -- full MPE. Or does it already??

It does already - Enjoy !

Oh interesting. So not to hijack this thread, but when running Pianoteq in Bitwig Studio I've added a vibrato LFO to control Pianoteq's pitch bend. The "poly" button which enables polyphony in other plugins is grayed out for Pianoteq, and I was told something along the lines of Pianoteq not supporting full MPE. If its aftertouch is polyphonic (I don't have an aftertouch keyboard), then I wonder what's going on? My knowledge of MIDI is limited so just trying to wrap my head around this stuff.

And it would be nice if Pianoteq supported polyphonic aftertouch -- full MPE. Or does it already??

It does already - Enjoy !

Hey Smilie,

lets see how you can do with aftertouch effects on damper return function during note-off events.  :-)

We've had this conversation before - here...

They say a picture tells a thousand words...

What you are looking at is the acoustic keypress, the delay before the sensor picks up the movement, the initial calculation for NOTE ON (This is when AfterTouch starts - in red) and note duration, the gradual acoustic key release and finally when the sensor picks up key release (stops After Touch and sends out an arbitrary value for NOTE OFF)

What you get through MIDI (in green) is an approximation of what's actually happening at the acoustic keyboard... As I said before, MIDI in it's current state is not able to do what you'd like.

WHAT YOU CAN DO...
is Beg, Beg, Beg Modartt to read and recognise the full data transmitted from your strip and replicate the actual* key movement of your piano - not the MIDI conversion. Subject to copyright of 3rd Party software - they may not agree to this?

* I say actual (this is wholly dependant on the data detail of your strip).