User 905133

Good question. All my Workspaces come up with [Workspace]. So, I unchecked "Track Control Manager" from the "Load from Workspaces" column. That seems to work for me. It keeps the Workspace from changing what you have. So if you have "Custom" as the previous Track Control configuration, when you switch Workspaces, it should stay as "Custom." BTW, it looks like the Track Control setting can be saved with Screensets. Thank you for asking!! I have wondered how to do that myself, but never allowed myself the time to explore it. You gave me the perfect opportunity to move it to the top of my "to-do" list. So, if I shut down Cakewalk with (1) my "==> MIDI" set of track widgets on the Track Control drop down button and (2) my "TEST" Workspace as my last Workspace before shutting down, "==> MIDI" is there when I load a new project. PS: I am not sure if we can force a specific set of Track Controls from a Workspace.

Right click in the blank space of the Control Bar and make sure it is enabled.

https://static.roland.com/assets/media/pdf/DP-10_eng01_W.pdf In continuous mode, can you program NI Komplete to do half-damper with the 0-16 scale? Or, can Komplete map it to a 0-127 range? If not, perhaps one of Cakewalk's MFX [Midi FX] would help, if MIDI-OX can't rescale it. I have used MIDI-OX for a while, but never used this tool. If I were to try to use it to scale 0-16 to 0-127, I'd start here. I'd try it, but I don't have anything that outputs any CC in the 0-16 range. UPDATE: Yeah--that should do it! As a test I mapped a knob on a usb keyboard [set to transmit on CC 64 (0x40 hex)] to CC 65--just as a test. The I/O range seems to work the way you want:

Thanks for the feedback. I already started subtracting tracks to make a minimal project and can use that to write up steps to consistently reproduce the issue with remote control. Just as an FYI, pedal down causes virtual buttons to light, pedal up causes virtual buttons to dim. The actual functions do not change. Same issue with knob/slider data (0-63 = off, 64-127 = on). I will try note and other data, though. Remote control button state + functionality does work properly with track echo to soft synth, though. ADDENDUM: Based on your comments, I have looked up "remote control" in the previous forum. I will need to spend more time there, check to see if those older issues currently exist, look for workarounds that might work, etc. The two-state, flip-flop toggle might be considered a feature request as opposed to an issue. Thanks for pointing me in the direction of previous discussions related to remote control.

I would like to be able to use CC64 via a momentary contact foot pedal to latch and unlatch the track arpeggiator. Ideally, it would be nice to function as an on/off toggle. Using the accepted Remote Control method, the foot pedal changes the state of the button, but not the underlying functionality (latch on/latch off). As a result, the button status and the latch function get out of sync. Also, I would like to use MIDI to control other arp functions. How can I do this?

Unfortunately, there are many different threads where people ask for help related to downloading Cakewalk via Bandlab Assistant and workarounds such as downloading it manually. Here's one from a few months ago. It has suggestions and is marked SOLVED; maybe it will help.

I think you mean the blue on/off button next to the Latch button (in the MIDI tab of the Inspector) as shown below. Thanks. I will continue to explore possible issues I have been having.

There have been a few comments from users that seem to suggest [i.e., this is my wording, not theirs] that only "legacy users" [aka, "old-timers"] are so "old-fashioned" that they use text-based midi-editing (as opposed to more modern "up-to-date") graphical editing tools. ? Just call me "chronologically advanced." With some aspects of using Cakewalk [i.e., "New - Fangled Features"], I am a beginner [aka "Noobie"]. ?

There's this, but it's a global setting (i.e., not per project). ADDENDUM: You can bind a key to toggle the Click Behavior [Transport Seeking Stops Playback] on and off. I tested it with "Z." So if W rewinds and continues playing, I can change that behavior by invoking Z.

I have never before used the Loop Construction View (long-time Cakewalk user, since MS-DOS). However, one of my 2020 goals is to teach myself new-to-me features. So, I tried the Options > Click Behavior > etc. setting you recommended and it worked for me. I am currently using a Workspace that has the Console on Monitor 2 (of 2). So after the click behavior change, the Loop Construction View opened up there. Not sure if yours is a Workspace issue, but maybe try switching to a different Workspace. (If that solves the problem, I highly recommend custom Workspaces-especially since the recent improvements from when they were called "Lenses.") ADDENDUM: Check the Views drop down menu. If Loop Construction View is not there, choose a Workspace where it is there. *as long as the Views are part of the current Workspace. From what I have seen, if something is not in the current Workspace (such as a specific View being excluded), the related functionality will not be there--even from short-cut keypresses.

Assuming you are accessing midi data on midi tracks, this might be a Workspaces issue. If there is no Event List, in the Views Menu drop down, try switching to a different Workspace. Workspaces can include/exclude Views.

I agree! As you point out, from a problem-solution focus, these are all different problems--even if they seem to possibly have some common underlying causes and characteristics. My bad.

Possibly related issue previously noted, described, and confirmed, but not reported (using 2019.09 build 70). Thanks for the visuals show the problem!!! A few pictures are indeed worth more than several dozen words!!!!

merged into Q & A question

I never use automation, but I am wondering if what you are getting is similar to what I wrote up this morning. What do you mean by "you can't [1] toggle it* off or on [2] with the control**?" It sounds a little similar (not sure, though) to my attempts to control the Latch functionality with a Remote Control CC. *toggle what specifically? **with which control?

Not sure if this a Cakewalk settings issue or an audio card software issue. I have 4 stereo outs enabled and new buses get assigned to the first one. I do recall that there was (and possibly still is) some interaction between my card's software and Cakewalk. The advice way back when was to make sure the ASIO channels are setup and available in my card's software first so that SONAR can access them properly. Not sure that's required now. It might be that once its setup, the required info is in an *.ini file [AUD.INI?]. Just a thought pending other replies; I defer to others who are more knowledgeable than me on this issue. UPDATE: I don't think my observation (about possible interaction between the audio card's software and Cakewalk) is pertinent to your situation. I did a test by (1) deleting AUD.INI and (2) deleting the ASIO 1/2 strip from my card's software. Cakewalk still picked up my first output port and sent audio to it; however, my software was not able to send it to my selected output since there wasn't a strip for it in the card's software. As for creating a Master bus from a new, blank template, Cakewalk did indeed direct it to my card's first "hardware output."

AHA!!!! I think you are talking about the Control Bar. Set that up the way you want. You can have them all collapsed vertically if you want or just some. Then make sure when you save the Workspaces all of the Control Bar options are selected to be saved (and then restored). See "Manage Workspaces..." at the bottom of the Workspaces drop down. Aside: For some of my Workspaces I use horizontally collapsed module buttons in a collapsed Control Bar. However, there is a bug in how it restores those which has been reported and logged in for fixing. I mention this in case you might be interested in a narrow Control Bar at some point.

Another option I tested, had some success with, but don't really use much is to save per-project screen sets. (Workspaces are global, as you probably know.) The theory was to save a screen set in slot one and lock it, with an unlocked duplicate in slot 10. For me it has been easier to have 90% setup in a Workspace and then just move things around as needed, so I don't much use the screen sets. Just thought I'd mention it as an option in case it fits better with your workflow.

I usually create new with the current Workspace as changed and then save it with a new name. For example, I wanted to change my usual/current Workspace with a full screen Console on Monitor 2. So, after loading in my then-current Workspace, I set up the Console on Monitor 2, selected New, and saved it with the same name but with "-CONSOLE" appended to the name. You might want to check Workspace Management to make sure you are saving everything you want restored. PS: I suppose you could reuse "CURRENT" to avoid a build up of different Workspaces. I decided against recycling the same name. (You can see the result below.) BTW, one of these days I will reduce the list by moving unused Workspaces into an Archives subfolder (which will not show up in the list--as of now).

moved to Q & A section

This almost sounds like something related that I could use: The ability to have events inserted into the Event List (1) to trigger things at certain times (e.g., clips, settings macros, etc.) and (2) to jump to certain place in a recording such as markers. I suppose if these were on one dedicated track it could be named "Arranger Track," but it would be nice if any track could have these trigger and jump to events. (Not sure if I posted about these before; might have started a post and not finished it--or deleted it because it was a distraction from a problem-solution thread. It does seem directly related to this feature request, though.) While the ability to Drop and Drag, slide, nudge, etc. named visual things (markers, sections, etc.) might eventually be nice, for me it would not be as important as having them as in the first place (i.e., to be added in the Event List manually).

Diagnostic Questions: Are you intentionally or unintentionally using Workspaces [formerly Lenses]? If so, what Workspace are you using (e.g., a factory Workspace or one of your own [custom Workspace])? Does setting the last Workspace used to something specific (the Workspace of your choice) when you shut down Cakewalk make a difference when you boot Cakewalk/open projects? Are you using Screen Sets? If you are unfamiliar with using Workspaces, you might want to read up on them in the documentation and look at recent problems and solutions other Cakewalk users have written about recently. Just a bunch of thoughts. It might not be Workspace related, but using them might give you more consistency.

You can probably make it so the markers, the bar, and possibly the selection shading are the same color as the ruler, if green makes you see red. Maybe not. Numbers become invisible. ?

Footnote: Someone recently asked about the green markers on the timeline (aka time ruler). In many themes, the Selection Markers are a variation of grey/black and might be hard to see. (They were for me.) In fact, if someone has a theme with the markers as green (e.g., Tungsten). it might seem like they are new. Colin Nicholls has the parameter identified in his Theme Editing Guide-in-Progress (the ones in hot magenta): In the current version of Cakewalk (2019.12), hovering over the endpoints have parallel lines with a left- and right-pointing arrows and the letter S [for Selection] for sliding the end markers left or right. The Loop Markers have an L. This is just a footnote to point out the parameter that can be changed for those who don't have green Selection Markers but who might want to turn them green (or any other color) in their preferred theme.