On 16/10/14 19:02, Bill Gribble wrote:
Here's a vote for anything (lv2 extension, OSC convention, or something else)
that makes information about how a host is using a plugin available to the
plugin.
This kind of introspection is useless for most plugins, but those that need it
can't get the information any other way.
Indeed, "most plugins" seem to get this in information as to what track
they are in (Calf MonoSynth, randomly) so how do I implement that in "my
plugin"? :)
pX
In MFP [1] I have support for a loading an editable patch as an LV2 plugin. It would be
really useful to be able to find out from the host what channel each instance is on, both
for presentation in UI and for support of automation-type behavior where the plugin might
automate usage of (for example) a hosts OSC API, using its channel number to parameterize
the OSC call properly. This is what I think of as the "max4live" workflow.
Thanks,
Bill Gribble
[1] http://github.com/bgribble/mfp
On Oct 16, 2014, at 11:42, Phil CM <[email protected]> wrote:
Is there a way to retrieve this info (and others, ideally) from the host, thus removing
the need for a "midi channel" control port?
Also, is there a way to tie the "volume" controller of the host (in Qtractor's case, the volume
fader of the mixer strip) to one "volume" control port of the plugin, thus removing the need for
the "control mode" control port ?
Yes because you see, here in my Qtractor (latest SVN - but it has always been
that way) I can either edit the plugin (about 50% of my plugins behave that
way) controls but then the mixer's volume is inoperant, or control the volume
w/ said mixer but NOT the plugins controls. How can I have my cake and eat it?
Ta-ta
--Phil
_______________________________________________
Linux-audio-dev mailing list
[email protected]
http://lists.linuxaudio.org/listinfo/linux-audio-dev
_______________________________________________
Linux-audio-dev mailing list
[email protected]
http://lists.linuxaudio.org/listinfo/linux-audio-dev
_______________________________________________
Linux-audio-dev mailing list
[email protected]
http://lists.linuxaudio.org/listinfo/linux-audio-dev
