brundlefly

Seems only to affect track/bus names shorter than 7 characters.

If you draw tempo changes, it's easy to end up with more tempo changes than necessary. I recommend drawing tempo changes with snap enabled at a resolution that matches the interval between notes in the region. Your issue may also be specific to Kontakt or the specific patches you're using. You might try it with different instrument in a copy of the project just to compare. You might also try setting a non-zero BounceBufSizeMsec= value in AUD.INI (Preferences > Audio > Config File). By default (BounceBufSizeMsec=0), Cakewalk uses the real-time ASIO buffer size to process audio offline. Setting a higher value in AUD.INI, can improve rendering performance. I have mine set to 20. Values up to 200 are reasonable.

I would never have run into this because I almost never nudge MIDI notes in the PRV; usually only whole clips in the track view, and usually only one track at a time.

Most current templates include Master, Metronome and Preview buses. I think only the 'Empty Project' template does not. .

FWIW, I tried LANDR a couple of times, but generally did not like it better than my own best effort. Its primary value might be in providing an alternate perspective - e.g. "Hmmm... maybe I should bring the mid-bass up a bit".

Hmmm... I was actually able to reproduce this, but only once. After Undo, which removed the new track (an empty duplicate of the second of two MIDI tracks selected) as well as undoing the nudge, I could no longer reproduce it, even after restarting Cakewalk. FWIW, I nudged right using Numkey 9 (Nudge 1).

When I updated to the Win10 1909 release, Windows stopped loading the driver for my MOTU MIDI Express XT on boot. I tried everything I could think of to resolve it short of wiping my PC and rebuilding from scratch - not worth it. I just have to power up the interface after boot now. Unfortunately, there's no way to avoid having Cakewalk re-assign MIDI track I/O to other available devices or virtual ports. The trick is to realize it right away, and avoid saving the project with incorrect I/O assignments. If you have to save because you made additional changes to the project, save it with a new file name suffix so you at least have a version with the correct assignments for reference. If you do this as a matter of course when saving, you'll always have a 'good' version to go back to. And, finally, if a MIDI device is going missing in the middle of a project, I would suspect a bad/loose USB cable or internal card connection/seating if the ports aren't coming directly off the mobo. That could also explain an intermittent failure to detect it on boot if your problem with Win10 isn't that same as mine (100% repeatable). Not all PC problems are attributable to software, and coincidental hardware failures do happen.

For the time being, onboard sound is just fine. And it won't affect the quality of exported audio, as this is a purely 'offline' process, not involving the soundcard/interface. For best results, set 'WASAPI Exclusive' driver mode in Preferences > Audio > Playback and Recording, and set the Buffer-Size slider in Audio > Sync and Caching as low as you can, without getting pops/crackles or dropouts on playback. P.S. Welcome aboard. Lots of old guys around here ready to help with any questions/issues you might have, but it does help to read about the basics of MIDI, Audio and DAWs in Cakewalk docs and around the Web at large. Youtube is a great resource.

A driver is a software component that an application uses to communicate with and control hardware. Every audio interface generally comes with a driver and sometimes a software mixer that should ideally be installed before connecting the interface. The latest version is usually available on the manufacturer's website. Make sure you have the most current driver installed for the Behringer, and if you have ever installed a generic ASIO driver like ASIO4All, uninstall it.

In case it is plugin-related, you might try disabling 64-bit Double Precision Engine in Preferences > Audio > Driver Settings.

Utilities > LANDR Online Mastering If it's not installed, you'll be prompted.

Go to Views > Event List, pick the imported MIDI track, and look for orange controller messages, especially SysxData. Patch Change and Modulation events. You can delete them, or copy only notes to another track, using Select > By Filter. But it will be a good idea to look up any controllers you find first to understand what they do.

I run two 2408mkii interfaces on a PCIe-424 card, and they work beautifully at very low buffer sizes. In addition too uninstalling ASIO4All, I recommend you go into Preferences > Audio > Configuration File, and click Reset Config to Defaults. This makes a backup of your AUD.INI file, and replaces it with a default one. Then verify Playback and Record Timing Masters and other audio settings. If problems persist, you should check your system's DPC Latency: https://www.resplendence.com/latencymon

I'm pretty sure the instrument auditions are generated in real time from internal MIDI sequences as opposed to being recorded audio samples. For fun, I once transcribed the sequence used for the fretless bass audition, and it sounded pretty much identical. Imported tracks may contain controller messages that alter the sound of the assigned instrument. So you'll want to start by checking that. If you can share the MIDI somewhere, it would help to understand the difference you're hearing.

- Ctrl+A to select the whole project. - Alt+A to open the Audiosnap palette. - Click the Enable/Power button. - Select 'Auto stretch' in the dropdown to the right of Clip Follows Project. - Click Clip Follows Project button. - Manually tweak tempos in the Tempos view by clicking above or below existing tempos (not possible to drag) in the map or editing numeric tempos in the list pane. - MIDI and audio will both follow the changes and remain in sync with each other. - When you're satisfied with the timing, save a copy of the project as 'Live Stretching' version. - Bounce to Clips each audio clip independently using an appropriate 'Offline' stretching algorithm to render the stretching permanent. - Save that as a 'Rendered Stretching' version so you can easily revert to the original, unstretched version, or to the live stretching version for more tweaks if needed.

So, if it plays fine, at what point does the crash occur? Sounds like you might have time immediately after loading the project to switch the audio engine off, and remove the offending plugin. If not, Start the project in Safe mode by holding Shift while you launch it, and don't let it load the plugin that's causing the problem.

I don't know what the default is for the Basic Workspace, but it looks like I/O is selected in the Track Control Manager at the top of tracks pane. Change it to Mix or All to see Vol, Pan and Gain/Vel+.

Confirmed selection range is lost on delete in the current relase, and was not in SONAR 17.10. Can't say when it changed, but does not seem helpful so probably not deliberate. Maybe related to introduction of selection markers.

No, I never said that. I may only have ended up with a dozen or two custom bindings, but that doesn't mean I haven't spent a fair amount of time in there over thirty years. Not sure what you mean by 'get deeper', unless you mean create/alter many more bindings. If you have a recipe fo demonstrating a specifiic issue, you should share it. Thank you. Always glad to help.

Interesting site. Of his four conclusions about keybindings, I only minimally agree with the first two (TERRIBLE defaults, Can't serach all 'areas'), and absolutely disagree with last two (slow and prone to corruption) . - Everybody has different opinion about what default bindings are needed and make the most sense. I've only had to make a handful of changes to customize it to my needs and preferences. But I have the benefit of having worked with Cakewalk through it's entire history, and learned new keybindings as they were introduced/changed, so they seem mostly natural to me. Ultimately, I don't see how any software with many hundreds of functions is going to have a completely satisfactory mapping of those functions to a 101-key keyboard. - The division of bindings into different 'area' is a double-edged sword. It can sometimes be difficult to find the exact name of a function in order to bind it, but in general, it seems to me that if you're aware of the existence of a function that you want to bind, it should be pretty obvious in which area you'll find it and what keyword will bring it up. - The UI doesn't seem at all slow to me. The writer says he hates Windows; maybe in part because his system has performance issues. - In 30 years, I don't recall ever having my keybindings get 'corrupted' - possibly another example of issues with his Windows environment. I agree the OP needs to make specific recommendations for changes he would like to see.

Looks like a simple doc bug. I can't see that it would be possible to load a mix scene with a track template into a project structure that didn't match the mix scene.

I'm curious to know whether the issue reproduces with Session Drummer or TTS-1 or SI Drums in your environment.

This happens when you Punch-record with Mute Previous Takes enabled. You can unmute all the notes in one go by sweeping through the top half of the clip with the mute tool (sweeping in the bottom half mutes) .

At the mixing stage, input monitoring should no longer be enabled on any audio tracks, so feedback should not be possible. But if you're using onboard sound as the audio interface, make sure the Input in the onboard mixer app is set to Line or Mic In rather than 'What U Hear' or 'Stereo Mix' which monitors and records from the output rather than the input which can lead to feedback.

How many recording moguls does it take to screw in a lightbulb? Recording moguls don't screw in lightbulbs; they screw in hot tubs.