bitflipper

Yes, that's what I meant - that CC7 and/or CC11 messages are included in the data stream. Those are normally the only way volume information is conveyed. There is, I believe, a SysEx command for setting the master volume (similar to the master tuning SysEx command), but that's rarely used and certainly wouldn't be applied by default. Of course, individual instruments can choose how they respond to any CC, such as some orchestral libraries that tie CC1 to volume to make it easier to automate swells. Given that the files do contain volume information and it hasn't been modified, and those are just numbers that presumably Cakewalk doesn't alter, then we have to conclude that it's down to the way the VIs are responding - either in Cakewalk or in Reaper. There could have been some CC scaling going on in Reaper, making the instruments quieter and now they're just back where they should have been all along.

To answer the first part, as long as you keep SONAR installed you'll have access to every plugin that came with SONAR, including the proprietary ones that are explicitly tied to SONAR and can't normally be used in other DAWs. As far as the software is concerned, CbB is still SONAR. The speed with which waveforms are redrawn isn't impacted by the video card, even if it's a fancy one like yours. The overhead is incurred while Cakewalk/SONAR scans the audio data to create a "decimated" (low-res) version that's saved in the picture cache. As you can imagine, it's going to take a while to go through a gigabyte's worth of data. But you should only have to endure that process once, on import. If the only editing you're doing is splitting the clip and nondestructive slip-edits, that shouldn't require updating the picture cache. You don't actually have to physically delete those sections. For example, let's say you're separating a live recording into individual songs and eliminating the dead air and chatter in between. Just split the clip and use slip-edits to trim the two pieces. After that you can slide them along the timeline if necessary. These operations do not physically alter the underlying data, only how they are played back.

There are two possible explanations (assuming we can ignore the VIs): changes to volume (including expression and aftertouch) or velocity data. I don't have a great deal of experience importing MIDI, but my recollection is that velocities are not altered on import. I can't imagine why they would be. You'd have to examine the original data in another application or (even better) open it in a hex editor to make sure you know what some of the velocities actually are. If somehow there is no velocity data in the MIDI file (if that's even possible), then Cakewalk would set everything to the default value of 64. Of course, if that was happening it would be obvious because every note would have the same velocity. From your description, it sounds as though the music sounds correct but is just too loud. That would seem to eliminate velocities as the problem. So I'm guessing volume or expression CCs would be a more likely candidate. By default, Cakewalk does not send any MIDI volume commands to soft synths unless they are already embedded in the MIDI data. If the value over the volume slider says "(101)" that means "not sending anything". You should be able to look at the event list to see if there are any CC7 or CC11 events in there. If there is, then I'd expect Cakewalk to simply process them without modification, in which it comes down to how each synth interprets volume and expression, as there is no standardization here.

The idea is to save it up for your entire lifetime. Then, when you meet your final reward (e.g. driving your RV to Arizona), you dump it all out. I've been there, and can attest that that's what they've been doing. So much of it has been discarded all over the countryside that now nothing can grow there but cactus. Another mess us boomers have left for subsequent generations to clean up. Scattered light. For myself, I'm doing my part by burying all my saved up light in the backyard. No way those ungrateful kids are getting it. You know they'd just blow it all on one gloomy Northwest December. So the sun sets at 4:00 and it's raining every day? Oh, boo hoo. When I was a kid, before my generation gave you global warming, it snowed every day in Seattle. And we liked it that way.

Whenever someone asks me if I'm an idiot (frequent occurrence), I respond by saying: "If I was, would I possess the requisite comprehension, self-awareness and perceptivity essential to determine this fact?" - UbiquitousBubba

Really, what's wrong with people who are into feet? Personally, I'm rather attached to mine. In fact, I am bipedal. Better keep that to myself, I guess.

I think you should consider an alternate version with Zargg's vocal sung in German. Duct tape some fireworks to his boots and then make that video.

Don't dismiss tambourine players. Do you have any idea how long it takes to tune a tambourine? Ours is still trying to figure it out. I suggested there might be a YouTube tutorial. Joke's on me, there actually was one.

There are three chapters, each funnier than the last. I told myself that the new SSD I just bought was for sample libraries...then my inner Viking came out. Before I knew what had happened, my fingers had ordered an RTX 2060 Super XT. It will increase my Cakewalk FPS.

I remember an argument with a bandmate, wherein he explained that "there's no set way to sing a melody" and his was just his own interpretation. I countered that if he expected the rest of us to provide backing vocals he'd do well to stick with notes that were within the key of the song. This seemed to be an alien concept to him. And he wasn't even a bass player.

Yes, that was interesting. Thanks for sharing the link. For no particular reason, I'd always pictured Furman as maybe a subdivision of some Taiwanese manufacturing giant (which it now is), not a mom 'n pop startup by hippies. I'm looking at a Furman product right now, at the bottom of my rack.

A reasonable presumption, I agree. However, I assume the OP wants to know if the K-system is worth learning about. Hopefully, my terse affirmative didn't come off sounding condescending, and instead conveyed that yes, it's worth investigating. And now thanks to your thoughtful addendum, he knows that it is neither coffee- nor coffee-house related. So aleo, if there's anything you want to know about K-metering and speaker calibration, just let us know. Even InstrEd knows a lot about it. I, on the other hand, know nothing about k-cups other than to assume they are bigger than d-cups.

If it's in the Coffee House, just wait an hour. It'll slip off the first page and be forgotten. J/K. If it's your own post, just shoot me a PM (or scook, John, Wookie, chuckebaby) and I'll gladly remove it. I'd also suggest that if you've posted a question or issue and then subsequently resolved it on your own, everybody will appreciate it if you post a follow-up detailing what your solution was. Don't be embarrassed if it's just an "oops, it was user error" - those lessons are valuable, too.

Yeh, pretty much everybody.

Apologies to anyone who may have been put off of Melodyne 5 by me mistakenly assuming the software copy protection was Pace. It isn't. BTW, the upgrade was worth it just for the new leveling feature. Saved hours of editing.

Correction: I may have been wrong about the Pace requirement. I've been unable to find the paragraph that said that (or that I interpreted as saying that). It may be that the options are between an iLok dongle and software-based protection that is similar to Pace but not supplied by Pace. The difference is that while it's still tied to your computer, you don't need an iLok account to make it work and won't need to have the Pace driver service running.

Good stuff, Wook. So relaxing. You'd never know it had been created by an 8-foot tall monster. I think the new drums sound great. Minor suggestion: the crash cymbals are a bit overpowering and might benefit from a little more variation, e.g. adding another cymbal for variety or using a side-hit ride. OTOH, they might just need to have their velocities backed off. I find that SD3's crash and china cymbals often fit better at lower velocities.

Neither the problem nor the solution has anything to do with Cakewalk. Waves' copy protection is notoriously fragile, a mousetrap with a hair trigger. Repaired your motherboard? Sorry, we assume that means you are a criminal. Replaced your network adapter? No RBass for you today! What you have to do is re-authorize your Waves plugins using their tool. I've had to do that twice in the past, but neither time did I need to open a support ticket. Actually, back then I couldn't open a support ticket because at the time they denied support to anyone not enrolled in their protection racket (aka WUP). Since then, I've managed to avoid the problem, mainly by no longer using Waves plugins.

When you go to buy a new plugin and find out you already own it...is that a sign you have too many of them, or just an early indication of coming dementia? At least if it's the latter, every day will be like Christmas.

Yes, version 5 requires iLok. However, the hardware dongle is optional. You can use the software-only Pace driver instead. [EDIT: SEE CORRECTION BELOW] This locks it to your computer, but they allow multiple registrations if you use more than one computer. Just don't forget (like I once did) to delete previous registrations if you upgrade your computer, lest you run out of authorizations (like I did). Unlike some other companies who employ draconian protections (rhymes with "Raves"), Melodyne has never left me in the lurch by suddenly deciding I didn't own it. Hopefully that continues to be the case. Also note that Windows 10 is required There is no 32-bit version An internet connection is necessary for authorization VST2 is no longer an option (VST3 only) Rewire is no longer supported (but not needed in CW and never worked well anyway)

I came this close to buying it. Then I logged into the site and was informed that I already owned it from the last time it went on sale. Guess I should take that as a sign that I have too many plugins.

Celemony has been pestering me to upgrade for months. I've resisted because version 4 already does everything I really need it's going to be offered at a lower price before year's end I wasn't convinced that the new features weren't just bells 'n whistles iLok requirement they don't take PayPal Then I discovered this guy, Rich Crescenti. He does for Melodyne what Dan Worrall does for FabFilter, namely gets you excited about using the product, even if you already do. Like Dan's FF videos, Rich managed to take a tool that I thought I already knew intimately and showed me new ways to use it. It was his piano leveling demo below that made me cry "uncle" and give them the $149, Black Friday be damned. Here's a link to all his videos, which mostly pertain to vocals as expected, but also bass, drums and piano. Plus some Studio One-specific tutorials for you S1 users. Note that even though he's pushing Melodyne 5, 95% of what's demonstrated applies to version 4 as well, so it's worth a look even if you're determined to postpone the upgrade for now. I feel like a hypocrite, as I hate iLok and I don't like giving out credit card info online. Oh well. It was only a matter of time before somebody got me to capitulate. But this is the last time. Really.

If history repeats, there will be last-chance offers to us holdouts before the year's out. My last three Melodyne upgrades happened that way, even though the discounts have gotten progressively stingier over the years ($59 to $79 to $99). I feel a little silly postponing the update over a mere fifty bucks' difference, but version 4 does everything I need and there isn't anything in version 5 that screams must-have-now. The de-esser, I guess. It's supposed to be more transparent, but after ten years of practice I've become fairly proficient at pulling off invisible edits.