bitflipper

I have longtime roots in Sandpoint. My grandparents settled on a couple hundred acres there in 1949, and it was the first destination of my life at 2 months of age. At 13, I spent a summer there logging with my grandfather. Mom 'n Dad bought a couple acres with a cabin on the lake in the 60's and it was our annual summer destination growing up. Lost my virginity in those woods (not a joke). My folks built a rammed-earth house there in the 90's, but we had to sell it when Mom died and Dad got dementia. So yeh, lots of fond memories there. But I am genuinely sad to report that Sandpoint ain't what it used to be. It has traffic lights now, and the traffic to go with them. It's become San Francisco of the north. The local government has been infested with California refugees with their big-city ideas about zoning rules and such. No more building your own log cabin without a permit. Lots of music still happening, though.

Do you love epic cellos and basses, but your own recordings seem a little limp compared to what you heard in your head? This is Viagra for your celli. $49 bucks and no Kontakt required. Abbey Road One: Legendary Low Strings I bought it immediately on the strength of the demos. That, and well, it's Spitfire. Currently waiting on the download, will report back when I've actually had hands on it.

Yup, Cakewalk has always been very good about backward compatibility. I once successfully loaded a dozen Cakewalk 1.0 projects dating back to 1986 into SONAR 8.5. The hardest part was finding a floppy drive. But those were all MIDI. Where you're likely to run into a snag is with old plugins you no longer have. Not a showstopper, though, unless they're virtual instruments.

A $4,000 microphone won't make you sound like you have a $4,000 voice. If anything, it'll amplify your flaws. I reckon my voice is worth about $300, tops, which is why I use an inexpensive AKG handheld and reserve my expensive mics for things that warrant the extra detail.

Nah, only about 17 years. My sig is the Shannon-Nyquist sampling theorem. I adopted it after a longwinded online argument over sample rates. It means you can argue about just about everything else, but the math isn't a matter of opinion.

Sadly, I've never been able to get my old DOS games to work properly within a modern command prompt. I'd love to see Redneck Rampage or Shadow Warrior again.

Many of the games I've gotten the most mileage out of weren't graphically impressive. Games are about gaming first, visuals second. Civilization was a favorite for a very long time. That said, the first game I ran with my new video card was Assassin's Creed Valhalla and it's a marvel to behold with all the graphic options turned up to the max. The first day I was playing it, I was engrossed and didn't notice my son-in-law had come into the room. Then behind me I heard "holy crap, it's like watching a movie!" Yeh, except you don't get to personally decapitate anyone in the movie theater. Not if you ever want to come back, anyway.

These videos were produced for a "visit Oregon" campaign. Yes, pot is legal there. Sadly, if you go you may be disappointed. I have been to Oregon hundreds of times and only saw a flying whale once. The giant bunnies are totally legit, though.

First, make sure the "zero controllers on stop" option is checked. In CbB that's on the Preferences -> Project -> MIDI page. I don't remember where it is in 8.5. This will prevent the most common CC64 issues. You can also try increasing the size of your MIDI playback buffers. This defaults, IIRC, to 200 ms. Some users report fewer problems after setting that to 500 ms or more. However, this is usually recommended for when notes are intermittently missed during playback. Still, I've seen reports of changing MIDI buffers unexpectedly resolving other issues. Sometimes, this can be a symptom of a system problem such as very high DPC latency. Probably not your problem, but it's always a good idea to check your latency occasionally using LatencyMon. I have also had this happen due to a malfunctioning sustain pedal. If you're using a keyboard controller or synthesizer that has a sustain pedal, try unplugging it and see if the problem persists. Note that this problem is not unique to organs, it's just more likely to be noticeable because organ notes don't have fixed decay and release values, being just on and off. FYI, CC121 is the "reset all controllers" MIDI command, and CC123 is the "all notes off" command. Not gonna help in this scenario, though.

My best theory is that it's unavoidable due to the extreme dynamic range of acoustic pianos. I can't think of any other acoustical instrument with as great a dynamic range, except maybe a pipe organ. I have experimentally determined the dynamic range of my best sampled Steinway at around 50 dB. As to how to address that wide a range in a mix, there's only one way I know of and that's compression. In particular, parallel compression so that you get both downward and upward compression.

Yup, most buyers are just chasing the latest shiny thing. A GTX1060 will handle almost any game, even if you have to turn off high-res shadows or something equally trivial. Nobody wants it because it starts with a "G" instead of an "R". There's no real-time ray tracing in Skyrim.

Meanwhile, children in some remote African village are probably taking up a collection to send advisors to Texas who'll teach them how to provide drinkable water. Living in the First World was fun while it lasted. We did not know how fragile it was. Oh, wait, we did know. From the last time this happened, 10 years ago.

No, not for mixing. One of the reasons other DAWs report latency numbers is that certain other DAWs didn't use to have PDC, requiring the user to figure how much compensation was needed. Cakewalk was among first to make PDC a standard feature on an affordable DAW, instead of a premium feature you paid extra for.

No, it's not the microphone. Still not sure what it is, but we can be fairly certain it's not that. USB cable does make sense, though. Cheap cables, broken cables, cable extenders, all can cause data corruption/loss. That could, I suppose, cause latency that the driver and DAW would know nothing about.

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.