bitflipper

I once played a bar where they had a dart board just to one side of the stage, three feet from my head and just inches from my PA. They wouldn't let us move it. It was a tense gig.

Bite your tongue, man! Nobody wants that. What if Behringer bought Fender? Fiat bought Lexus? Spirit Airlines bought Singapore Airlines? The North Korean government bought Microsoft? Löwenbraü was being brewed in frickin' Texas? Oh, sh*t, that last one's already come true.

In that case, ignore everything I've suggested thus far. This is not an issue with your audio interface. Question: did you use the same gear to record the guitar and harmonica? Meaning the same mic, same preamp, same signal chain?

Buffer size: anything bigger, e.g. 1024. I am surprised that your interface isn't recognized unless you use ASIO. I thought WASAPI was compatible with anything. So never mind on that one. The main thing is to make sure this problem isn't limited to just one project. We don't want to make a global correction that will affect other projects that don't exhibit this behavior. Note that what I'm about to describe shouldn't be necessary when using ASIO drivers. At least, that's what I've always heard. But there may be a problem with your specific driver wherein it's not reporting latency correctly. If that's the case, then the cure is to enter a correction into the Manual Offset field under "Record Latency Adjustment" at the bottom of the Sync and Caching page of Preferences. Don't worry, you can always un-do this if it doesn't work out. Before you can do this, you'll have to figure out just how far off your vocals are, in samples. Do this with all fx plugins bypassed. In the upper-left corner of the track view there's a box that shows the current time position. Right-click on it and select "Samples". Now your time is going to be displayed in samples. Zoom in on the beginning of an audio clip and jot down the number shown. Now do your nudge trick to get the audio lined up properly, zoom in on that same place and note the new value in the time position display. You now know how many samples you had to nudge the track by, so we can tell Cakewalk to do that nudging for you. The difference between those two numbers is the amount of manual adjustment that will be needed. Enter that into the Manual Offset box and un-check the "use reported ASIO latency" box. The above method is not terribly precise. You'll need a loopback test to get it smack on. However, a) we just want to see if it fixes your problem, and b) it really doesn't have to be absolutely smack on - you won't notice if it's off by a few samples. Or even a few hundred, actually.

Sorry, I'm talking about the "Buffer Size" slider on the Audio -> Driver Settings page, and the "Driver Mode" selection on the Playback and Recording page.

Try these experiments...does the sync issue persist - if you increase the buffer size? - under WASAPI instead of ASIO? Yes, you can increase the buffer size and therefore overall latency and still record live vocals that will line up properly.

Uh oh. Be aware that if you post that question, opinions will span many pages. Better set aside a few days to read them all. I could just give you the correct answer now, but that would be off-topic.

Could you post a screenshot of your Audio -> Device Settings and Audio -> Sync and Caching settings in Preferences? (If you don't see the latter, click on the "Advanced" radio button at the bottom.) Also let us know what driver you're using (e.g. ASIO, WASAPI).

Great. 10,000 more new users who are sure, on day one, that they've found a bug everyone else has missed.

Just wait until the Dallas DLC comes out in November!

Last fall I read that the long-anticipated game Cyberpunk 2077's release was imminent - along with the new RTX3000 series cards. Perfect timing, I thought. My old RTX960 could barely keep up with Fallout 4, so I made plans to upgrade. The fact that the 3090 would be cheaper than my 960 was at 3x the performance was going to make my XMas self-gift just perfect. Of course, you gamers know how that went. Cyberpunk was a buggy mess. The only way to get an RTX3090 was on eBay for $2000, and then NVIDIA recalled the first batch of cards as defective. All's well, though. I recalibrated my plan and bought an RTX2060MAX and Assassin's Creed Valhalla. Good times ensued. Christmas was saved.

" Apologies for the long delay"

^^^True. It may seem counterintuitive to talk global warming when it's snowing outside, but yeh, it's all related to rising ocean temperatures. And we ain't seen nothin' yet.

It's just not for me, that's all. If you're doing contemporary pop, it might be quite useful.

It's all the fault of those darn windmills, you know.

At Audiodeluxe. At checkout, it automatically applied a discount code that brought the price down to $26. This is a bundle of three percussion instruments, for foot stomps, claps and finger snaps. The regular $80 price is a bit unrealistic, but for $26 it'll be a useful addition to my percussion toolbox. I'm starting to like such little single-purpose percussion instruments. Skaka was also a recent purchase, an easy-to-use hand-percussion looper. I bought it on a whim because it was cheap but ended up using it a LOT. Unfortunately, its $25 intro price is done now and it's currently double that. Still a cool little plugin, though, and worth watching for it to go on sale again. [EDIT] Note that it's also $29 direct from Boz. I should have checked there beforehand, as I've no problem paying $3 more for a more convenient buying experience.

Shh..that's my secret weapon.

Most of us spend our hard-earned FX money to make vocals sound better.

I've used it. It's OK. Like Pollux warns, use it gently for best results. There are actually better solutions out there for spectral ducking, but all are more expensive and/or more difficult to use than Trackspacer.

Kontakt is a significant investment in time (learning curve) and money. You'll find that a great many users here are fans, and some of us have invested obscene amounts of money into the Kontakt paradigm. But although I am an ardent proponent, I agree with bdickens when he suggests it's probably not the best place to start - unless, of course you are wealthy and not planning on buying a new car this year. Cakewalk bundles the TTS-1, which is an excellent choice for getting your feet wet. It's actually a pretty decent sample player. There are a number of free instruments out there, enough to keep you engaged for a long time while you mull over what to eventually spend real money on. There are many lists online (example, example, example, example, example) to get you started. They're all free and don't require a sample player like Kontakt, so there's no risk in downloading and trying them out. Note that many of these lists include older VSTi's that may not have aged well, or have since become paid commercial products. If you're specifically after organic instruments rather than traditional synthesizers, I would encourage you to take a look at Spitfire Labs stuff. Spitfire is one of the best sample library developers out there, but most of their high-end products require Kontakt. However, the Labs line uses its own player and is totally free. They have been adding new instruments pretty regularly - the collection now includes strings, piano, brass and percussion instruments.

Whenever I want to replicate parts, I just select the tracks, mark the region I want to copy on the timeline, then hold down the CTL key while dragging. Works great whether doing one track or many, or whether copying to the same track or a different one. I know the new Arranger feature is supposed to eliminate the need for that, but I do it so rarely that it's never occurred to me to figure out how the Arranger works.

More likely it's just because the 64-bit option causes Cakewalk to use twice as much memory during the render. When a process runs out of memory it has to request more from the operating system, which takes a little time. Worst case, you could be running out of physical RAM and forcing Windows to page out chunks of memory to disk. The fact that it correlates to Ozone may just be because Ozone uses (I should say can use, depending on settings) far more memory than most other plugins. IMO there is no benefit to the 64-bit render option, so regardless of what the actual underlying problem was, you've fixed it.

Maybe you could edit your thread title, Larry, to avoid confusion and potentially hard feelings. I know, "Mastering the Mix Reference Free Limited-Time Demo" is a bit unwieldy, but it's the difference between helpful redirection and clickbait.

I've got a 4-year-old here who loves to twist knobs. She can't resist the mixer, so it's always a delight when I power up the PA with every channel at max volume. But wait a minute...isn't your kid about 18?

It's worth a shot. You'll still be auditioning patches long after she's had time to cool off.