Morten Saether Posted January 29, 2020 Share Posted January 29, 2020 It's our pleasure to announce the 2020.01 release, a continuation of our focus to make Cakewalk as stable as possible and easy to use. A big thanks to our community for sharing your valuable time and feedback - you're helping us build an unquestionably superior Cakewalk with each release! Thanks,The Bakers For new feature details, see New Features. Update Feb 13 2020: Build 26.01.0.28 hotfix Fixed several stability issues. Long MIDI project crashes on playback after seeking to high time value. Smart Solo does not unsolo as expected with Instrument Track Per Output. Insert Time/Measures only shifts markers if clip data exists. Instrument Track Per Output does not insert tracks in folder if Create Folder is selected. CWAF Tool does not work with Cakewalk 2020 builds. Mackie Control does not mute per-output Instrument tracks properly. Update Feb 24 2020: Folders with 'VST3' as part of the name ('VST32', etc.) are treated as VST3 folders and fail to scan VST2 plug-ins. Note: If you installed the Build 26.01.0.28 hotfix prior to February 24, 2020, it did not include the updated VST scanner. To get the latest VST scanner, download it from here , then copy the VstScan.exe file to C:\Program Files\Cakewalk\Shared Utilities. Lastly, perform a VST scan in Cakewalk (Edit > Preferences > File - VST Settings). 2020.01 Features & Enhancements Behavior changes The Duplicate Clip command now respects Snap By. Multi-timbral soft synth enhancements Instrument Track Per Audio Output In Cakewalk 2019.11 and earlier, Simple Instrument Tracks are limited to one track per instance of a VSTi, and a single stereo audio out. Cakewalk 2020.01 has a new Instrument Track Per Output option in the Add Track menu and Insert Soft Synth Options dialog box for multi-timbral soft synths that support multiple outputs. It pairs a MIDI track with a separate audio output track (mono or stereo) for each synth output, assigning sequential MIDI channels. This allows you to have multiple Instrument tracks for a single instance of a synth. The Instrument Track Per Output option is similar to the All Synth Audio Outputs: Stereo and All Synth Audio Outputs: Mono options, except Instrument tracks are created instead of Audio tracks. Note: As with Simple Instrument Tracks, you must split the Instrument tracks if you wish to edit MIDI automation. MIDI chase support for MIDI event buses MIDI chase is now supported for VST3 MIDI event buses that support it (e.g. Vienna Symphonic Library). Show/hide Aim Assist text in Time Ruler You can now show/hide the Aim Assist text in the time ruler. To do so, do one of the following: Go to Edit > Aim Assist and select Show Aim Assist Time. Right-click in the time ruler and select Aim Assist > Show Aim Assist Time. Press ALT+X (can be reassigned to any other shortcut in Edit > Preferences > Customization - Keyboard Shortcuts). CPU metrics Diagnosing glitches in audio playback is now easier with the new Engine Load and Late Buffers metrics in the Control Bar's Performance module tooltip. To view these new metrics, hover the mouse over the Performance module. Note: you must have Show Tooltips enabled in Preferences > Customization - Display to see this. The Engine Load value is a percentage of the total time the engine took to process an audio buffer. If it takes 100% or more of the allotted time, the buffer is processed too late and it will result in audio glitches/distortion. The value in parenthesis represents the max engine load since the time the engine started. Engine load is a better metric to help troubleshoot audio glitches during playback since it accounts for other delays in synchronizing and processing audio workloads beyond what the CPU meters report. It's normal for engine load to be higher than the average CPU meter value shown. The Late Buffers count indicates the total number of buffers that took too long to process since the time the engine started. Too many late buffers will result in audible glitches or distortion in playback due to the audio device not receiving buffers in time. Note: It's OK to have a few sporadic late buffers during playback since it will not result in audible glitches. Optimizations Experimental aggressive task scheduling model We continue to work on improving our multi-threaded engine performance and have added a new "aggressive" task scheduling model. The aggressive task scheduler utilizes more efficient task management that can result in better multi-processing and fewer thread context switches. This feature is still experimental so report back if you notice any improvements or problems when using it. The new scheduling model is activated by setting the ThreadSchedulingModel value to 3. This can be done via Edit > Preferences > Audio - Configuration File. Bug fixes WASAPI Exclusive mode fails to open inputs on multi-channel audio devices. Cannot open some audio devices such as Roland Octacapture as 16 bit in WASAPI Exclusive mode. WASAPI Shared mode kills audio in other apps. Edit tool has inconsistent drop arrow in Mercury theme. MIDI Chase should support VST3 event bus. Duplicate Clip command doesn't obey Snap By, only Snap To. Split tool uses fade-in curve for both fade-in & fade-out. CPU meters do not work at buffer sizes lower than 1 msec. Audio engine won't restart when changing latency while Preferences is open. Scan of VST3 folder should only scan .vst3 files. Potential crash on app shutdown. Plug-In Browser search is not functional with FX Chain presets. Latest release notes are here. See prior release notes. Check out all new features released to date. 3 10 Link to comment Share on other sites More sharing options...
Recommended Posts