David Baay

Mine was one MIDI track and multiple synth audio tracks for the separate outs of Session Drummer 3. I saved it from Sonar and validated by bringing it into a new project from the Basic template in CbB to be sure it wasn't dependent on Sonar somehow. They both reference a common set of Cakewalk Content directories so the same drum maps and track templates are available to both. I've saved other drum track templates in the past to save time setting up the multi-out routing, track naming, panning, etc. Not sure I ever tried to include a drum map before but it seemd to work fine. And I've saved Simple Instrument tracks a templates and neve had trouble getting the synths to load with them.

My Roland keyboards and rack modules all call Middle C (Note# 60) C4. I recall Yamaha generally went with C3.

Working for me. The only "magic" was (as mentioned previously) to save/re-save the map after setting the Outputs to the desired synth (if it didn't load that way in the first place).

This is not the fault of CW. There is no standard for MIDI octave numbering. Greg Hendershott long ago chose to start numbering at 0, I assume just because that's the natural thing to do from a programming standpoint. This makes Middle C "C5". So-called "Scentific Pitch Notation" calls it C4 and many keyboard manufacturers follow that convention, but not all, and synth develpers are also all over the map on this (pun intended). A fair number of them call Middle C "C3" so, yes, you would have to go up two octaves in CW. Fortunately, CW offers a solution: "Base Octave for Pitches" in Preferences > Editing.

I often have dozens of versions of a project in the same folder, and rarely have a reason to separate them. I run Clean Audio Folder (or more often Cakewalk Audio Finder) periodically (e.g. before a backup) and don't otherwise worry about redundant audio files that might be created by bouncing audio in later versions and not clearing out earlier ones. If I really need to know what goes with what, CWAF can tell me.

What tempos, what buffer size, and how far off is the recording with the count-in? I did a quick test and unepectedly found a very small error in the timing of the click recorded with a 1-measure count-in enabled, but it was only about 16 samples (early) with a 128-sample ASIO buffer at 125bpm. Are you using ASIO mode?

I'm curious how they handle the case that a project somewhere else in the file system - maybe just an older version of the same project - is referencing the original audio file. In the case of Sonar, you would have to delete such projects or remove the reference from them before the original audio file could be removed by Clean Audio Folder. And what happens if you try to undo a destructive edit... does it recover the file from the Recycle Bin, or does it maybe wait until you close the project to actually delete files? Or does it just say, "I'm sorry Dave. I'm afraid I can't do that"?

I’m not surprised. I mentioned in another thread recently that there is almost never good reason to do that. My guess would still be be some issue with o/s or driver files or audio hardware. I would recommend renaming CW’s ini files but your clean install probably included removing them.

Sorry, I dId not realize Sonitus preset storage worked that way. I was just throwing out options that will address the overwrite issue in most cases.

Maybe include some specific examples.

See ‘Advanced Editing with Keyboard’ or some such in the Ref. Guide. Old feature that was never widely embraced. You might do better to just get your mouse ballistics, snap and zoom level optimized for mouse editing.

It’s possible the Yamaha has a limitation on editing sound during playback of external MIDI, possibly related to the particular mode it’s in. If you have a bank and patch set in the track, that will get reloaded every time you start playback, overriding any unsaved changes to the patch. But nothing CW does would prevent making changes during playback.

I think you need to do this again from a clean boot, and make sure you got the latest.. Everything is pointing to this being the cause.

- Give custom presets custom names. - Define your own content folder location that Cakewalk doesn’t write to.

With ‘Recycle’ enabled, you can hold Ctrl when clicking to open new plug-in windows.

… or the project or preferences. The vast majority of issues turn out to be due to one of those three or hardware.

Old = stable

Audio performance issues are not common/consistent enough to be attributed to the app.

Much better advice in my view.

Have to say I have never done a “clean” install on anything but a new PC and would never recommend it without hard evidence of “corruption”. That’s a total copout, and for an automated reply to suggest it is really egregious..

Yes, critical points.

Selecting the clip(s) to be transposed would be a prerequisite for any method. Event Inspector is a control bar module and always present in mine - nothing to open or close except possibly the control bar itself.

I actually checked that before posting and it didn't seem to be a problem with the Bounce Buffer at 20. But there could be an interraction between the two settings, and you're right to point out that some plugins may not play nice with 64-bit DPE.

That might be handy handy but I don't transpose often enough for it to be a big time-saver over entering '+2' in the Event Inspector's Pitch field.

@Cobus Prinsloo Looks like those tracks probably all have Prefader Sends to 'aux reverb'. If you don't have LinkPFSendMute=True set in Preferences > Configuration File (i.e LinkPFSendMute=1 in AUD.INI), those sends will remain active when another track is soloed. Depending on what's on that Aux, you could continue to hear those tracks more or less clearly when the one is soloed.