AZSlow

Yes All are working. AWESOME Job Thank you. I will definitely send future donation if it is asked for I haven't been looking around the site but will. So going forward all Updates to reaper 7 will not affect?
I think you mentioned I needed reaper 6 to start and then reaper 7 would read 6...so the modified file will be read by all future reaper versions now?
Also didnt know anything about reaper 6 or having different lanes...so the Lanes are compatible with this modification to reacwp?

Thanks for version 72b, Haven't tried anything yet since my last reply as I had gotten busy and forgotten.
The plugins I used were UAD 1176 and other UAD PLUGINS, WAVES VEQ3, VCOMP and others. It seemed like it didnt matter what plugin manufacturer I used none had worked PROPERLY. It may have been REAPER 7 for me I didnt know I needed to be using a 6 version. will report back. Thanks

Hi Alexey

I studied your post #12 again and now I understand it properly.
I implemented based on your scheme and it works completely.

I use the 'Project' 'open' to send a single Hello CC message to the PICs.
When the project is closed then I send a single 'goodbye' message which sets the PICs in their standby mode.

What does all this do in practice?

- The two AZ instances output no 'normal' CC and SysEx feedback messages to the PICs when Sonar is loaded but no project is opened.  This stops the PICs from being flooded with unnecessary information.

- Only one PIC is active at anyone one time, so the inactive PIC receives no 'normal' CC and SysEx messages when inactive.  Again this means the PIC does not have to deal with a lot of unwanted messages.

- When the project is closed, both PICs are set into inactive state.  Sonar and the tape machines receive shut down information; e.g. REC ARMs are all turned off.  Solo's are all turned off etc.

- The start up process i.e.
Load Sonar
Load project
Make one mode (RECORD or REPLAY) active is now properly controlled.

Thanks so much for all your help with this handshaking project.  It is really great to have it working so well.  I might be getting to the end of this big project -> Just kidding!  There is always another improvement to make -> but not today!

Best regards
Robert

Thanks Alexey

I need to spend some time studying all you have said so I can really understand all points.

I'll get back to you when I have made some progress.

Regards
Robert

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