[Dejan]

@theatomicwonder 23806 wrote:

AND if Toxic is so wonderful – do you even need Combustion? I think it’s on it’s way out, but I could be wrong. I mean, it has happened before.

Different price tags, so yes.

[Dejan]

Never, and never seen anything close to that.

What do you mean by “very shape”

Sharp?

In what format are you rendering them?

Are you rendering only the matte or the whole RGBA?

If so, is this premultiplied or not?

Are you dealing with these files in the correct way in Flame?

I don’t know but it sounds like a premult/unmult issue.

[Dejan]

I don’t think so but you can use your depth pass as a matte, and start from there.

Maybe someone has a better solution for this or some spark to deal with depth info in the correct way.

[Dejan]

Almost miss your second question 🙂

Well if your image is not pre-multiplied you should leave that checkbox from the reader unchecked and either use a AddMix node to superimpose your stuff or pre-multiply them before your merge them using a MMult (Premult) node which you can find on the botton bar or in the Merge menu.

Cheers,

[Dejan]

This option is there so you can make sure that when a Nuke LUT is applied to a reader with a premultiplied file Nuke will do the correct process before applying the LUT, which is unpremultiply -> apply the LUT -> premultiply.

You will be able to see the difference on semi-transparent pixels when you have a sRGB lut applied for instance.

I see no reason to check this box if your sequence isn’t premultiplied since you will divide (unpremultiply) something that was not pre-multiplied, and this would be a problem.

Hope it helps,

[Dejan]

Your image doesn’t load here, so I couldn’t say.

As for black borders it’s hard to tell without seeing them but it sounds like a premultiplication issue.

[Dejan]

Glad it helped. But there is some stuff in there that is not needed at all.

As for fmod (x, y) it computes the remainder of dividing x by y. The return value is x – n * y, where n is the quotient of x / y, rounded towards zero to an integer. Check Nuke docs for info on functions that can be used in Nuke.

[Dejan]

You can use those fields to set variables or termporary expressions to be used on the channel expression. The left colum is the name of the temporary expression or variable and the right one (the longer one) is it’s contents.

For instance on those top boxes you can have this:

var1 for the variable name and Ar*Br as the content
var2 for the variable name and Ar/Br as the content

And in the Red Channel Expression box this: abs(fmod(frame, 2)-1)==0?var1:var2
This will check the result of “abs(fmod(frame, 2)-1)” and case it’s “0” it will use “var1” case the result is different from “0” it will use “var2” instead.

This is a really bad example but I think it will give an idea of what is possible.

[Dejan]

You need to indicate A and B inputs with the Channel you want to do the math.

For instance Ar*Br will multiply Red Channel from input A with the Red Channel from input B. Ag*Bg will do the same thing for the Green channel and Ab*Bb same thing for the Blue channel.

Hope it helps.

Cheer,

[Dejan]

He’s saying that if you hit TAB with your line selected you will have access to the vertices of your shape which can be animated.

But for ‘write on’ effects you should use a simple particle emmiter with their emission rates and life changed or the old trick with the Text operator with billions of dots typed and then animated with the Write On parameter.

No direct control for growing lines in c* from one point to another.

Hope it helps.

cheers,

[Dejan]

eltopo wrote:

Could be that Autodesk wants to leave the low end market and concentrate on the high end. they probably see too much competition fom Adobe and Apple. Perhaps they could sell Combustion to the latter

Don’t know man. I kind disagree with that since the concept of high and low end is really thin these days. Apple doesn’t have any app to compete with c* and if you stop to think about compositing and not motion graphics neither do Adobe. Combustion got a nice niche on the market, it’s a versatile tool and I still think they don’t have any reason to stop it’s development unless they come up with something to replace it. Which I guess won’t be Toxik.

Let’s wait and see. If they drop it and leave a empty space it will be a shame but I won’t die.

As for Apple coming with a Fusion, Nuke or even a FFI killer I really have my doubts. After what I saw with Shake’s development (which was kinda ridiculous) I’m not that sure anymore.

[Dejan]

sidewalksurfing wrote:

how could they possibly continure with combustion if they are releasing a stand alone version of Toxic? that would be rediculous. It’s not like there is a established user base for toxic like there is for Max and Maya.

How much this stand alone version will cost?

For what I’ve heard from a discreet reseller is about six times the current price of Combustion. Which would be something around the price range of Fusion and Nuke, and even Shake in a recent past.

To simply put, different market shares. Different products for different needs.

[Dejan]

MiKaEL_T wrote:

Anyone heard anything about combustion 5. There was no info about a new version at siggraph. I also heard rumors Autodesk is going to stop combustion and will replace it with Toxic. Have you heard anything or have an opinion to share ?

The price range difference has a huge difference don’t you think?

I doubt that they will leave a open space for Adobe After Effects, besides C* has a large user base and has a accessible price so I see no reason to stop it’s development.

And Toxik still has a long way to become a useful compositing app if you ask me.

[Dejan]

The only one I know for sure that has these sparks is ILM, but they won’t share it 🙂

I’ve heard of guy that was developing some sparks for Flame to deal with OpenEXR files but I don’t remenber where.

Try to do a search in this forum because I think there was a discussion covering it and maybe it was in there that this guy mentioned it. But in the end I think such thing never became a public release otherwise it would be all over the place.

cheers,

[Dejan]

kuban wrote:

Has anyone seen that flicker and banding problem with 30″ Dell monitors?

This problems seems to be solved with the DELL ##07WFP line. I use a 2007WFP at home and didn’t noticed a single glitch relating banding and flicker.

Check DELL’s comunity forums because it seems there is a way to check the build of your monitor and case it’s the problematic one you can send it to DELL to get a new one.

cheers,

[Author]

Posts