DSP Robotics Support

Got to vent a bit..
The way Ruby timing works is veeery un-intuitive. Everything get's processed at the same time-slice, even though you trigger them to happen after each other. For example, if two ruby modules receive a trigger from the same trigger button they get processed at the "same time", hence making any parameter exchange between them useless. I've been building modular processing nodes (i can just pile them up x100) and this "feature" has been driving me nuts

There is of course workarounds.. involving time-delayd outputs etc.


If there is better ways to do this, let me know. Like writing stuff up as classes?

matti wrote:..if two ruby modules receive a trigger from the same trigger button they get processed at the "same time"..

sure when you have on source, but there is a triggerordering in the same order you connected the the modules( what was connected first get served first)

there are several ways to take control over your triggers, but without schematic it is difficult to tell

Yes, would be good to see the schematic.
Another potential problem is that "green" and "Ruby" are on different CPU threads - so when you convert between Green<->Ruby, the timing can't be guaranteed. Passing data between Ruby blocks will be more stable using the 'Ruby Value' (white V) connectors and links.