Jesse Jost Posted July 25, 2019 Share Posted July 25, 2019 2019.07 Early Access 2 (EA2) installer now available! Our sincerest thanks to those of you who have provided feedback on Early Access 1 - your support this week has been fantastic! We've addressed more issues and found opportunities for additional refinements as well. We invite you to try out the latest updates in EA2. Please note that Early Access installers are update installers, which only update from a specific version. Please choose the installer that applies to you: If you are updating from Early Access 1 (EA1):Download Cakewalk 2019.07 EA1 to EA2 installer If you are updating from 2019.05:Download Cakewalk 2019.05 to EA2 installer If you haven't already done so, please read about the Early Access Program before participating. Thanks again for your participation!The Bakers New in Early Access 2 Improve Time Ruler marker/loop/punch/selection handle feedback while dragging User reported crash on launch Change title capitalization in Preferences dialog If Notifications are turned off, Check For Updates menu item does nothing Regression: Using 3 monitors causes notifications to stop appearing Edit Filter not set correctly after writing automation Dragging audio to time ruler to do ARA convert audio to tempo map does not prompt Dragging audio from browser to MIDI track to do ARA MIDI extraction does not prompt Dragging multiple audio clips from browser to convert to MIDI stacks MIDI on same track Nudge causes MIDI notes to change lanes Automation selection not working correctly in lanes in attached project Regression: Crash dragging empty cell in Matrix View Tab to next/previous note in the PRV can cause crash Preview not working when cropping a track folder composite clip Draw tool mouse cursor flickers rapidly when moving mouse over envelopes Snap Module Displays Whole Duration When Creating New Project Projects with edit filter set to clip automation load with only one envelope visible Clips drag drop or paste across lanes can lead to inconsistent clip envelope visibility Pasting take and automation lanes simultaneously has unexpected results View list of updates in Early Access 1 8 2 Link to comment Share on other sites More sharing options...
Jaime Ramírez Posted July 27, 2019 Share Posted July 27, 2019 The most smooth version of all times... Thanks guys.. 2 Link to comment Share on other sites More sharing options...
Keni Posted July 27, 2019 Share Posted July 27, 2019 Running well here too. I had been having a lot of crashes changing songs/projects that contain the Waves Abbey Road Studio 3 plugin, but it has not crashed since early access 2.... 1 Link to comment Share on other sites More sharing options...
FJ Lamela Posted July 27, 2019 Share Posted July 27, 2019 New update works.But i found this version a little bit slow when i close projects.The update is great anyway! Link to comment Share on other sites More sharing options...
Jaime Ramírez Posted July 27, 2019 Share Posted July 27, 2019 The "Aim Assist" disappears some times, i need to resart the software... Link to comment Share on other sites More sharing options...
Bill Phillips Posted July 27, 2019 Share Posted July 27, 2019 I'm mixing in Console View and dragged an Ozone 8 Imager VST3 from the FX rack of a track to the adjacent track and Imager followed by Cakewalk crashed. Both created crash notifications. I've attached screenshots of the notifications. Cakewalk created a recovery project file which I haven't tried because I had a recently saved copy to revert to. The crash is somewhat repeatable. I was able to repeat it once using the same steps as the first time. I've caused what appears to be the same crash randomly opening/closing and moving the plugin. I'm using version 2019.07 Build 65 (Early Access 2). I recently signed up for early access. No other problems with early access 1 or 2. Since this is my first crash report, I'm not sure how/where to post it. Let me know if I need to do anything else. Link to comment Share on other sites More sharing options...
Lemar Sain Posted July 27, 2019 Share Posted July 27, 2019 Getting crashes with simple copy and paste special with midi. Link to comment Share on other sites More sharing options...
noynekker Posted July 28, 2019 Share Posted July 28, 2019 Yikes! I'm having an issue with the mute button in this early release . . . when I try to mute a single track, it mutes a bunch of tracks, but not all tracks . . . then I see the "mute all tracks" button has become activated . . . toggling the "mute all tracks" button on and off . . . well, there's a definite bug there. The Bandlab Assistant won't let me roll back ? Am I hooped for now ? Anyone recall how to undo this early release ? Link to comment Share on other sites More sharing options...
Grem Posted July 28, 2019 Share Posted July 28, 2019 To roll back from this release, uninstall CbB and then install the released version with BA. Link to comment Share on other sites More sharing options...
noynekker Posted July 28, 2019 Share Posted July 28, 2019 Okay, I've uninstalled the early release and reinstalled back to 2019.05 . . . but this mute button issue still exists. I've now discovered this is actually an issue with my controller keyboard, when unplug it, Cakewalk MUTE button works as expected. Sorry, so this is not an early release bug, it's something with my keyboard controller. Off to troubleshoot. 1 Link to comment Share on other sites More sharing options...
Noel Borthwick Posted July 28, 2019 Share Posted July 28, 2019 8 hours ago, Twisted Fingers said: I'm mixing in Console View and dragged an Ozone 8 Imager VST3 from the FX rack of a track to the adjacent track and Imager followed by Cakewalk crashed. Both created crash notifications. I've attached screenshots of the notifications. Cakewalk created a recovery project file which I haven't tried because I had a recently saved copy to revert to. The crash is somewhat repeatable. I was able to repeat it once using the same steps as the first time. I've caused what appears to be the same crash randomly opening/closing and moving the plugin. I'm using version 2019.07 Build 65 (Early Access 2). I recently signed up for early access. No other problems with early access 1 or 2. Since this is my first crash report, I'm not sure how/where to post it. Let me know if I need to do anything else. I have seen crashes with Ozone in the past - the crash dialog above shows that Ozone itself is crashing not CbB. So you can submit that error to iZotope. Please upload and send me a link to the dump file as well so we can check it out. More info on this here. 1 1 Link to comment Share on other sites More sharing options...
Noel Borthwick Posted July 28, 2019 Share Posted July 28, 2019 13 hours ago, FJ Lamela said: New update works.But i found this version a little bit slow when i close projects.The update is great anyway! We have made some UI optimizations after EA 2 that might help a bit. However I haven't seen anything slower with closing projects. 1 Link to comment Share on other sites More sharing options...
Noel Borthwick Posted July 28, 2019 Share Posted July 28, 2019 7 hours ago, Lemar Sain said: Getting crashes with simple copy and paste special with midi. @Lemar Sain can you upload and send me a link to a crash dump for this? Also if you can include the project file with instructions to repro it will be useful. 2 Link to comment Share on other sites More sharing options...
Keni Posted July 28, 2019 Share Posted July 28, 2019 (edited) New problem has arisen! Not sure if this is due to the update, but I can't find any other reasons... I'm no longer getting any imput from my nektar impact ix49.... I've done factory rest on it as well as re-opening CbB etc. Not seeing any midi input activity at all! Edit: Kybd works fine on standalone synths Edit2: Working fine in other DAWs and when CbB is open MIDI activity appears active in tray Edit3: Examined everything I could think of. Works everywhere but in CbB though the tray midi monitor shows activity. I get no activity on a midi input track. Did anything change related to input/midi issues? This one is quite debilitating right now... <ouch>! Thanks! Edit4: BTW... don't know if it matters but this is a usb/midi device. Edited July 28, 2019 by Keni 1 Link to comment Share on other sites More sharing options...
Starship Krupa Posted July 29, 2019 Share Posted July 29, 2019 (edited) Keni, this is a long shot, but I recently had the dreaded "MIDI can talk to everything but Cakewalk VSTi's" effect, and what it turned out to be was a rogue control surface entry. I looked at Preferences/MIDI/Control Surfaces, and for whatever reason, the input device was set to be my MIDI keyboard controller, and so Cakewalk was interpreting all of its keypresses as control surface movements. Once I set that device to be what it was supposed to be (my nanoKONTROL), all was well. Edited July 29, 2019 by Starship Krupa 2 Link to comment Share on other sites More sharing options...
Keni Posted July 29, 2019 Share Posted July 29, 2019 19 minutes ago, Starship Krupa said: Keni, this is a long shot, but I recently had the dreaded "MIDI can talk to everything but Cakewalk VSTi's" effect, and what it turned out to be was a rogue control surface entry. I looked at Preferences/MIDI/Control Surfaces, and for whatever reason, the input device was set to be my MIDI keyboard controller, and so Cakewalk was interpreting all of its keypresses as control surface movements. Once I set that device to be what it was supposed to be (my nanoKONTROL), all was well. Thanks SK! That sounds very possible. Not realizing that the same device couldn't be keyboard entry as well as commands. I was just testing methods of assigning need the keys to transport controls for a friend. Headed back to the studio now to try! 1 Link to comment Share on other sites More sharing options...
Keni Posted July 29, 2019 Share Posted July 29, 2019 (edited) 52 minutes ago, Starship Krupa said: Keni, this is a long shot, but I recently had the dreaded "MIDI can talk to everything but Cakewalk VSTi's" effect, and what it turned out to be was a rogue control surface entry. I looked at Preferences/MIDI/Control Surfaces, and for whatever reason, the input device was set to be my MIDI keyboard controller, and so Cakewalk was interpreting all of its keypresses as control surface movements. Once I set that device to be what it was supposed to be (my nanoKONTROL), all was well. Thanks again Starship Krupa! [Solved] You nailed this one fast. Deleted the control surface, then it required CbB to be restarted and all is well! Entirely my fault and thankfully, not the early release! Edited July 29, 2019 by Keni 2 Link to comment Share on other sites More sharing options...
Giorgio Gabriel Posted July 29, 2019 Share Posted July 29, 2019 Hello. Is this small issue fixed? Thanks a lot, Giorgio Link to comment Share on other sites More sharing options...
Blogospherianman Posted July 29, 2019 Share Posted July 29, 2019 19 minutes ago, Giorgio Gabriel said: Hello. Is this small issue fixed? Thanks a lot, Giorgio Not yet! They're really doing a great job though! I'm very pleased with the changes made! ?? 1 Link to comment Share on other sites More sharing options...
Starship Krupa Posted July 29, 2019 Share Posted July 29, 2019 5 hours ago, Keni said: You nailed this one fast. Excellent! The telltale was where you were seeing MIDI activity in the system tray icon but nowhere else in Cakewalk. 2 Link to comment Share on other sites More sharing options...
Recommended Posts