OutrageProductions

OK, just installed the 2021.06 (Build 053) update, and WORKSPACES STILL ignore the visibility toggle of the Browser when saved. Can you guys see if this can be dealt with anytime soon? Example: in Track View, I close the Inspector (I) and the Browser (B) and save workspace. Next time I choose that workspace, the Inspector is hidden at the left, the Browser still shows up on the right. I would like to see the Browser hidden when I toggle it to hide in a workspace, Please! It seems to hide in ScreenSets just fine, but I want something that is Application universal, not just session specific. [EDIT] Actually just tested it on a couple of other sessions, and on my other computer, and it will not hide the Browser in SCREENSETS either. Issue has been in the application since the inclusion of WorkSpaces!

Really nice having Tempo Track grid lines. However, all but the two top-most horizontal grid lines disappear when Alt+T is toggled. And this version seems to have broken something in SCREENSETS; will NOT save the toggle position (open or hidden) for the BROWSER.

Hey guys... absolutely LOVE the tempo track revisions, and a couple of the minor bug fixes are very welcome for my Modus Operandi. However, I notice that the Visible/Hidden status of the Browser (B) is still being ignored by the Screensets Module. Can that be addressed in future? Inspector pane (I), and Dock (D) status are saved in Screensets, but not the Browser.

I have this issue of disappearing dialogs only with the Drum Map view <Map Properties> dialog. in keyboard view of PRV any Note Properties dialog stays focused. My normal operation is for the PRV to be full screen on Monitor 3... when I have a VST window open (and PINNED) it will pass behind the PRV until the next time that I call focus to that VST track or instrument, then it comes forward again. I often have 3 to 6 VST windows pinned behind the PRV and they always come fore when called. Just FYI.

I don't know how long this has been happening but I found an issue (albeit minor) in using the Drum Pane of the PRV when the PRV is undocked as a floating window or on another monitor. Right click on note to open Map Properties dialog and it will not retain focus, so it slides behind the PRV window and can't be found again without closing/resizing the PRV window. Workaround is to immediately pull the Map Properties dialog elsewhere on the screen real estate so that it is not covered by any open windows. This makes renaming/routing/editing drum notes very frustrating. Maybe add an <Accept/Cancel> routine to the API call for the Map Properties window so that it retains GUI focus until closed?

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.

Johan; did hou find the solution yet? I found that the update had automatically changed several things in my preferences file... like filtering out the ability to record MIDI notes and controller data. Reset my metronome defaults, changed to default keyboard shortcuts file, etc. Things that you would NOT expect to experience with an update!

Not mission critical but: I've noticed that when exporting a mix (IRT) from the master bus and IF <Waveform Preview> is turned on, only the right channel shows picture after the export UNTIL you click in the track view for the master bus, then it will appear.

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.

No. I completely disabled the control surface (except for audio I/0) and no change. KK S61 is transmitting all Midi data into computer as indicated by Midi Monitor (tried both PocketMidi x64 and MIDI-OX x32) . It is just not getting into CbB at all. As I said in OP, all standalone VSTi's are working too. It has to be something with input data being blocked on the way to Cakewalk. Would a clean re-install be advised? Or is there something in the Registry that is corrupted? Could the page file (even after cold reboot) be holding on to the TTSSEQ.ini data?

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. Anyone know what else I can do to get this fixed? [also posted in Cakewalk by Bandlab top level]

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.

It happened on the last 4 projects that I opened and worked on after the 2020.09 update. I have since reverted (as stated in OP) to 2020.08 and not had the issue at all. I had to keep working because the soundtrack cues were on deadline. If no one else has experienced this, then when workflow slows a bit I will try again... could have been a fluke?

I must be crazy. The 2020.09 release seems to be having very odd behavior relating to frozen tracks. When I try to freeze a VSTi from the Synth rack, it requires me to select the actual synth track in the track view first before it will freeze to audio. When I UNfreeze a VSTi from either the Synth rack or from the Track View, it fails to reload the VSTi and sample pool. (ie: Kontakt or Komplete Kontrol will open but no instrument is loaded). This is a problem because I don't always remember the exact patch and/or tweeks that I made to the instrument before freezing. I reverted to 2020.08 and do not have this issue at all. Anyone else?

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?