Jonathan Sasor

I tested the VST3 version and verified that it retains all the patch information correctly on project reload. If you have any further details, we can look into it.

There's a bunch of hurdles involved with having to deliver the app through Steam, so rather than divert those resources, it'll remain as a download from BandLab as it is now.

Yes.

Lets keep the contents of this thread on topic or it's going to be shut down- please, and thank you.

Okay guys, this thread is not particularly on topic for this section of the forum, so I'm shutting it down. There's plenty of other threads with people's thoughts on pending changes, elsewhere. Also friendly reminder in general just to make sure that the discourse on this forum stays civil. Thanks!

I stand corrected, there were the multi-part X1 downloads. Apparently after a decade things can get a little fuzzy when you've got plenty going on to stay busy. ?

Those versions were never "connected" products. They don't have the same install mechanism as SONAR Platinum. X3 was the first version to offer a full download of any kind. You'd need your install discs for them.

Cakewalk Command Center version 1.1.8 is now available! This version addresses an issue where existing Command Center versions are unable to connect to the updated version of the Cakewalk website. This new version can be downloaded from here: https://legacy.cakewalk.com/Command-Center Please Note: Cakewalk Command Center is only required for use with legacy Cakewalk Products and is not required for Cakewalk by BandLab. Thanks, The Bakers

We stay busy around here. Things are forthcoming. ?

That link should definitely be valid for the rollback installer to 2022.09.

I'm not seeing any issues with the download on my end, but if you keep having trouble you can send me a PM

Because it's relative to what you're working on.

Based on the dump file BBC Symphony Orchestra (64 Bit).vst3 is what's crashing.

This is a limitation on the BandLab App end. The web/mobile app only supports one tempo currently.

I mean, we definitely encouraging reporting issues when you experience anything with stability. But as you said, it can be difficult trying to triangulate things sometimes. The moment we're able to identify where a stability issue is, we'll fix it, but that requires being able to track down the root of the problem. For plugin crashes, there's often not much we can do on our end as if it's not the app itself that's crashing, it's up to the plugin developer to fix issues on that end. That said, we did add improved crash reporting, so even if you do not get a prompt about the crash, check the Minidumps folder in C:\Users\<user>\AppData\Roaming\cakewalk\Cakewalk Core\MiniDumps to see if a system dump was copied there as the app crashed. Beyond that, for intermittent issues, that would boil down to trying to eliminating other variables to see if you can isolate a cause that we can investigate. I appreciate this might not be the most exciting thing for many users, however troubleshooting things on the user end can greatly speed up being able to fix any potential issues on our end. Try noting whatever common threads you can find when you get a crash, particularly if the app just silently crashes.

Try the installer in the Update 1 Early Access post that Noel linked above.

If you're installing the new update, you should have an installer called Cakewalk_by_BandLab_Update_Setup_28.11.0.013.exe. If you're on the 2022.09 update, this installer will run to get you to the current version. If not, then it sounds like there's a discrepancy with the version checking on your system.

If you go to your C:\Users\<username>\Downloads\Cakewalk folder, what is the most recent installer version you have in there?

Hi Milton, First off, the official 2022.11 feedback thread is here: If you re-run the Early Access installer, does the project still hang on open?

Hi Milton, we have two methods for doing an Early Access drop. Right now, we're doing an informal Early Access where we're making the new build available publicly via this forum thread, but it's not pushed to our back end where it would appear in-app via Check for Updates. This simply allows us to expand the number of users on the latest build to the broader audience of this forum without necessarily pinging all CbB users to install it yet. My previous comment was just to indicate that I updated the build in the original post since we fixed a few things. We're still in the same phase of Early Access as before, so you'd need to grab an updated build if you had already installed the initial EA drop from yesterday.

@scook @FJ Lamela @IgoRr please note the build link in the original post has been updated to version 008 which should resolve the delete issue. Thanks!

You are correct there. Simple Instrument Tracks have a MIDI input, so you'd need to route to something with an audio input to record the synth output directly as audio.

It definitely seems like it's tied to using the percussive detection in Melodyne, which I'm guessing it's using in the Universal case there since it's not giving you any pitches. I suspect this is likely on Celemony's end. If you do the edits in melodic/polyphonic mode, it stretches normally.

Hi Tez, Can you send us a copy of your project? I can't readily reproduce your issue on our end.

Mackie Control is standard in the installer, you just have to add a surface instance on that page of the Preferences and choose the appropriate ports- assuming the Arturia controller uses that protocol.