HOOK

Once in a while, I still learn a new (old) trick. I'm glad we had this conversation. Thanks.

Well, Mark. I've been using Cakewalk since 94. Never once have I even noticed "Snap By" - or heard of it for that matter. My songwriting workflow has always consisted of TONS of cut clips and snapping to the grid. And I can't tell you how many countless hours I spent in the early versions manually fading my cut points because of clicks and pops. And the auto-crossfade never cut at the snap point so I never could use it. I just played around with "Snap By"...and now I feel like an idiot. 🤣 Dare I ask? HOW LONG has "Snap By" been a thing?

Yeah. I can't wait to pay for Sonar again. 🤥

Track/Bounce to Tracks and choose the split mono option.

Klaus...I've had that disabled since the mid 90's because it causes splits to not fall exactly where you place the transport. The problem with Auto-Crossfade is this: Say you're clipping the left side of a waveform on beat 2. When you split it with Auto-Crossfade activated, the clip actually splits BEFORE beat 2 and then fades-in to beat 2. Do it....look closely. You'll see what I mean. And then, if you decide to drag and drop that clip onto a different part of the grid, it snaps to that cut point (which was never on the grid) - and the audio is off by that much. I've never understood how this is useful for anyone.

Hi Mark. Indeed, it works that way. The problem I have with the auto-fade function is that it snips the clip at a point prior to and after the desired grid line and fades into or out of your intended split point. If you do that to a group of tracks and then drag that group of waveforms over a few beats, now EVERYTHING is off by that much because it snaps to the cut where the fade starts. That's no good. If you guys change the S shortcut to do the same and I can't shut it off, it'll ruin me. I've been using S to split clips for a couple decades man....don't do that to me! 🥺

To be frank, it doesn't matter if I or anyone else agrees or disagrees with your speaker choice. Neither of those sets of speakers are "cheap". But you are here asking why your mixes won't translate when you mix with your speakers. For future reference, you can "demo" the higher end gear through the on-line gear shops. Basically, you pay for it and they ship you a demo unit. That gives you a few days to use it and decide - in the real world. If you don't like it you can ship it back and try something else or get your money back. Once you decide you love a piece of gear you can ship back the demo and get a new one delivered. Happy mixing!

I fought and fought these problems as a younger man - even in a well treated room - thinking I could make due with what I had. I'd burn 10+ throw away CDR's a day trying to dial in a mix until I got speakers I could trust, and not just speakers I had listened to a lot. It was very frustrating. I was using Alesis Montior One speakers in the beginning. I thought they sounded great. And heck...they were studio monitors, right? You can have speakers you love to listen to, and know very well, and they can still straight-up lie to you when you mix on them. To be totally honest, I don't like listening to music on the speakers I mix on, even today. But they deliver a mix I can trust. And I knew that when I did my very first mix and took it to my car many years ago. They still astound me when I take a mix out in the real world, how well the mix translates. Some good advice has been given in this thread. And if none of it gets you where you need to be, I'll just add that - if I were a young man today and I was broke like most young people are, I'd certainly look into the Slate VSX, Waves NX or Sonarworks software and consider mixing that way until I saved enough cash to demo my first set of great monitors. Not just decent. Not just what I can afford today. A wise man once told me to stop buying cheap crap just because you can't afford the good stuff - when you already know you'll want to upgrade later. Save your money and buy a world-class solution once and move on. Speakers are definitely on that list of crap.

Yes...pops and crackles you'd have to deal with manually, one way or the other. The custom button is quick. But having the ability to tweak this in preferences would be ideal so that you'd never have to worry about it again.

I have a custom button set up for a 1ms fade to "Fade Selected Clips" after I split a clip. I lasso the clips and hit the button. It applies the fade to both ends of any clip I highlight. This totally stops any audible click or pop when splitting a clip at a non-zero crossing. PLUS, that 1ms fade in and out is so fast that it's not audible. It would be good to see an "Auto-fade when Splitting Clips" setting in Preferences where a user can set the auto-fade time as he/she see fit. I know there's a setting similar to this for comping. And I know there's a setting for auto crossfade. But I'm specifically talking about splitting a clip in two and then having the fade applied automatically to the new clip sections that don't overlap.

That's odd. Looks like, on my system, all mutes are cancelled while the bounce processes...and then goes back to muted at completion.

I regularly use their Microshift and Alterboy on a vocal bus in Cakewalk. I can't even have those turned on in the project if I want to track anything else on other tracks. When I dropped them in Reaper, I tracked all day with them on the vocal bus while I tracked guitars and whatnot. I still was unable to track vocals in real time without a huge latency issue. Not a real problem...don't need it for tracking. Point is...for some reason they play way nicer (and as VST3) with Reaper. I didn't test to see if that was because of Reaper's Anticipative FX Processing or not.

That's true. Before posting here I contacted them and asked for the previous installer. They happily supplied it via link.

Subsequently, I looked at my other two Soundtoys plugins and they're both VST2...so I'll have to be careful of those if new updates come around. I did send a support message to Soundtoys as soon as I realized it was an issue with their plugin. I'll share what they have to say, if it's worth sharing. Still. Pretty surprising that Cakewalk didn't like that VST3 when I run quite a few other plugins as VST3. Reaper ate it like candy.

I'll be damned. That was it. VST2 installed and the whole problem is gone! Thanks for the heads up.

They ARE pretty hard on the Cakewalk engine. I use a couple others that I basically can't use if I still have tracking to do. I'll uninstall the plugin and see if Vst 2 is an option. thanks

I went into my programs list and arranged by install date. I deleted several recent installs that could have been reaching out on the internet, but nothing helped. But I did see the Soundtoys Little Radiator 5 update I thought hmm.... Deleted it from the project and the problem is gone. What sucks is that I've been using that plugin with Reaper for the last week with no problems. And I use it on kick, toms and bass on just about every mix in Cakewalk for months now with no issue. No bueno.

I don't think so, Craig. I looked in the ASIO registy entry. See above.

Thanks. Yeah...I looked in the registry immediately because I did this same thing to myself with Cubase a few months ago while I was troubleshooting some hardware. I only see one thing in there labeled as ASIO - and that's the Lynx driver that should be there. The other two...not sure what they are. They read: (Default) (Value not set) CLSID {AC4B2DC6-BB54-4a47-8C83-4954E6B13769} I'm just smart dumb enough to find regedit and dig around. But not smart enough to competently delete stuff. 🤣

Did that. All looks the same.

Is there a known issue with Reaper and Cakewalk on the same machine? I installed Reaper a few days ago and spent a few days working there exclusively. A few days later, I went back to Cakewalk to play something for a writing partner, and now I have kooky playback issues...occasional stuttering and digital beeps. Had none of that before the Reaper install. Thanks for your input.

Will we be able to import and use our current CwB workspaces, custom buttons, fx presets, track templates, plugin folders and project templates into the new Sonar? In other words, will this coming paid update keep our customized workflow intact, or will we have to rebuild? Thx.

Back in the mid 90's I had a writing partner and we wrote/recorded a bunch of tunes with early versions of Cakewalk, when computers really weren't up to the task of aggressive audio tracking and mixing. We managed. But they weren't as cool as what we can do with today's Cakewalk and today's computer power. In late 2022 we decided to finally revisit and re-record some of those songs from the ground up. This one is called Fall For You.

☝️THAT

I may not be following your routing completely, but this sounds like you have input echo on at the track level. Turn that off and check it out.