AZ Controller plug-in for Cakewalk SONAR > Discussions

Renaming bus cache clear has not been implemented on latest Cakewalk release

(1/6) > >>

norfolkmastering:
Hi Alexey

The advanced copy of the new Cakewalk by Bandlab version: 2023.09 has just been released.

You may remember that you reported an issue to Mark McLeod that 'When destination (bus) is renamed, old name is reported by  GetMixParamValueText(... MIX_PARAM_OUTPUT ...).'

You may remember that Mark agreed to provide a fix to clear the cache whenever Bus, Aux track, or Patch Points are renamed.

I just updated to the latest version and the problem appears to still remain.

I've attached the test AZ preset which I used to test.

I have also read through the bug fix list and the fix does not appear on the list.

As this is the last planned update to the free Cakewalk by Bandlab, I want to get this fix included in the final release.

I remember you preferred to deal with Mark on this so can you let me know if you are okay to raise it with Mark? or whether you want me to do it?

Link to the update and feedback is at https://discuss.cakewalk.com/index.php?/forum/36-early-access-program/

Regards
Robert

azslow3:
Hi Robert,

report your observation to Cakewalk, I don't have any special relations to them. Also I am not sure I can test anything next days (the end of vacation).

Alexey.

norfolkmastering:
Okay I have reported as feedback in the early release topic.

norfolkmastering:
Hi Alexey

I got a reply from Mark confirming that the new release of Cakewalk by Bandlab does clear the cache whenever Bus, Aux track or Patch Points are renamed.

They forgot to add it to the list of bug fixes on the new release documentation but it has been done.

So I did further testing of my system using:
Cakewalk by Bandlab Version: 2023.09 (Build 055, 64bit)
AZ V0.5r11 b422
AZ Controller Preset 'Bus Names v4 (I sent you a copy in last post)

Here are the issues I have observed:

1. When a bus name is changed, a track routed to that bus does not reliably trigger a corresponding AZ feedback.  Occasionally a feedback output is triggered but most times not.

2. Changing a track send destination triggers the corresponding AZ feedback output only for track 1.  Other tracks do not trigger AZ feedback when their send destination is changed.

3. Track send destination names are always reported as the stereo pair friendly names rather than the mono friendly name, e.g. a track send destination to 'DAW1' is reported as 'DAW1 + DAW2'.

I have written a major new enhancement for my mixer control software which will allow total flexibility of the number of tracks in Cakewalk within a project and will allow track slot positions to be rearranged whilst preserving the mapping of Cakewalk to mixer mapping.  This is similar to what I have already been able to achieve for buses when I changed over to name based routing.  However I cannot implement the new software until the issues I have listed have been resolved.

I would appreciate if you could test the above issues when you have time.

Best regards
Robert

azslow3:
Hi Robert,

I have replied in the Cakewalk thread. Sends related API is still broken (at least I can't get it work correctly...).

Changes in bus names seems like working ok for me with 'Bus Names v4' preset.

I can only return the destination name I get from Cakewalk... But somehow I have the feeling (not sure) that the "number" returned for the destination does not changed when switching between L/R/Stereo. Or that may be yet another consequence of reported problem with Sends, I mean the value is cached when it should not.
Note that in API mono outputs are "visible" as separate, but there is just one number for "destination" and no indication it is stereo or mono.
It seems like Cakewalk is using different API calls to get names for sends and outputs, bypassing these numbers. But from what I remember I have specially switched from it for target names,
to not overload Cakewalk. So the situation is somehow messy...

Navigation

[0] Message Index

[#] Next page