Promidi

What about buffer size? I also have never had issues with tempo changes with VSTis

What sample rate, bit depth and buffer size are you using?

The default of 250ms is a little on the low side..... Try increasing it. I have mine set to 750ms. I use tempo changes all the time in my tracks and never have stuttering. Mind you, I am using external synths. Do you have any tempo based delays on that Kontact instrument?

I downloaded "Theme from Mission Impossible" and opened it up in CbB. The SYSEX data is definitely there. It's in track 1 right at the beginning. What I do when looking for SYSEX data in a MIDI file is I select all tracks. The open event list. If present, the SYSEX is at the start, but sometimes it can appear in the middle of the track. I do this at times with the MIDIs I create. You can use the event manager (Under the view menu on the Event List window) to restrict the view to just SYSEX data. As sysex does not contain channel information, it can be in any track.

What is your MIDI prepare buffer set to?

The fact that, in Event list view, CbB replaces with blanks really long patch names as they appear in instrument definition files. I have contacted Bandlab support about this but they have not addresses this issue yet.

ASUS monitor connected with HDMI should be irrelevant. Have you tried updating your video drivers. The fact that Java had issues indicates a system issue rather than with BA. (note: Oracle Java is not required for Bandlab assistant. Maybe you're thinking of JavaScript - which is a different thing) I have always just downloaded the BA installer directly from here: https://www.bandlab.com/download/assistant/windows Of course, when you install BA, make sure the BA process is not currently running by using Task Manager and checking for the presence of "BandLab Assistant.exe" under processes.

I've used SYSEX MIDI messages for the last 20 years with Sonar and Cakewalk products (up to CbB 2019.9 Build 70) to control an external XG device. In all that time I have never had an issue. First this was with an internal PCI card (SW1000XG) that responds to SYSEX. Now it's via a USB to MIDI converter (Roland Um-One Mark II) to an SW1000XG in a second PC. SYSEX data has always been sent and recognised by the intended equipment. Note: With CbB, I found that I needed the MIDI driver mode to be set to MME rather than UWP. UWP always gave me issues of missed data - especially sysex.

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.