No problem!
 
The key is "AssDisplay" (Assignment Display) Feedback Actions list.

• Change text in first 3 actions to add space, so 'Tr' is 'Tr ' (note the space after). That is for readability. And remove "Assign:Par" condition (set it to <Any>).
• In "Se" "Pn" "P" "EQ" and "F1" change "Replace" to "Append". Do not do this for D1 (it is not strip dependent).
• In Format Text change "Trim to 2" to "No format" (or delete that Action)
• Delete "LC/MC Assign Display" Action. Even in case your device somehow imitate it, we no longer produce "correct" strings.
• Test the result

OK thanks, I'll have a look at that later today when I have a moment! And I'm going to hold myself back from joking about "AssDisplay"...

subtlearts
And I'm going to hold myself back from joking about "AssDisplay"...

I think that is good abbreviation for 2 characters 7 segments display in 2015...

azslow3
I think that is good abbreviation for 2 characters 7 segments display in 2015...

Well put...
 
Well sir, you certainly know your stuff! I followed your instructions even though I basically didn't know what I was doing at all, and almost certainly never would have figured it out or even found that stuff on my own, and it worked perfectly! Now in Vol mode it switches from 'Tr' to Bu' and back, and in Pan mode it switches from 'Tr Pn' to Bu Pn' and back. I guess that's what the Append business was about. Anyway, it's clear and it works as I'd hoped for! Thanks again!

This is so confusing but I want to learn lol. It'd be nice to just shove any control service in and map in freedom. You've said you slowed down aslow due to lack of community interest, but it might just because this thread is at a technical level higher than most of the users knowledge. 
 
If you can get me to understand how to set it up you can get anyone else in the world to =p. Keep up the good work!

Just started taking a look at  this Alexey, nice work.  
I'll have more feedback in the weeks to come, but one thing that drove me nuts was trying to find how to map parameters to a synth and I finally made it to the "Rack" option.  Maybe call it synth rack.  I'll sign up on your page and post more there.
 

Genius Animus
But it might just because this thread is at a technical level higher than most of the users knowledge. 
 
If you can get me to understand how to set it up you can get anyone else in the world to =p. Keep up the good work!

Most technical discussions is this thread was about one of two most complicated presets available in Sonar, Mackie Control. And the details was how to use it without the original device
 
Most configurations are significantly simpler. There is "Startup" preset, to use out of the box. There is "ACT MIDI Explained" with click by click guide and explanations, I have reworked it a bit recently. I also offer to build basic preset for any particular device, as we have done with ZED.

azslow3
Most technical discussions is this thread was about one of two most complicated presets available in Sonar, Mackie Control. And the details was how to use it without the original device

Indeed, I doubt that most users with simple needs will run into as much technical detail as I have, trying to make a fairly fiddly 10-year-old controller emulate a completely different one... The fact that the plugin is incredibly deep and flexible should not be a turnoff - but it's useful for someone like me - as soon as I get one thing working my brain goes "cool, but now what about this other thing?"...
 
For example, now I have transport control, track select, volume, pan, mute, solo, and record enable, all switchable from bus to track, and movable by channel and bank (8 channels), with WAI and input focus updating as they should. Plus a decent chunk of ACT control (8 knobs and faders, movable in banks), and a heads-up display that tells me what controls are active and available. Nice, right? Yeah, but I don't have ACT buttons, and that irks me. I don't know if I'll ever use them, mind you, but I want the option...
 
So Alexey... how should I set this up? My default approach is going to be what I've been doing so far - taking existing MCU buttons whose functions I don't need or care about, and repurposing them within the plugin by changing the logic instructions. The Kore unit can send different things besides MCU buttons, but so far I don't know how to get the plugin to respond to them in as predictable a fashion, as I've started from the MCU template and at this point it seems salient to continue with it - or rather, with my altered version of it.
 
More interestingly, I'm going to want to figure out how to get the info for what the buttons are mapped to, into the AZ display, presumably in a 3d row of text - I've already figured out how to set the size and layout of the display, which is pretty straightforward, now I just have to extrapolate from the code that sends the info about the rotors and sliders... wish me luck!
 
 
 
 

ACT buttons are not there...
 
You can add "ACT Switch <button number> + OffAct X 8" let say in "MuteX" action list, right after "WAI CtrlGroup Mute" (before "Toggle"). Add condition "Assign:Dyn" to it. Done.
 
With display it is not so difficult too (since we do not need imitate anything). In the same action list, add action and position it right after "Parameter Value Monitor". Set it to "Parameter Name Monitor". In the Feedback (you will see new monitor there), add Actions "Text Para. Name Parameter" and "Display Row 3 Column <button number + 1>".
 
In display options, change "Group" to "No", "Rows" to "3" and then "Group" to 3.
 
With that modification, the third row will show what "Mute" button is going to control (Mute or ACT parameter name).
 
Note that if you copy/paste Monitor Action in the Logic list (to second "Mute") it will copy also monitor actions. Do not forget to change <button number> in 2 places after copy.
 
And since you have asked... Good Luck!

I don't have much to add beyond a huge THANK YOU to Azlow for this tool. I have started programming my BCR2000 and once I have this fully set up it is going to be amazing.
 
I urge anyone who finds this to daunting to use the quickstart on Azlow's site. The program is clunky and logically deliberate in its implementation, but I would guess the steps laid out in the quickstart post would get the vast majority of users to where they need.
 
The program itself opens up an ease of use for the controller that I think would have been difficult to achieve with ACT alone. I will admit I am not an ACT expert though, but I get the feeling once something is assigned in Azlow's program it will be a rock-solid connection. It can be a bit time consuming, but unlike some of the other remote/midi control options I feel confident in the functionality of the created control template as I move between projects.
 
In short: the interface is not the prettiest, it can be both logical yet unintuitive, but it is 100% capable and should not be missed. It is functional genius in my opinion.