David Baay

I think you meant to say "the bus assigned to the track output". In any case, I'm not able to reproduce that.

You need to manually rebind Tab and Shift+Tab to Goto Next/Previous Transient Marker in Keybindings. The default bindings were removed in 21.12, and affected Tab-to-Notes as well as Tab-to-Transients.

Hmmm... yeah, getting just a little long in the tooth. I'm a bit surprised your CPU even supported the Win10 upgrade. You will definitely want to upgrade sooner than later and get a dedicated audio interface if working with CbB is going to continue to be a significant part of your musical life. With proper optimization, that machine should still be able to pull off a clean recording at 128-sample buffer in a basic project with not too much going in the way of plugin processing or multitrack audio playback streaming, but will continue to struggle as your projects get more complex.

You can nudge the whole selection, but not individual markers...? I read it as wanting to nudge the Now Cursor which can be done with CAL. See post 23 here: http://forum.cakewalk.com/quotnudgingquot-the-quotcursorquot-now-time-m1339533.aspx Ah, that pesky Aim Assistant; he quickly gets on my nerves, and the timestamp in the timeline is indeed problematic - almost always disabled here..

I'm not clear what exactly is popping up that interferes with grabbing loop markers...? If Loop and Punch markers overlap, you can get one or the other depending on how high in the timeline you hover the mouse. Getting to an overlapped Selection marker is harder. One way is to hold Shift and click nearby so that it moves out from under the loop marker without affecting the other end of the Selection. The Ref. Guide says; Tip: If multiple markers overlap, you can click any of the overlapping markers and keep the mouse button down, then press TAB to cycle through to the marker you want to move. For example, if a selection, loop, and punch marker are all at measure 5, pressing TAB (while holding down the left mouse button) cycles through S (selection), L (Loop), and P (Punch). However... I found this is not working since the default binding of Tab to Goto Next Transient/Note was removed in the last release, and now has to be deliberately bound if you want to use use it. This manual binding overrides the tab-through-marker-types function. The Bakers might need to revisit this.

It should not normally be necessary to go that high in a properly tuned DAW recording a single track. but it could be WiFi or something is causing a spike in DPC latency. You can watch DPC latency in real time and get an idea what's causing it with this: https://www.resplendence.com/latencymon The fact that it happens shortly after you start recording also suggests it might be due to anti-virus scanning the new audio file. I can't actually check the audio file because my browser security doesn't like the URL.

No change here. Synth properties opening as expected when inserting an Instrument track

Random thought: symptoms sound a bit like effects of the 'Generic Low-Latency ASIO Driver' that Cubase (or other Steinberg software) installs.

I missed that there were multiple takes over time. Files for contiguous clips that start at 00:00:00:00 can be easily dropped at the beginning of their respective tracks with snap enabled, and all is good. But you would first have to bounce the takes in each track to a single clip in the source project and at that point you might as well export them.

Assuming the clips all start at 00:00:00:00, you can just open the bundle, save it as a project, and drag the audio files from the audio folder into the target project.

I believe this is only in the specific case that the track is the last track in the project, and the folder you want to move it into is immediately above it. In that case it's easy enough to drop it above the last track, and then drag it down. Or you can right click and Move to Folder; since it's below the folder, it'll end up in the last position.

In my experience, it takes at least as much more work to get all the the beat markers correctly aligned in the clip map as to Set beats as needed, mainly because editing clip maps is so mouse-intensive where SM/BAN is all keyboard-driven, using Spacebar to start and stop playback, and hitting Tab, S, Enter where necessary to set beats (I have S bound in place of Shift+M because I use it so much). In addition to being crash-prone, and placing tempo changes off the grid, edited clip maps aren't saved/restored as they should be, so you have to get the whole job done in one session.

You can execute Undo (Ctrl+Z) as many times as necessary to get back to the point before the mistake was made (until you save and close the project which is why I recommend Save As periodically) . But it's also possible that no mistake was made earlier, and you are trying to set the wrong measure/beat, or trying to set it to the wrong Now time. This should be clear from checking the location of existing nodes in the tempo track as you listen to the playback with the metronome on. If you want to share a copy of that audio somewhere, I can 'Set' it for you and summarize the process. Hopefully we're not dealing with Mahler's Symphony No. 3. ;^)

As I said, Undo is your friend when this happens. To understand the problem, just show the tempo track; if there's a node at or very near the beat you're trying to set, that's the problem. With more experience, you 'll encounter this error less frequently. Tab to transient is still going to be subject to transient detection errors, so you might need to double-check that the Now time is in the correct place. I usually do this by playing a measure at time, and stopping just before or after the beat I want to set, and then tabbing forward or back to it. If Tab doesn't put it right on the start of the transient, I'll click with snap disabled to set the Now time more precisely. Start by setting a downbeat every 4-8 measures, and then make additional intermediate sets as necessary to tighten it up further. Getting that initial 'rough' set done will help Cakewalk 'guess' more accurately which beat you're setting, and help avoid the 'Invalid" error. And, finally, do a Save As with a filename suffix like "My Project - Set Thru 32" every once in a while so that you can easily back up to some intermediate point without completely starting over.

You can set as many or as few points as needed. Each tempo change will persist until the next one. If a section is locked in for several measures with a fixed tempo, there is no need to have superfluous tempo changes. This is what I prefer about SM/BAN vs. Melodyne that will interpolate tempo changes every 8th note even where there are no notes or Audiosnap/Fit Improv that want exactly one tempo change at every beat, and nothing in between. Also Audiosnap has a long-standing regression bug where it doesn't place the tempo changes exactly on the grid, which is messy and complicates copy/cut/paste operations. If you get an "invalid" error with SM/BAN, the error is yours; you've tried to set a beat that is already set or would require a tempo outside the range of 8-1000 bpm to align with the current Now time. If you find this is due to a previous 'Set' being wrong, use Undo to get back to the last 'good' state, especially if there is MIDI in the project. Deleting tempo changes directly will foul things up.

You might also need to right-click the Volume widget in each MIDI track, and choose 'Disable' to prevent Cakewalk writing the value to the MIDI file regardless of whether anything is shown in the Event List. This also happens at playback; Cakewalk sends CC7 with the specified value from each track before starting playback. If more than one track is assigned to the same output channel, the setting of the last (i.e. highest numbered) track with an active Volume widget will pertain. The same goes for the Pan widget (CC10). Disabled controls will show parens around the value. The default if the control has never been touched is (101).

I recommend using Set Measure/Beat At Now. It's faster, more flexible and more reliable than editing the Clip Tempo Map, and yields a cleaner and more precise project tempo map than either Audionsnap or Melodyne. (Note that the default keybinding of Tab/Shift+Tab to Next/Previous Transient (or MIDI note) was deliberately disabled in 21.12, and has to be manually re-bound if you want use it.)

Hmmm... I can't reproduce that. Are you the latest release of CbB? You might try toggling off 'Use Paste Special Options on Paste' in Preferences > Customization> Editing, and doing a non-Special paste of multiple tracks.

Cakewalk knows that won't sound good, so it's not allowing it. ;^) Try hitting N to toggle snap off altogether, and and see if you can drop it anywhere near 3. If that works, I would guess that you have some Landmark option enabled in your snap settings; that's the only thing I know of that would prevent a 16th snap resolution from working everywhere in a measure.

I found it to have a pretty jarring transition to the higher overtones present in a harder strike; they come in all at once with a very small change in velocity. I've encountered this issue in a lot of sampled pianos (both acoustic and electric ) that I've tried over the years. I haven't checked it out thoroughly to determine exactly how many velocity layers it has or where the changes occur, but if I didn't know better (and I don't), I would suspect it has only two or three. I generally prefer synths that use some form of modeling or actual 'synthesis' of sounds to help deliver a more naturally progressive timbral response to velocity change, and pure sampled pianos with no modeling component really expose shortcomings in the number of velocity layers. If you're even a moderately capable keyboard player, you're likely to be disappointed with the playability of this instrument, more so if you have experience with hardware digital pianos or some of the more advanced software pianos that model resonance, release, and continuous pedal response.

To me it's pretty well expected that a button that is intended to globally enable/disable a function will affect all instances and modes of that function. If it didn't affect one mode, it wouldn't be very useful, and the alternative would be to go through all plugins in the project and individually disable Upsample On Render, which would be a nightmare, and could justifiably be called a bug. Performing a null test of a track rendered both ways should give you the answer. Just make sure it's a plugin that renders repeatably in a given mode.

Good bet that's the issue. I don't use Workspaces (set to None), and I use the default D binding to toggle the multidock open and closed a lot without issue as I'm sure many other users do.

@Maxim Vasilyev It would be good to see the sends from the source track to the patch points to make sure the first one didn't get doubled up. I would also be curious what is shown if you arm the Drums Aux to show the input level vs. the output level and/or change the Drums New Aux to use the same patch point as the Drums Aux for input. This will tell you if the patch point itself is raising the level or something is happening in the track between the input and output. If it's actually a bug, any of those actions might conceivably reset something, making it difficult to diagnose, but if the behavior remains consistently wrong, you should send a copy of the project to the Bakers for analysis - preferably stripped down to just the tracks that show the problem with all unnecessary plugins removed. Also, though it's probably not relevant in this case since both Aux tracks are getting input from the same source track, you should change the Input to your Kick Instrument track (and all other MIDI/Instrument tracks) from 'Omni' to a specific channel of your keyboard/controller to avoid receiving unexpected MIDI input from other physical/virtual ports or channels. Incidentally, regarding an earlier post about frozen tracks gaining 3dB, this is a long-standing issue with freezing tracks that have a mono input from a soft synth. I haven't checked it for a while, but I believe that problem still exists.

Which key(s) for which function(s) in which context(s)? Setting up custom bindings can be quirky, but once established should work consistently unless maybe there's come conflict of assignments in different contexts.

In very broad terms, I would say that it's unusual to see the Audio Engine running over 100% and showing a lot of late buffers with the Audio Process load below 50-65%, and the Audio Engine reading typically averages closer to 1.5x to 2x the Audio Processing load than the 3x factor you're seeing. But it depends on the plugins being used, and it's a rare project of mine that needs more than a 256-sample buffer to run smoothly on a lowly 4-core i7-6700K processor. I just don't use that many heavy-weight plugins in any one project.