Promidi

Actually, come to think of it, I can see why this question - and the question does make sense. When you stop playback, you sometimes get hanging notes, regardless of where your playback cursor is. Is that right? Does the pressing MIDI panic button while a hanging note is sounding silence those hanging notes?

Is the very first note of your project on the very first measure?

In the piano roll view with a controller lane visible, add the MIDI Events CC64 > 0 and CC123 > 0 (can be any value really) You could also use the Event list view to add the required MIDI events.

There is a CAL script called "Thin Controller Data.CAL". This deletes every other controller event. That may do the job. I have also written a CAL script that removes any series of controller events that are less than 30 ticks of each other. (first and last of the series of MIDI events are never deleted). The 30 ticks can be changed in the code.

That would be a question for Arturia....

What graphics card are you using? (make and model number)

Automate the feedback level

Someone who has this issue should lodge a ticket with Cakewalk support to get this sorted.

Just did a test with midichfilter simultaneously routed to Pigments and Truepianos (that is, 3 tracks). I saved the CbB project file and reloaded a couple of times. Each time the settings, routings and what-not where retained. I was able to play both Pigments and Truepianos at the same time. I even saved the midichfilter SIT as a Track Template. The input settings of the midichfilter SIT where retained,

This one works for me. https://www.codefn42.com/midichfilter/index.html

Until the Bakers do that, one workaround would be to load a Simple Instrument Track of a vsti plugin that functions as a thru (MIDI OUT is a copy of MIDI in data) Then for any destination MIDI tracks, set them to receive MIDI from that vsti plugin.

What happens if you move the DirectWave.dll file to another folder (one that Cakewalk does not scan) and then do your scan? A quick google search indicates that this product is for FL Studio 20 only.

This “180 days to download” thing only applies to content like samples. Amplitude 5 max is all effect so you can download this even after 180 days from purchase.

Turning off all input echo via the mix Module also turns off the input echo for Aux Tracks - effectively silencing them. If one has a project with many Aux Tracks, turning them back on is quite a chore (unless you group all of the Aux Track’s input echoes). It would be handy if you can either lock an Aux Track’s input echo to “enabled” on a track by track basis or set it to not be affected when you turn off all input echo via the mix Module.

Same here.

This worked here. Remember these custom automation lane names are saved with projects and any Project Templates. They are not global.

Holding CTRL while clicking node sides adjusts simultaneously Allow invert by crossing the edges. (both horizontal and vertical -horizontal would reverse) When holding CTRL while clicking centre node moves all affected CCs with rectangle

Title says it all.

Can we please have the ability to rename CC lanes in the PRV (When the name is visible)

Currently, Instrument definition files only function for external synths and external sound modules. It would be good if we can add Instrument definition files for VSTi plugins. Mainly for CC types so the correct names show up in the CC lanes in the PRV. I know these names can be configured globally. However per plugin would be nice. Yes, I know I could “just use Automation lanes”. But PRV CC lanes are, currently more flexible (transform tool for exampel),

Sorry, you never mentioned that. My crystal ball is still in getting repaired.

I gave Bluearp a quick try and I was able to get it working here (uninstalled it now) Steps: · Load SIT of Bluearp - enable MIDI out and input echo. Set to MIDI channel 1. Set MIDI in to MIDI Controller (PRC-800.) input echo on · Load SIT with VST that I want to control (Rapture Pro) - input echo on. Point track’s input the Bluearp (Should be present on MIDI in list) · Load preset on Bluearp · Press Space bar - to make Cakewalk by Bandlab play. · Play keys on PCR Pattern from Bluearp played using Rapture Pro.

Always start your projects on Measure 2. Shift your entire project along by 1 measure. Starting everything on the absolute 1st measure does not really give anything time to initialise.

What were you using for the drums in the original Cakewalk project before you did the export to the MIDI file? If you used a drum VSTi, then that is the issue. MIDI files can not have the VSTi configuration in then - these files simply contain MIDI data.. If you don't have an external sound module (like a Roland Canvas for example) that has drums, after you load the MIDI files into Cakewalk, you will have to reload the drum VSTi and then route your MIDI track to that VSTi. You will need to keep the Cakewalk project file as CWP files to keep that routing intact.

Last reply nearly 2 years ago. You might want to start a new thread..... Note: I have yet to have this issue.