msmcleod

Just a FYI - if you're running Sonar as Administrator (which you really shouldn't be), then drag/drop to & from the application won't work. This is a restriction Windows puts on any application running as Administrator.

Interesting.... is there more than one MIDI input port on the KeyLab? You might find that the transport messages are sent out on a different port, in which case you should probably be not using that port as an input for recording. FWIW - If you've set up a non-ACT control surface that handles messages on those ports, then they're usually "swallowed" before sent to the track for recording.

FWIW, soft synths aren't sent Sysex data, so them being there shouldn't make a difference. You could take @Amberwolf's advice and uncheck "System Exclusive" from MIDI -> Playback and Recording within preferences. Beware however, if you're using a control surface, this may need to be left checked.... actually if you're using a control surface, it could be that sending the sysex out... double check your input ports. From what I can tell, the Nektar LX49+ only uses standard CC messages for it's buttons/knobs/faders, so it shouldn't be sending sysex out (unless you've initiated a MIDI dump), so it's likely coming from somewhere else. The other thing to check is your templates - as a sysex bank gotten itself into one?

Agile.Net is a .NET code obfuscator. CbB's start screen was written in .NET, but AFAIK nothing in Sonar is using .NET. My guess it's a 3rd party Windows Explorer shell extension, written in .NET and obfuscated using Agile.Net. The fact that it happens on the Save As dialog (and no-one else has reported this), leads me to this suspicion. Why it thinks a debugger is running though, is strange.

The first CbB vs Sonar article: https://discuss.cakewalk.com/topic/56103-cakewalk-sonar-2024-feature-overview/ Then there's the specific release notes for each version since then... https://discuss.cakewalk.com/topic/79893-sonar-202407-overview/?do=getNewComment https://discuss.cakewalk.com/topic/80753-sonar-202408-overview/?do=getNewComment https://discuss.cakewalk.com/topic/81670-sonar-202409-feedback/?do=getNewComment Sonar 2024-11 should be out fairly soon.

Not entirely accurate. As it currently stands, when your subscription elapses, you lose the ability to save or export. Apart from that, Sonar will continue to operate.

There is no default binding, but you can bind it yourself in Preferences. I've bound SHIFT + F2 to Rename clip here:

Yes - but not all small boxes are the same. Some will use exactly the same internals as the cheap USB cables, so if you can, get one you can return with a full refund if necessary.

I've use a Miditech MidiFace 8x8's, which has been rock solid for me (I've actually got two - one in the studio, and one in my office). They also do a 4x4. Think of USB MIDI interfaces like a bucket with a small tap at the bottom. The tap is the MIDI speed running at 31.25KBaud, but it's being filled up at USB speed. If you fill it up too quick, stuff will spill out the top... this means dropped MIDI events in the MIDI interface world. The only way to stop a bucket overflowing is to have a bigger bucket. For MIDI interfaces, this is the internal buffer size built into the interface. Cheaper MIDI interfaces have a tiny buffer size, some as small as 128 bytes. Better MIDI interfaces have a much larger buffer size.

Yes - the ring is the mouse wheel. It works really well. I tend to use my forefinger & middle finger for controlling the ball, and my ring finger for the wheel and right button. The left button I use my thumb.

By far the fastest & easiest way to fix this permanently is to: 1. Select all your MIDI clips 2. (Main Menu) Process->Length, then set to 200%: 3. Click OK. This will slow down the MIDI performance to 1/2 the speed, so it'll play correctly at 60bpm.

What was shown in the tempo track? If it showed 120bpm, just set it back to 60bpm after you've imported it. If it's still playing at 120bpm, then it's likely the project was just recorded in double time - by that I mean, who ever recorded it used a tempo of 120bpm but played at 60bpm. There's two ways around this: 1. Set the tempo to 30bpm; or 2. Stretch the MIDI clips to 200% to slow them down to half speed.

You also need to arm your track.

"None" becomes "Omni" when "Always Echo Current MIDI Track" is checked. It's effectively a workflow short-cut to mean ignore all MIDI input on all tracks except this one I'm working on. The MIDI input filter on each MIDI / Instrument track allows you to select specific channels on each device listed. You can even save that choice as a preset if it contains only hardware MIDI inputs. If you change None to something else, then this "None" to "Omni" behaviour goes away and it'll only receive MIDI input from the devices/channels you've chosen. Just change the MIDI input to your MIDI keyboard device and it'll work. It's up to you whether you want "Always Echo Current MIDI Track" on or not. Personally, I find it useful as it saves me having to manually enable/disable input echo. Also consider disabling MIDI output on VSTi synths. Unless they're actually generating MIDI themselves, there's normally no need for it to be enabled as their input can be picked up by other synths when switched on.

@Ricky Wayne Hunt - have you got the latest version of Cakewalk's VstScan ? IIRC, MODO Bass 2.03 started using the new VST3 convention of putting the .vst3 in a MODO BASS 2.vst3 directory. The older VstScan did not support this convention (it was treating the MODO BASS 2.vst3 directory as if it was the plugin itself). You can get the latest here: