Well, there it is again ...
 
Installed REmatrix (full version) and tried to customize the ACT controller assignment. It works as long as I do not close Sonar, but when I exit Sonar and start again, my ACT mappings for REmatrix are all messed up.
 
I notice both xml files in the "%APPDATA%/cakewalk/ACT Data" get changed and when compared to other ACT mappings in the file (which were there for a long time and do work e.g. Channel Tools) the REmatrix ACT stuff looks reasonable, but still it doesn't work i.e. it's all messed about after restart.
 
I tried renaming those ACT files so that Sonar creates new ones, but I get the same situation.
 
BTW I'm using ACT on the VS-700 (but I think ACT is ACT so this shouldn't be a controller specific issue)

Have you checked already that is not coming from:
http://www.azslow.com/index.php/topic,4.0.html
http://www.azslow.com/index.php/topic,5.0.html
 
Then we had VST3 related mapping problem, and recently I have not managed to remap EQ, some parameters just could not be moved between control types (but I have not tried to do all magic dances around).
 
I am really thinking about my own mapping instead of ACT. For that I have to find out how to always detect what is focused, and in looks like there are another bugs on the way. The alternative is to "remap" from ACT mapping

azslow3
Have you checked already that is not coming from:
http://www.azslow.com/index.php/topic,4.0.html
http://www.azslow.com/index.php/topic,5.0.html
 
Then we had VST3 related mapping problem, and recently I have not managed to remap EQ, some parameters just could not be moved between control types (but I have not tried to do all magic dances around).
 

Hi Az,
 
What you described in your links is exactly what is happening! These 2 issue (plus the VST3 problem) are full blown bugs i.e. ACT remapping is broken and not usable at all!!!
 
Have you officially reported this to Cakewalk (CWBRNs?) ... did you get any reponse?
 
Could I manually create an ACT xml file that would work (theroretically I should be able to deduct all required information, parameters and IDs from the existing xml files ... a simple macro or script could then create the proper xml syntax) ... do think this is doable??? considering how much attention is given to control surface related issues this could take ages to be fixed ...

I have not reported any bugs... Till now I could solve ACT problems either with the procedure described in links or manually editing files. At the end once it works, it works persistent.
 
I have more disturbing problems with CS API. From some indirect discussions, some of them have routes down to Sonar 3... And that time there was quite active CS development. I doubt CW has time to do/fix anything there now. Almost all hardware devices are discontinued, Tascam has nothing, so why should they care?

Considering the interest a post on ACT gets, you can basically tell that hardly anybody is using it ... hence, I think I also refrain from wasting time and reporting theses ACT issues (again ... as some have been reported months/years ago) ...
 
I think I go fiddling with the files and try to fix it this way :-(