Chris,
I think your idea is great!
Andi
Chris Smith wrote:
Yeah, Bob, and a few other folks had that suggestion which is a
brilliant workaround. It's definitely doable for some sliders.
Here is part of what I wrote to Avid as my thoughts on it:
...Obviously you can create node tree structures and save them as a
preset, but without a custom UI it defeats the purpose to have a handy
tool.
Like my Shake nodes that I made are not revolutionary, but they made
work far quicker because I did the work upfront creating the node
trees for a specific result and made a specific User Interface that
quickly tweaked internal parameters that do something.
This way an end user that doesn't know how the internal node structure
is done can use the effect quickly. And even if you know how it was
made, grouping the 4 parameters you will actually use in one window
makes things so quick and elegant.
Example. When Aviator came out, on several forums some folks
(including myself) were obsessing on how they recreated the 3 strip
Technicolor process. After many days of searching through some
original Technicolor specs, I recreated a pretty complicated node tree
in Shake that simulated it amazingly well. So then I took the 5
parameters that came from many, many nodes that would mean something
and created a custom front end. Then gave it away to other users. If
I couldn't make a front end, I would have to have written quite a ref
manual just so someone could use it. But more importantly, it
wouldn't be an efficient tool anymore to the original user because you
would spend 80% of your time sifting through node parameters rather
than quickly tweaking the few that matter all at once.
A few folks on the DS list had the great idea of using a composite
node to have arbitrary sliders to link to parameters. But I wonder,
how hard would it be for the Avid team, to at the minimum, create a
simple widget node? It's only special powers would be to be able to
work as the front end node that you see where there is usually the
blank parameters page that talks about expanding the tree to see
what's inside. And allowing some simple nameable sliders and
buttons. I realize that color picking would be a bit harder, but if
you just had a color well that when you clicked on it either brought
up the system color picker or much better a temporary viewer with a
color 'disc' that you can grab a color from.
So just my .02 is that adding these "simple" changes could really mean
a lot more effectiveness out of the effects tree and inspire more talk
and exchange among DS users with ideas and presets (or custom nodes).
Well, at least that's what I think :)
*Chris Smith*
*Partner/Film Director*
*Sugar Film Production*
*3699 McKinney #222*
*Dallas 75204*
*214.655.2662*
*http://www.sugarfilmproduction.com*
On Sep 29, 2005, at 5:47 AM, Tony Quinsee-Jover wrote:
" Man, if they just give me the ability to create custom UIs as a
front end to custom node trees like Shake I won't complain myself at
least for a few weeks ;)"
Hi Chris,
For now, just use a Composite Node, name each input whatever you want
it to be, then use Expressions to link those controls to whatever you
wish.
Voila! Instant Custom Node
Regards,
Tone :)
--
Andi Loor
www.andiloor.se
---
Subscribe? E-mail Majordomo(at)Softimage.COM with the following text in body: subscribe ds
Unsubscribe? E-Mail Majordomo(at)Softimage.COM with the following text in body: unsubscribe ds
