Search the Community

@sjoens The ripple edit setting worked for being able to delete the spaces out of my arrangements that I tell cakewalk to delete. Thanks ! : ) Also, through plenty of trial and error, and hair pulling, I did eventually figure out that if I was already selected on track 1, then I copied and pasted sections of the arrangement, then paste later in the timeline, that my track orientation would be kept. But I was hoping there was a setting that addressed this because it is super frustrating and non-intuitive that I have to tell Cakewalk that when I copy measures of my entire song then paste them later in the timeline that I dont want all the tracks jumbled up. Basically every time I cut and paste I have to take the extra step of first selecting track 1 to inform cakewalk that I don't want the software change all the track orientations : ( I cant imagine a style of composing where every time I cut and paste a section of an arrangement I want the software to randomly shift all of the tracks in the song starting at whatever track I happen to have last been focused on. I actually cant imagine any time at all that I want to shift my bass track midi data to the keyboard track, and shift my keyboard track data to the hi hat track, and shift the kick track data to data to the synth track, etc. your info about the ripple edit setting is a lifesaver : )

Yep, turn on Ripple Edit: All and that should do what you're after PRO-TIP: Turn the damn thing off immediately after or you're going to Have A Bad Time.

Using Ripple Edit is the best way to remove "dead" space.

Turn off ripple edit.

Looks like ripple edit is enabled

Ripple in the Arranger works completely differently from Ripple in the clips. In 2020.05, the Arranger completely ignored the project Ripple status, as it has its own ripple behaviour. This behaviour has not changed. In 2020.07, the Ripple Edit does the following: 1. If either Ripple Selection or Ripple All is enabled, the Arranger Move/Copy drag operations act as if the SHIFT key is pressed - in other words instead of "Blend Clips", the operation is "Shift Existing Clips" 2. If Ripple All is selected, sections in the other Arranger tracks are also rippled. If you want to use the existing ripple behaviour, select the section with data then drag the clip instead of the section.

When you Ripple Edit a selection in the track view , whilst dragging your clip(s) the whole track appears to move and not only the selected part..once you let go of the mouse button it corrects itself but visually it's confusing as it looks like you are moving a whole bunch of stuff that you're not.

Just to throw my hat into the ring here, a few quick things that come to mind right away for me are: Consistency - some views work a certain way, others don't. I get the reasoning behind the *why* we might want to have a left-mouse lasso to grab things in the PRV as opposed to a right-mouse one in the Track View, or different double click options, etc. but for a new user, imagine getting used to the standard conventions of most operating systems and then finding "oh that works when I enter in MIDI notes, but how come I can't grab a bunch of clips using that method?" when you try it. Again, I understand exactly why we have it like this and it works really well once you get used to it, but I can see that as a clunk for someone who just dives in. FWIW, REAPER did this first and I remember hating it when I first tried it out. To me it feels more natural in CbB, but it's still a "well that's odd" thing if you're used to selecting things in Windows in general. Consistency (part 2: The Revenge): Some views have been switched over to the Tracks / Inspector paradigm (eg: Tempo Track, Arranger Track, Articulation, etc). Fully onboard with that - these are GREAT enhancements rather than fiddling around opening up different views to do things, thus removing clunk. What about Meter/Key? Markers? If this was expanded to offer stuff like DDP creation, would this stuff live in here? From what I've seen from Cubase, that's how they have the top of their main track view and it's very elegant. Additionally to that, this goes back to my "Shell Game" thing - unless you hit the hotkey to toggle Tempo View, where is it? You can actually drag down on the blank space above the track headers and it magically appears. Again, I get why this is, but why am I even guessing about it? There needs to be something obvious for new users especially. Additionally with Markers, why do we have to delete them by clicking on them with your left-mouse, and while holding it down, pressing the delete key, or changing into the Markers View? Nothing else does that, and it's a big hold over from the CWPA days. It's little things like that which confuse and frustrate people, despite not really being a slower workflow at all. It's just unnecessary stuff to remember. Shell Games: I saw it mentioned in a thread that adding new VSTs can be confusing. I'll admit, I've been burnt by this one. So you install a new Reverb plugin. CbB scans for it and says "hey there it is, great stuff" and then you look in your Plugins Browser and... where the hell is it? If it's a VST3, there's a good chance it's been added into the right category for manufacturer or effect type, but a lot of the time it gets dumped into Uncategorised. There should be a Newly Installed category and a chance to adjust where that new effects subsequently appears from there. No more guessing or hunting, much like I mentioned for hidden tracks like the Tempo track earlier. UI/UX: Workspaces are fantastic, and are a real timesaver once you learn them. Screensets too. But how many people here can really tell the difference between Workspaces and Screensets? Yes, *I* know, but there's been SO MANY questions about this stuff over the years. Workspaces can also really bite people badly when stuff isn't where they expect it to be. How many times have we seen "Cakewalk is crap, they took out X feature!!11!! SONAR used to have this, I'm moving to Bitwig!!!!" and then they're told to change to a different Workspace that reveals that item they were ranting was removed, but really wasn't. There's got to be a better way (besides the new installation onboarding dialog) that helps you choose and understand what Workspaces do, and then after you're already established, helps you understand why things are missing or different. I have no good suggestions here, honestly. But there's got to be some solution to make this better. Following that idea (and this was alluded to earlier in this thread) why can't we drag things around to the different docked areas, eg: like in Adobe products? In Audition, I can make any one of those areas show whatever I want, so for example, docking an ARA view on a side tab rather than the Multidock would be handy, or putting Big Time above the Synth Rack View, or Markers View in a side dock rather than down in the Multidock, or that kind of thing. Ideally for me (and I've mentioned this before), I'd like the "everything is a multidock" idea where rather than specific areas like Inspector/Browser/Multidock, we have "area 1" "area 2" "area 3" etc and in each area we can add whatever view we want to see. Then, to keep consistency with how CbB is now, have a "classic" Workspace that puts things like Media/Plugins/Notes in the area where the Browser is, Arranger/Tempo/Clip and Track Properties, etc. in the area where the Inspector is, and that kind of thing. And then allow us to split those views or add tabs as we see fit. Both of those things stop confusion and stops a bit of the Shell Game with where stuff is going to appear, if someone can set it up to suit their workflow better. Bonus UI thought: How many people here know we can rearrange the Track Header widgets (ie: the volume control, pan control, R/W/A/* buttons etc, by holding down ALT + dragging them around with the left-mouse button? Really powerful stuff for getting things how you like them (it'd be even better to be able to remove them entirely this way, or move them to the Track Inspector to show/clean up the Track Headers). Menu Diving: And this is slightly related to the previous point: How deep do you go with menus before it's too much? How much do you simplify them before power users get angry and go to REAPER to get their endless menus fix? (Sorry REAPER fans, but the default config of REAPER before you clean up anything is absolutely NUTS!) For people using interfaces with a lot of I/O, this is bad enough trying to add a track or assign inputs or outputs, etc. because the list is crazy long. Got a bunch of plugins that expose sidechain? Welcome to Menu Hell. There's got to be some kind of submenu thing going on there (although that takes us back to the menu diving problem again) or have common tasks at level 1 of the menu and then a submenu for other things. Eg: Level 1 could have a simple INPUT > entry and at the top of the list that pops out of there have SIDECHAIN >, but all of the regular interface I/O right underneath it. That way it's really only barely past 1 level of menu to get to the obvious stuff, but any more advanced things need to go down another level. Kind of related to that, and also calling back to consistency, has anyone here tried to add an Aux track? It's easy to do, just go to an existing track and then choose the output to go to New Aux Track or New Patch Point from a send or the Output. Great. Now try to add one without doing that, like you'd do for an Audio or MIDI track with the context menu. What's that? You can't? How about from the Tracks menu? Nope. OK fine, how about we create it using the way I mentioned before and then change all of the outputs of every other track to this new Aux track. Select them all and go to the Tracks menu and... where is my Aux? I only see busses and hardware outs. Huh??? So what I'd have to do is open up the other tracks, shift+select them all, find the Output of one of them, hold down CTRL and then change the output of that so the multiselect works on all of the other selected tracks. THIS is a great example of unnecessary clunk. It's all certainly possible but there's hoops you need to jump through to do it. I have a bunch more stuff I could probably mention but this is a good start. I will say too that I'm purposely avoiding talking about new features here, but like I mentioned earlier about Ripple Editing and the Arranger, sometimes a couple of new features can entirely remove some of these problem areas just simply by making them redundant. The switch to in-app updates rather than dealing with the weirdness of Bandlab Assistant for updates is another good example there. A new feature was added that entirely took the old problem out of the equation. I'm *very* familiar with CbB and work very fast in it, so a lot of these things don't affect me personally much on a day to day basis, but if I was looking at this with fresh eyes, or was new to the app, I could see how this would trip a lot of people up. But going back to my OP, in the day to day driving of CbB, I personally find it just as smooth or as few operations to complete a task as any other app I've used for the most part, and not finding it overly clunky myself, but there are most certainly areas that could do with some attention.

There's certainly got to be some middle ground to cater enough to both parties. Fix the pinch points that are clearly making things annoying for people (new users especially) while retaining enough legacy functions/layouts to not lose long-time users. I mean, that really sounds like that was the point of Cakewalk Next: make a product that didn't have to worry about 30 years of legacy users to keep happy, do it the "right" way from the start (which is still obviously subjective, of course). It's going to be interesting to see what that's like. I think what I'd like to get out of this thread (aside from the great perspectives so far - cheers, everyone, these have all been excellent answers!) is, what areas are obviously not as good as they could be which we could pass onto the Bakers to refine, but without going so far as to change how the core layout and application works. Retaining as much as we can while taking out some barriers. Clearly some parts are going to need a huge overhaul (the drum maps thing was a great point) but some basic things should just do the job with no fuss. No menu diving, no extra dialog boxes, no need to hunt for things or play a Shell Game looking for something that apparently is changed but no real idea what... That kind of thing. That said too, some whole new features have really made a difference to day to day workflow too. Remember how painful cutting out sections of songs was before we got Ripple Editing? What about moving them around before we got the Arranger? We could do both things before but both things eliminated a bunch of Clunk and pinch points just by existing. I have a good list of stuff I'd like to see refined or added too, of course, but I'm also realising how much legacy muscle memory I have when I see threads like this too.

Hello-- I saw the latest enhancement included an indicator in Track view when Ripple edit is engaged. I just tried it out, and I can't seem to locate the indicator. I have the most current patch of CW, so maybe I'm blind. Can anyone share a screen capture so I can see what the indicator looks like? Thanks, Stephen

At last we got a ripple edit indicator. A long awaited tool is here. Thanks so much Noel.

I've found that the click on the section header CAN be finicky sometimes too. I just pay attention to what I'm doing. Ripple Edit has interesting effects on the process as well. I usually don't have envelopes created until I have the whole arrangement settled, maybe that's why it doesn't bother me much.

"Not by dragging, but Cut Special and Paste Special should do the trick. In both dialogue boxes, select markers only." This worked perfectly for my needs. I've done various ripple edits over the years that worked perfectly moving the tracks but for whatever reason my bookmarks weren't in place. This fixes that if issue quickly.

This seems to work fine, indeed! 👍🙂 I have no idea why. The original purpose of this ripple editing is to automatically remove holes when you delete parts of a track, isn't it?

[Updated 29-Jan-2021] Version 2021.01 Update 1 (build 27.01.0.098) now available! We're pleased to announce the 2021.01 release! This release introduces Arranger enhancements, SSO (Single Sign-On) for activation, import and export improvements, optimizations, and over 40 bug fixes, all in keeping with our goal of making Cakewalk as reliable and enjoyable as possible. Thanks, The Bakers For new feature details, see New Features. Should you need to revert to the 2020.11 release, you can download the Cakewalk 2020.11 Rollback installer. Update Jan 29 2021: 2021.01 Update 1 (build 27.01.0.098) Enhancements and optimizations: MMCSS improvements When Use MMCSS is enabled in Edit > Preferences > Audio - Playback and Recording, all threads are assigned to the same MMCSS task groups for better efficiency. In prior releases on multicore systems with 16 or more cores MMCSS limits could be prematurely reached, resulting in lowered efficiency with some audio threads not running at pro audio priorities. The MMCSS thread limit has been boosted to 128 to handle machines with a higher number of cores (requires a reboot after installing this update to take effect) VST3 Host Bypass enhancement The VST3 Host Bypass button now also works when this parameter is not automatable. Bug fixes Stability: Crash inserting Kuasa plug-in. Crash when switching projects using different sample rates with PreSonus Studio 192. Plug-ins: Projects containing certain plug-ins fail to open in 2021.01 release. Plug-in Load balancing threads were not being released. Arranger Tracks: Ripple All not working when deleting from Arranger Inspector. Ripple edit delete using section overlaps crops the clip at the end of the left sections. Ripple Edit delete Section with overlapping notes at the end not working. Arranger: Fix for trailing notes being incorrectly picked up by a section. Articulation Maps: Ripple Edit Delete at beginning of project isn't working with Articulations. Deleting an articulation occasionally splits it into two smaller but invisible articulations. Show/Hide Articulation Pane in Piano Roll does nothing if there are no articulations on the track. Adding a new articulation event should default to velocity 100. Articulations sometimes deleted when using Project > Insert Time/Measures. Automation: Automation write not working with certain VST2 plug-ins until envelope was created. Freezing a synth could cause synth automation on all tracks to get orphaned. Skip non automatable parameters in Choose Parameter dialog. UI: Add Instrument Track not putting audio track in folder / unable to remove from folder. Increased contrast of Piano Roll clip outlines so they are visible regardless of current theme. Misc.: Opening project at different sample rate can fail to engage audio engine. MMCSS threads not properly unregistered on engine termination. MMCSS threads could exceed quota with repeated changes to preferences. Cakewalk no longer attempts to set ASIO thread priority when MMCSS is not enabled. Unexpected sample rate conversion message when bouncing audio. Remove unexpected dropout message when creating or loading new projects. Fixed bitmap memory leak in when editing using AudioSnap that could cause blank screen. Updated CWAF tool latest known version number string to 27.13.0.xxx. Update OAuth to new BandLab backend protocol. 2021.01 Highlights Arranger section inclusion of outlying MIDI notes When dragging sections or committing arrangements, Cakewalk has logic for dealing with leading/trailing MIDI notes that overlap section boundaries. In the following example, section 2 is selected. The underlying MIDI clip contains note events that start slightly before section 2 and end slightly after section 2. By default, selecting section 2 will ignore the portions of overlapping note events that fall outside the section boundaries. Cakewalk now lets you optionally include the full duration of overlapping note events. Notes that overlap section boundaries: Leading/trailing notes are often created in the following scenarios: The recorded performance is unquantized and notes appear slightly earlier than the section start. When using a sound with a slow attack, and the notes have to be played early to make up for the attack time. Leading notes as part of a lead-in phrase, or droned notes that overlap with the section boundaries. You can specify the threshold that determines which overlapping note events are included when moving sections. To do so, click the Track view MIDI menu and point to Arranger Section Event Overlap Threshold, then select one of the following options: Off. Ignore overlapping notes. Note value (Whole – 1/256 Triplet). Only include notes that overhang by a duration equal to or less than the selected value. Any Overlap. Include overlapping notes of any duration. When overlapping notes fall within the threshold set, those notes are included in the section move/copy and the clip start/end is automatically resized (slip-edited) to accommodate the notes. The moved notes are also removed from the neighboring sections. This requires Non-destructive Editing to be enabled, and works best with Split MIDI Note enabled. The Arranger Section Event Overlap Threshold setting affects all arranger drag operations, delete, commit arrangement, and Duplicate from the section context menu. Absolute time in Arranger tracks The time base format for each Arranger track can be set to either Musical or Absolute. The time base format determines what happens to sections when you change the project tempo. To toggle between musical and absolute time, click the icon to the left of the Arranger track name in the Track view: Musical . A section’s M:B:T position stays constant, and its absolute position shifts. Absolute . A section’s absolute position stays constant, and its M:B:T position shifts. Absolute time is useful for scoring to film/video. The Arranger track tooltip shows time as H:M:S:F and samples. When committing an arrangement, the following rules apply: If all the sections came from absolute time Arranger tracks, the committed arrangement track will be absolute. If the sections came from musical Arranger tracks (or a mixture of musical/absolute), the committed arrangement track will be musical. SSO (Single Sign-On) for Cakewalk activation Cakewalk supports SSO (Single Sign-On) for activation, which allows you to log in via any service supported by BandLab as your sign-in authority. Google, Facebook, Apple ID, mobile phone and BandLab user/password credentials are currently supported. SSO is only used for Cakewalk activation, and under normal circumstances you will only need to sign in once. Cakewalk will attempt to refresh your activation status silently and automatically on occasion during start up. Use the SSO login as you have done with your BandLab account in the past. Note that BandLab Assistant is still required for requesting offline activation of Cakewalk on computers that don’t have an Internet connection. Misc. enhancements Cancel VST scan You can now cancel an in-progress VST scan with the new Cancel Scan button in Edit > Preferences > File - VST Settings or via the Cancel option in the VST Scan toast notification. The next scan operation will resume where the canceled scan left off, starting with the plug-in it was last scanning. If the last scanned plug-in was a shell plug-in (such as Waves WaveShell), the scan will resume from he first plug-in in the shell). Auto termination of VST scan Shutting down Cakewalk will now automatically terminate any scan in progress. This allows in-app updates to work properly even if a scan was in progress when the app was shut down to perform a new install. Zoom to Fit Project Horizontally shortcut The new Zoom to Fit Project Horizontally key binding zooms to fit the entire project in the Clips pane, without affecting the height of tracks. The default keyboard shortcut is CTRL+ALT+F. Improved selection with Arranger sections If there are gaps between a range of selected sections, the unselected clips remain unselected. You can now unselect fully selected clips from a selection and they will not be moved with the section. Cutting Arranger section deletes hole Cutting an Arranger section with Ripple Edit enabled now deletes the hole to make it consistent with the Delete command. Clicking on an articulation section now triggers keyswitch events Clicking on an articulation (without modifiers), or changing an articulation’s type or MIDI channel now sends any triggered MIDI events associated with the articulation. Control Bar Select module changes Four new buttons have been added to the Control Bar’s Select module in Large mode: Select Track Envelopes with Clips . When enabled, selecting a clip will also select any overlapping track envelopes. Select Track Articulations with Clips . When enabled, selecting a clip will also select any overlapping track articulations. Select Events with Sections . Enable/disable automatic selection of track events when selecting Arranger sections. By default, clicking an Arranger section also selects underlying track events. Clicking again de-selects track events, while retaining selection of the section. Select Sections with Time Ruler . When enabled, making a time selection in the time ruler will also select any overlapping Arranger sections. Right-click or keep the mouse button pressed for a brief moment specify if sections should be selected in all Arranger tracks, or only the active Arranger track: Select Sections with Time Ruler (Active Arranger Track). Making a time selection in the time ruler will also select any overlapping Arranger sections in the active Arranger track. Select Sections with Time Ruler (All Arranger Tracks). Making a time selection in the time ruler will also select any overlapping Arranger sections in all Arranger tracks. The four buttons are linked to the corresponding menu items within the Track view Options menu, and work in exactly the same way. The previous Large mode for the Select module is now the Medium mode. Moving clips between lanes on the same track obeys Auto Crossfade setting Moving clips between Takes lanes on the same track now obeys the Auto Crossfade setting. Insert Instrument track behavior When selected from the track context menu, the Insert Instrument command now inserts the instrument before the current track rather than after the last track. The Add Track button and Insert > Soft Synth command will continue to append after the last track. Similarly, the Append Instrument Track command in the track context menu will append the new per-output instrument track directly below the current track. Selecting Append Instrument Track from the Synth Rack context menu will continue to append after the last track. Phase/Interleave buttons on Instrument tracks Phase and Interleave buttons are now available in the Track view and Inspector for Instrument tracks. Tip: You can show and hide controls in track and bus strips in the Track view, and even create presets for your favorite control layouts. To show or hide the Phase and Mono/Stereo Interleave buttons in the Track view, open the Track Control Manager and specify the visibility of the Interleave/Phase group. Option to only use external MIDI inputs MIDI track’s that have their Input control assigned to All Inputs receive MIDI data from both external (i.e. hardware) inputs and any soft synth outputs from other tracks. When inserting a soft synth, Cakewalk defaults to enabling MIDI output if it is supported by the synth. As a result, MIDI output from Instrument tracks may be inadvertently played/recorded on all other MIDI tracks if the tracks are armed for recording or have MIDI Input Echo enabled. To address this, MIDI tracks now have a new All External Inputs input option, which only appears when at least one soft synth with a MIDI output is present in the project. All External Inputs means any MIDI input that isn’t an output from a soft synth, such as hardware MIDI ports and virtual controllers. In earlier versions, switching the active MIDI track would normally select All Inputs. This behavior has changed to: If the track previously included soft synth outputs in its inputs, then it will show as All Inputs. If the track previously only had hardware inputs, then it will show as All External Inputs. Export to Standard MIDI File respects selection Export to Standard MIDI File (File > Export > Standard MIDI File) now respects the selection. If there is no selection, the whole project is exported. Updated LAME MP3 encoder The integrated LAME MP3 encoder has been updated to version 3.100. This includes bug fixes and stability improvements to MP3 encoding and also speeds up the encoding process. Additionally, Cakewalk has been updated to now handle discarding padding samples when importing MP3 files. i.e imported MP files will not contain extra data at the beginning of the file. Updated libsndfile encoders The libsndfile library used for import and export of various audio formats has been updated to version 1.0.30. This fixes numerous issues with handling BWF, Wave64, AIFF, FLAC and Ogg files. Optimizations Dynamic plug-in parameter optimizations Cakewalk 2021.01 introduces improvements in responsiveness and memory footprint when loading and editing projects with lots of tracks and high parameter count plug-ins. In previous versions of Cakewalk, plug-in automation parameters for all listed plug-ins were always created up front. This could result in a significant performance and memory hit when using plug-ins that expose hundreds or thousands of parameters, especially in projects that contains many tracks. Internal parameter objects are now created on demand when a parameter is actually used, either by modifying a parameter or by creating an automation envelope for it. A track’s Edit Filter menu no longer lists hundreds of parameters for plug-ins but instead only shows in-use parameters. To select other parameters in the Edit Filter menu, point to the plug-in name and select Choose Parameter to open the Choose Plug-in Parameter dialog box. Improved handling of ProChannel automation Automating the ProChannel Enable parameter would previously only work if the ProChannel UI was visible. ProChannel bypass automation is now UI independent and also buffer accurate. ProChannel bypass will also properly enable/disable with automation during fast bounce and freeze operations. Bug fixes Stability Crash when running onboarding more than once Crash when attempting to load new sample in Drum Replacer Hang on project load while VST scan is running Redo of crop then move of Articulation crashes Automation crash on project close Rare crash after modifying event in Piano Roll then pressing play UI Step Sequencer Clips intermittently fail to show notes Step Sequencer Beat Counter fails to repeat on Groove clip repetitions PRV does not display repetitions of Step Sequencer loops Track names show incorrectly in plug-ins after 2020.11 update Transport fails to roll with Realtime Bounce when freezing Cursor moves unexpected after cancel of Kind in Event List After deleting last event in Event List, selection should go to previous event Assignable parameters not created for FX Chains on project load Project Editing Time displays inconsistently in File Stats Rename clip doesn't work on MIDI clips if articulations exist on the track Installer Text/Progress Bar for Silent Install is truncated Bus pane not updating correctly after using track manager to hide/show buses Clicking on a note within the Piano Roll view or swapping active tracks automatically opens the Articulation Map pane Arranger Ripple Edit Cut not shifting Arranger sections as expected Section/Arrangement titles missing in 2020.11 Articulation Maps Allow drag move/copy of multiple articulations Mouse cursor gets moved/stuck on articulation events in Event List Scaling PitchWheel events gives incorrect results Automation Cannot bounce or freeze ProChannel Enable automation unless it is done in realtime Selection becomes stuck unexpectedly when selecting envelopes Bus envelopes from multiple buses not copied correctly in duplicate clips/arranger operations Toggling track interleave causes plug-in automation to lose sync ProChannel automation cannot be reassigned to plug-in automation in tracks Automation read/write not being acknowledged for newly created FX parameters Copying and pasting FX automation envelopes create orphaned envelopes until parameters pre-created FX Chain Input/Output Gain envelopes controlling incorrect parameter in FX Chain UI Synth Rack automation not shown when changing synth parameters Misc. Allow adding of additional per-output instrument tracks via Synth Rack context menu Add Track inconsistent Insert Track behavior Projects with multiple instances of plug-ins with high parameter counts become very sluggish trying to close/remove instances UseGlobalSnapForStaffView variable stops working after opening older project Imported .wav file has clicks from time stretch Drum Maps are saved unexpectedly with Track Templates VST Scan does not close with the app Control Surface Refresh value does not change as expected below 25ms Custom bank selection does not take effect in Event List view Insert/Append Instrument fails to place track in folder Latest release notes are here. See prior release notes. Check out all new features released to date.

This seemed like the most-requested, longest-awaited feature over at the old forum. The devs not only made an indicator, but a multipurpose button, which is a "wow."

With Ripple Edit you don't need to delete special with Delete hole any more

Here's what happened. I was using my Icon Pro Audio QCon Pro G2 Control Surface and I found out by accident that the F2/Copy button along with the Rewind button turns on ripple editing. I was trying to press the M1 button and the rewind button to go back to the beginning of the song, but I mistakenly hit the F2/Copy button, which is under the M1 Button, and my clip movement went bonkers. Thanks again for helping out SCOOK!!

Scook, Thank you sooooooo much, Ripple Edit was checked off. I unchecked it and was able to move my clip with out any problems. 👍👍 👍👍

ripple edit?

It depends on material but what works most times is drag and drop the audio track to the timeline. Melodyne option box will open and choose percussive . You can open the tempo map to see what results. The next step to make it musically line up with the measure is turn on Ripple Edit and drag the audio track so it’s lined up with the second measure downbeat. This way the tempo map will follow the audio. Make sure turn off ripple editing when done. I think I demonstrate this in Tutorial #23

"Slide Over" was TARFU before ripple edit was introduced. Nice to see it back on the bug list.

[Updated 29-Jan-2021] Version 2021.01 Update 1 (build 27.01.0.098) now available! Introduction The 2021.01 release introduces Arranger enhancements, SSO (Single Sign-On) for activation, import and export improvements, optimizations, and over 50 bug fixes, all in keeping with our goal of making Cakewalk as reliable and enjoyable as possible. The following highlights are intended to provide an overview of the more significant changes. Please also refer to the new features section of our documentation for more detailed information on the features. Please give us feedback on this release. We hope you like it! Update Jan 29 2021: 2021.01 Update 1 (build 27.01.0.098) Enhancements and optimizations: MMCSS improvements When Use MMCSS is enabled in Edit > Preferences > Audio - Playback and Recording, all threads are assigned to the same MMCSS task groups for better efficiency. In prior releases on multicore systems with 16 or more cores MMCSS limits could be prematurely reached, resulting in lowered efficiency with some audio threads not running at pro audio priorities. The MMCSS thread limit has been boosted to 128 to handle machines with a higher number of cores (requires a reboot after installing this update to take effect) VST3 Host Bypass enhancement The VST3 Host Bypass button now also works when this parameter is not automatable. Bug fixes Stability: Crash inserting Kuasa plug-in. Crash when switching projects using different sample rates with PreSonus Studio 192. Plug-ins: Projects containing certain plug-ins fail to open in 2021.01 release. Plug-in Load balancing threads were not being released. Arranger Tracks: Ripple All not working when deleting from Arranger Inspector. Ripple edit delete using section overlaps crops the clip at the end of the left sections. Ripple Edit delete Section with overlapping notes at the end not working. Arranger: Fix for trailing notes being incorrectly picked up by a section. Articulation Maps: Ripple Edit Delete at beginning of project isn't working with Articulations. Deleting an articulation occasionally splits it into two smaller but invisible articulations. Show/Hide Articulation Pane in Piano Roll does nothing if there are no articulations on the track. Adding a new articulation event should default to velocity 100. Articulations sometimes deleted when using Project > Insert Time/Measures. Automation: Automation write not working with certain VST2 plug-ins until envelope was created. Freezing a synth could cause synth automation on all tracks to get orphaned. Skip non automatable parameters in Choose Parameter dialog. UI: Add Instrument Track not putting audio track in folder / unable to remove from folder. Increased contrast of Piano Roll clip outlines so they are visible regardless of current theme. Misc.: Opening project at different sample rate can fail to engage audio engine. MMCSS threads not properly unregistered on engine termination. MMCSS threads could exceed quota with repeated changes to preferences. Cakewalk no longer attempts to set ASIO thread priority when MMCSS is not enabled. Unexpected sample rate conversion message when bouncing audio. Remove unexpected dropout message when creating or loading new projects. Fixed bitmap memory leak in when editing using AudioSnap that could cause blank screen. Updated CWAF tool latest known version number string to 27.13.0.xxx. Update OAuth to new BandLab backend protocol. 2021.01 Highlights Arranger section inclusion of outlying MIDI notes When dragging sections or committing arrangements, Cakewalk has logic for dealing with leading/trailing MIDI notes that overlap section boundaries. In the following example, section 2 is selected. The underlying MIDI clip contains note events that start slightly before section 2 and end slightly after section 2. By default, selecting section 2 will ignore the portions of overlapping note events that fall outside the section boundaries. Cakewalk now lets you optionally include the full duration of overlapping note events. Notes that overlap section boundaries: Leading/trailing notes are often created in the following scenarios: The recorded performance is unquantized and notes appear slightly earlier than the section start. When using a sound with a slow attack, and the notes have to be played early to make up for the attack time. Leading notes as part of a lead-in phrase, or droned notes that overlap with the section boundaries. You can specify the threshold that determines which overlapping note events are included when moving sections. To do so, click the Track view MIDI menu and point to Arranger Section Event Overlap Threshold, then select one of the following options: Off. Ignore overlapping notes. Note value (Whole – 1/256 Triplet). Only include notes that overhang by a duration equal to or less than the selected value. Any Overlap. Include overlapping notes of any duration. When overlapping notes fall within the threshold set, those notes are included in the section move/copy and the clip start/end is automatically resized (slip-edited) to accommodate the notes. The moved notes are also removed from the neighboring sections. This requires Non-destructive Editing to be enabled, and works best with Split MIDI Note enabled. The Arranger Section Event Overlap Threshold setting affects all arranger drag operations, delete, commit arrangement, and Duplicate from the section context menu. Absolute time in Arranger tracks The time base format for each Arranger track can be set to either Musical or Absolute. The time base format determines what happens to sections when you change the project tempo. To toggle between musical and absolute time, click the icon to the left of the Arranger track name in the Track view: Musical . A section’s M:B:T position stays constant, and its absolute position shifts. Absolute . A section’s absolute position stays constant, and its M:B:T position shifts. Absolute time is useful for scoring to film/video. The Arranger track tooltip shows time as H:M:S:F and samples. When committing an arrangement, the following rules apply: If all the sections came from absolute time Arranger tracks, the committed arrangement track will be absolute. If the sections came from musical Arranger tracks (or a mixture of musical/absolute), the committed arrangement track will be musical. SSO (Single Sign-On) for Cakewalk activation Cakewalk supports SSO (Single Sign-On) for activation, which allows you to log in via any service supported by BandLab as your sign-in authority. Google, Facebook, Apple ID, mobile phone and BandLab user/password credentials are currently supported. SSO is only used for Cakewalk activation, and under normal circumstances you will only need to sign in once. Cakewalk will attempt to refresh your activation status silently and automatically on occasion during start up. Use the SSO login as you have done with your BandLab account in the past. Note that BandLab Assistant is still required for requesting offline activation of Cakewalk on computers that don’t have an Internet connection. Misc. enhancements Cancel VST scan You can now cancel an in-progress VST scan with the new Cancel Scan button in Edit > Preferences > File - VST Settings or via the Cancel option in the VST Scan toast notification. The next scan operation will resume where the canceled scan left off, starting with the plug-in it was last scanning. If the last scanned plug-in was a shell plug-in (such as Waves WaveShell), the scan will resume from he first plug-in in the shell). Auto termination of VST scan Shutting down Cakewalk will now automatically terminate any scan in progress. This allows in-app updates to work properly even if a scan was in progress when the app was shut down to perform a new install. Zoom to Fit Project Horizontally shortcut The new Zoom to Fit Project Horizontally key binding zooms to fit the entire project in the Clips pane, without affecting the height of tracks. The default keyboard shortcut is CTRL+ALT+F. Improved selection with Arranger sections If there are gaps between a range of selected sections, the unselected clips remain unselected. You can now unselect fully selected clips from a selection and they will not be moved with the section. Cutting Arranger section deletes hole Cutting an Arranger section with Ripple Edit enabled now deletes the hole to make it consistent with the Delete command. Clicking on an articulation section now triggers keyswitch events Clicking on an articulation (without modifiers), or changing an articulation’s type or MIDI channel now sends any triggered MIDI events associated with the articulation. Control Bar Select module changes Four new buttons have been added to the Control Bar’s Select module in Large mode: Select Track Envelopes with Clips . When enabled, selecting a clip will also select any overlapping track envelopes. Select Track Articulations with Clips . When enabled, selecting a clip will also select any overlapping track articulations. Select Events with Sections . Enable/disable automatic selection of track events when selecting Arranger sections. By default, clicking an Arranger section also selects underlying track events. Clicking again de-selects track events, while retaining selection of the section. Select Sections with Time Ruler . When enabled, making a time selection in the time ruler will also select any overlapping Arranger sections. Right-click or keep the mouse button pressed for a brief moment specify if sections should be selected in all Arranger tracks, or only the active Arranger track: Select Sections with Time Ruler (Active Arranger Track). Making a time selection in the time ruler will also select any overlapping Arranger sections in the active Arranger track. Select Sections with Time Ruler (All Arranger Tracks). Making a time selection in the time ruler will also select any overlapping Arranger sections in all Arranger tracks. The four buttons are linked to the corresponding menu items within the Track view Options menu, and work in exactly the same way. The previous Large mode for the Select module is now the Medium mode. Moving clips between lanes on the same track obeys Auto Crossfade setting Moving clips between Takes lanes on the same track now obeys the Auto Crossfade setting. Insert Instrument track behavior When selected from the track context menu, the Insert Instrument command now inserts the instrument before the current track rather than after the last track. The Add Track button and Insert > Soft Synth command will continue to append after the last track. Similarly, the Append Instrument Track command in the track context menu will append the new per-output instrument track directly below the current track. Selecting Append Instrument Track from the Synth Rack context menu will continue to append after the last track. Phase/Interleave buttons on Instrument tracks Phase and Interleave buttons are now available in the Track view and Inspector for Instrument tracks. Tip: You can show and hide controls in track and bus strips in the Track view, and even create presets for your favorite control layouts. To show or hide the Phase and Mono/Stereo Interleave buttons in the Track view, open the Track Control Manager and specify the visibility of the Interleave/Phase group. Option to only use external MIDI inputs MIDI track’s that have their Input control assigned to All Inputs receive MIDI data from both external (i.e. hardware) inputs and any soft synth outputs from other tracks. When inserting a soft synth, Cakewalk defaults to enabling MIDI output if it is supported by the synth. As a result, MIDI output from Instrument tracks may be inadvertently played/recorded on all other MIDI tracks if the tracks are armed for recording or have MIDI Input Echo enabled. To address this, MIDI tracks now have a new All External Inputs input option, which only appears when at least one soft synth with a MIDI output is present in the project. All External Inputs means any MIDI input that isn’t an output from a soft synth, such as hardware MIDI ports and virtual controllers. In earlier versions, switching the active MIDI track would normally select All Inputs. This behavior has changed to: If the track previously included soft synth outputs in its inputs, then it will show as All Inputs. If the track previously only had hardware inputs, then it will show as All External Inputs. Export to Standard MIDI File respects selection Export to Standard MIDI File (File > Export > Standard MIDI File) now respects the selection. If there is no selection, the whole project is exported. Updated LAME MP3 encoder The integrated LAME MP3 encoder has been updated to version 3.100. This includes bug fixes and stability improvements to MP3 encoding and also speeds up the encoding process. Additionally, Cakewalk has been updated to now handle discarding padding samples when importing MP3 files. i.e imported MP files will not contain extra data at the beginning of the file. Updated libsndfile encoders The libsndfile library used for import and export of various audio formats has been updated to version 1.0.30. This fixes numerous issues with handling BWF, Wave64, AIFF, FLAC and Ogg files. Optimizations Dynamic plug-in parameter optimizations Cakewalk 2021.01 introduces improvements in responsiveness and memory footprint when loading and editing projects with lots of tracks and high parameter count plug-ins. In previous versions of Cakewalk, plug-in automation parameters for all listed plug-ins were always created up front. This could result in a significant performance and memory hit when using plug-ins that expose hundreds or thousands of parameters, especially in projects that contains many tracks. Internal parameter objects are now created on demand when a parameter is actually used, either by modifying a parameter or by creating an automation envelope for it. A track’s Edit Filter menu no longer lists hundreds of parameters for plug-ins but instead only shows in-use parameters. To select other parameters in the Edit Filter menu, point to the plug-in name and select Choose Parameter to open the Choose Plug-in Parameter dialog box. Improved handling of ProChannel automation Automating the ProChannel Enable parameter would previously only work if the ProChannel UI was visible. ProChannel bypass automation is now UI independent and also buffer accurate. ProChannel bypass will also properly enable/disable with automation during fast bounce and freeze operations. Latest release notes are here. See prior release notes. Check out all new features released to date. Previous release: 2020.11 Feature Overview 2020.09 Feature Overview 2020.08 Feature Overview 2020.05 Feature Overview 2020.04 Feature Overview 2020.01 Feature Overview 2019.11/12 Feature Overview 2019.09 Feature Overview 2019.07 Feature Overview

Bonus tip: If you want to just delete everything from the end of your project, including any left over bits that are making your project to continue to play past the end, do this: 1. Put your cursor at the place where you want your project to end 2. Do CTRL+A to select everything 3. Enable Ripple All (just above the ruler): : 4. Click the Set From = Now button in the Select Module on the Control Bar: 5. Press Delete. Everything from where your cursor is to the last event on your timeline will be deleted, making this now the new end. 6. DISABLE RIPPLE ALL! Seriously, double check you did this before you tangle yourself up in a big mess. I've done this. It sucks.

I just pulled the tempo from Creedence's Cross tie walker today. It drifted from 94-99BPM. There was just one little spot that glitched and jumped to 150 due to a funky guitar riff he was using in the 3rd verse. Easy to fix if you know how. But basically I recorded the song directly from You Tube using my Loopback input and then drag it to the timeline and use percussive algorithm. Then I turn on ripple edit and drag the whole song until it lines up with the grid and leave room for a count in. Then I run the metronome and listen for any drift. It's amazing how tight the metronome stays. If there's a drift you just move a node up or down until it's right. Then I play along and build the song part by part and because it's on the grid I can quantize parts. This one was easy because it is just Bass and drums . I added a piano for the heck of it too. After I'm done I just deleted the audio and the tempo map and set the tempo at 99. It's a great way to copy the exact arrangement of cover songs and add the correct little pieces like drum fills. I had to add a better ending as it was a fade out which doesn’t work for live music . I have successfully done this for many fully mastered songs including rebuilding my own that were recorded pre DAW era. I've actually never tried audio snap method. Looks like too much work to me when I watched the videos. I think the Melodyne tempo detection has improved a lot with version 5. But the material needs to be dynamic. I don't think it will work on brick walled stuff. Needs the transients. The Creedence song worked because you can see every snare hit in the waveform.