User 905133

Do you have the most current version of Bandlab Assistant? Evidently there is a newer one today. My attempt to update it "Failed." ? (1) Will see if I can work around that. (2) So far, the download button and the download doesn't help. (3) AHA! There was a hidden installer dialog that was blocked by another dialog. I said OK and it updated Bandlab Assistant to v. 5.1.2. Last one I had (before just now) was a verison before that--maybe v.5.1.1 or v.5.1.0. Try looking for buried dialogs. This is the one I had that prevented the installer from completing. Once I said OK, the installer finished updating Bandlab Assistant. Just a guess: (1) possibly the automatic installer failed, but left some processes on my computer. Then (2) when I clicked on "Download" and tried running that *.exe file from my browser's storage, the processes caused the manual installer to ask me to close the failed attempt processes. I know in the past I have had success with Bandland/Cakewalk working by manually killing the leftover processes via Task Manager.

Do you mean you have one instance of Cakewalk stretched across two monitors? I am trying to understand how the Workspace button would not be visible. Since I have my monitors at different resolutions, I have Cakewalk open up on my main monitor and have parts of Cakewalk placed on the second monitor. That way the Workspace button/dropdown is always in the upper right of my main monitor. One of my Workspaces has a full Console [in the MultiDock] on monitor 2. If I press D, the MultiDock/Console toggles between minimized and full screen. Above: this Workspace opens with some plug-ins on monitor 2 based on the project loaded. Pressing D then D again places the MultiDock/Console on top of the plug-ins. I have a different Workspace with just the Console on monitor 2. (The black space on the top left is because the monitors have different resolutions and that's the way PrntScrn captures it. I don't see the black space on the monitor.)

One technique I use is to have multiple channels set up with different patches on a hardware or software synth and just change the transmitting channel on my keyboard. So, that can be an intentional performance/recording strategy. Just a matter of personal preference.

Hmmmm. I have never used SMPTE (except for testing and deciding it was not what I needed ages ago--pre-Windows CMS interface + a striped tape), but with all the cross-synchonizing devices that have come out since, might SMPTE offer an even more precise option?

I have had SONAR synced to an external MIDI clock and I can see the value (based on your description) of not only keeping in sync while recording, but also mapping the external clock to a tempo track. Not sure if the developers ever considered implementing that and decided it would take away resources from recording, audio processing, etc. The workaround to record a click track and then do a Fit Improvisation / create tempo map sounds like a decent option as @David Baay suggested. I wonder if Cakewalk can record the metronome to a metronome track for that purpose (possibly with the audio not being outputted at any audible level). If so, maybe it would require a single-pass operation to make a tempo map. This assumes the performers are synced to a BPM/midi clock that can be reliably captured as a metromone/click. I know in earlier versions of Cakewalk/SONAR it was possible to record the Metronone onto an audio track--even by accident!

Does this help?

Are any of the patches multisamples with different zones? For example, I have soft synths (and gear) that have orchestral instrument groups arranged in different ranges across the keyboard. With a single patch like that someone might want separate tracks--First Violins, Second Violins . . . Basses. Just as guess.

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.