sjoens

True. I do all my editing in PRV and then wonder why all these "clips" are floating around in Track View. For me it's usually an annoyance to clean them up.

+1 for Bouncing. Highlight the entire track so all clips are selected, then right-click and choose Bounce to Clip(s). They will all become one clip so that you only have one full length clip and one righthand icon. There is usually no reason to have multiple MIDI clips floating around on a track unless you're comparing takes.

I use VSTSynthFont64 and it works. Maybe something's wrong with your set up? Yeah, I forgot it only works in 32 bit Sonar.

Any of those should work but maybe your routing needs adjustment? http://www.vst4free.com/free_vst.php?id=217 Used to be included in Sonar, but no more?

You're right. I actually have an unused MIDI port and label it NONE so it's an actual option. I would also try this in a new project to see if the project has gone roague on you. A few pics of the OPs setup & connections might help too.

This is a good feature request item as doubled notes aren't always obvious and can ruin the sound.

Painted fonts are hard to get spacing and letter width "exact" with app fonts of same face & point size. For fun, type a letter in Photoshop. Then keep typing that same letter several times. The 1st 3 or 4 letters will be displayed slightly different. If you keep typing the letter it will repeat those variations. If you grab a screen shot of some text item in CbB/Sonar and zoom in you'll see multi colored pixels, not so with painted text.

Tahoma, Arial, MS San Serif, & Times New Roman FWIW paint programs will never display fonts the same as an application does. If you need "exact", grab a screen shot and photoshop the text. Then copy&paste where you want it to go.

Go to your Addictive Drums track and select MIDI Input source to NONE or a different source than your synth.

… or even from view to view when they're open.... is the Aim Assist Line. Clear it off screen before moving on or closing and it shouldn't linger any longer.

Good to know. Normally I shut down the system every day. I turned off Fast Startup to see if any difference but didn't notice any. Anyway, I wonder if this is helping to cause some of the crashes and other anomalies with DAWs. Trying to RE-set my controller yesterday caused CbB to just POOOF! disappear completely. Rebooted and it worked fine.

I'm on Version 1803 build 17134.590 which updated a day ago. No idea what was updated but my system boots up a lot faster than it had been prior. Just read that the latest update 1809 build 17763.379 may cause trouble with multiple audio devices.

1. Go back and read my post above. 2. You don't have to upgrade to download Bandlab Cakewalk. It resides as a separate program.

@SteveC I'm not seeing that, as mentioned. Mine looks like the velocity grid in SPlat & CbB. @Variorum Yes. (white out) Good idea.

Yes, but... a simple knob would be so much faster. AAAAANND could be assigned to a - per track - controller knob for even faster control.

You will never outsmart the scook... Never!

A simple way to route a MIDI track to multiple synths would be the best way.

Good to know Bob. Thanks. I actually want to access the keys as well as play the whole range. Hard to do with a 61 key synth, so I got an 88 key controller.... Guess it's too late for "free".

FYI, For those just tuning in, Theme Editor does not change anything in the two default themes, Mercury and Tungsten. You save changes to a new theme as mentioned above. Then you have to select the new theme in Preferences.

There is no "auto-tune" in Sonar/Cakewalk. The flanger you've highlighted does seem to be DOA. Skip it and continue down the list to "Cakewalk > Flanger…" and it will open. Just below 'Cakewalk' is 'Sonitusfx' so you already have those too, tho I don't see a flanger there. To install plugins (dll files), just place them in the Cakewalk VST folder and run a scan to pick them up. To install plugins (exe files), just double click the file and run the installer. Also, the "Process" menu will 'permanently apply the effect to the audio clip. It may be better to add the flanger to the FX bin first so you can play with the settings nondestructively. Once you've settled on the right settings then you can "process" it if you want.

Nothing is ever 100%, but if they say it works, it should work. For the most part it does so I'll probably keep messing with it.

Funny it coincided with the addification of Google ads to the old forum on mobile devices (both mobile app and regular website). Collapsible Banner ad at the top, intermingled thru posts, & trailing ads at the bottom. The mobile app also displays links to the new forum under the Featured Articles button. FWIW, you can still log in to the old forum.

So some the same and some different.The only way to be sure what's to blame may be having a computer with ONLY Cakewalk on it so there's no interference from anything else to eliminate. I've requested that but we'll see. If they can't replicate any of the issues then they wouldn't know what to fix or update. I'll mention your findings to them. I suspect more people don't have issues because they haven't explored all the features or they simply don't report them. Even though these are minor they should still work as advertised.

What can I do if I'm the only one having these issues? I have a Nektar LX88+ that behaves sporadically in Sonar X2, X3, Plat, & CbB. It behaves normally with X1 & all other DAWs on my system. Nektar says it behaves normally with their copy of CbB. What could be causing this?: 1. "Patch' buttons don't cycle thru the Synth Rack as they should. 2. 'Patch' buttons act like Play/Stop buttons. 3. "Inst' button only brings up one instrument even when a different one is selected. 4. Control Bar displays computer code characters in the middle screen instead of instrument name.

I followed the download & installation instructions. I should have mentioned that but for me it's a given. According to Nektar support, it works with their testing of CbB and haven't heard from anyone else with issues. I sent them some MIDIOX midi data reports and they say the data looks normal. My X1 works fine with it. For some reason X2, X3, Splat, & CbB don't. There is clearly some data corruption going on there so I need to keep investigating. FWIW, it works as expected in all my other DAWs.