Promidi

Strictly as a test, do you get the same issue with Insight 2 (You can try the trial version)

Hi guys I am on CbB 2021.4 Build 144. I have my global snap set to 1/16 and snap behaviour set to “Snap to”. My PRV snap override is turned off. Aim assist is enabled with the “Show Aim Assist Time” time display is enabled. This issue only happens in the PRV. In track view, it’s fine. When the mouse pointer is over anything but the PRV ruler, the Aim Assist line snaps to the correct location. However, when the mouse pointer is over the time PRV’s ruler, the Aim Assist line itself is actually offset to where it should be. The Aim Assist Time as displayed is correct. Also, the time of the next action (note placement) is also correct. ie the note gets placed where the Aim Assist should be. I did not notice this happening when checking the ER Can someone please verify this for me. My next move is a Cakewalk support ticket, but I just wanted to see of anyone else is experiencing this issue.

More info needed.

I would rather the CPU cycles required to do this be used for audio processing. If this was ever implemented, first thing I would be looking for is a way to disable it.

For the Roland SC-880, what you might want to do is, with no projects open, go to MIDI - Playback and Recording and make sure “Driver Mode”is set to MME My configuration is as per my signature and I do not have any MIDI stuttering.

How about now? I just tried and no problems here.

.

Are all of your sample rates set to the same value everywhere (in Cakewalk and Windows)? To check Windows, start + run , "mmsys.cpl" <ok>. Double click your audio interface > head to the advanced tab. To Check your DAW, no idea - you didn’t mention which DAW or version.

As long as it comes with native Windows ASIO drivers, I can’t see why not. That being said, hopefully someone who actually owns a NI Kom­plete Audio 2 with Cakewalk by Bandlab can chime in and relay their experience (listing PC specs as well)

The definitive answer to this would really only by answerable by the Cakewalk developers. That being said, I personally don’t touch the Bindings registry entires. I only use Preferences to make changes to keybindings . There are times when I press a keybinding and nothing happens when it should. To fix that, I simply export the keybindings from Preferences and then edit the resultant KBN file with a standard text editor. I then look for duplicate entries and then resave and reimport.

Does the Roland Rubix22 come with it own native ASIO drivers. If so, then ditch ASIO4ALL

Yes

I just did a test on a track folder and I was able to move it. On the track folder, move the mouse pointer to either side of the folder’s icon until the mouse pointer changes to a vertical double arrow. Then you can drag the folder to your new desired position.

That's how it works here. (I am on ER 2021.4 Build 125) As a test, I created a Workspace with Control Bar Layout unchecked in the right hand pane. When I load that test Workspace, the Control Bar stay put and does not change its layout. I do use Workspaces with custom Control Bar Layouts, so I would know if the test Workspace made a change to the Control Bar Layout. Are you on the latest public build of CbB? (2021.1 Build 98)

You did a fresh install? Do you install all updates (before running BA) - including Vdist runtimes? See: https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads

This configuration only prevents quality updates touching the drivers. If you have not run Windows update for at least 6 months, then you'll receive what’s known as a feature update (Say from 2004 to 20H2). Feature updates do can still update drivers, even if this driver setting is configured not to update. That being said, in all the times I have had Windows 10 (from 1511) I have only had a driver balk once (a few years ago). Even then, all I had to do was uninstall and reinstall the driver. The driver involved was my custom modified driver for the Edirol PCR-800. Even recent feature updates leaves this driver alone now. To report your issue to Cakewalk by Bandlab, See: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Set your Track Control Layout Preset to “All”

When ever I install Cakewalk, it does not offer to change the location. I think on a fresh install and you do a custom install, I think it asks you for your VST location. The location field should initially contain your default location. It's been years since I have done a fresh install, so don't quote me on that.

This should be logged as a standard support request. (including crash dump) See: Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Maybe drop a note Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

The fact CbB it still loads and runs CAL scripts and Studioware panels. I would be lost without these.

Try uninstalling and reinstall your drivers for your audio interface? While you’re at it, make sure you’re using the latest version of all hardware drivers (check using manufacturer's websites rather than Windows updates) One other thing, you might want to configure Windows not to touch any hardware drivers. See: https://www.laptopmag.com/articles/disable-automatic-driver-downloads-on-windows-10

I have created a CAL script that translates Channel aftertouch events to Key Aftertouch events using a selected note to determine the Key Aftertouch note. Translate Channel Aftertouch to Key.cal

Try this https://help.cakewalk.com/hc/en-us/articles/360022063794-I-see-a-white-screen-when-launching-BandLab-Assistant If that doesn’t work try updating the VDist runtimes https://support.microsoft.com/en-au/help/2977003/the-latest-supported-visual-c-downloads If that doesn’t work try contacting Cakewalk Support https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

I think the confusion is that when you lasso select ordinary automation nodes, they do actually become available for cut, copy and paste operations. However, when you lasso select tempo nodes, they only become available for delete operations. In this respect, tempo tracks differ slightly from standard automation lanes. Maybe you could make tempo nodes that have been lasso selected also available for cut, copy and paste operations. The time range can be derived from the time of the first selected tempo node to the time of the last selected tempo node.