![]() |
|
#1
|
||||
|
||||
|
FFRend now supports plugin authoring, which means you can export a FFRend project as a Freeframe plugin. The exported plugin is called a metaplugin, because it uses other plugins as components. A metaplugin can be used in any Freeframe-compatible host application, and behaves as if you were running the equivalent project in FFRend.
It's been quite an ordeal. Thanks to everyone who helped beta-test this release, and special thanks to KillingFrenzy for suggesting the idea in the first place. I'll post some metaplugins soon... Download: http://ffrend.sourceforge.net/download.html Documentation: http://ffrend.sourceforge.net/Help/M...etaplugins.htm ck |
|
#2
|
||||
|
||||
|
Brillant!!!
Ive been building some freeframes, its so useful for resolume.
|
|
#3
|
||||
|
||||
|
ok, bear with me for a moment, but I'm trying to make some plugins with metaffrend and I think I've hit a stumbling block. Is it true that for for a metaparameter you can only have one target parameter? If so, this needs to be changed. As an example, I'm trying to have four little fisheye lens move in four different directions/ranges using a single parameter. Without the ability to map a single metaparameter to multiple individual plugin parameters this isn't going to be possible. Condensing a bunch of parameters into a few would seem to be the point of a metaparameter. Otherwise, you've just got the same parameters and no way to "simplify" a complex plugin.
Please set me right if this is not the case. Apologies for not fiddling sooner, I've been out of the country/away from the computer.
__________________
~~~~~~~~~~ ~KillingFrenzy~ ~~~~~~~~~~ |
|
#4
|
||||
|
||||
|
I thought.. metaplugins.. so what... but its really useful! Thanks!
If you'll need any help with GUI graphics, tell me I'm here just for you!
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|