AZSlow

Well, if you introduce "Project" Set, as I have explained in my post #12, it will be relatively simple.
The only point from your last attempts - do not condition State Monitors, condition what they do when triggered.

Hi Alexey

Thanks for the explanation.  It's more complicated than I thought!

I'm going to try and simplify the protocol and hopefully find a better way forward with this challenge.

Best regards
Robert

I have uploaded modified version (b72). In initial tests, it works correctly with REAPER 7.

State Monitors are CHECKED when corresponding state is changed. Once. So if you later change Conditions (like set Device->Active), the monitor will not be checked again till corresponding state is changed (f.e. you switch from tracks to console in the project).

Also State Monitor keep silence when in was last time triggered with the same state, even if it was changed in-between (when conditions have prevented triggering).

So:
Load Sonar -> Not triggered (Device inactive)
Open project -> Not triggered (Device inactive)
Set 'Device' to 'active' -> Not triggered (Device is active, but no Context change!)
Close project -> Triggered with 'NoProject' (Device is active, Context change to 'NoProject' from 'Undefined')

Open project -> Not triggered (Device inactive)
Set 'Device' to 'active' -> Not triggered (no Context change)
Close project -> Not triggered! (Device is active, but Context is changed to 'NoProject' and so there is no changes for THIS Monitor)

Open project -> Triggered with 'Console/Track/Plug-in'! (Device is still active, Context is changed from 'NoProject')
Set 'Device' to 'active' -> Not triggered (no Context change)
Close project -> Triggered with 'NotProject' (Device is active, Context is changed, last triggered with different state).

I hope that explains.

Hi Alexey
Further to my previous post this evening.

I made a simple test preset which shows the same issue as I described, please see attached preset.
It has one user software set called 'Device' with default state 'inactive'.

Here is how I did the testing and the results:

Load Sonar
Open project
Set 'Device' to 'active'
Close project
Logic action 'Test Context' triggers
Feedback actions follow: 'Device -> inactive, set engine state
'Device Inactive' Ch1, CC0 Use Value

Open project
Set 'Device' to 'active'
Close project
Logic action 'Test Context' does not trigger.
Instead the Logic Action 'Fader 1' triggers (proving that the Logic action 'Test Context' did not trigger)

Open project
Set 'Device' to 'active'
Close project
Logic action 'Test Context' triggers
Feedback actions follow: 'Device -> inactive, set engine state
'Device Inactive' Ch1, CC0 Use Value

Open project
Set 'Device' to 'active'
Close project
Logic action 'Test Context' does not trigger.
Instead the Logic Action 'Fader 1' triggers (proving that the Logic action 'Test Context' did not trigger)

So every second time the Logic action 'Test Context' does not trigger.

I hope this helps to identify the reason for this issue.

Regards
Robert

Hi Alexey

I did some experimentation.

If I reload the AZ preset after loading the project, then the 'context' control triggers every time the project is then closed.

So the issue I described seems to be related to the AZ preset not being 'refreshed' every time you close a project then open the project again.  (But only every other time as I described before).

Does that give a clue to what is happening?

Regards
Robert

So, something set "Device->Offline" before Context Monitor is called...

You have not mentioned where you set "Device->Online". Also you have "Device:Offline", but not "Context:" when sending hello from the monitor. Context can be triggered during project working (as I have explained before, you can avoid that by using new "Project" Set), may be that unexpectedly triggers something.

Hi Alexey

I am returned from my travels, so I spend time today to implement the final handshaking elements based on your advice.

It is mostly working well except for one issue which I will try to describe carefully.

Default states are as follows:
Device, Offline
Hello, active

I use a Logical 'Context' Control to sense when the project is closed.
Monitor, Monitor State, Context
with the action condition, Device: Online

This triggers the following Feedback actions:
'Context:NoProject' - Device -> Offine, set engine state
'Context:NoProject' - Hello -> active, set engine state
'Device:Offline' - Ch:15 CC:14 Value (14bit)@ 3f80

The problem is that the 'context' control is only triggering every second time the project is closed.

Here is the simplified sequence:
- Load Sonar
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - 'Context' control triggers correctly.
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - 'Context' control does not trigger
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - 'Context' control triggers correctly
- Load Project (PIC receives Hello message from AZ and PIC sets Hello -> inactive, PIC sets Device > Online)
- Close Project - control does not trigger

This sequence continues over and over.

If I remove the action condition 'Device Online' then the 'Context control works every time.
I am using 'Set engine state' for all Set state actions.

Do you have an idea why this is happening?

Regards
Robert

I have only started to dig into that, but it seems like the bug is triggered by REAPER 7.

So, please try to convert using REAPER 6 (you can download any previous version, install as portable and use the same license file).

I can only check "FOCUSRITE SC Plugin" later (the only I have in your list), for the moment I have just checked different plug-in with recent REAPER version.

Note 1: that take lanes will not be converted correctly (since ReaCWP use REAPER 7 style for them). But at least you can check presets are fine. If yes, I can upload a version with "old style" REAPER 6 compatible lanes conversion.

Note 2: once saved in REAPER 6, REAPER 7 opens the project with correct preset (at least for one plug-in I have tested).

So I see the "roadmap" I can follow to understand and hopefully fix the issue. But I unlikely have time for that next days.

EDIT: may be early versions of REAPER 7 also work, I have not checked that yet. That will be preferable workaround, especially if new take lanes was already working in "compatible" version.
 

Thanks for the response. I couldn't hear any difference, so it sounds like the utility guessed correctly!