Lord Tim

The way to do it these days is enable Ripple Editing and just delete the section you want to remove. I've found that to be very predictable.

I came across the MP3 generating noise thing a couple of times and reported it, so with any luck it'll be fixed in the next update. Everything else seemed to be working OK for me, though.

What plugins have you got running in the project, and what's your buffer settings in the Export screen? Some plugins really misbehave with faster than realtime exports, or get tangled up with a buffer setting they don't like.

If you wanted to add an outside glow to anything, you would need to make the button image smaller and make the outside glow entirely within the button limits itself.

Ha, yes - if running a record label has taught me anything, it's You Do Not Want To Get Postage From Australia. ?

Yeah, that crashing is definitely not normal. If this is crashing directly to the desktop, you might be able to force it to give you an error first, which will let you capture a crash dump so the problem can be diagnosed. In Preferences > File > Initialization File, add ExceptionHandlingSeverity to the Option field, and 7 to the Value field, and press Set. Then restart Cakewalk. This *should* give you an error message and chance to get a crash dump, and you can get that off to support by following Noel's instructions here:

I have one, but I haven't used it since... wow, ages ago now I think about it. I'll see if I can dig it out and give it a test.

What driver model are you using? You might find you'll get decent results by using WASAPI Exclusive, since a lot of work was done on that since the change to CbB from SPlat. I'd ordinarily always recommend ASIO but it's worth a shot.

Interestingly enough, there's a lot of the icons from pre-X series SONAR in there if anyone wants to grab Resource Hacker and dump the BMPs/PNGs to make a Classic SONAR theme.

We've actually covered a couple of Queensryche songs over the years, in fact, and toured with the guys a couple of time. Big fan (Rage for Order was my first metal record) This is one of the very first studio tests we did here once it was finished (I think it passed ) https://lordofficial.bandcamp.com/track/the-whisper-queensryche-cover

I wonder how much of this stuff is lurking in TTSRES.dll TTSImage.dll and other Cakewalk libraries? If that image gets swapped by changing it, there must be multiple versions of stuff in there. EDIT: Yep, looks like it's part of TTSImage.dll - lots of redundant stuff in there going back to SONAR 8.x so I'd say it's a common library that CbB has inherited.

If nothing else, a Distressor is great on the way in so you don't clip the converters, even if you decide it's not in your workflow to strap it over the master.

ASIO4ALL is part of your problem here, and if you have issues using the proper Focusrite drivers, then there's something not right on your system. Some badly written drivers can cause issues even if they're just installed, even if your don't actually have them selected. The reason those other apps work is because they're likely using MME, which is compatible with everything but will give you terrible performance and latency. WASAPI can work but you may run into the issues you're experiencing here. Uninstall ASIO4ALL, and any other generic ASIO driver that may be on your system (eg: Magix Low latency or Steinberg Low Latency, Realtek ASIO, etc.) Then download the correct ASIO drivers for the 2i2 from the Focusrite website and install them. Try running Cakewalk again. If it crashes, you may need to delete your aud.ini file to stop it, which you'll find at %AppData%\Cakewalk\Cakewalk Core (paste that into File Explorer to go there). Do this while Cakewalk is closed and it'll make a new one the next time it launches. If that still crashes, you possible may need to clear out some of those bogus ASIO drivers from your registry. Let's try this stuff first.

Are you using the correct ASIO drivers from Focusrite? And what is audio latency set to? 2i2 is a very popular interface around here and people are having really good luck with it, so there's no issues with compatibility.

Yeah, that's very lean for a DAW in 2023. That's obviously not a regular thing or the forum would be up in arms about it, so we need to track down what's happening on your system that's causing it. Probably your best course of action is to capture a crash dump and get it off to Support to see exactly what's going on. Instructions here:

Ha, yes! There were a lot of workarounds on this, and that even dictated how the song itself was written in places because I had to line up accents with whatever existing parts I was able to pull out of the demo tracks. Interesting exercise though!

If you're missing any part of the UI, it's likely hidden by a Workspace. Try using Advanced from the dropdown box in the top right of the screen. This is also likely your toolbar issue as well since it's applied at startup. So you'd set that to None or you would save your layout as a New Workspace.

Cheers for the listen! For this style of music, the guitar is intentionally up front. It may not to be to everyone's taste but it's consistent with how this style works. The best thing is that if you download the demo project, you can remix it however you like.

@Scott Kendrick Cheers, Scott - thanks for your reply in the Production forum too! Hmm... the PDF should be extracted to the same location as the project file, but if not, I have a direct link HERE.

Cheers, Scott The faux mastering I put on the master was maybe a bit iffy, honestly, but considering it was all stock without anything specifically made for mastering, I think I just got away with it! But yeah, as I said, this is not a great way to do things if you're planning to keep the mix all in one process (aside from the big benefits of good organisation), but if you plan to make stems or alt mixes, this method is super useful. And doing alt mixes with the Mix Recall module as I did is really easy - you can load each one into the export module as a Task then set it to export while you go have dinner - it's great!

Yeah, nothing is sticking out as obvious from what you said and in the screenshots to me (maybe someone smarter than I am might have an idea?) The other suggestion I have, if this is real for you, is to post your .cwp for us to have a look at. You don't need audio in it, but it might help to look at the project itself to see what the routing is doing Failing that, the only other thing I can suggest is bypassing all of the plugins and seeing if what you're exporting lines up with what levels you expect it to be, and work backwards from there by enabling one at a time until you find the discrepancy.

Further to Glenn's advice above with Exception Handling Severity generating a dump you can send in to Support, I'm wondering what audio interface you're using and what driver model you're on (ASIO, WASAPI, etc.). It's possible you have some flaky driver doing strange things, or alternatively there might be some Windows system libraries that are mismatched or damaged too. Cakewalk is pretty solid for most of us, so this is definitely out of the ordinary! And yes, good advice for troubleshooting just above too - if that doesn't crash, something wacky is definitely up, so getting a crash dump will help considerably.

Indeed! I do that as well - super useful creative tool!

Go into Offset mode (look for the Offset button on the Mix module up in the Control Bar) - your control labels will get a + next to them. Do you see anything in there suggesting a -6dB cut anywhere along the way? Further to that, is your master bus going directly to your hardware outputs? If you import that master back into Cakewalk in a new project, does it still show -6dB? Just ruling out any other playback problems outside of CbB. It might be helpful to see a screenshot of your routing with the master bus expanded and all of the controls visible so we can rule a few things out. You definitely shouldn't be losing 6dB on a master bus, I use CbB for mastering all the time and it definitely should not do that, and does not do that for me.

For any lines that are very obviously leads (including any lead harmony lines that are meant to sound like single vocal parts rather than choir parts) I tend to put the de-esser on the track itself, so it's all independently adjustable. You might find that some vocals need a bit of a different setting so you're not sounding like you have a lisp. On the other hand, if I have stacked vocal harmonies, I clean them up at the track level first to remove noise between the phrases and tidy up the timing, then send that to a Bvox bus and I'll do all of my de-essing and EQ shaping there. We typically have 30 to 80 layers of harmonies, so treating each independently is asking for either an angry computer or walking into the ocean by the time you're done with that! Honestly though, whatever works is the correct answer. You actually might find that you have one layer of Bvox that are particularly sibilant - there's nothing wrong with throwing its own de-esser on there to tame it and still having one on your Bvox bus. If it works, it's correct.