Promidi

Yeah, I could have done the loopback recording of the MIDI test. However, as soon as I saw the +10 change to the +50 between CbB and Sonar, I stopped the video. As long as it's just a display issue, and even then only if not using 960 PPQ (which I have not done since 2017), I am not going to lose sleep over this one. It'll be fixed when it’s fixed.

Here is a shot video showing this issue. https://drive.google.com/file/d/1_vsRPeXIpHICjZ8cfmiJewZK-ZfYw4M5/view?usp=sharing

Preferences - Customisation - Display > Base Octave for Pitches. I use Yamaha devices, so mine is set to -2 See: http://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B06

My suggestion is valid. Perhaps I was using some common DAW terminology that you may be unfamiliar with? PRV = Piano Roll View. CC = Continuous Controllers - MIDI events that do things , like adjust volume, pan, etc. Controller lane - Part of the PRV where you can enter Continuous Controllers. (Cakewalk’s user manual is your friend) Velocity - how hard (or fast) a note is played on a keyboard. This is one of the MIDI Note event parameters. The other being duration.

Confirmed here as well. I saved a 192ppq CWB file with a single MIDI track with an offset of +10 ticks in CbB. I loaded the same file in Sonar 2025. The MIDI track offset does indeed become +50 ticks. I confirmed the clock opened as 192 ppq in Sonar 2025 (as expected due to clock being per project). I opened the test file again in CbB, changed the clock to 960 and resaved. When I opened the file in Sonar 2025, the offset still changed to +50. I confirmed for this instance of the file, the clock was set to 960 ppq in Sonar 2025. Looks like Sonar 2025 can indeed change the MIDI track offset of older projects where those clock are set to a value less than 960 ppq. The reason I never saw this situation arise is that since the Platinum days, I am always used a clock of 960ppq. I do use time offsets, but when I open older projects in Sonar 2025, MIDI track offsets did not change for me.

I was thinking this as well, but then I realised this is a per project setting - this clock setting gets saved with the CWP file. Even if you save as a MIDI file, this click setting is embedded in the file as part of the MIDI spec.

This is still the stuff you will need to learn if you want to do things like this.

Please have on your agenda to one day purchase a proper audio interface that comes with Native ASIO drivers. Then you can uninstall the Magic Low Latency 2016 driver. This is not a true ASIO driver but is a wrapper that makes your non ASIO audio device present to your DAW as a an ASIO driver. Cakewalk does not like any form of ASIO wrapper software. An example of such an audio interface that comes with Native ASIO drivers is the Focusrite Scarlett Solo. https://focusrite.com/products/scarlett-solo

What is the make and model of your 5pin DIN to USB adapter?

Open the MIDI tracks in the PRV. Then open up the controller lane. The fade outs will either be by means of CC Events (Probably CC7 or CC11) or the notes’ velocities. If it is via CC events , using the Smart Tool, selected all of the CCs responsible for the fade out except for the first CC event at the start of the ramp. Then delete. If it is via note velocities, using the Smart Tool, select the notes that are fading out. Then, while holding SHIFT, drag the velocity of the last note up. This will edit all of the velocities to create a line of velocity values. Simply drag the velocity of the last note to match that of the first. That will get rid of the fade out for that track. Of course, you will have to do this for all the MIDI tracks in this MIDI file.

We need more information from you. Which version and iteration of Cakewalk? (numerically - don’t just say “the latest”) If you are recording MIDI information into a MIDI track, you need to route that MIDI track to something that can actually make sound - like a synth plugin, or and external keyboard capable of receiving MIDI data.

That actually sounds like a PC issue (or driver or even a plugin) rather than a Cakewalk issue.

What happens if you select none?

Paste this into Start + Run to go to the correct folder. %AppData%\Cakewalk\Library

What is your sample rate, Bit Depth and Buffer size? Is “Plug-In Load Balancing” enabled? - Try with this disabled if enabled. Because it’s not mentioned, I am going to assume you are using native ASIO driver mode.

Did you perform the sign out then sign out from Cakewalk by Bandlab’s help menu?

I use outboard gear that relies on Sysex data being transmitted to and received by that outboard gear with perfect integrity. I am not sure I would be trusting a no name brand USB to MIDI adapter to perform that particular data transfer in a way I would trust a more expensive brand. Even If all you are doing is using an older keyboard that has on older 5 pin din MIDI out port to play your VST plugins, I would still avoid a cheap no name brand USB to MIDI adapter. Of course, another option is to simply buy a more modern keyboard (or even a MIDI controller) that has a USB port.

On the current version, clicking in the top half selects all between from the marker to the left and to the marker to the right of where you click. If no tracks were selected before clicking, all tracks are included in the selection. If any tracks are selected when you click, the selection narrows (or expands) to include the data from the marker to the left and to the marker to the right of where you clicked.

I sincerely hope this never happens.

Under Global Bindings Go to Thru Go to From (In that order)

That would be true for the cheap no-name brands. The branded ones tend to be more reliable and do have buffering - I use a Roland UM-ONE mk2 and I do not get stuck notes.

More information needed. Which version (numerically, don't just say “the latest”) and iteration of Cakewalk/Sonar? Is this while playing live or when playing back recorded MIDI data (or both)? How have you connected your keyboard to the PC? (5pin din MIDI or USB or via a USB to MIDI adapter) If USB, is this connected directly to the PC and not via a non powered Hub? What are you using for the sound source - the keyboard’s internal sounds, or a VSTi Plugin (if the latter, which one) What are your PC specs. What is your sample rate, bit depth and sample buffer size. What driver node (true ASIO or WASAPI) What is your Preferences - MIDI - Playback and Recording > Prepare Using N Millisecond Buffers set to?

Are you using a workspace? If so, does setting the workspace to “none” solve the issue?

If you have set a selection marker in the timeline, the left edge of the marker is “From” and the right edge of the marker is “Thru” I have mapped “;” to “set Now=From” and “ ' ” to “set Now=Thru”

Check the Event List for any CC events. Also, are there any automation nodes for the MIDI track at that point in the track