posted 06 June 2009 13:40            

This is actually quite involved. The important factor here is that Kyma doesn't give us the raw midi date but instead gives us what we need for mono and poly playing of sounds.

If we look at Kyma mono midi first and soprano only (bass is the same only upside down).
We get !KeyDown and !Pitch (and its variations).
We need to know what is currently the highest played note.
!Pitch gives us the pitch of the most resent note played. Now when we play chords the info is passed one note at a time even if we don't arpegiate the way we play, so we could keep a record of every note that has been pressed and pick out the one with the highest value, but we are missing an important piece of information. We do not know when any of the note have been released. !KeyDown will only tell us when all the notes have been released, but we need to have this info to make it work.

Imagine you play a chord where note 60 nn is the highest note. if you then (while keeping the chord held) played note 59 nn as well you would expect the soprano to stay at 60 nn, but if note 60nn had been released before 59 was played you would expect the soprano to move down to note 59. As we are not given note off info in mono mode this is impossible to do what you want no matter how much capytalk or smalltalk we write.

Now lets look at poly midi as provided by the MidiVoice module.
Here kyma gives us more info from the incoming midi, but is still in a pre organized form.
If we chose a poly of 8 in the Midi Voice it will make 8 invisible copies of any modules on the left of the MidiVoice, and pass to each of the copies a different !KeyDown and a !Pitch. We need all this info in one place as we need to do comparisons between all 8 notes. So we could put a sound to global controller module to the left of the midi voice and make sure that each transmits a different name using VoiceNbr append to the controllers name. We could then turn the !Pitch into nn or use !KeyPitch but replace the value with -128 every time that !KeyDown is off, making use of capytalk logic. This will be transmitted to all other modules in the sound, and we can use one to gather up all the notes info in one place. The reason I say replace nn with -128 during note off instead of zero will become apparent later.

Now if we put another sound to global controller to the right of the MidiVoice module, we can use an 8 cycle capy talk loop which reads out of off an array filled with the 8 controller names. This can do a running comparison to find the vmax: of the currently pressed notes values and this is what gets transmitted from this global controller as the soprano pitch. Also Note On info can be extracted by the " ne: -128" formula. Alternativle you could do long hand formula made of 7 vmax: with the 8 controller names thrown in.

The bass can be done by another sound to global controller using the same 8 global names except it would find the running vmin: of the ABS olute value of the global names. Thats why the note off had to be -128 not zero.

This would take quite a bit of work and I may have missed some anomaly that will get in the way but it may be worth a try.

Hope it makes sense.

Pete

posted 07 June 2009 11:42            

quote:

---

Originally posted by pete:
So we could put a sound to global controller module to the left of the midi voice and make sure that each transmits a different name using VoiceNbr append to the controllers name.

---

quote:

---

Originally posted by pete:
We could then turn the !Pitch into nn or use !KeyPitch but replace the value with -128 every time that !KeyDown is off, making use of capytalk logic.

---

quote:

---

Originally posted by pete:

Now if we put another sound to global controller to the right of the MidiVoice module, we can use an 8 cycle capy talk loop which reads out of off an array filled with the 8 controller names. This can do a running comparison to find the vmax: of the currently pressed notes values and this is what gets transmitted from this global controller as the soprano pitch. Also Note On info can be extracted by the " ne: -128" formula. Alternativle you could do long hand formula made of 7 vmax: with the 8 controller names thrown in.

---

Here again, I´m stuck. If you have time for this, it would be great if you could give me an example of how to build this kind of capy talk loop and running comparison!

Hi Bill, as my knowledge in programming Max is even worse than in Kyma, I´d be glad if this could be done with Kyma...

Thanks a lot!
franz

[This message has been edited by franz (edited 07 June 2009).]

posted 07 June 2009 12:53            

(notein) -> (thresh 200) -> (minimum) -> (noteout)

The "thresh" object will collect all of the MIDI note numbers received in a specified window of time (e.g. 200ms) and send them as a list to the "minimum" object. The "minimum" object outputs the lowest value in that list, which you can then transmit as a MIDI note.

You can also route to a "maximum" object to get both the highest and lowest notes numbers in each chord.

posted 07 June 2009 15:08            

This non-Kyma kludge ( sorry SSC ) may be of some help to you.

apulSoft's apTrigga2 is an audio sample trigger plugin for Mac OS X (VST/AU) and Windows (VST). It supports audio samples in .WAV, .AiFF, and SD2 format. MIDI input Note-On messages are converted to trigger events which makes it possible to play audio samples with apTrigga and a midi keyboard.
http://www.apulsoft.ch/aptrigga/index.php

posted 07 June 2009 16:00            

in Value put

!KeyDown true: !KeyNumber false: -128

in GeneratedEvent Put

('Note' & ?VoiceNumber) asHotValue

hope it helps

posted 08 June 2009 14:27            

Thank you!
Franz

[This message has been edited by franz (edited 08 June 2009).]