bitflipper

Once played with a drummer who used the stage name Buck Futz. I borrowed that name when I needed to populate a test database. My business partner then adapted the test database as a demo database and started using it for product demos at trade shows. We lost a potential sale when a show attendee spotted it on a report and said we she couldn't take us seriously with such a sick sense of humor. I told him that customer would have been trouble anyway.

Can be toggled via a button in the upper-right corner of the track view window. Button changes color when ripple edit is enabled.

Nobody touches her "giant c***k" - her name for it, not mine. Last rehearsal our bass player requested she not use such crude nomenclature on stage, a request that was duly noted with all the respect you'd expect in a democratic enterprise - and then subsequently mocked ruthlessly for the rest of the day. Fortunately, "c***k-hater" did not stick as his new nickname. Poor Steve, he's the new guy. But he's gradually learning that she not only takes pride in her Janis Joplin, she literally channels Ms. Joplin, Southern Comfort and all. We've been playing out pretty regularly since December. Turns out, there are plenty of gigs and a mysterious shortage of bands to play them. At this point, 3 of the 6 of us have had COVID. I have avoided it mainly by being an antisocial curmudgeon. I knew it would pay off someday.

The new keyboard stand arrived yesterday. It's nice. Very stable. As I expected considering its price. Here's the new rig, in my cluttered garage / rehearsal space. Yes, that's a plastic chicken in the image. Our singer didn't want to be limited to tambourine and cowbell.

Incredible arrangement. Dolly is such a treasure.

That would actually be a cool enhancement, to open a default project just for editing MIDI. It would not be easy to implement, though, since a MIDI file can contain multiple tracks/instruments. From a practical standpoint, it makes more sense to click on the cwp file and open the project. I'd be uncomfortable editing one MIDI track in isolation without being able to hear it in context.

Those kinds of artifacts aren't uncommon. I've even seen them in my own software over the years. It always came down to the video adapter (and/or its driver). I used to see them on my system years ago, but they went away when I upgraded my graphics card. Often those artifacts will disappear when the screen is redrawn, such as when restoring the main window after being minimized.

+100! Recommended reading for beginners and old hands alike.

Only part of that suspicion is true. Yes, if you are a keyboard player, a pro synth will feel better under the fingers than most low-priced MIDI controllers. There are, however, MIDI controllers out there that mechanically feel like a real piano. But if you're a hunt-and-peck kind of keyboard player, e.g. a guitarist who dabbles with keys, then there is no reason to spend more than a couple hundred bucks on a MIDI keyboard controller. Sound-wise, what you have on your computer's hard drive is likely to be as good as, or in many cases, far better. It's about storage limitations. The NS3 has just 2 GB, the Kronos has 60 GB, upgradable to 120 GB. I have individual Kontakt libraries that wouldn't fit into the Nord's entire memory. Some people actually do transfer things like Omnisphere patches into their stage synths, but when you do you only get between one and three velocity layers. Not everyone will agree with this, but IMO the only reason to invest in hardware synths of any kind is for live performance. And, being too old to attract groupies, the only reason to do live performance is to get out of the house once in a while.

Just ordered a 2-tier stand, so that I can continue to use the Kronos until I've had time to master the NS3. When I had a 2-tier stand in the past, I didn't like it because the top keyboard covered up the controls of the bottom keyboard. This new stand's supposed to be more flexible. Fingers crossed. If it sucks, Sweetwater will take it back. I don't know how keyboard players can stand floor wedges for monitoring. Most of the time, they're out in front and nearly inaudible due to being completely blocked by the keyboards. My (powered) monitor sits atop a speaker stand, just below ear level and off to one side. It's small but mighty, purportedly pushing 1KW. Hey, if you're gonna go deaf, you might as well enjoy pristine audio quality while you do it.

That's why I will never have a tattoo. Heck, I agonize over what shoes to buy. I can't imagine buying a pair of shoes that I'd have to wear for life.

Log in to celemony.com. Version 5.2 includes minor enhancements and fixes. If you're using iLok you'll require a new activation, which should already be in your iLok account. For the rest of us, it's a simple install.

Nah, Rick didn't have key splits. And, I have a wizard cape. Well, it's more of a Samurai cloak, but it has a sequin dragon on the back, so that says "wizard cape" to me. Coincidentally, Wakeman's primary instrument nowadays is the exact one I'm getting rid of. Could he know something I don't know? Probably, yes.

That was the first thing I thought of, too. However, if one of the vst3 paths was missing , that would affect vst3 effects, too. Not just instruments. The OP says vst3 fx work. That's what makes it a mystery.

First I had to cut out sugar to cure my diabetes. That worked and I've adapted to a low-sugar life. But now I have gallstones and have to cut out fat as well. That leaves just one macronutrient (protein) that I can eat. And AFAIK there's just one food that's nearly 100% protein: no-fat cottage cheese. Yum. I'll stir in some laxatives for when my guts turn to cement.

Well, that can't quite be accurate if he can't get ANY VST3 instruments to work. However, the best course of action is still to send Toontrack the dump. They will probably be able to diagnose the problem even if it isn't SD3's fault. Bad Mac, I hope you post back here after you've figured it out, as I'd be curious to know what the problem turned out to be. I checked dependencies for a handful of VST3 instruments and found none that weren't also dependencies of VST2 instruments. IOW, I couldn't find a single point of failure that would apply to ALL VST3 instruments and ONLY VST3 instruments. If you want a specific VST3 instrument that's known to work, but won't cost you anything to acquire, I'd suggest Spitfire LABS.

No joints needed 'round these parts. Just walking around while breathing will suffice.

Yeh, I could probably fly to Sweden and buy it there for the same money. Just like I could fly to Mexico for dental work and save money. I was actually lucky to find it in stock at Sweetwater. The case is on back order, though. Anything that arrives here by boat is a challenge. Supply chain something something. I try not to think about that. I am heavily invested in the color black. The last red thing I owned was a Vox Continental in 1967. Oh, and there was that red VW bus a decade later. Even my hair isn't red anymore.

I think the main perk we're getting is we don't have to pay for parking.

Just found out we've been booked to play the main stage at the Evergreen State Fair in August. And get this: we nailed down the coveted 11:00 AM slot - on a weekday!

Well, friends, today I took the plunge and ordered a Nord Stage 3 Compact. Five frickin' grand. To justify that I'm gonna have to keep gigging for the rest of my life. But I reckon $5k is still cheaper than another back surgery. While it doesn't have all the bells 'n whistles of my Kronos, it weighs a mere 25 lbs. in the bag, versus the Korg's 83 lbs. in the road case. This will allow me to attend the many jam sessions around town and thus help keep my chops up between gigs. I do in fact plan to "chuck the synth into the car, show up with a cable and plug into the PA", and thus prove Tezza's premise for this thread.

The only way to prevent this headache when building a new DAW is to save plugin presets in your old computer and copy them over. If your old computer is still up and running, whenever you have to finagle a plugin substitution just save presets on the old computer on a case-by-case basis. With very rare exceptions, the new version of a plugin will almost always be able to read presets from the previous version. The good news is that it's rarely a case of the new version being incompatible. I've only seen that happen a couple times. More likely, the new version has been installed in a different path, or (less likely, but not unheard of) the new plugin has a different name than the old one. Using VST3 won't completely eliminate such problems, but it can mitigate them due to enforced consistency for install locations.

Here's an example of a poorly-designed plugin. It's a screenshot I made for my 2018 review of DDMF's Plugin Doctor. Two points: 1. You won't see this kind of result from a quality fx plugin. This is a particularly awful one. 2. Even though visually there is obvious aliasing, it's debatable whether reducing it via oversampling would make an audible difference, because the aliased frequencies are 70dB below the main signal. Even in this extreme example, you might not even notice it. In fact, this dreadful plugin is widely used and has fans who swear by it.

I don't want to seem argumentative, Craig, as you've done a fine job of illustrating a case where oversampling offers a clearly audible difference. However, it's an edge case. We have to be careful generalizing from edge cases, lest beginners read more into them than is justified. This, I think, is the hole many users step into: that because oversampling can make a difference in unusual circumstances, it must therefore be useful or even necessary much of the time. This fundamental misunderstanding, I believe, is the genesis of hyperbolic phrases such as "game changing". In the few instances where I have encountered aliasing from internal processes, it's been a poorly-designed processor or synth. Find me a patch in Omnisphere that benefits from oversampling, and I will immediately concede your point without reservation.

CTL-Z works fine for me.