bitflipper

There is no need to globally exclude audio files because they'll only be re-indexed after being edited or updated. You probably aren't going to be editing the audio that plays when you get an error message or an email, or the sound files from video games. I exclude my entire project drive, plus my sample libraries drive for good measure. Granted, I may be waiting a few milliseconds seconds longer for a Kontakt library to load as a result, but I can live with that.

He doesn't really need a separate interface, as the Mackie is also an audio interface over USB. The lack of pan knobs is troubling, but it appears they've dealt with that in a more compact way, with a single switch that separates channels 1 and 2 into L and R. I'm just guessing, but it looks like that button labeled "Stereo Pan" needs to be depressed.

Wow. 80 vocalists singing "aaaow" in unison. Pretty clever arrangement. Here's another one. Disco version of "Another Brick in the Wall".

That does sound like the kind of generic name Behringer would use. Maybe somebody here who is a Behringer user could tell us what the driver shows up as. IIRC, and that's a big "I", Behringer either initially didn't have ASIO drivers for their products, or did have but dropped them. Entirely possible that's just my old brain mis-remembering, I dunno.

^^^ Yup. Much bigger deal than file indexing. An even bigger boogeyman is your network interface. Might want to consider shutting that service off if you're having any performance issues. When I was struggling with a potato computer, I wrote a batch file to disable the network before starting up SONAR. Windows just assumes that nothing you could possibly be doing on your computer is more important than getting Microsoft notifications in a timely manner.

As long as you're excluding your audio data, indexing should not have any noticeable impact on performance.

Interesting. I use Trilian and always end up freezing it (it can be such a hog), but have never seen this behavior. I am not in the habit of rewinding or doing any other preparation before freezing. Do you guys also use Omnisphere, and if so, does it behave this way as well? My understanding is that both instruments are basically the same under the hood, as evidenced by each being able to play the other's samples. The reason I ask is I'm wondering if the issue is actually within the instrument or if the problem lies elsewhere. It just doesn't make sense that an instrument could cause this behavior on its own.

For drop-D tuning, of course!

I get that the two white keys are A and E. But why are there three?

Black mics do indeed matter. Especially when you show up to a gig and can't find it. The only black mic I ever owned got misplaced for over a year. I thought it was gone for good. Then one day I decided to empty my cord bags and sort them (drink enough coffee and it works like meth). There it was at the bottom of the bag, hiding among the hundred other black items in there. Its replacement was, of course, another black mic. Might add some yellow electrical tape to it. No rush since it's a stage mic and it won't be travelling to any stages for the foreseeable future.

Steve, ol' pal, this is what eventually happens when you've become an obsessive plugin collector. One day, everything just goes to sh*t. There ought to be a support group or something. As a codependent friend, though, I have to ask: have you tried FabFilter's Pro-R? Duh. What am I saying? Of course you have. I just thought of it because Pro-R is what I turn to when I want the reverb to dissolve unobtrusively into the mix.

Same here. I intentionally ignored it for weeks but you know how annoyingly insistent YouTube can be when pushing its recommendations. You watch one video on how to cook scrambled eggs and it thinks your life now revolves around that topic.

Thanks for the reminder, SK. I'd excised mode 3 from my brain, the same way I've purged most memories of my teenage love life. Unlike the latter, mode 3 is still a WiP.

Needs Kontakt 6. Still waiting for that must-have library that'll push me to upgrade from K5.

Is this one of those "my mic is bigger than yours" threads? Mine looks a lot like yours, but it has a "K" in front of it, which I assume means "kbetter".

I'm surprised you don't know that one, Ed. That's the Red Hot Chili Peppers' bass player. The photo was taken at his sister's wedding, right after he mistook some pastry frosting for cocaine.

As noted above, some INI settings affect how Cakewalk deals with latency, but there is nothing in there that's going to be able to reduce latency. Especially when that latency occurs within a plugin, in which case Cakewalk has no choice but to wait it out, even if means doing nothing for N milliseconds. ThreadSchedulingModel tells Cakewalk which of the three variations (0-2) to threading algorithms to employ. The newest of those methods (#2) is intended to be more efficient with modern CPUs (4+ cores) and was designed with WASAPI in mind specifically. However, Cakewalk will utilize all of your CPU's cores regardless of which model you choose. EnableCacheWriteThru is a true/false value that's true by default and is meant to make writing to disk more efficient by bypassing the drive's hardware cache. It is only relevant if write caching has been enabled, which it usually isn't - at least, not for audio applications where speed trumps efficiency and even reliability.

SONAR will only recognize the device if Windows recognizes it. First step, then, is to verify that Windows knows it's there. Go to the Sound control panel and make sure the Behringer shows up in the input device dropdown list. If it is, then you know that Windows is aware of it and is able to talk to it, eliminating potential hardware issues such as a bad USB port or cable. Next, verify that SONAR has been told to use that device. Go to Preferences within SONAR and make sure the interface has been selected. If Windows is happy and SONAR is happy, switch to a native driver and see if that works. MME is the most reliable of the native drivers (but not recommended for recording) and tends to work when others do not. If MME works, try WASAPI. If that works, it'll actually do better performance-wise than Asio4All. Behringer does have a proper ASIO driver if you have your heart set on ASIO, and it'll be more reliable and more efficient than ASIO4All.

A journey down memory lane...yes, Charles did build an XP-compatible version, I tested it for him and became a fan in the process. I still like Imperial Delay, though, as well as Timeless 2 and even the good ol' Sonitus. But it'll always be the tritik delay that gets first crack at a track. Kudos to Clint for turning me onto it. Sorry to the OP for taking the thread off track. But there are parallels, I think. The main difference is that everybody needs a delay, everybody needs a conventional algorithmic reverb, but nobody needs an infinite-feedback reverb due to its limited applications.

This does the same thing as Shimmer, but takes the idea a bit further, e.g. the ability to shift pitch by a musical interval. If you already have Shimmer, this would be somewhat redundant given how seldom most people actually use such beautiful but potentially mix-destroying effects. But if you don't currently have Shimmer or similar effect in your kit, this one will do a fine job - and is currently the least-expensive in its class. Gonna pass because you already have plenty of versatile reverbs? I felt that way about delays, too, until I tried tritik's delay. Now it's my first-call delay plugin.

If the waveform is not visibly clipped but sounds distorted, then we can assume that the distortion isn't from clipping. Record a sine wave, then zoom in on the waveform display and see if it looks like a sine wave. For example, see if the peaks have an inverted section. Zoomed out, it'll look fine but sound nasty. That particular symptom indicates an overdriven ADC, which has nothing to do with recording levels in the DAW. Make sure you're going into the audio interface's LINE input and not its MIC input.

7 GB is indeed quite large, but not outside the realm of possibility. CbB's design philosophy of non-destructive editing means nothing ever gets deleted. Lots of comps means lots of unneeded bytes languishing on disk. I understand your reluctance to start deleting files. I'd feel the same way. But if you're short on drive space on your backup disk, you may have no choice but to do some purging. Fortunately, there is a safe way to do it. Use "Save As" to make a copy of the project. The new project will contain only those files that are actually referenced in the project, less the redundant files. You can then open and play the copy to reassure yourself that it really does contain everything you need. If it does, you can then safely delete the original project, or keep it on disk but back up the trimmed-down copy instead.

I used to be on insulin. It struck me as weird that the treatment for high blood sugar was more insulin, when the underlying problem was excessive insulin to begin with (due to insulin resistance). The biggest annoyance with the insulin wasn't the 4-times-a-day shots, but the hassle of having to do it before every meal, even on an airplane or in a restaurant. And making sure any hotel I stayed at had a fridge for my insulin. When they took me in, the paramedics in the ambulance said my blood sugar was something in the neighborhood of 500-600, and my blood pressure was pegging the meter. This was all happening during a heart attack, so it was a memorable day. That was 14 years ago. I am no longer diabetic and take no medication for it. The solution was weight loss and sugar avoidance (sugar, not carbs; I eat all the rice and potatoes I want). I relate this to you as a way to say the future need not be as bleak as it might seem at the moment.

Wikipedia sheds some light on the meaning of the group's name... I knew a bass player who had uncontrolled vocal cords, and now I know his condition has a name. No, it's not "tone deaf".