David Baay

Oops. Should have figured that out, myself. I've never paid much attention to the Lens/Workspace feature, so wasn't thinking about how they're stored. %AppData%\Cakewalk\Cakewalk Core\Lenses

.INS files are Instrument Definition files - no relationship to ruler settings. If you don't have a Workspace enabled, ruler settings are project-specific - i.e. stored in the .CWP.

Looks like an anomaly with Elastique stretching enabled on the second track. Changing the Online Render algorithm to Groove eliminates the issue. I've encountered similar issues with Elastique stretching both on and offline. Not sure if it's inherent in Elastique or related to Cakewalk's particular implementation.

If you record MIDI without hearing anything, does it record as expected, and there is activity in the MIDI meter on playback? If so, you probably just need to enable Input Echo - looks like ))) - on the MIDI track or have Always Echo Current MIDI Track enabled in preferences, and have the MIDI track focused. If MIDI records and plays back and live input is echoed per the MIDI track meter, but you don't hear anything, then the question is where is the audio coming from and how are you monitoring it? If audio is from the Motif, itself, are you using the built-in mLAN digital audio interface, or analog or SPDIF output to an audio interface? Either way, if sound is to be monitored through Cakewalk, you need to have an audio track in the project with Input set to appropriate port/driver enabled in Preferences > Audio > Devices and Input Echo enabled on the Audio track.

It sounds like possibly you haven't installed the ASIO driver for the MOTU. See 'AVB / Pro audio' section of this page: https://motu.com/download Top Google hit on 'ASIO acronym' (from Wikipedia): Audio Stream Input/Output Audio Stream Input/Output (ASIO) is a computer sound card driver protocol for digital audio specified by Steinberg, providing a low-latency and high fidelity interface between a software application and a computer's sound card.

I can't replicate this, either. All automation curve types are honored as expected with Sonitus EQ. The only idea I have is that this might be O/S specific. Are you on Windows 10?

PR is Piano Roll, usually called PRV for Piano Roll View. I almost exclusively use the Smart Tool, and Ctrl+left-click allows selecting multiple notes. But I just tried with the Select tool, and Ctrl+click did not work as expected; it's necessary to Ctrl+click and drag to lasso each note. So try it with the Smart Tool.

Actually, I did read the post fairly thoroughly, and your suggested changes to PRV tools are exactly what I was referring to. I don't have the time and patience to respond to everything at once, especially knowing that I might have misunderstood some of them, but here are a few quick examples: Screensets, Workspaces and the Multidock have already been mentioned as solutions to getting persistent and desired window layouts, and will also likely account for Control Bar and Autozoom persistence issues. As you may know, holding Ctrl while changing a control in one of two or more selected tracks change all of them; this is Quick Grouping. It works with I/O assignments as well. That should already be happening. Make a separate post to troubleshoot. Cakewalk deliberately differentiates between selection (the source of a copy), and focus (the target of a copy). This facilitates all kinds of track-to-track and lane-to-lane editing that wouldn't be possible if clicking in a lane moved both selection and focus. What might work would be to have clicking in an empty part of a lane move just the focus there, but the possible consequences to other workflows would need to be considered.

The trouble with 'laundry list' posts is that trying to have an ongoing exchange of information, ideas and opinions about any one of them rapidly leads to total chaos. Suffice it to say: - All crash/bug/fix scenarios will require detailed steps to reproduce in order for Dev to have any chance of fixing them; many of them are not reproducible as described for me. - Many features mentioned already exist in very near or exactly the form described (as I understand them). - Many suggested changes to UI input/tool behaviors would need to be optional in order not to foul up long-time users who have adapted to the current implementation, and allowing this kind of customization inherently compromises maintainability/supportability. A lot of the complexity that new users complain about is due to the already vast array of preferences and options, and the difficulty of relating an unexpected/undesired behavior to a setting. EDIT: That said, I should add that I think there's some good stuff here, too.

This came up a few days ago with another Kontakt 6 user. He found that disabling 'External Sync' in Kontakt eliminated the problem.

Looks like a side effect of the ancient bug with drag and drop option 'Slide over to Make Room'. Change that to 'Blend', in Preferences >Editing, and I think you'll be good to go. If you do actually need the 'Slide Over' behavior at some point enable Ripple Editing instead.

I can't reproduce a gap appearing when the crossfade is moved with or without snap enabled. What tool are you using, how far are you moving it, and how big a gap appears? Are the fades lost/changed or just move with the clip boundaries? And are you running the current, hotfixed, version 2019.11.63?

Cakewalk is more lane-aware than it used to be. By default, material will paste into the same lane from which is originates. This is convenient in most use cases, but not in this particular one.

I'm sure Cakewalk's MIDI port management could be re-architected in some way to preserve the assignments, but it's probably not a trivial change. I'd settle for having an alert when Cakewalk is launched that ports/drivers enabled in MIDI Devices are missing.

If you paste to a focused track in Blend mode (i.e. sound on sound) with no specfic lane focused, Cakewalk should put the clip in a new lane. But I recommend you just take charge - create the lane, and drag or paste deliberatley to that lane.

Yes, that's the first thing I looked for as well. Tempo of 77 at 1:01:000 changes ot 96 at 9:01:000. Dragging the clips to a region with a lower tempo will make the clips appear shorter since the M:B:T timeline is the fixed scaled in Cakewalk.

Any number of programmable soft synths (some free or dirt-cheap) may be able to emulate the MU80 sounds. If you have Dim Pro, Rapture or Z3ta from earlier installs of SONAR, you might start there. But, frankly, I wouldn't bother unless your intent is primarily to learn synth programming; I would just use the hardware.

Yes, X just toggles Aim Assist on/off - it has no other effects: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.19.html

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.