Discussion; Nuke import UI

While enjoying using Nuke, I’m suprised at the hardcore line cmd nature of the import UI. To get just simple DIR lists seems a little rigid to me.

And the font import element in the text node is nothing more than a windows fontfile list – it’s like something from the Middle Ages (note to self: check if they had computers in Middle Ages)

I’m not expecting the imort userface of c/f/f/i* (to me one of the useful and elegant file importers, with added scrubbing) nor do I expect to flip through fonts in an interactive way (dont I? Why don’t I ??… it’s not unreasonable…) – okay, actually, I do now, here in 2010, expect to flip through fonts in an interactive update way.

And to pre-empt answers of
‘Well, pipeline compositors only need DIR UI’s because all their footage is on a server", well, thats fine, but my pipeline consists of two, and both of us like to at least see – if not scrub thru – a shot before loading it, especially when all the file names are just a bunch of frame references, and it’s late, and it was a bad idea to open a beer just to see us through the last few shots.

and as for…

"Only motion graphics programs need font utilities"
Well, either you have a text node or you don’t. And if you do have a text node, don’t force me to open up a $20 font viewer to do the job a $3000 compositor just can’t handle!

Seriously, Im a nuke newbie, so am I missing something? Is there a secret UI friendly button I haven’t hit? Does everyone just use a third party script as standard?

Or does the latest compositing kid on the block really want to make me feel like I’m 20 years old again, typing BASIC into a DEC10?

Discuss! 🙂

No Responses to “Discussion; Nuke import UI”

Post a Comment