msmcleod

"Entire Mix" is the source category - which means, as you say, it's grabbing audio from the hardware outputs. This is totally separate from what you're actually sending to the entire mix.

It's not a bug. The export dialog is selection based. To export everything you either need to: 1. Select everything; or 2. Select nothing ( CTRL + SHIFT + A selects nothing ) The OP's screenshot shows "Track 10 Drums" selected, so none of the unselected tracks will be exported. Also, as Track 10 is a MIDI track, no audio will be exported unless it's corresponding audio track is also selected. The difference between selecting everything or selecting nothing is subtle: Selection: 1. A selection specifies both tracks and a start time/duration. If you save this as an export task, then the task won't pick up any new tracks or change in duration (assuming you've chosen Range = Selection). 2. When choosing Tracks or "Tracks Through Entire Mix", all tracks will be exported at the same length, i.e. the length of the selection. No selection: 1. No selection implies all tracks. If you create an export task, any new tracks will automatically be picked up. 2. No selection + Range = Entire Project will always export everything for the whole project duration 3. When choosing Tracks or "Tracks Through Entire Mix", each track will be exported at its own specific duration.

Sorry for chiming in so late in this discussion - last week was a busy one. I don't use any of the Roland TD modules, but I do use both the Alesis Nitro Mesh and DM5 with AD2. The Nitro is used for the standard kit pads, and I'm using the DM5 for extra cymbals (I modded some Remo practice pads to turn them into triggers). I've got both modules going to a separate input in my Miditech MIDIFace 8x8. The first three inputs/outputs are used by my Mackie MCU, XT and C4, with the Nitro Mesh on input port 4 and DM5 on input port 5. My main MIDI controller keyboard is connected to my Focusrite 18i20. Despite the heavy MIDI traffic, I've never experienced any glitches. If you want to use both the TD6 and the TD8, I'd recommend using a similar set up - i.e. have them connected to their own separate MIDI IN ports. Cakewalk will merge all of the inputs for you, but personally I prefer to set the MIDI filter to only listen on the two drum module ports and my main controller keyboard. This ensures that it never picks up anything from anywhere else. I had to build my own map within AD2 due to my strange hybrid setup, but mine is pretty close to GM. IIRC AD2 has drum maps set up for the Roland TD modules, but you can tweak the AD2 drum maps to adjust velocity curves as required.

Did you download the Focusrite ASIO drivers from their website? If not, do this. Windows will not automatically install the ASIO drivers, only the class compliant WDM/WASAPI drivers.

Why not just use articulation maps? Key switches are exactly what they were designed for. Also, there's no way for Cakewalk to know what keys match what instrument. Even if you based the keys/colours on the articulation map definitions, there's still no way for the the PRV to know which articulation map to pick, as 1. you could have many articulation maps in your project, and 2. you could have more than one articulation map defined for the same VSTi. If you've recorded key switches by playing them in real time, you can easily convert them to articulations by adding the articulation map to the project then right clicking on the articulation lane header and choosing "Extract Keyswitch Articulations". If you want to turn articulations back into notes, select "Apply Group 'xxxx' Articulations to Track" or "Apply All Articulations To Track" from the same context menu.

There is no difference in CPU usage either way.

This was changed a while back to get around a long standing (> 11 years old) Windows bug that has gotten worse since Windows 10 - if you go beyond around 1000 menu items, it starts removing items. This wasn't an issue in the past, because not only was the menu limit much larger (around 4000), most people didn't have that many plugins. So the workaround is to popup a brand new menu using a different UI framework.

Uncheck "Select Events with Arranger Sections" within the Track View Options menu.

Either: 1. Export a selection; or 2. Create arranger sections for the parts you want, then use "Arranger Sections" as the source category when exporting.

Each take lane has a notes section. Just expand the take lanes, and you can enter in the notes there: If it absolutely has to be at the track level, Melda's free MNotepad can be added to the FX bin.

I believe Scaler can do this

Sorry, I meant to reply to this sooner. I did try automation out on a real MCU, and things were far more straightforward. I didn't see the behaviour you're seeing with the G2. The MCU faders are touch sensitive, so automation recording starts as soon as I touch the fader. IIRC Cakewalk was correctly punching out as soon as I stopped touching the fader, however if I left my finger on the fader without moving it, it would automatically punch out after 250ms. I spoke with Noel regarding this, and this is expected behaviour. At no point did it switch to latch mode, or behave as if it was in latch mode like you are seeing.

Thankfully, keyboard shortcuts and menus are pretty much centralised by their command handler - i.e. it doesn't matter whether the command is invoked by a menu or a keyboard shortcut. The only tricky part is determining context, which for the most part is determined by focus and/or selection.

Are you leaving the Melodyne region effect active? If that's the case, then that's your issue. When a region FX is active, Melodyne has ownership.

Note that control surfaces are COM DLL's, so simply copying them to the Shared Surfaces directory isn't enough. They'll need to be registered: 1. Right click on the desktop, and select "New->Shortcut" 2. Type in cmd as the location, then click "Next" and then "Finish" 3. Right click on the new shortcut, then select "Run as Administrator" 4. In the command prompt, execute the following: regsvr32 "C:\Program Files\Cakewalk\Shared Surfaces\alphatrack.dll"

Cakewalk uses two different pitch/stretch algorithms used, one for online render (i.e. playing in real time), and one for offline render (bouncing/exporting). The idea is that the online render is quick and dirty so as not to impact your flow at the expense of audio quality. The offline render is higher quality, but much slower due to the computation involved. The intended workflow is to use the online render until you get the timing right, then use Bounce to Clip(s) to apply the pitch/stretch using the higher quality algorithm. However, not all algorithms are suitable for every type of material. So it's likely in your case that the offline algorithm is better suited to your material than the offline render. This can happen if you've chosen a totally different offline render algorithm to the online render - e.g. you're using Elastique for online, and Radius for offline. You'll get much more consistent results if you choose the same type of algorithm. The algorithms are specified in preferences:

From a job security point of view, AI honestly doesn't bother me - I by that I mean not just for me personally, but for programmers in general. Everything I've seen from AI (especially ChatGPT) is either "variations on a theme" - i.e. regurgitated code it's scraped from various online resources and paraphrased accordingly, or it requires an incredible in depth of knowledge of how to build an appropriate AI model and source training material. Also, if you speak to any AI experts, they'll usually try out a few different approaches before settling on the best compromise. From an analytical point of view, AI is incredible at seeing patterns in huge amount of data that humans would be incapable of. But from a creative point of view - either in art or engineering, in my opinion it's not there yet. I've yet to see anything that is really "new", creatively speaking, from AI. Sure it'll get you results quicker by giving you example code, but you still have to understand it in order to maintain it.

I've been weaning myself off Waves plugins for a while now - the biggest reason being the license seat restrictions. At one point, I was buying two licenses for each plugin but of course that pretty much waved goodbye to the WUP cap. The cap is still there, but it's per machine - so the cap is essentially twice the normal amount. For analog emulations, I mostly now use Analog Obsession; for more clinical/creative work, I use MeldaProduction. I'd bought enough Melda plugins over the years to get the complete bundle for a fraction of the price. To be honest though, 99% of the time, the stock ProChannel EQ and compressors work fine for me. I've also started using the Sonitus plugins more - they may not look great, but they're very good at what they do, and the CPU usage is very low. One set of plugins I do find very useful, albeit as a temporary solution, is the CLA Drums/Guitars/Vocals/Bass etc bundle of effects. If you've just done a tracking session, and want a very quick rough mix, slapping appropriate plugins on the appropriate tracks can give a pretty good approximation to a finished mix. Very useful if you've just tracked a local band and want to give them something to take home with them. It's far from perfect, but sounds orders of magnitude better than just a balance of the raw tracks.

To remove the trimmed audio from clips, either use "Apply Trimming" or "Bounce to Clip(s)". Apply Trimming simply removes the trimmed-out audio, whereas "Bounce to Clip(s)" will also combine all selected clips into a single clip , and also apply any clip automation to the new clip. To remove unused audio files, use "Save As" and save the project to a new location.

Check your import bit depth within Preferences->File->Audio Data. If it's set to 64, then it'll be converting everything to 64 bit on import. IIRC, the default setting is "original".

There is definitely a bug here. It looks like it was introduced a few years ago, when we refactored the "Slide Over" to use Ripple Edit Selection under the hood. The way it should work, is it should slide everything over you've checked in the Paste Special box, regardless of whether you've got that type of event in the clipboard or not. The only exception is clips themselves - it won't slide clips in tracks you're not pasting to. If you need this, use Ripple Edit All. As it stands, it's only sliding over if you've copied that type of event with Copy or Cut special. Tempos however, aren't sliding at all. We'll get this fixed.

When using a wave editor, the wave file is permanently changed. This is how the whole mechanism works - i.e. when you launch the external tool, you're giving control to the wave editor to edit the file directly. When you save, Cakewalk recognises that the file has changed and updates the clip accordingly. To be honest, I very rarely use this workflow - it's only ever as a last resort when I actually need to edit the waveform in detail. For scenarios like the OP's one, I'd probably re-record, but if this is not possible, then a wave editor is probably the next best thing. Yes, you can split the clip and mess around with clip gain and fades to hide it, but smoothing waveforms out by hand can be quicker for one-off clipping issues. FWIW I've compared editing mistakes to just re-recording over the years, and in most cases I could record another 10 or so takes in the time it took to edit the mistake. And of course I'm improving my playing at the same time.

Although you can't bind a shortcut to previous/next arrangement section, you can bind for previous/next section. So to get around this: 1. Bind "Go to Next Section" / "Go to Previous Section" to a key or MIDI note within Preferences->Keyboard Shortcuts 2. When you load your project, commit the arrangement for the setlist you want (don't save your project tho!) Hit play, then use the shortcuts to navigate. If you need the transport to pause after playing each section, you can insert MCI commands at the end of each section within the event list, e.g. this will pause the performance just before measure 33. It's important to put it just before the end of the section, so it's seen as part of that section and not part of the next one. If you're using the MCI commands, you could skip committing the arrangement and just use the navigation keys/midi notes to go to the next section you want to play. Note: There are two MCI commands you can use: "pause" and "stop". Pause will stop the playhead at the current position, whereas stop will potentially rewind to the last marker / zero, depending on your settings.

Unless it's changed very recently, Audacity is unsuitable for the CbB Utilities menu because it doesn't save to the original filename. I guess you can get around it by doing a "Save As", but the given that there could be many .wav files in the project's audio directory there's a danger you could pick the wrong one. Personally, I use SoundForge for the most part, but I don't have licenses for all the machines I've got CbB installed on, so Acoustica 6 BE is a good alternative for the very rare cases I need it.