scook

Yes there does have to be a file somewhere. AFAIK, Toontrack does not make VST3 plug-ins so the EZD plug-in has a dll extension. I am sure an EZD install contains multiple files. The log created using VST reset should contain information about all the plug-ins. If "Generate Scan Log" was enabled, when the reset completed a toast messaged popped up with the path to the scan log.

A VST reset clears and rebuilds the Cakewalk VST Inventory in the registry. It is like running a scan for the first time.

Not third party plug-ins like EZDrummer. Could try running a VST Reset with "Generate Scan Log" enabled from preferences. If the plug-in is still missing from the default "Sort By" layouts review the log.

Make sure the ASIO drivers are installed and Cakewalk is setup to run in ASIO driver mode. Latency has two sources a user can affect the interface driver buffer setting plug-in delay compensation To see if plug-ins are part of the problem click the FX button in the Mix Module. If the delay gets significantly less, one or more of the plug-ins in the project are the problem. While reading about the FX button check out the info on the PDC button. There is no way to completely eliminate the delay when monitoring through the DAW. This is why Focusrite has direct monitoring. This sends the input directly to the interface output eliminating the latency caused by the driver and plug-ins. Distorted audio may be the result of running too small an interface driver buffer.

The Piano Roll View is disabled until there is an instrument or MIDI track in the project. If you are just messing around use the Add Track menu to insert TTS-1 into the project. Read the To create Instrument tracks in the link. While your at it disable the MS GS Wavetable synth in preferences (there should be no MIDI devices selected because you don;t have any) and get used to using TTS-1 for GM sounds.

select the MIDI and audio track then bounce the track

IF the MIDI is broken out by instrument bounce each MIDI track separately to get per-instrument audio tracks or create an instance of the drum synth for each MIDI track.

1. No but a MIDI keyboard can be handy for data entry maybe start saving one now. 2. Not immediately (maybe not ever) unless you plan on recording audio but you may eventually get one so it can't hurt to save up for one while saving for a MIDI keyboard. 3. If running Win10 use one of the WASAPI modes (probably WASAPI shared). ASIO4All is not a driver, it wraps the WDM driver and presents it as an ASIO driver. Cakewalk can use WDM or WASAPI drivers without an ASIO wrapper. 4. The master needs to be routed to your audio interface (in this case the PC sound chip).

There are a couple of things that might interfere with Cakewalk accessing the internal sound chip. Running Windows and Cakewalk at different sample rates is a problem because an interface can only run at one sample rate at a time. Giving a program other than Cakewalk exclusive control over the interface. ASIO4All is not an audio driver. Instead it wraps existing Windows audio drivers and presents them to software that can use ASIO. The original purpose of ASIO4All was to provide programs that only used ASIO drivers a way to use the internal PC sound chip. Very few programs use ASIO and even fewer use only ASIO. Cakewalk can use ASIO but it can also use Windows audio drivers. I am not sure if there is any advantage to running ASIO4All instead of the WASAPI driver in Win10. I am sure there is an additional layer of software and config when running a wrapper like ASIO4All.

I cannot recommend the video because MIDI import skips reading tempo data from the MIDI file. Instead of import, I recommend opening MIDI files using the main menu File > Open. In addition to opening MIDI files without stripping data, Cakewalk automatically adds TTS-1 with the correct instrument assignments. The automatic addition and mapping of TTS-1 only happens when no MIDI output device is selected in preferences. If there is a MIDI output device selected in preferences, the file opens without adding TTS-1. Either way, File > Open is intended to be used when opening MIDI files as new projects. File > Import > MIDI is intended to bring MIDI data into an existing project. WRT adding additional plug-ins such as EastWest Hollywood Orchestra; once the plug-in is installed and scanned by the Cakewalk VST scanner (for info about the scanner see this page), it will be available to add to a project. One way to add a synth when working with existing MIDI tracks is use the insert synth function (A in the image below) in the synth rack view. Then change the MIDI tracks outputs and audio tracks inputs to point to the new synth as desired.

The look OK to me. Tracks 2 through 8 are MIDI tracks. Here is a description of MIDI track console strips http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Views.32.html#1257733 I usually leave the MIDI in one track and use separate audio tracks for the drum kit pieces. How the audio is split out to different tracks usually involves some setup in the drum synth then adding audio tracks with their inputs pointing to the synth outputs.

these are the updates needed for 2020.04 also looking at the theme image posted the cross fade and ripple edit indicators images below the punch recording module the duplicate track image below the track view view menu the notes image in the browser the export module I am pretty sure there are images in the PRV and possibly other views as well that need updates. It's pretty easy to see which images need updates in a dark theme because the default images come from mercury, a theme with a light background.

The better search strategy is use the CbB documentation index. When using the sites keyword search many of the old SONAR urls in the results can be changed to the current doc by altering the product name in the url to Cakewalk. While I mostly use the documentation index, I do occasionally perform keyword searches, after getting the result I use the "SONAR Platinum, Professional Artist documentation" filter at the top of the page to eliminate the older versions of SONAR, pick a page and if necessary perform the product name change in the url. There is also a pdf but it may be a release or two behind. The web-based help is always current.

Have you tried https://freesound.org/

There are several of sample-based synths in the list.

As noted above it is up to the synth not the DAW. Here is a pretty good list of plug-ins with that support microtonal tuning https://en.xen.wiki/w/List_of_Microtonal_Software_Plugins

Sample rate is not stored in the the project. The program logic for determining sample rate is as I explained above. It does not matter when the project was created. Project sample rate may be changed at any time until there is an audio clip in the project. The current project sample rate is shown in the transport module.

It's even in the documentation http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Recording.38.html

If there is no audio in the project, the sample rate is set by reading the Sample Rate value from the Default Settings for New Projects section of Preferences > Audio > Driver Settings Once a project references an audio clip, the sample rate for the project is read from the audio clip header.

Themes made before CbB 2020.04 will have display issues. Also, they likely have with some colors and images not modified based on the theme. Aside from a couple mentioned on this page, search this section of the forum for titles with the keyword "updated" and there should be quite a few threads containing links to themes updated for 2020.04. If you like an old theme, you could bring it current using the Cakewalk Theme editor.

Either drum samplers such as Sitala and Poise or general purpose samples like TX16wx and Grace (on the same page as Poise) will do the job for free.

That's correct. I have posted twice and will try one more time. To access the MIDI FX rack for an instrument track use the instrument track inspector. The links are in my other posts or just look it up in the help.

Look at the size of the file(s) being imported

The ASIO4All driver however it is packages still looks like the ASIO4All driver when running its config. Custom ASIO drivers setup screen look nothing like ASIO4All. Still, I have not read about any attempt to use a different driver mode. I have no experience with Behringer gear but did have an M-Audio inteface years ago. M-Audio wrote their own drivers but it turned out there was no advantage to using their ASIO driver. The interface performance was the same whether using WDM or ASIO. The point is not to get hung up on one driver or another when using prosumer grade gear. Try them all. Then again, the problem may not be driver related at all.

As I explained in the other thread, the MIDI FX rack for an instrument track is available in the MIDI tab of the track's inspector. IOW, click "T", and add MIDI MFX plug-ins into the MIDI FX rack "B"