Re: [Qtractor-devel] DSSI Plugin on audio track mono, and some other (more DSSI specific) questions

[Rui N. C. <rn...@rn...>]

On 01/12/2010 06:19 PM, Mathias Krause wrote:
> 
>>> 3. My plugin has some control ports, and they all seem to work fine. But 
>>> i do need a control port output at the plugin, so that a response can be 
>>> sent to the plugin gui (which is also started fine by qtractor). So i 
>>> created a control port as output of the plugin. Now, when i change the 
>>> data of this port from within the plugin, the GUI and qtractor do not 
>>> recognize that the value has changed. Do you know if there's such a 
>>> mechanism?
>>
>> hmmm... now that you speak, there may be an issue regarding dssi output
>> ports--unlike the newer lv2--dssi output control ports are not being
>> marshalled to the gui. in fact, they are being just ignored. i guess, no
>> one (ie. me:) has ever found the need to date, so i never implemented it :o)
>>   
> hm ... only this problem is remaining. How can i send some information 
> from the plugin code to the gui. Unfortunately the plugin is not really 
> useable without the GUI feedback.
> 

problem here is that qtractor as a ladspa/dssi host is connecting all
output control ports into the void. i will address this issue asap. stay
tuned ;)

> How is that solved for the Calf Monosynth Dssi? I can see the filter 
> changing, when i play a note.
> Maybe, the GUI only does receive the MIDI information and then calculate 
> it's own GUI events?
> 
> I think, i am not able to use a input port, and set it directly from my 
> plugin code!?
> 

good question. one could look at the source but i guess the gui is
having a peek on the plugin descriptor and read from the input data
ports directly. hmmm...


> Is there any other method, to send some data from the plugin to it's GUI ?
> 

for an out-of-process gui, as in a dssi gui, i would say there isn't.
but then again, one has to investigate which magic tricks are the calf
plugins using ...

> For better understanding. My plugin does a FFT for the incoming audio 
> data, and the result of that FFT (only one (some) integer number (s)) 
> has to be used in the GUI for making some visualization of what is 
> happening after the FFT as this is a kind of pitch correction (or pitch 
> changing).
> 

will do my homework re. ladspa & dssi output control ports ...

seeya
-- 
rncbc aka Rui Nuno Capela
rn...@rn...