[ANSWERED] How To Make Closed Loops Work
-
another weird behaviour;
when I just recreated this small section of the patch the pulse generator immediately stops working if the comparator is connected to the gate, whether the trigger has been fired or not.
if I add second counter after th gate it works just fine, and the toggle works as expected, but this does point to a worrying situation.
If upstream actors effect actors which are earlier in the logic path, then that makes troubleshooting a LOT more difficult.
-
Isadora prevents that you can generate a closed loop. You can get around this by using a "broadcaster" actor at the output side and a "listener" actor at the input side.
Best Michel
-
As Michel said, it's to do with Isadora detecting a closed loop and locking those actors to prevent an infinite loop. I prefer not to use Broadcasters and Listeners for this because there can be a channel number conflict if you copy some work from one file into another. I usually fool the closed loop detection by adding another actor that goes outside the loop (to make it not be detected as a closed loop), as I did in the Total # of Scenes User Actor.
You'll see in the MIDI Cycler I built for you that there's also a seemingly-superfluous Trigger Value actor coming off the Comparator actor (top right), but I should have labelled that one with the same info about infinite loops for you.
-
None of this explains the original problem though... just my failed attempt to sandbox and troubleshoot it.
any thoughts on why the comparator wasn't triggering the the toggle for the gate in the original patch?
I'm running Isadora 3 on Win10
Machine 1- AMD 1700x 8 core CPU, 32GB RAM, and an AMD Radeon RX580 GPU
Machine 2 -AMD 5900HX , 8 Core APU, 16GB Ram and an integrated GPU -
-
Sure here it is in a user actor.
as far as I can tell the pulse generator should stop once the value in the user input is reached. However it doesn't. So instead of triggering the number of instances that I want to it triggers all of them every time.
I'm running Isadora 3 on Win10
Machine 1- AMD 1700x 8 core CPU, 32GB RAM, and an AMD Radeon RX580 GPU
Machine 2 -AMD 5900HX , 8 Core APU, 16GB Ram and an integrated GPU -
Do I understand correctly that when the scene starts, the pulses should not pass after the given number (in your patch 20)?
I think the toggle actor is causing the confusion. Try this:
If you want this to work several times within a scene you have to do a form of reset of the counter actor and a trigger for the new start.
best
Jean-François
-
OK, i fixed the problem, but it wasn't what we thought. It turns out that the counter actor cannot keep up with high frequency pulses.
when I slow the pulse generator down it works perfectly. so it's just about fine tuning where it breaks down.
It's currently working ok at 60z but ideally it would be working faster, as I could be plausibly sending 56 signals which would take nearly a second, but I know that 120hz is too fast for the counter to function properly.
I'll do some tuning and see where I end up.
I'm running Isadora 3 on Win10
Machine 1- AMD 1700x 8 core CPU, 32GB RAM, and an AMD Radeon RX580 GPU
Machine 2 -AMD 5900HX , 8 Core APU, 16GB Ram and an integrated GPU -
To better see what was happening I had reduced the frequency but after that I always tested at 120Hz without a single problem.
best
Jean-François
-
for me it falls apart as soon as it goes faster than 60hz, i have no idea why, but I've reorganised how everything is triggering so that 60hz is good enough.
I think I'm past tinkering with this now.
Thanks for your help though.
-
I'm not sure, if this could be in relation. But is it possible, that the 'General service task' is responsible for this issues? If the 'Target Frame Rate' is at 50fps and the GST at 1, the actors only refresh every single frame, which would be at 50hz. Therefore the GST would need to be at 3x at least, to work with 120hz repetitions. Is it working this way, or am I wrong about it?
-
I have changed both factors, it changes the velocity but it is working.
