scook

If the speakers are not connected to the interface and the audio is playing through the speakers the DAW is set up with the UMC404HD as the input device and the output device is whatever is connected to the speakers (possibly the PC sound chip). If you wish to use the headphones on the UMC404HD while recording or pratcicing, CbB must be set up so that the UMC404HD is both the input and output device. In this case, it may be easier to connect the speakers to the UMC404HD and set it up as the default Windows audio device. This will permit using headphones, speakers or both in Windows and CbB.

Following the directions in the link?

BA never installed on the desktop. At least, not since BandLab has used it to deploy CbB.

Was it a clean install with default values.

Could be a bad install. Compare the File - Folder Locations in preferences between the two machines.

This is covered in the SD3 help in the section called "Using MIDI Patterns." MIDI note 33 plays pattern G. Also if the button with the infinity symbol (the button below "H") is engaged the current pattern will loop. Click on "Session Drummer 3" in the upper left of the plug-in UI the press F1 for the plug-in help.

There is no OSX version of Cakewalk by BandLab. It is a Windows only product. Is your qustions about the browser-based DAW called BandLab? This forum is primarily used by CbB users.

The "New or Updated" folder seems to work in v2. Mine shows 112 modules updated. Of course, the number is installation dependent.

I start VM today and it updated some presents Went to their website and saw update notice. Downloaded the 2.0.17 update from the link above Ran the update Started the stand alone There were quite a few module updates for 2.0.17 This has happened in the past. Some module updates require a particular version or newer.

From https://forums.cherryaudio.com/viewtopic.php?f=8&t=1014

I guess this device does not have a factory supplied ASIO driver. There is a download option on their site for an ASIO driver but it might be a copy of ASIO5All. Unfortunately some manufacturers substitute this software for a proper ASIO driver. Of course, ASIO4All is not a driver at all, it is a wrapper for WDM drivers presenting them to software such as DAWs as ASIO drivers. Trying the other driver modes is an option. To avoid latency completely use the direct monitor feature in the interface for the track being recorded. This allows one to hear the input directly from the interface mixed with the rest of the tracks from the DAW. If one track monitored through the DAW has no noticeable latency subsequent tracks should be the same. Often times, additional plug-ins are added to the project which are the source of additional latency (aka Plug-in Delay Compensation). To see if plug-ins are the issue, try bypassing all plug-ins using the FX button in the Mix Module, "E" in the image below. If the delay goes away, there are one or more plug-ins in series at fault. Either temporarily bypass them, freeze the track or find low latency alternatives for use while tracking. While reading about the FX button in the Mix Module, take some time to review the info about the PDC button too.

Not sure what the problem is. Details are important. Arturia Rev PLATE-140 VST3 versions 1.0.0.1874 and 1.1.1.2042 in 64bit SONAR Platinum 2017.10 build 14, CbB 2020.04 build 179 and 2020.05 build 30 on Win10 v1909 seems to work OK here.

Muted tracks and takes may be unmuted while the transport is running so must always be streamed from disk. It would be hard to comp if takes were not always read. Archived tracks do not stream from disk. Maybe there should be an archive option for takes.

From the Valhalla May 2020 newletter

I probably should have mentioned this in my last post. There is no need to have Guitar Rig on a dedicated audio track. I assume from the track view image the two audio tracks contain different instruments from Kontakt and only one of them uses the ampsim.

Routing looks OK. Guitar Rig is not capable of sending MIDI data out of the plug-in. The MIDI track going to Guitar Rig may be recorded and manipulated just like any other MIDI track. It may be recorded at the same time as the Kontakt track but it does not have to be.

Each plug-in needs it's own MIDI track. Kontakt needs a MIDI or instrument track to play the synth Guitar Rig needs a separate MIDI track to control the plug-in. The MIDI source may be shared by the two tracks. The MIDI Event Filter MFX may be used in MIDI FX Racks to restrict the data passed to the plug-ins. It may not be necessary; depends on how the plug-ins react to unneeded data.

different view, same solution

Make sure "Enable MIDI Input" is checked in the VST2 drop down above the Guitar rig UI along with a MIDI track with your controller as the input, Guitar Rig as the Output and input echo enabled.

This is because the program could not figure out the beat count. The "Beats in Clip" may be fixed in the clip inspector in the Groove Clip section or in the Loop Construction view.

Z3ta+ is a VST plug-in and does not have the same permissions problem Pentagon I has. Not familiar with a loading issue with the plug-in.

It's up to the plug-in

Use File > Save As instead of Export to create a new MIDI file

Please do not cross post this into the other areas but do provide more information.