About Me

Not Specified
Not Specified


Recent Forum Posts

Weird decimal behavior in numeric fields Jan. 13, 2017, 3:55 p.m.

Actualy 1 and 0.999…. are not equal and there is no proof, contrary to the assumed proof.

The reason is because one hasn't yet defined 0.999…

By writting 0.999… as is, one is saying it goes on infinitely.

If it's going on infinitely, one has not yet established what that number actually is;

If one doesn't know yet what the number IS, one cannot make a true comparison, whether it is equal or not.

I know I'm being a bit pedantic, but to say both are equal is simply not true and can lead to wrong assumptions about results one gets when writing equations.

1 divided by 3 gives a number that goes on infinitely, one will never get a true finite number from that operation.

It's good to know that there are many instances in which you don't get finite numbers, and in those cases knowing how your software/hardware will handle those situations eg. number of decimal place precision for floating point numbers before they become rounded, or if desired truncated - This, I think is a much more helpful way to look/understand the situation.

Weird decimal behavior in numeric fields Jan. 13, 2017, 10:19 a.m.

It's not a precision error. The solution is to understand why you are seeing what you have.

There are a number of sources that explain it but here is one: []

Alternative to Premier and Davinci Jan. 12, 2017, 10:22 a.m.

Well changing the exr format to none( in Mantra node), rendering a sequence then importing to Davinci gives me the same as what I see in MPLay.

So I'll go with Davinci since it has some nice controls to make subtle adjustments, it's almost like having an extra (post) shader.

Out of curiosity I tried Vegas again and same problems ( and I never mentioned it but I also made sure the resolution was set to the same as what I used for the camera in Houdini - 1280 x 720 ).