AZSlow

Hi Alexey
Thanks for looking at this issue for me.

First I added the set Text to "" as the first action in the Tk1IDENT Feedback list.
Next, I decided to experiment with the "Selection:Valid" condition.

I added the "Selection:Valid" condition to Parameter name action in the Tk1IDENT Feedback list.
This produces the correct Feedback output value when the FX Chain is deleted from the Cakewalk track, but it outputs the correct value twice.

Next I added the "Selection:Valid" condition to Parameter name action in the Tk1IDENT Logic list.
This produces the correct Feedback output value when the FX Chain is deleted from the Cakewalk track but only once.

This is working reliably on the test preset even with the Monitor action set to Ultra.

I will try this on my full console preset in Sonar and let you know how it works there.

Regards
Robert

Sorry for delay.

The problem is a bit complex. Please use https://www.azslow.com/index.php?action=downloads;sa=view;down=28
(test version). The modification can have side effects.

The monitor will be (still) triggered 2 times, but with this version it should not produce wrong results (at least for FXes).

Really you can correct the preset and it will work without new version, by checking "Selection:Valid" condition to detect FX is no longer there. Note you have to initially set Text to "" in any case (as you do with TKIDENT->Default), "Text Parameter" will not work in case parameter is not there or for other reasons, leaving text you compare untouched.

The difference in new version, "Text Parameter" really should no longer work in this particular case. It was returning old name before.

----

The problem is in my cache and Cakewalk behavior (always was like that, reproducible with X2).
Cakewalk normally inform surface plug-ins there are some structural changes. Even that is not always, but I think for FX removing it should do that.
Unfortunately, I see there is "idle" call before such notification. So, first monitor just "fail" to get values, thinking there was no structure changes. And next time, after Cakewalk triggers structure change notification, it detects "no longer there" condition.


In previous version, I was returning cached values in many cases (f.e. for container name) without reacting on "failures" at all. So even so the monitor was (correctly) triggered and setting "Selection:Invalid", "Text Parameter Container" was still returning cached values.

No problem, thanks for keeping in touch.

Sorry for no reply so far, it can take some more days till I can test it...

Hi Alexey

I have attached a test preset which works with CbB and shows the issue.

When the Monitor parameter value priority is set to Ultra then you always get the additional feedback message when the FX Chain is deleted.
When the Monitor parameter value priority is set to Slow then you do not get the additional feedback message when the FX Chain is deleted.

Could you have a look please and see if it is possible to stop the additional feedback message irrespective of the priority setting.

Regards
Robert

Hi Alexey

Thanks for your help with this.

This is the first time I have used this action combination so I will check if the issue exists in Cakewalk by Bandlab.  If it does then I will send you a test AZ Controller preset using CbB.

If the issue only exists in Sonar then I will send you a test AZ preset for use with Sonar.

It will be easier to see the issue in a small test AZ preset, so I will only send you my current very large preset if I cannot demonstrate the issue any other way.

Regards
Robert

Please upload your current preset. Can be its logic related.

a)I "slowly scan" for structural changes, doing so every cycle is not practical (some API calls as relatively slow). That can theoretically produce wrong report, when AZ Controller has already spotted the change, but has not upgraded all related information yet.

b)It can also be Cakewalk is reporting outdated information.

In any case, that can be checked and fixed (in case of a) or workaround (in case of b), once I understand from where it comes.

PS since I don't have new Sonar, I can only work in "demo mode". I hope the behavior is the same.

Hi Alexey

I finished the update to use the custom FX Chain names as track and bus idents.

There is one major issue which I would ask you advice about please.

I will describe the test sequence:

1. Insert an FX Chain preset to bus slot 1.

Timestamp 427839 outputs the correct MIDI message with the MIDI value representing the custom FX Name.

2. Delete the FX Chain in bus slot 1 and then I get two MIDI messages from AZ:

Timestamp 439639 outputs an INCORRECT message showing the PREVIOUS status, i.e. when the FX Chain is present (even though the FX Chain has been deleted).

Timestamp 439676 outputs the correct message when there is no FX Chain.

This additional INCORRECT message is causing big errors in my system and I cannot find a way to stop it outputting.


This additional INCORRECT message does not happen when I just report the value of an FX Chain control.  It only happens when I report the FX Chain custom name.

I have images to show the AZ preset and MIDI-OX messages but I cannot understand how to load images on this forum now.  It used to be possible.

I would be grateful for any suggestions to fix the issue.

Regards
Robert

Hi Alexey

In feedback, the action Text, Param. name, Container

seems to be returning the FX Chain custom name correctly, so don't spend any time on this for now.

I'll get back to you when I've finished my updates.

If successful then I can remove the need to use an FX control parameter as the track ident proxy.

Thanks and best regards

Robert

Hi Robert,

the only ideas I have at the moment, I can add "Named FX Chain" ("{*}" pattern) to the list of possible FX name selections (currently "Any" or some particular name) and remove '{}' from names (the result of Text, Param. anme, Container), if that will help you.

Regards,
Alexey.