Hi, I have a fader that would suspend MTP when it hit the top or bottom of the fader range.
Then the same trigger would reenable MTP after 1 second. So I can move the fader to the middle.
It was working before but now it just suspends MTP and won’t reenable.
I’m guessing because MTP is suspended it can’t do anything, but don’t know why it was working before.
Hi, could you share your project file or the relevant portion so that I can test it?
This one certainly works.
Enable-Disable-Processing.bmtp (1.4 KB)
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Ok. I even tried putting the enable translator before the disable one so it would be set to go, but isn’t working.
Fader Dis MTP Test.bmtp (2.9 KB)
(A side note): I was able to figure out the up/down relative movement using the z4 - z5 variable relationship, from what you helped me with before.
Yes, it looks like there is an issue with 1.9.1. I loaded 1.9.0 with this project and it worked but 1.9.1 did not. It looks like in 1.9.1 timers are also disabled when processing is disabled so the timer never trips.
I will report it.
Here is the project file I tested with.
Enable-Disable-Processing.bmtp (2.1 KB)
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
1 Like
Oh hi. I’m replying the same time you are. So the following was typed before your reply.
A basic test of using a keystroke A to disable and S to re-enable works in a blank project and my project.
The keystroke A to trigger both enable and a delayed disable does not work in either. So it’s not my project.
What I can do is trigger a re-enable at the 63 cc value. That’s not ideal but would work if my timed auto re-enable won’t.
Yes it looks like timers and delayed outgoing actions are also disabled when you use suspend on 1.9.1. I sent my example to Florian for evaluation. Of course yours is also posted here.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
1 Like
@J.Boss ,
Here is the fix for the timer delay re-enable. Apparently this is also a fix in 1.9.1 from 1.9.0 and not a bug.
Apparently you cannot have a delayed outgoing action on Enable Processing (translator 0.3). Instead I put the delay on the triggering of the timer which happens on translator 0.1.
Here is the updated project file.
Enable-Disable-Processing-a.bmtp (2.1 KB)
Timers still run but any delays on outgoing actions (which are not timers) stop.
As far as I can tell rules and timers still work when processing is disabled but outgoing action delays do not. The only outgoing action (without delay) that is available is to Enable Processing when your are in a Disable Processing state.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Maybe I spoke too soon. Let me play with it a bit more.
So I put a project file together to test the behavior of 1.9.1 and here is what I found
When processing is disabled:
- Input triggers are still evaluated. If they weren’t we would not be able to re-enable processing.
- Rules still work
- Any timers started will continue to run, however you will not be able to start or start any existing timers.
- The only translators the produce output are the ones with the rules
a) Project Enable
b) Project Disable - Project disable can have an outgoing delay and it will still work (after the delay)
- Project enable will work but only if there is no delay.
So if you want a watchdog timer to run before stop processing, then you should have the timer translator before the stop processing translator. You should put a slight delay in the stop processing translator to give the timer time to start. You can set an initial Duration, but do not delay the timer start outgoing action as it will not start after processing is disabled.
The attached works for me on 1.9.1. I did not test on 1.9.0 or do any behavior evaluation of 1.9.0.
Processing-Behavior-Demo.bmtp (3.9 KB)
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
1 Like
Oh, the delays break it too? In my project, using the variables rules method (instead of preset switching for enable/disable) I had a delay on the re-enable. So I put stops on both translators and removed the delay and it’s working now.
Thank you so much.
1 Like