bitflipper

Not in ProChannel. Of course, you can use anything you want in the fx bin. But ProChannel plugins are made specifically for ProChannel.

My first guess would be that you have a plugin running in demo mode. Nice production, btw.

My first music rig was over the top: 386 with 10 MB drive and 16MB RAM. In the mid-80's that was an enviable setup. The drive was $600 and half the RAM I stole out of a Sun workstation, as I deemed any computer that couldn't make music unworthy of a whole 16MB. Cakewalk 1.0 for DOS, five synths, a 2-track Pioneer and a 4-track TEAC 3340S. Altogether maybe $10-12k or so invested - when I was only making $30k a year. We have it so much better now!!!

Damn, if all tube amps had multicolored light shows inside, I might go back to valves myself! I did in fact have a look at the Hughes & Kettner amps during my research. I've always thought they looked awesome. But at $2500 I'll just buy some LED strip lights instead. Greg, is this your amp? It's considerably less-expensive than the Marshall, too.

Not to brag, but I was once the youngest person in the world. Granted, it was a title I did not hold for long. I like that you can approach CW old-school, as a replacement for a tape recorder if you want to. But if you're a beatz and loops kind of guy, CW will accommodate you just as comfortably. In fact, CW has encouraged me over the years to incorporate more modern production techniques. The result is a hybrid approach that combines old-school print-in-realtime audio, recording MIDI instead of audio, and hand-planting MIDI in the PRV. Even the occasional loop for tedious things like shakers and tambourines. The toolbox just continues to grow. The biggest breakthrough was discovering the hidden variable in aud.ini... DontSuck=1

Hmm. Now that's some food for thought, being as the Fender would be a whole lot cheaper than the Marshall, which will come to a grand with tax and slip cover. Only problem is he seems committed to tubes. Funny, he's 28 y.o. but often says he feels he was born in the wrong decade, being a fan of classic rock and classic tones. I guess that's why he's happy playing in a band with a bunch of geezers.

Good point. I've already warned him he'd better not become "that guy", you know, the one who decides he's the star of the show. Although in my experience it's usually been bass players who are more likely to have that problem. Anyway, his 40 Watts will still have to compete with my 4KW.

Put your glasses on, Ed.

Thanks for lending a few brain cycles to this, Shane. The amp had power and the light was on, but there was no sound at all out of the speaker. I spoke to the guitarist yesterday and suggested that he really needed a better amp anyway, as he has trouble getting enough volume on clean tones. Knowing he's broke, I volunteered to buy the amp myself and let him use it while he saved up enough money to buy it from me. Yeh, I know, that's almost as bad as loaning money to a friend, a practice I long ago vowed never to do again after bad experiences. But hey, if he bails on the deal at least I'll have a nice amp. This is the one we're considering. I watched some YT demos and it sounds quite nice, either dirty or clean. It's got an amp sim built in to the line out that I'll be able to run to the vocal monitors. Two channels, each with its own gain and master volume controls. Closed-back with a single 12" Celestion. Switchable between 20W and 40W.

That's how I do it. Always. That's really the key to recording most things: you can do anything with a clean recording, including changing your mind later. As to "real" vs. digital saturation - yes, it's an emulation and if you'd spent 40 years recording analog tape before moving to digital you'd be able to tell the difference. Nobody else will.

Channel Tools is an often-overlooked gem, probably because users don't initially get what it does or why they'd need it.

What you're dealing with is what's known as the "proximity effect". Basically, it just means that many microphones are overly sensitive to low frequencies when they're close to the source. Such mics typically have a high-pass filter built into them, with a switch. They're typically set to 80Hz, although there is no standard and some mics have two settings. Always use that filter if it's available. There are several ways to address the proximity effect: Sing further away from the microphone, not always practical if you don't have a well-treated room. Apply a high-pass filter in the DAW, not as effective as treating the problem at the source. Using a bipolar ribbon mic that doesn't have a proximity effect, which can cost some serious $$. Using a multi-pattern microphone such as a Shure KSM-44 or AKG C414. Again, serious $$. The most cost-effective solution is to create a dead space in which to record vocals, surrounding this "vocal booth" with rigid fiberglass panels, and maintain a distance of at least 10" when singing. This solution works best if you have a quiet room and a quality microphone. If you're trying to mitigate the problem in an already-recorded track, a dynamic EQ can do the job. Wait for a sale on Meldaproduction's MDynamicEQ, which was something like 50 bucks last time it went on sale.

So last night I plugged in the guitar amp to see what the problem was. I know the guitarist is extremely strapped for cash and wouldn't be able to take it to a shop. Frustratingly, it worked just fine. I've repaired a lot of amplifiers in my day, and Fenders are among the easiest to work on. But they've always had obvious, consistent problems (smoke being a reliable diagnostic indicator). Never had one that was dead one day and OK the next. I've reseated all the tubes, about all I can do for now. This is a model I've not seen before, much less opened up, called a Bassbreaker 15. In case anyone has any thoughts on what the problem might be.

Sounds like a great setup. Unfortunately, we're already a six-piece band and can't afford to bring in a second guitarist for operational redundancy. Then again, we have no fewer than three tambourine players. Just in case one of them goes out of tune.

Now, Ed, remember this is a family-friendly forum. There could be young children reading this who are also Joe Cocker fans. Or maybe not.

I've not tested this, but I think what happens is the aud.ini setting gets updated whenever you change the pan law, so that it always reflects your most-recent choice.

Could be related to the bug in the C++ redistributable installer that Noel talked about here. It was deleting a critical DLL.

There is a variable in aud.ini named PanLaw. This is what determines the default pan law in the absence of a project template.

I used to run my keyboards stereo, first through a pair of Roland keyboard amps, later through a pair of QSC self-powered PA speakers (which sound great). But I eventually gave up trying to go stereo because the audience refused to all group in the sweet spot in front of the stage, equidistant from my speakers at 45 degrees. Leslie effects aren't quite as good, but mono improves overall clarity and tone. Plus the guitarist and bassist don't have to listen to just my left hand all night when I play piano. I still use two speakers, high up on stands on either side of the drums. For better or worse, everybody can always hear me clearly.

Oh, you fancy folks with your confusing knobs and stuff. All you need is Sausage Fattener. [EDIT] (for clarity)

That might just work better than a line out. And I've actually got both. But I don't carry them in my gig bag and we were playing on an island hours away from the nearest music store. I thought I was adequately prepared because I'd brought a hat.

And most of those are bapu's. Just sayin'.

YouTube is especially problematic, with levels all over the place. Although they do implement volume normalization, it doesn't work. Sorry, but I don't know of a solution for this, but I'd recommend using YouTube's volume slider rather than your audio interface's volume control. At least then you can keep your amp's volume consistent, which will improve your mixes. If you've never noticed it before, in the context menu on YouTube there is a selection labeled "Stats for Nerds". Check it out, it's illuminating. Along with video info such as dropped frames, it also shows the original audio level and how much reduction was applied by YouTube. I've observed some as low as -24 dB and as high as +8(!)dB. I guess it would be far worse if YT didn't do any automatic normalization at all. Here are examples of how the content level affects both the volume you hear and the overall quality. One comes in at +7.8dB, the second at -6.8dB. Same concert, different levels. One is noticeably distorted. See if you can figure out which is which without peeking (it's not hard).

Could have been a disaster. The guitar amp was DOA. He had a small second amp that's normally used as a satellite on my side of the stage so I can hear the guitar better. We had no choice but to mic that little amp and run it through the PA. With no extra mic stand, we had to dangle the mic down the front, so we're capturing it off-axis. An SM-58 is definitely not a side-address microphone, so as you can imagine it sounded pretty thin and nasty. Fortunately, we had a great crowd and the performance went over well. Everybody was firing on all cylinders, even me, being fueled by Starbucks iced mochas. With my high blood pressure I'm not supposed to do caffeine, and normally avoid it. Put a couple iced mochas in me and I'm like that squirrel in Open Season. One of the reasons the performance worked well was that for the first time I was getting guitar through my vocal monitor. Being able to hear him clearly meant that we were in better sync than ever and I was able to play off him in a complementary fashion. Sometimes adversity spawns epiphanies. So today I'm trying to figure out how I can monitor the guitar like that in future. I'm thinking a line out to the board and just routing it to the monitors but not the mains.

Sounds like what the OP is experiencing is the muting you get when you use the free player with a licensed library that requires the full version of Kontakt. GodinLG, which library are you using? We might be able to suggest an alternative that is compatible with the Player.