[PD] VST plugin host
Vincent Vanbesien (DIEHCO)
electronique at diehco.com
Tue Aug 30 12:20:40 CEST 2016
Thank you IOhannes for the helpfull answer.
However, it seems ctlin and notein outputs are note syncronised then it
happens that the pack object triggered by first argument sends its
output with in second argument the previous/older note.
*Vincent VANBESIEN
*
Le 29/08/2016 10:51, IOhannes m zmoelnig a écrit :
> On 2016-08-29 09:45, Vincent Vanbesien (DIEHCO) wrote:
>> My question concerns the noise~ in input, can I replace it by a midi
>> notein object ?
> no.
> [noise~] produces an audio-signal (a bunch of numbers representing audio
> samples), wheras [notein] produces a message (a high-level structured
> event representing arbitrary data).
>
> not all vst-plugins take midi-notes, but [vst~] might have a way to get
> the available messages you can send to a given plugin (but i don't know
> as i never use it).
>
>> The element named "pd midi" in the patch seems to generate midi and
>> not to receive, is that right ?
> no, actually it documents how to send midi events (e.g. notes) to a plugin.
> the [s $0-vst] forwards all messages it receives to [r $0-vst], which
> sends them to the [vst~] object.
>
> so to answer your question, use something like
>
> [notein 1]
> | |
> [pack 0 0]
> |
> [note $1 $2(
> |
> [vst~]
>
> this will take the note-in data (key and velocity) and create a new
> message with selector "note" and the data and send that to [vst~].
>
> fgmasd
> IOhannes
>
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
More information about the Pd-list
mailing list