stefano

Hi everybody, i'm using a bline but i just need a integer result.

It seems that bline always generate a float ramp.

Hi everybody, i'm using a bline but i just need a integer result.
It seems that bline always generate a float ramp.
Is it just my problem?


bline-and-integer

that seems to be a bug indeed. from the reference page:

"An argument may be used to set the initial value to be stored and the OUTPUT TYPE for the object..."

Unless the object has been changed and the reference pages wasn't updated, I'd say that could be a bug!

Unless the object has been changed and the reference pages wasn't updated, I'd say that could be a bug!
Anyone??

I suggest that the 'bug' is in the reference page documentation. As far as I know, bline has always output only floats (and it should not now be changed to conform to the documentation because that would break existing patches). If you want to convert its output to int, just pass the output through an int object. --C

Of course using a int obj is the first thing that come in mind,

but the problem is that some time i need to increase or decrease the number just for one step, for example going from 13 to 14 or vice versa. This is the problem because when it increase the float ramp make the next int coming in delay, but when it decrease the int come immediatly...

if we are on 12. the time for going ro 13. is much longer than going to 11.99

however try it on the patch posted by MIB, when u go up or down with the incdec u can see the problem looking at the int.

However thanks to everybody, i just wanted to be sure that the bline was behaving like that with everybody, and not only on my machine.

Of course using a int obj is the first thing that come in mind,
but the problem is that some time i need to increase or decrease the number just for one step, for example going from 13 to 14 or vice versa. This is the problem because when it increase the float ramp make the next int coming in delay, but when it decrease the int come immediatly...
if we are on 12. the time for going ro 13. is much longer than going to 11.99
however try it on the patch posted by MIB, when u go up or down with the incdec u can see the problem looking at the int.
However thanks to everybody, i just wanted to be sure that the bline was behaving like that with everybody, and not only on my machine.
S.


If you don't want the truncating behavior of int, you can round the numbers instead. I think the round object has a bug that makes it malfunction in negative numbers, though, so I use my own rounding expression. Here's one that rounds the way I think you want.

bline and integer