OutrageProductions

Make sure that that many measures or length of time is not locked into your Workspace that is being used for your startup default project template.

I occasionally run across this issue too. When ZoomAll (horizontal [Shift-F]) and there is extra space at the end of the last note that doesn't belong there, my first thought is to <Select All> tracks in track view, Ctrl-Clik on the <Expand Automation Lanes> button on any track and see if there is a an automation envelope (or many) that extend beyond the end of the song and either delete or edit the last node back to the proper end of the track. Takes some seek and destroy, but solves my problem. Generally the session won't do that again after saving. I inadvertently will move/edit a section waaayy later after the song and then put it back into the arrangement, and at that point I find that there is usually a Volume (CC7) or Expression (CC11) envelope stuck out into the next county... Check that first.

Does anyone know if there is an easy way to create/edit the list of note names in an instrument definition OFF-LINE? (as in a text editor, etc outside of the CbB application) If so, what is the specific format and syntax? [Edit] Never mind... found the {.note names } section in an existing *.ins file, will work from there.

Don't feel bad. I write about 5 to 10 film cues every week. After I get about one minute of it done, I know if I'm on to something. Needless to say, I manage to keep only about 20% of my initial work to continue on. The rest goes in the trash. ?

Usually, there are fader channels for your hardware outputs on the far right side of the console view with VU meter indication if audio is leaving CbB heading to your Audio I/O. If it is showing signal over there but you still don't hear anything, then check the hardware.

If you learn things easier via video tutorial, Mike at Creative Sauce has a slew of well done videos covering CbB. Subscribe to his channel, you'll like it. https://www.youtube.com/watch?v=_2izQxY_x3Q

Those are the automation data tracks. Right click and delete the envelope and your fader will operate normally. Or 'unselect' the (R) in the track (automation read) and that works too.

I have a similar issue that is totally related to my mouse pointer placement in coordination with my Kensington Expert Trackball. If I don't hover and click on the first 2-3 letters of the FX name it won't open, also occurs in PRV when inserting articulation names. Have definitely pinned it down to the way my Trackball works w/CbB. Sometimes have to click thrice to activate. Other mice, no problem.

Unless you plan to sell your final product for profit (ie: you're in this for personal enjoyment), then don't bother with the gain knob. Lots of mixes (even back on large format analog consoles) were done with some of the faders in the -40db range and below. Yes, keeping them in the 0db range allows for more finesse for the professional product, especially when automating flying faders, but it's a matter of personal choice. If your initial instrument audio is printing in a healthy manner (not too quiet and not clipping) then just have fun. Always print your final mix with effects, cuz they can't be added later. And generally, a finished mixed audio track cannot be "turned back into MIDI". Also check out the YouTube channel from Creative Sauce, he does really good, simple, detailed tutorials, in plain (well, Aussie ?) language. Start here:

I do mostly audio post for video and always cut & print at 48k/24b because all of my video post mixing stages require that as a minimum. So therefore, there is no rendering necessary in any of the audio/dialogue/foley tracks that I send.

Folders are a GUI enhancement only for housekeeping purposes. I use tons of them for grouping instrument voicing in my soundtracks, and then collapse the folder to move on. However, try setting both midi tracks to (your midi control input 'omni') and then highlight the folder which will activate tracks in the folder and both tracks should play/record. Works for me. I have also set a midi split on my keyboard controller and send channel 1 to one instrument and channel 2 to another instrument with simultaneous success as long as both tracks have 'attention' and have midi echo on.

I don't know if you ever got an answer, but here it is: To enable MIDI outputs on a synth When inserting a synth from the Insert menu or the Synth Rack, select the Enable MIDI Output check box in the Insert Soft Synth Options dialog box. The soft synth will now appear as an Input option on all MIDI tracks just like any hardware inputs.

I've had this issue since Sonar 7 and pinned it down to a hang in my ASIO M-Audio driver. Power cycle on my Audio Interface has always freed the application from memory. Or the technique mentioned by Clovis (above) also works, but can raise issues if you have anything else other that Cakewalk running in the background.

I found this to be tricky as well in many DAW's. Kontakt/Komplete Kontrol NKS mapped controls can be either recorded/edited in the instrument track of the VSTi itself OR by changing the KK keyboard/Maschine to MIDI mode, assign the desired knob to a CC# and then record it on the driving MIDI track. Not exactly intuitive, but it works without fault once you grasp the concept. I use a mixture of either method depending on what I'm trying to manipulate.

I ecstatically second the above suggestions!!!

@jonathan-sasor sent an idea to me this AM that I haven't implemented yet as my island lost power this morning and I'm typing this on my phone. Check in Preferences/MIDI/Playback & Recording for <Notes> and <Controllers> I know, it seems non-logical, but... It may be possible that the 2020.11 update hashed my preferences in the registry. I haven't had a chance to look yet, but when the lights come back on in the studio, I will.

Yes, in 2020.09 I finally got that to work (cold boot required) and some patience as the VSTi sample pool was large and no longer stashed in the paging file.

Yes, and Yes (I've been using Cakewalk DAW's since ProAudio2 (1994ish) so I'm pretty sure I have the basics down pat. Thanks! Worked fine in 2020.09 two days ago. (EDIT... did NOT mean to have that sound snarky!)

Help, something broke! Updated to 2020.11 last night and I now have no input from my Komplete Kontrol S61mk1 master keyboard controller (running V2.5.0 SW for KK). Checked operation of VSTi's in standalone configuration (Kontakt, FM8, Absynth, Komplete Kontrol wrapper, etc.) and they all work fine. Open CbB, check preferences; Midi devices all appear and are checked. Open simple session (Midi tracks only driving TTS-1), check input/output routing, no Midi note response from my keyboard. CbB virtual controllers (keyboard emulator & Querty keyboard) work fine. Device manager shows all hardware is OK. (EDIT1) Also: Midi data on a track driving a Komplete Kontrol wrapped VSTi shows activity on the keyboard light guide, and does play any audio from the VSTI. (EDIT2) installed MIDI-OX monitor to see if KK61 is sending to CPU. Indicates both note on/off and controller information is being received by computer. (EDIT3) Midi Input/Output activity badge on taskbar shows output constantly. Is it possible that CbB is continuously sending a note off condition? (EDIT4) Removed and reinstalled Komplete Kontrol driver set v4.2.0. Rename TTSSEQ.ini, reboot, restart CbB; no change. My M-Audio ProjectMix I/0 is passing audio and still operates as machine control in Mackie emulation. Win10 Pro 2004, Core i9-9900k, 32Gb Ram Anyone know what else I can do to get this fixed?

It wasn't that far back (March release?) when CbB would still recognize a new midi controller or keyboard if it was powered on AFTER CbB was running, ask if you wanted to add it as a MIDI Device and then open the Preferences dialog. That no longer happens, and it's pissing me off occasionally. I have no issue with having to remember to power all my controllers FIRST (KK61 keyboard, Maschine, etc.) but it would have been nice if the coders had noted that this function was no longer available.

re: Promidi "I do, and for all of the ones I use, I deselect the option "Keyboard Shortcuts" under "load from Workspace" in Workspace Manager." Thanks, I'll try that. Seems that the 1800+ page PDF manual (that was fairly well done BTW, IMHO) doesn't contain that info, or at least that I could find using a multitude of search parameters. I've been with CW since ProAudio 2.0 [1992-94?] (even tho I was forced to use ProTools in my professional studio for 18 years), and this product just keeps improving! But with increased complexity, flexibility, and feeble mind, things get lost from time to time.

I've noticed that ever since the 2020-5 (May) update, that I have to re-import my preference default Keyboard Binding Set file into the preferences EVERY TIME that I start CbB. This is really annoying, as I have deeply customized my bindings, and having to reload them every time is a PITA. Why did you break this preference, and WHEN are you going to fix it?