SketalDaz

Okay here me out Mr. @msmcleod, What you suggested is close to the result I'm trying to get ...... but: 1. I need the "As Drawn (Linear)" to be translated to the faders / controllers as "As Ride-ed" or something; I prefer to ride my automation when I'm mixing because I feel like I'm performing at that moment while listening to what I'm mixing. Once I hit that STOP button, I'm done - I can't mentally recover what I'm trying to automate and then edit/fix it by drawing what I want into the interpolation line. To me, that's not how the "magic" work. You gotta be in it. Plus, the result I get from recording my automation via fader sounds more natural. 2. I still wish that the resolution can be adjusted. What I'm hoping to be able to do as an option is record the automation in the resolution that match exactly the fader movement when you move it manually on a regular basis (including while holding down ctrl). I can see you can achieve this via drawing by zooming in the wavetable, but referring back to my first point, I don't draw while in my mixing workflow (though, I more likely do so while sound designing). Still, thanks for you suggestion.

Thanks @scook I do appreciate the help, But OMG "1" and "30" felt the same to me or that the change of the setting didn't do anything from my point of view (the original value for the AutomationDecimationMsec was "5"). FYI: my current version of cakewalk is 2022.11 (Build 021, 64bit)

@msmcleod or any one else, Is there a way to increase the resolution of the automation? I like performing automation manually by using the "write" tool instead of the interpolation line, but it seems that cakewalk summarizes my actions after I finish riding the controls / faders. I can see how this can be handy, but for my workflow and style, it doesn't work for me (at least not at the current "resolution"); I need to have a direct / analog-esque control over my riding performance to capture detail moments. thx

You should probably post them at the "Content" section (https://discuss.cakewalk.com/index.php?/forum/38-content/), though I'm not sure which sub categories; it seems that the "ProChannel Presets" and the "Track & Project Templates" are best options for Sonitus / VSTs Presets posting unless Cakewalk staff members plan to add a dedicated sub category for those type of contents.

It would be convenient to have tracks also contain an FX Rack in the post fader area OR be able to assign individual plugins to post fader (I prefer the former, though).

@orhorCan I add this to your thread: ....too late; I already decided. Thanks!

@User 905133 Yes, you are on track on what I was trying to explain. And, no problem, I found joy explaining in depth and it helped me solidify the vision of how will use this feature in my workflow.

Hi Bruno, thank you for adding your perspective to this discussion. Although I personally didn't have too much of a problem to locate the Control Surface API and understand majority of its feature before creating my initial post, I can still empathize towards those who do had a hard time because, for one, the documentations are vague in most feature explanations. So, the user is left to understand the feature through trial and error, which is not necessarily a bad thing if the user end up discovering a workflow that is different from what the features was initially design to do and could be beneficial to everyone (hence my initial post). But, to those who just want to find a feature that a DAW is expected to have, most of them are left "hanging off a cliff".

Ewe, I'm allergic to that. lol

Hi Starship, Few days back, I extensively played with both of the settings -- Cakewalk Generic Surface and the ACT MIDI Controller -- for my Alesis VI49 and found that the Cakewalk Generic Surface menu to be more intuitive, but it does work for both settings. One thing you should make sure to do is after you assigned a CC to a parameter, don't just "twiddle" the rotary / slider; you need to push or turn them to the max negative and positive values. That is when the DAW can actually align the values of the parameter to your Korg nanoKONTROL2. Hope this helps. EDIT: Ok @Starship Krupa, I looked at the two options -- Cakewalk Generic Surface and the ACT MIDI Controller -- again and the main difference that I was able to find between the two is simply workflow on how Cakewalk register and read your MIDI Assignment. For the ACT MIDI Controller, the DAW would read your controller as if there are 8 columns of 1 rotary, 1 sliders, and 1 button, and expect that the user want switch the parameter of each row of rotaries, sliders, and buttons respectively via banks. It also will assume that the 8 columns correlates the first 8 tracks when launching the setup. So if you assigned a controller on your Korg nanoKONTROL2 to a cell labeled R1 (Rotary 1) and then, in the option menu, assigned bank 1 of the "ROTARY" row to control the volume and bank 2 of that same row to control panning , then that controller on your KONTROL2 will control the volume for track 1 when the ROTARY row is on bank 1 and will control panning for track 1 when the row is on bank 2. This logic applies to plugins, but he difference is that you can't customize how the parameters are assigned to each banks. The Cakewalk Generic Surface, on the other hand, isn't as dynamic as the ACT MIDI Controller 'cause it doesn't change the assigned parameters base on banks; it is static and predictable, which is the reason why I see this option to be more intuitive. One issue that I encountered when working with it is that it may not show all the parameters of a selected plugin, so one may have a difficult time trying to assign a parameter not shown on the menu. I had a similar thought in mind for as adding parameters, but for the Cakewalk Generic Surface menu. Also, instead of just one controller to a parameter, it would be nice to be able to assign various combination of controllers to trigger that parameter and then use a controller to adjust the values of that parameter. I discussed it in the following Feedback Loop thread.

You can also use a gate plugin, but I still prefer the volume automation method 'cause you can get the voice to sound more natural that way.

You're close but not exactly what I was trying to illustrate. Just to be clear, it isn't about over writing the information that the keyboard sends to the DAW; it is about letting the user customize how Cakewalk interprets those information when triggering and adjusting the value of a parameter whether it is a plugin or the DAWs surface. Certain actions on the midi controller must be met first in order to trigger that parameter. Only then the user can adjust the values of that parameter using the chosen button / knob assigned to it to do so. Alternative Perspective On a gaming controller (PS4), the LEFT JOYSTICK is used to trigger and control the direction of a character's walking animation. When, the player press and hold down the R2 button while using the LEFT JOYSTICK , the character starts to run. This means that the R2 button is use to trigger the running animation while still allowing the LEFT JOYSTICK to adjust the values of the character's direction. ------- I am sorry for the confusion and I hope this makes more sense. Anything detailed in programming will inevitably sound more complicated "on paper" then it actually is. If users only saw Cakewalk's source file(s) and not its UI, majority of them will think that the DAW is too complex for their needs. This is why I hope in the end the developers themselves understood what I was going for with my explanations.

Hello. I have been playing with Cakewalk's midi assignment features as of late with my Alesis VI49 and thought up an idea that I hope will be greatly beneficial and doable. Looking at the attachment, you can see that my keyboard as customization where I can edit the behavior of each knobs, pads, buttons, and keys -- including midi channels for each -- as presets on the hardware. What I was hoping that Cakewalk will eventually be able to do is allow the user to assign different combination of controllers to one chosen parameter. Example Scenario : Switch 1 / CC 48 (Toggle Button, Midi Channel 1, Trigger Value 127), Switch 13 / CC 64 (Moment Button, Midi Channel 4, Trigger Value 127), Switch 25 / CC 80 (Toggle Button, Midi Channel 2, Trigger Value 0), & Knob 1 / 20 (Midi Channel 2) are assigned to Track 1's ProChannel EQ - Low Frequency Gain Knob. The following statement will not satisfy the requirement or expectation of this parameter control connection: I don't press and hold down Switch 13 as I turn Knob 1 in order to increase or decrease the LF Gain Knob; doing this won't allow the switch's midi value to increase the trigger value specify to what has been specify in order to satisfy the "if" statement of this parameter; the midi value will remain at 0. In Alesis VI49 Editor software, I set Switch 1's "Toggle On" midi value to a number that is less than 127; even if I made sure to press Switch 1 to toggle it on, the midi value will not satisfy the parameters trigger value. Now, if I instead changed the trigger value to a number lower than 127 and kept the "Toggle On" value to 127, the toggled on switch will satisfy the specified requirement. In the "Editor" software, I changed the Midi Channel of Knob 1 to channel 2; if I fiddle Knob 1 to increase or decrease the LF Gain Knob, the parameter won't recognize it as the assigned knob because the Knob1 is no longer sending data through Midi Channel 1. Note: a potential satisfying scenario relating to this -- and knobs in general -- would be if I made Knob 1 as an assignment to the LF Gain Knob parameter via "Midi Channel" 2 and "Trigger Value" 50; then, assigned Knob 2 as my "Set Value" knob for the same parameter; as long I keep Knob 1 turned to a midi data value that's equal to or higher than 50, the connection will succeed and I can use Knob 2 to adjust the LF Gain. I hope I explained this clearly 🙃.

7. Have the option to set the style of knobs, switches, and faders individually.

Hi, I have some recommendation for the customization of the FX Chain: 1. Be able to have unlimited knobs & switches 2. Have the option to add faders (<-- Not important, but would be nice to have) 3. Unlimited parameters destination for knobs, switches, and faders 4. Be able to add FX Chain within an FX Chain like a plugin 5. Be able to customize Input and Output routing -- Left Channel and Right Channel, for example -- of each plugin into other plugins; It will be fine with me if you did the routing similar to Studio One, but a bonus if it can be done like Waveform. 6. FX Chain having a Dry/Wet Knob (<-- This is not Important, but would be nice to have) thx.