AZSlow
AZ Controller plug-in for Cakewalk SONAR => Discussions => Topic started by: almeister_65 on July 14, 2017, 04:11:46 PM
-
Hello, I'm new here. I would first like to say thank you to Alexey for creating this site and all his work. :)
I bought an X-touch mini to use to control Sonar Platinum as it was a cheap alternative to the bigger one. I downloaded AZ Controller and started with the generic preset. I've had a couple of pm's with Alexey and he suggested bringing it here. I'm new to surface controllers and have very limited knowledge of programming and how some of the logic works. I'm hoping that with the help of Alexey and this board that I can get a better understanding, learn some stuff and get some more functioality out of the X-touch mini. I'll start by trying my best to explain how I use it and the basic lay out.
There are two layers on the mini A & B. I use it to control 1 strip/channel at a time (not 8 ) and move from strip to strip with buttons.
For layer A, it is more for strip control, the fader controls volume, rotors control pan, send levels & pans (1-3) and input gain. The transport buttons work as they should and there are buttons for mode changing, moving WAI and some other functions.
For layer B, I have this set more for loop recording and Auto punch purposes. 2 encoders are set for jogging (one for measures, one for beats), and 2 are set for zooming horizontal and vertical.
That's basically how I have it set now but intend to tweak it more as I learn more.
Layer A
Fader is Track/Bus Fader (based on WAI)
Row 1 pads
B1 N/A (shift? if I can figure out how to do it) B2 Track Arm B3 Rew B4 FF B5 Loop B6 Stop B7 Play B8 Rec
Row 2 pads
B1 Solo B2 Mute B3 RTZ B4 Show/Hide Multi Dock B5 WAI -1 B6 WAI +1 B7 Set Strip B8 Mode Loop
Encoders
E1 Pan E2 Send1 Level E3 Send1 Pan E4 Send2 Level E5 Send2 Pan E6 Send3 Level E7 Send3 Pan E8 Input Gain
Encoder button
EB1 Input Echo EB2 Send1 Enable EB3 Send1 Post/Pre EB4 Send2 Enable EB5 Send2 Post/Pre EB6 Send3 Enable EB7 Send3 Post/Pre EB8 Bank (Loop)
Layer B
Fader N/A
Row 1 pads
B1 Set Punch out B2 Loop out B3 Marker -1 B4 Marker +1 B5 Loop B6 Stop B7 Play B8 Rec
Row 2 pads
B1 Set Punch in B2 Loop in B3 N/A B4 N/A B5 N/A B6 N/A B7 N/A B8 N/A
Encoder
E1 Jog Beat E2 Jog Measure E3 N/A E4 N/A E5 N/A E6 N/A E7 Zoom Horz E8 Zoom Vert
Encoder button
EB1 Auto Punch Toggle EB2 Go to Punch In EB3 N/A EB4 N/A EB5 N/A EB6 N/A EB7 Resize Zoom Fit All EB8 Resize Zoom Vert Fit
As you can see, there is plenty of room for improvement and to add functionality. I appreciate any and all comments, critizism (positive) and help. Thanks again to Alexey. 8) :) If there are any question, please feel free to ask or if there is anyway I can help, just let me know.
-
Alexey, here are the X-touch Edit Software Presets for the mini you asked for. Thank you again!
-
I have not yet touched the preset and we have to check the feedback to make strategic decisions, but I have several questions/comments:
1. Do you feel comfortable with the fader for the volume? Especially when quickly changing between strips or for fine tuning, an encoder can be better. The fader can keep its function (in parallel to encoder) or can always stay as WAI bus volume (when strip is track)
2. If we implement multi-strip layout later, it can be better to control not "WAI" but simply "focused" strip. Clicking on strip with mouse or using focus move control (see later) will focus the strip, making the track inspector in sonar and mini always in sync (WAI can follow automatically if required or stay unchanged for multi-strip operations)
3. Are you going to work with mini with one hand? If you are ready to work with 2, do you think having 2 modifiers (so not only "Shift" but also "Ctrl") is still ok? Depending on the answer we can put more layers or more "modifiers" per layer (Ctrl+Shift gives 4x for buttons and 2x for encoders, since "Shift"+Encoder should be "fine change")
4. I propose to use an encoder for selecting strip, that is much faster to use then pressing buttons (for let say +5 strips movements).
5. What is the upper limit of sends you use per strip? Is that really 3 or can be more?
6. It is better to use normal buttons for something with feedback (mute/solo/input echo) and encoder buttons for "silent" actions (Undo/Redo, RTZ)
7. Jog "by marker" is also possible on encoder (in general, an encoder can be used as 2 buttons and that is good for some repeatable operations)
As I wrote before, I will prepare "feedback test" preset. We have to test either LEDs/Rings can still be updated when device is in different layer (Compact is at least partially not doing so, but I could not test LEDs on it). The problem is that AZ Ctrl has no way to detect in which hardware layer you currently are. All controllers/keyboard I have used so far (AKAI, M-Audio, Novation, etc.) behave as expected, but Behringer is... Behringer.
-
Here's some answers as best I can at the moment:
1. I'm comfortable with the fader but am open to all possibilities. I do like the idea of it controlling WAI bus volume if an encoder is used though.
2. Yes, control by focus would be fine and having WAI follow (for single) would be good.
3. Sometimes will be working 1 handed with instrument in the other but I really like the idea of multiple modifiers for more layers and functionality.
4. encoder for strip selection is fine
5. I chose 3 sends because that was all the encoders I had available with my limited programming skills :) (just the stuff you've already suggested, amazes me)
6. I agree about the normal buttons for feedback and encoder button for silent.
7. Jog by marker on an encoder sounds like a great option.
A lot of what I set up on my preset was due to my limited knowledge/skills in programming this kind of logic. I am open to all suggestions from you or anyone, that will help make it a well functioning piece of hardware. The stuff you've already mentioned goes way beyond my expectation of what this will do. Again, thank you for your time and efforts (and what ever other magic you may use ;) ) And if I can help in any way, I will.
-
Thank you for prompt answers. That helps me to not think in all/wrong directions.
And if I can help in any way, I will.
Just please do not give up on that. I understand that waiting and then test "alpha" versions of preset can be frustrating.
-
Released: http://www.azslow.com/index.php/topic,377.0.html
-
Ok, ran test and here are results:
a) No Leds for stop or encoders (no lights other than small MC Mode led, telling me that it is in MC mode)
b) Play does not light when started with space bar and stop works. Play on mini only plays for a mil sec and stops, doesn't keep going if you hold button
Here is what I see in "Last MIDI event" for both
Play-toggles value- Ch:1 N94 Value:0 OFF to 127 | Play ('A')
Stop-toggles value- Ch:1 N93 Value:0 OFF to 127 | Stop ('A')
c) MC Button- No led- toggles value- Ch:1 N87 Value:0 OFF to 127 | Shift ('A')
Ctrl Button- no led toggles value- Ch:1 N88 Value:0 OFF to 127 | Ctrl ('A')
d) Layer button A- Lights on and off-works in conjunction with encoder- toggles value Ch:1 N94 Value:0 OFF to 127 | Play ('A')
e) Encoder- No Led Changes Volume of strip when Layer A not lit and Send1 when lit, moves in right direction, moves in really fine increments though
f) Encoder Button- toggles value Ch:1 N32 Value:0 OFF to 127.
g) WAI does update when change focus with mouse, WAI only on bus when focus is on bus. WAI lights track in focus and last bus (WAI seems to work as you expected)
I hope I was able to explain well and give you enough feedback. I'm not frustrated at all. It's a process of development and we are in quite different time zones. It will take time, I understand. I work in a prototype shop for a corporation here that manufactures anti-theft devices in retail stores, I know what it can take to develope a "product" ;) I find this quite interesting.
-
Thank! In fact everything is fine.
You have got fine resolution because you pressed Shfit before... it is working as CapsLock when pressed alone (you could not see that)
With Play I probably just have a bug.
I have tried to use "non Mackie" feedback on everything except "Layer A", and that does not work. I am sure Mackie feedback will work,
but "native" could be better. So just one question, are you sure that "Global channel" is set to "2" in Mini editor? Also when you open its drop down list,
which range this parameter has, 1-16 or 0-15?
-
I'll have to check when I get home from work, but yes, it was set to channel 2 and I believe it starts with "off" and 1-16, there was no zero channel.
The "play" not working may have been something else (loop set wrong) in temp project I was using to demo. I noticed this after I posted and just before I shut down and went to bed. I will double check this tonight and channel designations too. Thanks again Alexey, and have a great day!
-
I have updated my post with preset. I will do the same in the future, to keep progress at one place.
Please do not forget to re-select the preset in AZ Controller after importing new version.
Still in "feedback prove" status. I have described relevant tests.
But I have also put some ideas in which direction we can develop the preset. While just for simple test at the moment, the preset itself is already structured for rapid future development. So once we clarify the feedback, we can advance fast.
-
Hello Alexey,
Here are some observations, results and thoughts from your recent update:
loop and stop were on at start up :)
a) no lights in upper button row after pressing layer A button a couple times
b) loop, stop, play all work as should and corresponding lights do too
c) press stop for long time, RTZ, timing seems ok
d) shift and control work with lights accordingly
e) encoder 1 and 2 control track when layer A not lit, send when lit, action feels ok, may need slight adjustment (see below) but no leds light up at all
f) shift button works for fine resolution of encoders, track-volume res is good (coarse could be finer?), track-pan fine-res may be a bit too fine-it takes 4 clicks on encoder to get it to move 1%
Send-level res and Send-pan res may be just a bit too fine also and coarse just a bit finer
g) pushing encoder and turning works, note value on push jumps to 127, then cc value changes when turned, value goes to 1 when turned right and 65 when turned left
answers to questions
1.a+b) I like the idea of more mode switches as long as we can find a way to set punch in and loop, I agree, mode switches that light to indicate use is good idea
2. a) yes I would like a strip mode, with joggers make sense, also made input gain control in there somewhere and buttons for solo, mute, arm, input echo etc.etc.
b) send mode with modifier(i.e Ctrl) as a strip submode also sounds good---is there a way to "loop" thru sends? like, cycle from Send1 to Send2 to Send3 and if there
isn't a 4th it would jump bsck to 1? just throwing an idea out there
c) loop/punch mode would be great
d) multi strip mode also great idea if possible with the functions you mentioned, default doesn't really matter to me but maybe solo would work better
e) Plugin Dynamic mapping!! Not even sure how you can make that work but it sounds awesome. :)
f) some keyboard function would be good, I don't do many non-midi program changes (main instrumnet is guitar), so I play thru amp sim (TH3, Amplitube4), save and undo,
multi dock (D), inspector (I), and browser (B) are some of the main ones I use
3."Stop -> Undo -> Record again" sounds like a great feature to have, I use "comping" mode a lot
You didn't mention Zoom and fit all tracks, are those things we can add in?
The way I do stuff for myself is start with EZ or Superior drummer, guitar or bass and maybe EZ Keys, I'll comp and write, gets sounds I want, and then mix.
I think what you've descibed will work out well.
Actually, it far surpasses what I even thought was capable of doing! I don't have much experience with control surfaces (only seen them in videos and ads) and have never
had a MAckie or any large control surface to use so I'm not real sure of what they really are capable of. This is all "icing on the cake" (or Cakewalk if you will ;) ) for me plus I get to learn some
new things. Thank you again for your time and effort!
I've also attached a screen shot of the Behringer edit software in case you need any info from there, meant to do that last time but forgot :)
-
With rings it is bad... but not the time to give up Mackie mode, may be I just do not understand something yet.
I have made the preset a bit more "interesting" to test. We still need correct feedback first, but I have tried to demonstrate where we go with functionality.
-
Thanks Alexey, I will check it out tonight.
-
I forgot to map other encoders, so it is good you have not tested so far...
I have also tested the preset with Mackie emulator, you should see some rings now (if Mini is able to work with Mackie rings at all).
-
Hello again Alexey, :) Good news!
a) Encoder LED rings work! Seem to behave ok and are different. Volume moves clockwise to increase, counter clockwise to decrease, Pan is split/spread?
Looks like how I think it should work
b) Internal Display appears! 8) Layer A Button switches single to multi, Layer B switches to Plug-in mode! Crtl switches to sub modes!
Encoders work as they should for what they are designated.
c) I dropped the "_fEncParSet" setting for coarse down to 2%, I left fine where it was. "Accelerated" didn't cause any jumps.
I just want to say, I am AMAZED!! Holy S*#T! (please excuse the language, I'm just a bit excited ;D ) I can see how its starting to come together! This really is more than I could of imagined that it could do!
Thanks You again sir! Your knowledge of how this all works just amazes me!
If there was info I left out, let me know and I'll check/re-check when I can. Whatever help I can provide!
Have a great morning, day, afternoon, or whatever time it may be when you read this!
-
I am glad you like how it goes :D
I have added buttons.
Sorry, I have just noticed that I have "messed" with versions, so rings can be bad (or not available at all), I will fix that later (I have to go now).
Should be fixed now (and loop/punch set/go added).
-
Good evening Alexey,
Finally got a chance to download latest preset. Busy friday night so I didn't get a chance until today.
I tried to test as much as I could, may have missed an item or 2 so if there is something specific you would like me to check, just let me know
a) Most funtionality seems to work correctly. Rings work.
Transport works.
Layer A light stay on when Layer B pressed to indicate mode status of layer A
Layer B long press toggle display works.
Fader is not controlling bus.
Single strip layer
WAI follows and updates/synced as described
wo/ Ctrl
Encoder 7 moves focus but does not switch toggle between tracks/bus
Pressing last encoder toggles to jog by marker but doesn't toggle back to by beat/measure even with shift lit, stays on by measure.
so maybe it's just reading that it's pressed and not press and turn?
Buttons work
w/Ctrl works for sends control with exception of 6th encoder button for send3 Pan does not reset to unity
Buttons work
Mutlistrip mode works as descibed
Plugin layer works with Ctrl
b) strategic question
Pushing Encoder with out turning is possible if careful, I could see a possibility for it happening and making a slight change to a parameter.
Again, thanks for your hel and hard work. Let me know what else you need on my part. :) 8)
-
I have tried to addressed mentioned by you bugs.
So, since encoder push is not an nothing, I will think how to implement plug-in selection other way. May be with fast controls. But only in case you like how that work for Loop/Puch.
We have unassigned controls (one encoder and buttons) in the Single layer. You have mentioned some shortcuts before, so what should put there?
-
Hello again,
"Bugs" I had mentioned work now
Fader works as it should.
Encoder for jogger works when pressed and turned and toggle back to by beat/measure
"<<" and ">>" work as explained, I just need to remamber to toggle autopunch off to set loop points and vice versa
Record and long press record work as expained and with special function feature.
All seems to work as it should. The internal display from AZ Control helps with navigation of layers :)
If we could assign the keyboard "D" for the multidock toggle to a button somewhere and maybe for "I"-inspector , "B" browswer etc.
I'll have to put some thought into some things but the "D" key is definitely one I use alot.
I think you have most of the functions covered and layout makes sense too.
It's a great improvement over what I had achieved or what could be achieved with basic midi presets :)
I'm getting use to it and will be testing more deeply soon.
Thanks again Alexey
-
The preset is updated, see "Tests".
If you do not like Punch operations, we can think how to do this differently (f.e. work with Punch with Shift pressed and with Loop without Shift).
Other then that, I have implemented everything I have thought to implement. We still have one encoder in Single strip layer, but no more unassigned controls. So if current version works correctly, I will "release" the preset.
-
Hello Alexey,
It's a bit late here but I've tried to go thru and test, here is observations:
I'm getting use to the Loop/Auto Punch operation so I don't think we need to change that to operate by shift as you asked.
multi dock button (6) works, show/hide Browser button (7) is labeled wrong in AZ Control internal display, it's labeled as undo
undo button ( 8 ) isn't labeled at all but functions as undo
"<<" and ">>" work as should in both single and multi modes for loop/auto punch
in Plug-in Layer
"<<" and ">>"
FX and ProChannel work as described
Long pressing (>1sec) ">>" switch to Synth Rack or from Synth Rack to FX mode did nothing.
I had TTS inserted on a track and 2 Fx, track in focus and it didn't change anything. Synth Rack didn't open. Did I do something wrong?
I even tried while focus on different track, nothing changed.
Long press of loop brings up focused Fx plugin GUI
On another subject. I use comping a lot and K button is my friend when auditioning takes :)
Something to show/hide takes lanes?, scroll through takes lanes? is any of that possible?
I'm not sure if there is even any room left for those types of things but was just something I thought of as something I use frequently.
Not a big concern as I can do them as I always have, with keyboard/mouse
As it is, the mini does a lot more than I ever expected. You've really done some "magic" to it!
If there's anything I forgot, let me know.
Thanks again Alexey, I'm truly amazed. :D
-
Labels for last 2 buttons and Synth switching should be fixed now.
Note that TTS is not the best choice for tests... It is DX plug-in, it has not automatable parameters.
Cakewalk has "forgotten" to give access to any modern Sonar features (by "modern" I mean introduced in last 10 years...). So, there is no take lanes control (track view specific commands are also not available directly). But we can send computer keyboard shortcuts. For that we need some keys.... and we do not have any left. "Long press" for last 3 buttons? Shift+buttons? What you prefer? And which shortcut you want to send?
-
Well, leave it to me to pick the wrong synth to test ;D ::)
I will try a couple others. Would Dimension or Rapture work? I have UVI workstation, Aria Player (Garritan PO5) or Sampletank 3 also.
Unfortunate about the track view/take lanes but that's ok, this preset still has a lot of control over many features 8)
If we can try shift/long press (prefer shift) on last 3 buttons
Could we do shift for Browser button to toggle track Inspector ( I computer key)? Maybe long press/shift Undo to redo?
Shift Multidock button to bring up PRV? Not sure if that's even possible.
Is it also possible to do combo of Shift+Ctrl to add another function to a button (f.e. Ctrl+Alt+Delete style)? Just curious.
Other than what you have already done (and you've done a lot), I can't think of much else at the moment. Any idea you have is always welcome.
I will test Synth again, hopefully later tonight and let you know, Thanks Alexey and have a great day!
-
Added 3 actions with shift.
With Ctrl+Shift, technically is possible. But in our "roadmap", Ctrl selects sub-layer, in this case Sends. Shift is just changing the resolution. Changing actions of dedicated for commands 3 buttons is on the border of logic. But switching sends 3/4 on/off pre/post buttons to command mode with shift I think cross the red line of usability...
I was thinking about making "Shift+Buttons" always do commands (the same, in all modes). But it is easy to "forget" that Mini is "Capslocked" for fine parameter changes and do something unexpected (f.e. undo instead of mute...).
If there is no objections, its time to declare we have the first "release". I will put the information into "Presets" board then.
-
Sounds good Alexey!
I will try to give a test again tonight or tomorrow night (a little busy tonight so may not get a chance tonight).
Thank you again., you're a man of great knowledge and patience! :) 8)
-
Some funny stuff is happening with button lights
When Sonar is first started and preset loaded, Shift light, Crtl and layer A light work as should. When I change strip focus,
shift button only stays lit when pressed, is not staying lit (capslock?) to indicate whether it is on or off, same for Layer A, Crtl
Layer B light acts as it should but brings back Layer A indication when pressed. ( f.e If Layer A light was out but multi track mode working when Layer B pressed,
Layer A light comes back on, and stays on after return to Layer A from B until Layer A pressed again.) I'm not sure that I explained that well but trying to explain as best I can.
"<< >>" buttons also don't stay lit, they light when first initialize mode (auto punch) but once pressed again don't stay lit
Send buttons act similar but act differently, really quick press brings them on after turning off but slightly longer press doesn't.
I restarted Sonar a couple times to test if all these things repeated and they did.
undo/redo works, Browser/Inspector work, Muti dock/Prv pulls up multi dock with PRV
"<< >>" For Synth In Plugin mode work, Tried with a few Synths, some allowed more control than others.
It Was hard to tell if some things were working right with out the lights working for feed back.
Ok, so just as I was about to give up, I tried Multi Dock again to check Prv and everything started working correctly?????
I shut Sonar down and tried to repeat what happened again and now it all works as it should??? ???
I swear I'm not crazy (or drinking or anything :o ) but that's what happened. I'm dumbfounded. It was just weird that the button lights started working again?
It's late here so I will wait to hear from you, get your thoughts and test more tomorrow night.
Thanks again Alexey.
-
That is very strange.... It can be:
1) glitch with Mini itself
2) glitch with Sonar
3) glitch with MIDI drivers
4) glitch with AZ Controller
5) bug in the preset
6*) some strange MIDI looping...
And from the behavior, it more like (5). I mean LEDs are reactive on the same messages as button sends, so when you "release" a button, it sends "LED OFF" message. But it is sent FROM Mini, to switch off LED it should "bounce" back TO Mini. So, that can only happened if (1), (2), (3) or (4) is the problem.
If you observe that again, please check:
* does that happened on MIDI track pointing to VST with enabled MIDI output?
* is it continue glitching when you load audio only project?
Also I hope that you do not have MIDIOx, Bom translator or software MIDI loopers. Also check you do not have any Windows MIDI outs enabled in Sonar.
-
I will test again tonight. I don't have MIDIOx or any of the other stuff you mentioned. I will check the midi track and project with no midi.
One thing I forgot to mention, which may or may not be important, is that mini would trigger a note to play on the synth I had loaded for test (f.e. press any button, corresponding midi note would sound on synth). I was more worried about the light situation so didn't pay it much mind, later I was thinking that maybe something with i/o, midi channel, might have something to do with it so maybe it was more important than I thought. The light thing happened before I loaded a synth so that's why I didn't pay much attention to it. Any thoughts?
I'm going to give a more "structured" test tonight, start new project, load just audio and test, then load midi and synth and see what happens.
What should I do about the notes sounding when button on midi pressed? I know I read something somewhere about that, but I can't remember what and where I read it. I will investigate more tonight with that too.
Have a great day! 8)
-
Yes, that is related... I thing the following happens: MINI -> Sonar -> .... Synth with enabled MIDI output (default for all synth supporting that!) -> MINI.
Well, AZ Controller with our preset should BLOCK all incoming from Mini MIDI messages. So you should not get notes on Synth from it.
1) check that in Preferences / MIDI / Control Surfaces, AZ Controller is the only plug-in with input set to MINI. If there is any other plug-in (other instance of AZ Controller, ACT MIDI, Generic surface), the messages will "leak" (Sonar bug...)
2) if you have ever used "Remove control" (direct MIDI learning), that can be a problem (another Sonar bug).
I will think about other places to check, but usually that is (1).
Independent from "MIDI Leaking", check your plug-ins for enabled "MIDI Output". Just try to select an input in any MIDI track in the project, if you see any plug-in name, open its GUI and disable the output (under "VST2"/"VST3" button menu). Having that enabled is looking for troubles, such Synth can "leak" own MIDI into other tracks (which set to Omni).
Even more. Something is sending MIDI back to Mini. So probably you have MIDI track(s) with output set to it. If MIDI track is not assigned to some soft. synth, it is auto-assigned to the first available in the system Midi device. The same happens if the track was assigned to hardware synth and that device was disconnected. The same for removed soft. synth (when not all related tracks was deleted).
Users are asking Cakewalk to finally implement normal "None" as Input and Output and make it default. Also people are asking to remember "disable MIDI output" setting in the plug-in insertion dialog. And fix MIDI leaking from "Remote control...". These "features" are there for many years (yes, in replies Cakewalk declare first two as "features"!)
-
Thanks Alexey, I will try to implement these things when testing tonight.
I have never used "remote Control" so that should not be issue.
-
Hello again Alexey,
Did what you said, Act controller was also listed as controller, I just deleted it as I don't plan to use it
and could not see were to set it to "no in/output" and I have no other devices plugged in.
I checked the vst's and the "Enable VST output" was greyed out and not checked and input was checked but greyed out also.
All lights seem to be working correctly and no notes from Syths are sounding when buttons pressed.
As I'm checking thru the preset:
I noticed encoder 6 "V Zoom" isn't zooming but scrolls widow up and down instead.
When I toggle Multidock (from tracks to console), the focus is on bus and it doesn't defualt to last track used
(f.e. have console view with track 2 in focus, toggle multidock to track view, track to still in focus, toggle back to Console,
focus is just on bus and no track focus until I hit "Focus Strip" encoder button)
This doesn't happen if I close Console view, open PRV, and then open Console view back up (have to use mouse for that), now as I was testing I realized that
when I had toggled multi dock before, Console had been primary viewn and is not "linked" to Multidock button (D) so maybe that was what caused the focus problem?
Now if I close PRV, and toggle with console, all is fine. I loaded up Staf, Matrix, PRV, and Console View and all works and no lost focus now.
I will try this in a new project to see.
I tried in a new project with just audio tracks and it behaves correctly, however when I insert a Synth, open PRV with shift+multidock,
I get same behavior as before (loss of track focus when multi dock toggle)?
I went thru with new project, adding sends, multiple vst's, effects etc.
Everything else I try appears to work as it should.
Now that I've had a chance to use the shift+button on Multidock/PRV, browser/inspector, undo/redo....I'm thinking it may be a better idea (which I think you suggested)
to have long press for these buttons instead? I tend to forget that I left shift on when I hit multidock and if I had closed PRV it opens it back up instead of console
Is that possible to do and if so, would it be much trouble to do?
And is there a way to switch which view is current in Multidock? We have one encoder and encoder button left in strip mode, is it possible to do something with that?
Again Alexey, ( I may be redundant but feel I can't say it enough :) ) Thank you for all your efforts and sharing your vast knowledge with me.
Other than the few minor things I came across, this is really working great! :) 8)
I also thank you for your patience with me and my lack of knowledge of the ins and outs of midi routing with in Sonar.
-
Hello again Alexey,
Did what you said, Act controller was also listed as controller, I just deleted it as I don't plan to use it
and could not see were to set it to "no in/output" and I have no other devices plugged in.
ACT controller was the reason for the "leaking"
I checked the vst's and the "Enable VST output" was greyed out and not checked and input was checked but greyed out also.
But something was sending MIDI back to Mini, and that was not AZ Controller nor ACT controller. There had to be some MIDI track with the output to Mini (if there was no VST with midi output, most probably the same MIDI track had input from Omni).
I noticed encoder 6 "V Zoom" isn't zooming but scrolls widow up and down instead.
Should be fixed now.
When I toggle Multidock (from tracks to console), the focus is on bus and it doesn't defualt to last track used
AZ Controller is not changing the focus implicitly. So till you operate the focusing knob, it just follows what Sonar think is in focus.
Sonar is know to have focus inconsistencies, especially when used with folders, take lanes, hidden strips. It behaves differently when Console View is opened (even when hidden in multidock) and/or bus pane is opened. I mean nothing I can change.
Just check in the Control Surface preferences you follow "all strips" (not Console or Track view, that triggers extra bugs in Sonar).
Now that I've had a chance to use the shift+button on Multidock/PRV, browser/inspector, undo/redo....I'm thinking it may be a better idea (which I think you suggested)
to have long press for these buttons instead? I tend to forget that I left shift on when I hit multidock and if I had closed PRV it opens it back up instead of console
Is that possible to do and if so, would it be much trouble to do?
No trouble, done ;)
And is there a way to switch which view is current in Multidock? We have one encoder and encoder button left in strip mode, is it possible to do something with that?
Sonar "forgot" to expose Multidock operations to surfaces... In general, once any preset is doing a lot, related Sonar bugs and limitation are what become obvious. They simply have not touch the thing since more then 10 years.
Again Alexey, ( I may be redundant but feel I can't say it enough :) ) Thank you for all your efforts and sharing your vast knowledge with me.
Other than the few minor things I came across, this is really working great! :) 8)
I also thank you for your patience with me and my lack of knowledge of the ins and outs of midi routing with in Sonar.
You are welcome. You have brought an interesting idea to use 8enc+8button controller in one strip mode. I had one strip presets before, but they all was for dedicated to one strip devices. So the knowledge was flowing in both directions!
-
Good after morning! :)
"But something was sending MIDI back to Mini, and that was not AZ Controller nor ACT controller. There had to be some MIDI track with the output to Mini (if there was no VST with midi output, most probably the same MIDI track had input from Omni)."
Again, you are correct, after I posted last night and went back to my original test file, there was one lone midi track not linked to any Synth, so yes, I believe that is part of the problem. I believe I used a the "basic" Sonar template to create file and it starts with one audio and one midi track, ::) my bad. This is something I will look out for in the future.
I'm understanding better now how the focus works, multidock and the limitations faced with Sonar itself affect things , thank you for the explanation. :) 8) Too bad Cakewalk wouldn't invest a bit more time into that end of development. 10 years , wow.
I will test the two "fixes" tonight and let you know, I expect that they will work fine :D and again, thank you!
-
:) 8)
It all works! (and I knew it would ;) ) Long press now instead of shift on 3 buttons, V zoom works, re-tested some other functions and all works.
I think it's good to go to "release". Works for what functionality I desired. Some other folks might have ideas to add too (or be smart enough to customize to their liking). I'm going to read up on the mapping for the vst control and tweak that to my needs. I may have a question or 2 but I think you explain it very well from what I've already read.
Thanks again Alexey, great job! :D
-
Super! I have moved the preset post into "Presets" board. I will also post in CW Forum, that is the first complex integration for modern controller ;)
Thanks for your ideas, time and patience!
-
Thank YOU, Alexey!
Your willingness to help others is very admirable and inspiring!
I managed to do some mapping for Act too. Your Actfix program and "tutorial" are really helpful! :) 8)