msmcleod

Have you updated VSTScan ?

I suspect Concrete Limiter is tied to a particular release of SONAR Platinum/Professional. So the "re-install right version" is probably referring to SONAR Platinum/Professional. I'd recommend re-installing SONAR Platinum/Professional, installing Concrete Limiter, then re-installing CbB.

It looks like you had 32 bit plugins running under bit-bridge, Cakewalk didn't shut down properly leaving bit-bridge running, then you restarted Cakewalk and tried to load a project that uses 32 bit plugins running under bit-bridge. BitBridge was only really meant as a stop-gap while people were migrating from 32 bit to 64 bit operating systems. IIRC it was targeted mainly at Windows XP, but there have been several Windows versions since then. I'd recommend either ditching the 32 bit plugins for 64 bit replacements, or investing in JBridge. JBridge plays far more nicely with modern operating systems, and gives you a bunch of options to mitigate problems with older plugins.

I'm guessing "Always Import Broadcast Waves at Their Timestamp" was checked?

Not that it's a bad idea to export all your projects to a common format, but we've no immediate plans to discontinue Cakewalk. In any case, the new Sonar is 100% compatible with all Cakewalk by BandLab projects.

Maybe you changed this in the past, and it somehow got reset?

^^^This. Melodyne 4 doesn't work with Windows 11. FYI: Windows 7: works with Melodyne 4 only. Windows 10: works with Melodyne 4 or Melodyne 5. Windows 11: works with Melodyne 5 only.

Send an email to support@cakewalk.com

Have you tried re-installing the Visual C++ redists? https://aka.ms/vs/17/release/vc_redist.x64.exe (link taken from this page: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 )

1. Record your notes in a single audio clip. 2. Process->Apply Effect->Remove Silence Be mindful of the settings here.. in particular, your hold time HAS to be less than the gap in time between the notes. If in doubt, make it zero and increase as necessary. 3. Select all the clips in that track 4. File -> Export -> Audio and choose a source category of "Clips". Set something like {trackname}{clipindex} as your filename

@gimmexlz1 - thanks for pointing this one out. It's been fixed and will be available in the next update.

What is in your audio file is largely irrelevant during playback, as everything is clamped to 0db at the point it gets sent to your audio interface, as it needs to be converted to either 24 bit or 16 bit (depending on what your audio interface is set to).

There's no real advantage in exporting at 32 bit vs 24 bit. 32 bit is a floating point format, whereas 24 bit is an integer format... so although 32 bit may technically support a greater dynamic range, for all practical purposes in a final export, they're equivalent in quality. 32 bit has an advantage when recording/mixing, because it's basically impossible to clip even when going to 1000's dB, and you can go incredibly quiet without losing information. This is why all DAW's use either 32 bit float / 64 bit float internally. This is essential when mixing multiple tracks, but of little use with a single exported file - unless of course the file is incredibly loud or incredibly quiet. In 99.9% of cases, your final export will be in the normal dynamic range of human hearing. So 24 bit is fine. In fact I'd argue that 16 bit is more than adequate as a final export format, as it more than surpasses the dynamic range of human hearing.

You also need to bear in mind that in the 70's, 80's & 90's, a band's primary income was from album sales. Singles were just another way of promoting the album, as was touring. As long as the band broke even on the tour, they were happy - they'd even take a loss on the tour if they were confident it would translate to an overall profit in album sales. Nowadays, most people stream music for a fraction of the cost, with the band getting fractions of a cent for each play. Now the primary source of income is a percentage of ticket sales and the merch they sell at concerts.

As far as I know, Next only supports a single tempo at the moment. A release with a tempo track is imminent though. I think what you're talking about is tempo detection - i.e. automatically building the tempo track from an existing recording, so it effectively snaps to the grid (because your "grid" is changing to match the audio). Tempo detection is on the roadmap, but won't be available in the first cut of the tempo track. What you will be able to do however is record at a tempo of say 120, alter the tempo in the tempo track, then get you're recording to follow your tempo changes.

I quite often record things in Sonar or CbB, then open in SONAR Platinum - I don't have any issues. Even features such as the tempo track are handled properly - i.e. tempo changes are properly shown in Platinum, and if I save / re-open in CbB or Sonar, it converts it to a tempo track envelope. Arranger sections are obviously lost, but that can be easily worked around by saving your arranger tracks as an arranger template and re-importing it.

The Mackie Control surfaces are designed to work as a group - i.e. as if they're a single control surface. So for example, if I had an MCU, 2 x XT and a C3 and I want them all to work together as one, I'd set them up as: MMcL Mackie Control XT #1 MMcL Mackie Control XT #1 MMcL Mackie Control #1 MMcL Mackie Control C4 #1 If I had an additional MCU that I wanted to use for controlling buses, while the others are controlling tracks, I'd set it up as follows: MMcL Mackie Control XT #1 MMcL Mackie Control XT #1 MMcL Mackie Control #1 MMcL Mackie Control C4 #1 MMcL Mackie Control #2 <- additional MCU But unless you want them to work separately, there is no reason to use the MMcL version of Mackie Control - just use the one shipped with Cakewalk/Sonar.

No. Tempo isn't actually automation - it's just shown as an envelope. Automating tempo makes no sense - tempo underpins everything in the engine. Automating it would be like changing your car wheel size while you're driving it.

Sonar is officially released, and has been for a few months. There is always a continuing beta program as is common with many software products. This allows us to get early feedback on new features / enhancements, and fix any newly introduced issues before it is released to the wider public.

I still think uploading to BandLab is the best solution. Not only is it free, but you could have the tracks marked as private so you can limit access to each client.

You can use MNotepad from Melda Production - it's part of their free plugin collection:

It's Windows update time again... I bet Windows is preparing the update in the background...

The most common reason for this: Best to set the controller to something you're unlikely to use, e.g. 120. If you're not using MIDI events for triggering commands at all, uncheck "Enabled".

Interesting... zip up your project folder and send it to @Jonathan Sasor... we'll see if we can repro the issue.

It might also be worth recomputing the waveform picture... maybe it's gone stale somehow.... Right click on the clip, and pick "Associated Audio Files", then on the dialog select all the files and click "Recompute Pictures"