[PD] VST plugin host

[patrice colet]

Hello,

  DLL's needs a win32 API to work, and this is provided by wine server 
under linux.

DLLs that could be opened on both win32 and linux have to be compiled 
for both platform, it's very rare.

On the link it says that you need wine server anyway...

You might want to try fsthost instead of a PureData external?

Le 01/09/2016 à 13:00, Vincent Vanbesien (DIEHCO) a écrit :
> Hello,
>
> So, it seems that puredata does not send all note off to the vst 
> plugin instrument. I would like to try newest source.
>
> Is it possible to host vst instrument file .dll in puredata under 
> linux (and without wine) ? (One old post trouble me 
> http://recording.org/threads/vst-under-linux-is-real.9979/)
>
> Under Linux, I downloaded sources, I can compile pd using autotools 
> and flext using the build.sh script and now I am looking for compiling 
> vst... build.sh seems not so easy to execute for the external.
>
> *Vincent VANBESIEN*
> Le 30/08/2016 17:03, Vincent Vanbesien (DIEHCO) wrote :
>> hello,
>> I did some print before and after the object [pack 0 0]
>>
>> For the [notein] with m-audio keyRig 49, inputs and outputs are 
>> coherent. But not for the BCF2000 switches and [ctlin] (anyway it was 
>> just a testing for the latest).
>>
>> Finally, the problem seems come from the vst~ that miss some event 
>> when releasing (note 0) (but also sometimes when pushing). It is easy 
>> to reproduce pushing only 2 keys. I understand that the VST plugin 
>> instrument stay in sustain period until receiving again the note 0. I 
>> tried with different plugins.
>>
>> My config is windows 10, puredata 0.43.3 and vst~.dll is from this 
>> page : http://grrrr.org/data/dev/ext/windows/pd/
>> Should I compile the whole with newest source for puredata ? from 
>> cygwin or Microsoft Visual C ?
>> regards,
>> *Vincent VANBESIEN*
>> Le 30/08/2016 12:59, IOhannes m zmoelnig a écrit :
>>> On 2016-08-30 12:20, Vincent Vanbesien (DIEHCO) wrote:
>>>> 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.
>>> i'm not sure whether i can parse this.
>>> [notein] will first output on the right outlet and then on the left
>>> outlet, so the [pack]ed message will be correct (as it only outputs the
>>> list after the left inlet is filled - which happens after the right
>>> inlet got it s data).
>>>
>>> i don't know where you get your [ctlin] from (you haven't mentioned it
>>> before). but anyhow: in MIDI each event is atomic (so a note-on event
>>> cannot be interrupted by a control-in event), but the sequence of
>>> arrival is defined by the sender: so if you first send your ctlin
>>> message and then your note-on, then the ctrlin even will naturally
>>> appear before the note-onl.
>>>
>>> in any case: Pd makes it easy to synchronize messages: use
>>> hot/cold-inlets and triggers (this is probably the single most 
>>> important
>>> thing to understand about Pd)
>>>
>>> fgm,asdr
>>> IOhannes
>>>
>>>
>>>> *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
>>>>
>>>> _______________________________________________
>>>> Pd-list at lists.iem.at mailing list
>>>> UNSUBSCRIBE and account-management ->
>>>> https://lists.puredata.info/listinfo/pd-list
>>>
>>>
>>>
>>> _______________________________________________
>>> Pd-list at lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management -> 
>>> https://lists.puredata.info/listinfo/pd-list
>>
>>
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> 
>> https://lists.puredata.info/listinfo/pd-list
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list

-- 
Patrice Colet
fr: 0632660357