It's generally good practice to take that into consideration, as it can in some cases can cause issues with math. If you want the right order you should probably set both values first, before doing the division. So in the case for the image you are posting, the order is: Order of execution goes from left to right and top to bottom. Though the order of execution in Axoloti should also be taken into consideration. I know other had issues with this too, it takes a little while to get used to.įor the image, yeah that looks about right for division, if you want to divide 1 with 2.1. This is one of the sides of Axoloti that creates some confusion and took a while for me to get used to. Axoloti uses mainly variable types like int32_t(for dials), integers for number boxes. You can use them, but you need to do some conversion. In Axoloti you don't have to think about that, as all inlets are hot, control rate is updated 3000 times a second and audiorate is updated 48000 times a second.Īxoloti doesn't actually use floats as main variables.
So you always have to set the right inlet first and then send value to the left input and that is basically what's the trigger bang float is used for here. The right value is stored until a value is send to the left inlet and then you get the result. In control rate objects, like the division object you are using, the right inlet is COLD inlet, which means its not actually processed before you do something to the left inlet. The reason for having to to this in Pure Data and Max is because objects has hot and cold inlets. What happens on the right side of the image you posted, where you are using the trigger bang float object, first you set the incoming value to the float output, and then you trigger the "1" value from the bang output, to get the result. The data will be processed in this order: If Max works the same as Pure Data, which I am pretty sure it does, the order of processed output is right to left. For a trigger bang float, all it does is create a specific order of how the outputs of the object is processed.
0 kommentar(er)
