- This topic has 12 replies, 11 voices, and was last updated 10 years, 6 months ago by .
-
Posts
-
Hi guys,
Is there a way to export a Flame set-up into nuke ?
(sparx not included of course)Thank you.
A long long time ago Nuke had a ‘Action’ node.
I think DD had to take it out due to legal reasons but im not 100% sure about that.the node still seems to be there but I am not sure what t would actually support or how well it works !
t.
@aneks 23532 wrote:
the node still seems to be there but I am not sure what t would actually support or how well it works !
t.
Well, in 4.7v2 there’s no action node per se. The thing is, you do have cards with a trans geo node which are working in screen space with 1 equal to the full width of the render size.. Axis… I believe works in screen values as well. Cards support bilinear as well as bicubic transformations so that will roll over with a little massaging. You then have trilinears (deforms) support for projectors, cameras, obj/geo, lights and simple shaders and textures. You don’t really have particles (well you do, but I wonder if they could possibly translate over).
Obvioudly the keyer and colour corrector nodes aren’t going to be the same but the rest could in theoory be parsed over to a Nuke scene.
But who has the time…
Best,
ChrisJust a stupid question to ask, I’m thinking about buy Flame, but my friend said ‘why not buy Nuke…, it’s cheaper and there’s nothing Flame can do that Nuke can’t. So, really I just wanna set this straight…, what are obvious pros and cons between the two? Which of the two works on 32 bits float better?
thanks very much
PC@huumingh 29408 wrote:
Just a stupid question to ask, I’m thinking about buy Flame, but my friend said ‘why not buy Nuke…, it’s cheaper and there’s nothing Flame can do that Nuke can’t. So, really I just wanna set this straight…, what are obvious pros and cons between the two? Which of the two works on 32 bits float better?
thanks very much
PCPerhaps you can give a small idea of what you wanna do with the Flame/Nuke.
Second question …are you sure that you wanna buy a Flame? I mean normally people know very well of what it is capable of before they spend some 150K on a VFX-System.why not research the forums first ? i think this question has been asked several times over the years.
@7even 29413 wrote:
Perhaps you can give a small idea of what you wanna do with the Flame/Nuke.
Second question …are you sure that you wanna buy a Flame? I mean normally people know very well of what it is capable of before they spend some 150K on a VFX-System.@rohit 29419 wrote:
why not research the forums first ? i think this question has been asked several times over the years.
… and what was the conclusion?
@7even 29429 wrote:
… and what was the conclusion?
As with everything, it depends what you need the software to do.
Nuke excels at VFX work where a comp team will work on a selected VFX shots for days/weeks/months.
Nuke is really at home working with CG render passes, especially .exr files.
It has superb customisation support through Python and TCL scripting, gizmos (macros in Shake-speak) and the NDK (Nuke SDK for plug-in development).
It is optimised for wall-to-wall 32-bit float “linear light” support.
Full support for RGBA (and more!) channels throughout the app.
Elegant tools for stereoscopic workflows.
Optimised for good interactivity even on modest hardware through the viewer only rendering what you see (either rendering a region of interest when zoomed-in or line skipping when zoomed-out).
Since Nuke is supported on all 3 major platforms (Win, Mac, Linux) on various hardware, it’s quite easy to leverage existing 3D render farms to support Nuke.
Bigger VFX shops seem to be all moving to Nuke (ILM, Digital Domain, SPI, Framestore, Animal Logic, MPC, etc…)Now that Smoke Advanced has a batch module, I really don’t know who Flame is targeted at. It would seem that Smoke is the new flavour of the month for advertising/client driven/lots of tape IO sessions. And I honestly haven’t heard anybody getting Flames for film VFX work in a while now.
Anyways, Smoke (or Flame) excels at one-man-band client-driven sessions that involve lots of tape IO (as in the client walks in with a stack of HDCAM tapes and expects to walk out with tapes for 4x 30-second spots, ready-to-air, in 2 days).
Since Smoke is really an editing/finishing tool, it obviously blows Nuke (non-existent) editing tools out of the water.
Smoke has a great disk-based clip player. No cacheing to RAM necessary to play long clips like FrameCycler.
It has a 2d tracker that’s very efficient at locking onto tricky targets.
The color correction tools like Color Warper feel a little bit more polished than Nuke’s.
The interface is really wacom-friendly with big buttons and minimal use of right-clicks and double-clicks.
Seasoned editors seem to like the way the app is laid out and the one-stop shop mentality of Smoke / Flame.–Xavier
If you can keep a flame busy it will make you a lot of money.
Now that I think about it, if you can keep a Nuke station (or thirty, for the money) busy you’ll be doing fine as well.
They both do the same stuff in a software sense: keying, roto, comping, color correction. There may be a few modules in Flame that are better than Nuke (and vice versa), but no where near $300,000 worth or whatever the price difference is. Flame’s are good for client-y stuff, and the operators generally have more refined client skills due to the nature of the job.
You can grade in Apple Color and you can grade on a Baselight, for a relative analogy.
As to your specific question, Nuke is better at 32bit float.
Another way is to buy an Avid DS, which has a floating point node compositor, uncompressed timeline, and realtime R3D/color corrector support, and run Nuke along side to do the tricky stuff.
Just a thought. 😉
Another way is to buy an Avid DS, which has a floating point node compositor, uncompressed timeline, and realtime R3D/color corrector support, and run Nuke along side to do the tricky stuff.
Just a thought.
Excatly what i do – Nuke displays on my broadcast mon, as it sees the Aja card, and runs renders off the SAS array, render out DPX from Nuke and DS runs them native & instantly
They complement each other well.. DS has the tools that Nuke lacks, Nuke runs rings around DS in complicated comps, DS is light years faster on simpler comps.
d/
the DS option is nice to run with nuke.
- You must be logged in to reply to this topic.