David Baay

I'm always advising against using continuous tempo changes because it's not musically necessary to have tempo changes in between notes and can cause problems with many instrument and FX plugins. You can avoid this by enabling snap at a resolution that matches the smallest note interval when drawing tempo changes.

Hmmm... that makes it less likely a new project is going to help . I dunno...

I thought about this one for a while, but had no really bright ideas. Pretty weird set of symptoms. I actually would not expect it to be fixed by a re-install. Something's going on with the plugin handling or possibly the project is corrupted. If the routing and plugin setup is not hugely complex, I would suggest importing the tracks to a new project started from the Basic template (rather than some potentially bad/ancient custom template), and see if the new project behaves better.

I meant with handling multiple soft synths and FX plugins. Streaming audio and playing back MIDI driving hardware synths is not that big a chore. The main limitation on audio track recording and playback will be the performance of your hard drive which can be dealt with by increasing the disk buffers if necessary

Not sure why you're getting re-directed to that URL. Below is the content of the post. I was quoting and responding to an earlier post. Open Notepad, enter this line: (do (+= Now 240)) Save as "Transport Forward 16.cal" Put this file to the folder with other CALs. Go to Options > Keybindings and assign this CAL to whatever key you like. Now if you press that key, cursor moves 16th note forward. For opposite do the same but start with (do (-= Now 240)) If you want cursor to move by bigger steps, enter 480 or 960 instead of 240. (Clock resolution must be set to 960 ppq) This deserves a bump. And FWIW, to prevent bad behavior when cursoring back to time zero, I did this: (if (>= Now 30) (-= Now 30) (= Now 0) ) Note: The "do" is not necessary if only one statement is to be executed. And the second statement works like an "else" in the case that the cursor is less than one full increment (30 ticks in this case) from time zero.

With all due respect, Mark was mistaken in this case. The regular quantize dialog can quantize beats within an audio clip as well as audio clip start times (though not at the same time), but you have to enable Audiosnap on the clip first to quantize beats. But this is unrelated to the OP's issue that Groove Clips can't be quantized either way.

The test I outlined was intended to confirm the playback is actually changing, and not a mistaken impression because I've never heard that myself or seen it reported by anyone else. If it checks out with the nulling test, it would be interesting figure out what's going on in your particular case. No doubt Audionsnap can produce some bad outcomes (whether from misuse or defects), including that "offline" rendering has timing anomalies that don't manifest in real-time "online" playback, but variable timing from one playback to the next is not typically one of them.

The thing about "Entire Mix" is that it's the sum of all hardware outs. So if you have a send to another hardware out (e.g. a headphone mix for a vocal booth), that's going to get summed into the exported file. Assuming everything is routed to the Master bus as it should be, and Master goes to the hardware outs that drive the monitoring system you use when mixing, exporting from the Master bus is the best practice IMO. It ensures the level in the audio file matches the metered level on your Master bus and isn't affected by using the level controls on the hardware strip to control your monitoring level, I highly recommend avoiding that since this extra gain stage so easily gets out of sight and out of mind and can cause confusion later on about why what you hear from Cakewalk is not the same as from another app (or another CW project with a different setting) playing your exported master through the same monitoring system.

Shouldn't be happening. Bounce the Master bus to a new track that outputs directly to Main Outs, invert the phase and see how it nulls with the live tracks. Depending on FX and the way stretching is rendered, nulling may be imperfect but it should sound the same every playback. The kind of audible timing variations you're talking about should produce some pretty severe flamming/echoing if it's really happening. One thing to watch out for if to make sure the mode for Clip Follows Project is Autostretch before enabling it. If it's anything else, things will move around and likely get out of sync as soon as you enable it. Also, If you're not editing clip maps to make sure the beat markers are locked into their respective transients, quantizing is unlikely to work well.

I don't have any Korg gear, but, yes, I would guess it will require sending a SysEx message.

A funny bug! Create a midi project. Set the time signature to 6/8. After a few bars, change the bar to 4/4. After this change of measure, the recording monitoring delays exactly 2 beats. Are you saying input monitoring of a live audio source has two beats of latency? Or recorded MIDI or audio input is laid down two beats late? Others have occasionally reported something like the second issue, but that seems to be system-specific. I cannot reproduce any problem recording or monitoring MIDI, live audio or synth audio after the meter change.

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.