Jonathan Sasor

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.

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.

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?

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.

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.

Ad Dave said, it's likely plugin-related, but without a dump file it's hard to say for sure. Try other scenarios, particularly in a new project and check if bouncing in general crashes or if it's specific to what you have set up in a given project.

For track parameters, if you hold the Shift key while dragging the control, it will slow the change rate for finer adjustments as well

There's a lot more wiggle room in the VST spec than one might think, and one thing we do frequently is work with other developers over issues with plugins. Freeware VSTs can be that much trickier as well depending on who is working on them and what their focus is on, so they might be great, or they might have some issues. It just depends on who is making them and what they're testing. If you're seeing a consistent crash with a plugin, your best bet is to try and contact the vendor/developer for that particular plugin and provide a dump file if possible which will allow them to find where the issue is.

There's nothing inherently wrong with having multiple older versions of SONAR installed, so long as the latest version is the last one installed (as there's some shared components and obviously you don't want those overwritten with older versions). We haven't shipped V-Vocal in a long time as that was a Roland product, but assuming it's still stable on your system, we haven't done anything in Cakewalk that would break compatibility. If it's crashing while you're trying to port a project, you might have more success if you try rendering V-Vocal via a 32-bit install of SONAR.

That's still symptomatic of a driver issue. Double-check it's showing the correct driver in the Preferences. You can also try seeing if the device plays okay in WASAPI shared for the driver mode.

It's the Focusrite driver that's crashing Windows per your original post, so reinstalling Cakewalk is not really going to change anything there. Cakewalk itself can't cause a blue screen crash. Possible there's something else with how the hardware is talking to the machine that's causing it to crash like that- maybe try a different USB port. I'd definitely suggest talking to Focusrite if just reinstalling the driver didn't resolve the problem.

The only way to make the Control Bar go away is by hiding it via the "c" shortcut. Accidental keystrokes happen to the best of us. Shift + C will toggle the mini control bar too... You could always save a layout with Workspaces as well if you wanted a fall back point (aside from the factory Workspaces).

It's possible it might be opening them to some invisible XY coordinates off screen. Try changing the display resolution while the project is open and see if that helps. If you're getting a bunch of seemingly random issues even in Windows though you might want to be careful in case you have a hard drive that's on its way out... That can often manifest in really weird ways when it starts to fail. Always good practice to have backups of your backups...

Can you post a screenshot when you're getting the error? If you're using our web installer, that should be giving you the correct Studio Instruments installer for ARM64 systems. Thanks!

That sounds like more than a driver issue. The unit should be able to get power regardless of the driver status, it just won't talk to Windows properly without the driver. If you have the option to try some different USB ports on the machine, see if that impacts it, or if you have the option to try it on a different machine, see if the interface powers up there. There could be an issue with the ports being able to provide enough power or the Roland (or the cable) could have some kind of fault.

Are they using a different DAW to export the other file? it's possible there might be some timecode that's being stamped on it. If that's the case, you can try deselecting this option in the preferences:

As Kevin said, sounds like your audio card/driver is trying to run at a sample rate other than what your projects are.

This thread has run its course, so I'm going to put a lock on it. Please feel free to create new threads about any relevant issues, and we'll be happy to investigate. Thanks!

I'm able to load Clarity Vx without a problem. It's possible there might be something with your local Waves install that might need to be addressed, but in general there doesn't appear to be any issues with it on our end.

The track Gain control is your signal level before FX and the fader is after FX.

It's a different team that handles the development for BandLab Assistant as opposed to the Cakewalk app itself. The download page for Cakewalk now offers the Web Installer directly so a user would not need to have BandLab Assistant at all.

If you can get us a project where it's readily reproducible, we'll take a look into it and see where the problem is. Thanks!