Input from Plugins

[P. Short]

Is there any way to have a plugin generate event data, rather than just consuming it?

Right now I'm thinking of filter applications, where the plugin receives data from somewhere or other (perhaps an output channel), and modifies it to create new channel data. An example would be a plugin that creates RGB waveforms for a throbbing heart with amplitude determined by the output channel (this is what would be editted in Vixen), and feeds it back to vixen for output on various other channels. This could also be used to implement dimmer profiles.

--

Phil

[teberle]

Phil,

Not sure I am folloiwng, do you want to receive something from vixen, modify then send it to a piece of hardware?

Tony

[wingrunr]

Well it seems that the current version of Vixen reads the program data on the fly. I say this because you can change parts of the sequence and Vixen will reflect those changes without a stop/restart of the current sequence. If your plugin parsed its input fast enough and inserted the data into the Vixen sequence before the Vixen parser gets to it, I guess it would be possible. I'm not sure if it's possible to access that part of Vixen yet, however.

[A Marchini]

Phil,

Not sure I am folloiwng, do you want to receive something from vixen, modify then send it to a piece of hardware?

Tony

We had a discussion on this, what Phil is looking for is a preprocessing plugin system. Basically the ability to pipe data from vixen, through a filter program and back to another plugin for actual output.

So you could , as in the example, create a plugin that took vixen values, then on the fly would fix them up on a curve for proper brightness output.

Another tool could capture the stream of on/off values and create a "twinkle effects" on a channel, for output to a dmx or renard.

Tony M.