Forum Replies Created
Might sound crazy, but try two columns of credits 🙂
Hm. AFAIK Red can’t sync its shutter to a moco rig. So I would imagine the lack of sync between passes is the problem rather than the camera moving… see http://www.reduser.net/forum/showthread.php?t=17002
If that is the case, you may have some luck using a decent retimer to shift the plates in time by less than a frame so they line up.
Or, if you have the latest Furnace on a Flame, the F_Correlate plugin tries to do exactly that for you… I’m not 100% sure whether it will interpolate between frames, which is what you want, but it’s worth a try…
Yeah, I don’t think the 1D LUTs that come with Flame are going to cut it for film work, really, the 10logto12 and 10logto8 ones…
What’s the crack wth FilmVis these days, has that gone from the current releases? I assume you can load one of the Lustre Colour Management cubes to achieve the same thing – import the shots with no LUT, then load one of the display/Kodak 2383 3D LUTs in the viewer…
I’d be interested to hear from anyone at Hydraulx or Peerless or whoever is doing film on Flames these days – are the Lustre 3D LUTs good enough or are you using Truelight boxes or something custom? Anyone working in 16 bit float yet?
You want “time” rather than “frame” in Shake 🙂 Like this:
KeyChew4.soften = time > 691 ? KeyChew5.soften : 0
In Shake you can fool a Move2D into doing it:
o Track your stuff with a Tracker or Stabilize or whatever and leave that node floating around but not in the tree
o Grab a Move2D and link it to the track with expressions on xPan and yPan of Tracker1.track1X and Tracker1.track1Y respectively
o Turn useReference on at the bottom
o Turn motionBlur up to 1 and fiddle with the shutter controls to taste
I really wish you could do this with a Stabilize node – all the buttons are there but sadly they don’t have the same effect. Setting the reference frame to “time” there results in no movement or motion blur at all…
Ouch! You should be able to use find/replace in a decent text editor to remove those extra bits from the XML. Or if you know a UNIX guru you can do that with a shell script.
Lewis, Molinare London 🙂
Just import the 3D for each shot separately and edit it in. Add a layer, then I think you can just move what’s there up then drag the 3D clips to the bottom layer…
I don’t see that it makes any difference doing it with one long clip though, if you’re just using the keyer soft effect on each clip which it sounds like you are…
I would avoid 3:2 more because it looks awful than because it’s hard to work with 🙂 Seriously, pans and wipes can look pretty nasty with pulldown rather than a proper timewarp.
pH, you ARE a colour space freak 🙂 PAL and NTSC use the same YCbCr space right through post, they only change into YIQ or YUV for analogue transmission. The only difference is I think some colours are not legal for broadcast in NTSC which are okay in PAL… check on a vectorscope or a legalizer to be sure I guess.
Yeah, I meant you could copy your original setup, then link every animated channel to the original with an eval(), but that would be a LOT of expressions to type if you have loads of animation 🙂
I guess if you had loooooads of versions to do it would be worth setting it all up with dummy axes for speed and offset, like eval(original_animated_axis.rotation, (dummy_speed_axis.pos.x * time) + dummy_offset_axis.pos.x). Then you could tweak those dummys around to retime and slip everything. Still a lot of typing, though 🙁
If you have a look at the files in the menu folder with a text editor, you’ll find the one with the colours in… it’s long, and a pain to dig through, but it is there…
Motion blur. The ReelSmart spark, Kronos, the new optical flow Motion Blur node in Batch, or at a pinch, just a bit of horizontal-only blur?
Sucks when you have to show the client how much sharpness they lose in the process, and they don’t understand why it can’t be both sharp and smooth… sigh.
eval() is your bestest friend for this.
eval(expression, frame) returns the value of expression at frame. So if you go:
eval(Axis1.rotation, frame * 2)
You’ll get the rotation of Axis1 from double the current time. So that would give you your 30 from your 60, with the animation doubled in speed. For a 45, use frame * 1.333 and so on.
Nah, there is a single line to change for all the blue buttons, it’s just hard to figure out which line it is you have to change 🙂
Xor. Exclusive Or. If one of the inputs is white the output is white but if both are white, the output is black.
It’s like, either, or, but not both.
If you’ve got coloured images it does all this for each channel on its own, so it’s easier to see by looking at R/G/B on their own.
I don’t quite know what the hell it’s useful for however 🙂
Oh wait, you mean the text button colours and that. That’s all in a text file somewhere in /usr/discreet/flame_9.5/menu/… I forget which. Hm… have a dig 🙂 I recall it’s a bit of a battle working out which line affects which buttons.