div module

gentleclockdivider

I am using a counter that goes in a floor division , set to 8
So the div slowly counts upwards , but the bangs it spits out are equal to the counter
How come ?
It seems that the bang module responds to an eventstream that the value module is also spitting out (which is not seen)

This screenshot will make it more obvious

seb-harmonik.ar

because each time the counter increments, the div is still getting a number and outputting a value, triggering the bang.

if you only want to trigger the bang when the value changes you can try to use a [change -1] or something after the [div]

gentleclockdivider

@seb-harmonik.ar said:

because each time the counter increments, the div is still getting a number and outputting a value, triggering the bang.

if you only want to trigger the bang when the value changes you can try to use a [change -1] or something after the [div]

OK , I understand that the division is still sending out a bang , but that is NOT reflected in the number value box , which as youstate is sending out bangs in between .

Edit , so I tried the change module and that is exactly what's needed ' removing repeated number from a stream '
It's weird that this feature is not build into the DIV module , because that's exactly what DIV is about

seb-harmonik.ar

@gentleclockdivider [div] doesn't keep track of previous values sent to it or its previous outputs. it is a very simple object. Keeping track of changes/history in such a low-level object would add some unnecessary overhead in a lot of situations (like if the output is going into a right inlet of a [pack] for instance, or in other numeric algorithms/applications) so the user is expected to do so where necessary

ddw_music

@gentleclockdivider said:

It's weird that this feature is not build into the DIV module , because that's exactly what DIV is about

Normal rule is, if you put something into a hot inlet, the object should produce output, even if it's the same as last time.

There are a few particular objects that "eat" hot-inlet messages: [spigot] and [change] come to mind. But these are exceptions -- not to be taken as a general rule.

hjh