I was wondering if there is any way to create input/output pins on a custom node other than Color,String,Transform,Value,etc provided in PluginInterface1.cs? I’d really like to create a plugin in C# where I can use the GDI and DirectShow types. Is there a reason those are not available to developers? Or am I just not seeing them someplace else?
Many thanks!
No, there is no way to create custom (or other) types of inputs/outputs. I think there are many different reasons why thats not possible - but thats a question one of the devs should answer.
in principle all that should be possible somehow.
we just didn’t have the time yet to dig into that matter…
Some kind off Enum support would rock too!! :)
I’d like to have a second video input pin for my freeframe plugin as well. Maybe one of the VVVV or freeframe developers can give us instructions how to implement such customized pin types here in this forum… If it’s impossible to realize even in future releases, this infos would be usefull, too.
enums are in the pipeline, a second video input for freeframe plugs is not very likely to popup in the near future.
may i remind you at SplitCamera?
it is a directshow cameradriver splitter which allows you to use 1 cam with 2 VideoIns. but if i remember well it has some performance needs.
the Software Tool Links are pretty helpful sometimes…
I have to stitch two videoframes of two different cameras together (I could do this using the corresponding VVVV nodes). At least I have to store the result in a texture which can be used as input for my freeframe plugin. Texture inputs are currently not possible, are they? Will it be in the near future? Maybe I can extend freeframe in a way that it supports texture inputs… Can you tell me how to to so (are there any sources how to extend freeframe to support custom input)?
use AsVideo (EX9.Texture)
Oh, of course, sorry…
Another question: is it a limitation of freeframe or of VVVV, that only floats, strings and colors are supported by freeframe? And how does VVVV know, if a dll is valid?
ou, late on that one…
is it a limitation of freeframe or of VVVV, that only floats, strings and colors are supported by freeframe?
the freeframe specification is limited to those types.
And how does VVVV know, if a dll is valid?
freeframe .dlls expose a function called “plugMain”. any .dll that exposes this function is supposed to be a valid freeframe .dll
btw. enums and some more pin-types will available for plugins in betas>20.