Promidi

Most Windows update related issues are driver issues. I have configured my Windows not to allow Windows update to touch any drivers. I do update drivers manually by visiting the respective manufacturer's websites and downloading them from there. I simply do not trust Microsoft with providing the correct driver.

Do you have a source for that. If you have a supported Graphics card (which I am sure the RTX 2060 is) then Windows 10 enables Hardware acceleration by default. I have never had to go to the registry to enable it - even when I had a lowly GTX650ti Just to confirm, I checked my registry and Hardware acceleration is enabled on my Windows 10 PC

Ah, now I get you. Nope, I don't think that's possible in Cakewalk.

Exactly, what do you mean? Which sampler VSTi? What do you mean "access additional ports" Need more details as to exactly what you need to achieve here.

Unrelated to your issue but Nvidia released version 440.97 a few days ago... Looks like the issue is sorted with the driver set to WASAPI mode. Mind you, you should plan on an external audio interface some time in the future.

What graphics card do you have? Are you using the latest drivers. Also, with a DAW software like Cakewalk by Bandlab, you will generally get the best performance using an external audio interface. Sure, you can use onboard sound in WSASPI mode, but a card or external audio interface that comes with its own ASIO drivers will give better performance. Also 4-5 seconds seems a really long time (was this actually measured?). That to me seems like a system issue that's nothing to do with Cakewalk. What Operating system. Is it fully patched. Are you using the latest drivers for all of your hardware. Actually visit the manufacturer's web sites to verify this. Don't rely on automatic driver update software.

After you have performed the import of the MIDI data into the SI bass MIDI track, open the event list view. Are there any events in there other than notes?

This update also resolved an issue I was having in the standalone as well. With 3.05, UVI Workstation would only allow the selection of the lowest buffer size for the ASIO devices. For instance, with the Focusrite 2i2, I was only presented with the option to choose 8 samples. This caused the CPU to max out after only a few notes pressed. I contacted UVI support but they really didn't provide a solution at the time. I was actually ok with that as I was able to use it normally in Cakewalk by Bandlab. I only ever used Standalone to audition sounds anyway. The ticket ended up being closed by mutual agreement. I suspect UVI revisited this issue because it was resolved with version 3.06. I can now choose my required buffer size.

I use 4 screensets per project and regularly switch between them. I also use a Lense. With the lense, I have deselected "Windows layout" using Lense Manager. This enables the project to load exactly as I have left it, complete with the Screenset it was set to upon save. This is because, with this configuration, it's the Screenset that is solely responsible for any screen layout. If you don't deselect "Windows layout" in the lense, the lense layout overrides the screenset's layout.

Lenses are global, where as screensets are per project Lenses are more to do with hiding features that don't fit with your workflow. For instance, if you never intend using the virtual keyboard, you can use Lenses to hide it from where ever it would normally appear. Lenses can also affect the way your windows are laid out - but you can tell a lense not to have any effect on screen layout. That way you can leave screen layouts up to screensets. Screensets are more to do with Windows layouts.

Registration has to be much made much easier than that. I don't need this plugin that badly for this number of hoops....

I doubt it will get any better than 80% off...... Log on to your IK account to see your price.

I had this issue also. What you can do it increase the height of the controller lane to give you more accuracy when trying to hit the mid point. When you adjust an existing wheel event, you'll see a dot when the mid point is reached - making placement a little easier. You could also edit the event in the event list view. I actually use a CAL script, but unfortunately that script would not work for every ones situation. You could also write a CAL script that edits an existing pitch bend event and changes its value to zero.

Keep a copy of the older drivers. They might even still be in your downloads folder if you have not cleared that. Mind you, I delete the older versions once I am happy with the updated version. I do agree, they should list older versions on their site.

The bad sectors are bad enough to fail to read on the first attempt, but may eventually succeed after multiple attempts. Once the system has that data (that it eventually was able to read) and copies it to a fully functional good disk, it will subsequently be able to read that data on the first attempt.

Just tested it here and I did not experience this issue. I used a 16 track MIDI only project that has multiple markers every 2nd measure. I insert a Meter change. All items moved by the inserted number of measures entered. CbB 2019.9 Build 70

The driver version I'm have is 4.63.24.564 dated 27 July 2019. This is for the Scarlett 2i2 2nd gen If you log on to your Focusrite account, you'll be presented with the correct version applicable for your audio interface.

Well, the developers obviously found an issue. These developers have the source code for the drivers and are privy to details about the driver in ways the end user could not even imagine. When the developers release a new driver, its usually due to a very good reason - even if those reasons are invisible to the end user. This is why I like to have the latest drivers - even if I'm not having any visible issues.

What happens if you transpose the audio clip using Process | Transpose - leaving the "Transpose Audio" checked?

It is %APPDATA%\bandlab-assistant\Downloads, However, once Cakewalk by Bandlab has been installed correctly, the installer deletes itself. What I do is copy installer file to an alternative location during the installation. That way I have a back up. Note: In Bandlab Assistant 5.06, this location is defined in settings under "System Folder"

I believe what is going on here comes down to what happens when the system encounters a bad part of the disk during data retrieval. When a disk is (sort of) faulty, the read might fail on the first attempt, so it retries multiple times until it succeeds. If gives it a damn good number of attempts. Of course, sometimes it just gives up, says stuff it, and throws up a disk error message. This is why your copy is very slow and why your audio from this drive glitches. You can imagine what happens when your system is streaming a file from a faulty disk - it will glitch when it gets to that part of the disk that is faulty as it tries to do the stream. I am pretty sure that even the fail retry and eventually succeed cycle will result in an event being recorded in the System Event Logs as a bad block. This is why it's always good to look in there if you suspect a disk issue. So no, you probably do not need a new cable. (unless replacing the disk gives you the same issue)

Focusrite 2i2 2nd gen here using version 4.63.24 No issues here. I make sure I have my sample rate set the same everywhere for all devices (even in Windows Control Panel)

If the DJ controller generates a signal, then it can be recorded by Sonar - assuming you have the audio interface configured to do so. It's more a function of what your audio interface can use as signal at its input. It would not even care what DAW you use - as long as it can process whatever your audio interface card is receiving. In my case, what I do is I feed the AUX 1 and 2 out signal of my Soundcraft EMP12 mixer into the line in of a Focusrite 2i2. This let's me record directly into a Cakewalk by Bandlab audio track. It's not really that involved. Just be careful to get your levels right without any clipping.

It's a portable application so clicking on the EXE is ok (DiskInfo.exe or DiskInfo64.exe) I would not deem Yellow: Caution as healthy. You may be able to back up your data from the E: drive, reformat and map out the bad blocks and then restore the data. However, there is no guarantee that you'll not get any further bad blocks. If this was my disk, I would be looking at a replacement now. Once the new disk arrives, back up your data from the E: drive if you haven't already, replace the drive and then restore the data. Remember, it may still be under warranty. If it is under warranty, then you can use the results from Seatools as evidence. If it's not under warrantry then consider a WD Black if spindle or even a Samsung Evo 860 SSD. What ever you do, that E: drive is cactus and is on its way out. Now would be a good time to back that data up.

You are so lucky you didn't burn out your CPU. Thank goodness for Intel's thermal protection - otherwise you'd be looking at a new CPU and possibly motherboard. Glad it appears you you got it sorted.