about XY Morph example (to bsork )
Hi nay-seven, nice to know that some found this patch useful, and I will try to have a look at it sometime in the near future, but I can't say exactly when. Troubles after a water leakage in the house and "crisis after crisis" at work takes too much time, ouch! 
The last version had some changes done to the handling of arrays, so that might be the cause(?). Anyway - although I don't remember much of the patch - I've learnt a lot about arrays in Usine since I created it, so I figure that finding a solution won't be a big problem.
The last version had some changes done to the handling of arrays, so that might be the cause(?). Anyway - although I don't remember much of the patch - I've learnt a lot about arrays in Usine since I created it, so I figure that finding a solution won't be a big problem.
Bjørn S
thanks , no problems , take your time...
hope all will be better soon for you , sometimes life is more a square osc than a sinus one.....
gone to see deeper myself too..
hope all will be better soon for you , sometimes life is more a square osc than a sinus one.....
gone to see deeper myself too..
Hi again, I've taken a look at it, and there seems to be something strange about the output of the array modules so that they only output the first value until something has been updated. While testing various workarounds, I also experienced that the one module I experimented with would either not be updated with the mouse, or if I had randomized the values, the array would return to have only one non-editable value when I clicked it to draw in new values.
I suspect that the changes done to the arrays in 3.66 is reponsible for the trouble. Any comments, Olivier?
Anyway, I exchanged the array modules with step modules which works as expected, with the added bonus of extra colours and lines in the interface. You can find the updated patch "XY Morph 2" in Add-ons/data tools. I removed the old patch.
[EDIT]:
I think that the script could be a bit better too, "spreading" the CPU load better to avoid some of the rather spikey behaviour it has. I'll upload another version within the weekend or something like that.
[/EDIT]
I suspect that the changes done to the arrays in 3.66 is reponsible for the trouble. Any comments, Olivier?
Anyway, I exchanged the array modules with step modules which works as expected, with the added bonus of extra colours and lines in the interface. You can find the updated patch "XY Morph 2" in Add-ons/data tools. I removed the old patch.
[EDIT]:
I think that the script could be a bit better too, "spreading" the CPU load better to avoid some of the rather spikey behaviour it has. I'll upload another version within the weekend or something like that.
[/EDIT]
Bjørn S
great ! thanks bsork , this one seems to work fine 
In the add-ons section, I have deleted version 2 and uploaded a new one, surprisingly :rolleyes: called "XY Morph 3". I have rewritten the script so that the CPU load is more evenly spread.
The difference is that now the parameters/array elements are always read and updated sequentially one at the time instead of just when something had changed in the XY module. In the old script, the whole program only did something every nth execution block (I had chosen every 10th block, but that could easily be changed), and if the XY values had changed, all 16 parameters were updated at once. This lead to a "spikey" CPU usage, whereas the new variety might draw some more CPU power as long as the user doesn't update anything, but will also not use significantly more power when some of the data change.
The difference is that now the parameters/array elements are always read and updated sequentially one at the time instead of just when something had changed in the XY module. In the old script, the whole program only did something every nth execution block (I had chosen every 10th block, but that could easily be changed), and if the XY values had changed, all 16 parameters were updated at once. This lead to a "spikey" CPU usage, whereas the new variety might draw some more CPU power as long as the user doesn't update anything, but will also not use significantly more power when some of the data change.
Bjørn S
you're the best ! gone to test it today
many thanks bsork !
many thanks bsork !
another goo idea I'll try it soon;
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Who is online
Users browsing this forum: No registered users and 18 guests
