Lord Tim

You should be able to just re-install Cakewalk over the top of itself and it will fix these problems.

^^ this is great advice. I was alluding to that in my earlier post and may have muddied the point by saying I thought the clean install fixed this stuff, but now I read this, I'm starting to question if I remembered correctly or not. Certainly give this a try if everything else fails!

Yes I did - my request was to add UPC/EAN into the Notes tab, and then expand the Markers (or Arranger sections) to include ISRC, composers, etc. like you'd find in most professional mastering apps. That way we could do a Mastering template over 2 tracks, and then drop markers at the start of song sections, and then export that to DDP or each section to MP3 with the info baked in. Not quite as robust as CDA or Studio One, but it would be good enough for simple projects that you could do all in-house without needing to export out to other apps. There's obviously a bit to think about by just using the regular Track View and the expanded Notes/Markers idea with proper redbook padding and doing automatic gaps and all of that kind of thing, so I'd say it'd take a bit of work to bake it properly rather than just doing a half-***** bolt-on job with it.

If you go into your Keyboard Shortcuts, do a search for "cal" (without the quotes) and you'll see Process | Run Cal right up the top, which is what you found, but if you keep scrolling down the list, you'll see the individual scripts under -- CAL Program Files -- which can be bound to a key directly.

Yeah, this is definitely weird. Like @Promidi said, this should NOT cause CbB to crash, even if it was one of the bad drivers I mentioned earlier. As far as I know, the Quad Capture isn't on the avoid list (someone jump in and correct me, though!) I'd tend to agree that there's something else at play here if a clean install hasn't fixed this, and you can't even boot into CbB with no USB device connected. Updating the runtimes is a good idea as per THIS post. Just confirming that this still happens with none of your devices connected? What other audio software is installed on this machine? You may need to do a registry cleanup, but IIRC the clean install instructions addresses that already. Didn't we just pass "patch Tuesday" when we typically get Microsoft updates? I wonder if you had a recent system update that coincided with this driver model change and muddied the waters? Windows may have "helpfully" broken something. It might be an idea to do a system integrity check just to rule that out so we're not chasing ghosts, @msmcleod explains how to do that HERE. In fact there's some other good chat in that thread that could be helpful too. Short of all that stuff, grabbing a crash dump might be the last resort to send in so a dev can pinpoint what's causing the crash.

Ok, the first thing I'd do normally is verify you're using the proper manufacturer's ASIO driver and it's installed properly. You didn't mention which audio interface you're using, just the MIDI controller. Are you using one or are you using the onboard sound, like a Realtek chip? This is fairly important to know. If you are using a proper interface, verify you have the right driver first. Then, in Windows File Explorer, paste this address in: %appdata%\Cakewalk\Cakewalk Core Then look for the file aud.ini and rename that to aud.old Cakewalk should now launch and let you choose drivers, etc. If not, you may need to go into the registry and clean out some dud ASIO entries. But try this first. If you have a proper interface, you should be able to select that now and choose the ASIO driver. If, for some reason, switching back to ASIO makes it crash again, repeat this process but change the driver mode to WASAPI Exclusive. That may give you decent latency results (although every device is different, and their proper ASIO drivers are always your first choice usually). However, if you're NOT using a proper interface and you're using an onboard sound chip, usually their ASIO drivers are garbage and you should use only WASAPI instead.

Which ASIO device are you trying to use? There are some very badly written drivers that should be blocked by Cakewalk, (eg: Realtek) but we should be able to narrow it down more if we know more about what hardware you're trying to use and what ASIO driver.

Yeah, I'd love to know the numbers so far. It's a bit tricky because fixing some long standing bug can have a knock on effect that solves a bunch of other problems that bug may have been exposing, but there would be a tracker for each actual reported bug case that would be able to be counted. I mean, if anyone way super bored, you could get a good sense of what's been addressed by looking at each update's release notes, but that would be a hell of a long job!

Not sure what the licensing rights are for companies, but it's $400 USD a year for the Media Encoder if you get it yourself, which you'd be paying for in the purchase/subscription price for paid DAWs. CbB is free and as we know, a lot of the paid addons that came with SONAR Platinum were taken out for that reason. I don't have the facility here in my studio to do surround currently, but I'd be happy to see Atmos all the same. But realistically, I'm not sure something like this would work with the free model Bandlab are using for CbB.

VST3 is very much recommended (not just by Cakewalk but by the VST3 spec) to go to "C:\Program Files\Common Files\VST3" and you'll see it's pre-configured in the VST path in Cakewalk too. If people are having issues with insufficient privileges getting to anything in Program Files, then this goes against the spec itself, which shows a much deeper problem somewhere. Sure, putting things in a different location may fix it, but this is more of a workaround rather than a solution.

Yes, but I was also responding to the people who said "I've never seen that", "what version" etc. but good job for getting in first.

Yeah there's some (open source?) libraries that REAPER takes advantage of that lets them do DDPs. It's very clunky, but it works. Probably the best implementation I've seen is the Project page in Studio One. I'd love to see something like that in CbB one day!

I should point out though that this experience is different to most users, though. The default locations will usually be fine, so long as nothing is installed using Admin or any permissions get screwed up. It's really not necessary to do this step unless there's a problem that can't be solved in other ways.

What happens if you go into the track itself and select the input on there directly, rather than using Tracks > Selected Track Inputs? Is that what you mean by you can't change it, or is it only from the Selected Track Inputs thing?

This dialogue is from Tracks > Selected Track Inputs. If you're not seeing either Audio or MIDI as options, it usually means those tracks are either not selected, or they've been archived or something, so the option to change them is disabled. Eg: if you select only Audio tracks, the MIDI part will be disabled in the dialogue box.

Yeah, sadly not in there currently, but I've sent over a few feature requests to expand the Markers or Arranger Track to include this stuff one day. Combining this with native DDP creation would save me a few trips outside of CbB for sure!

It depends on the VST. If you're not letting the installer itself decide, then if it's a VST2 plugin, it's usually at "C:\Program Files\Cakewalk\VstPlugins" and VST3 plugins always should go in "C:\Program Files\Common Files\VST3"

One of the devs posted a day or so back that the new update is coming very soon. Usually when things take a while like this it means that there's some big change or feature that's taking a while to bake. But it sounds like it's not far off.

Yeah, chiming in also to say this isn't a Cakewalk issue - all of this stuff works correctly here, and what Mark was saying was correct, it's blocked because of the different permission levels. You definitely don't want to run CbB as Admin unless you have to, not only for this issue, but just for system safety in general. When you installed CbB the first time, did you install it as Admin or as a regular user? Some permissions could have gotten mangled somehow in your folder structure too. I think once we get to the bottom of the HOW this happened, fixing it will be fairly straightforward and everything will work as you'd expect.

LANDR pre-dated Bandlab's involvment, so I'd say it's still there for legacy reasons, more than anything.

Download Cakewalk by Bandlab. It's free, and entirely backwards compatible with SONAR and all of your plugins registered to SONAR will work in Cakewalk. It's more or less exactly the same program as SONAR Professional but with thousands of bug fixes and extra features. Everything should simply just open in Cakewalk. Additionally, you might be able to contact support and see if they can recover your username and password if this was all registered via Cakewalk Command Centre. This is kept open as a courtesy to users of older software before Bandlab acquired the intellectual property. But I'd suggest going here and grabbing the Cakewalk installer and using the free current DAW: https://www.bandlab.com/products/cakewalk

You change that in the folder locations in Preferences, everything can be customised.

If it detects a previous installation on your system, it'll use the existing paths and try to upgrade rather than a fresh install. Use the following instructions for a Clean Install: https://help.cakewalk.com/hc/en-us/articles/360034066393-Clean-Install-Cakewalk-by-BandLab I'd also suggest using the Cakewalk Installer rather than the Bandlab Assistant, which is found on the same page as where you downloaded Bandlab Assistant originally.

Yeah, all of the Bluetooth is covered by the Bleak library that the main script imports. If I had more free time I'd investigate the same for MIDI but time, unfortunately, is not on my side. My programming skills are pretty rough these days so I'd expect more wailing and gnashing of teeth rather than working code ? OSC is a good angle though, I might dig into that a bit on my next breather