scook

Create a copy of the project, select and delete all the tracks (one could work with the original file but a safety copy is a good idea) Save the project as a MIDI file At the command line type: MIDIcsv.exe MIDIFilename > csvFilename Then open the csv file in a text editor or spreadsheet, clean up and format as needed The link has quite a bit of information about the tools and how to use them.

The track control drop down above the track headers in the track view contains track control presets and the track control manager used to maintain the presets. This is used for the controls displayed in the track headers. Workspaces affect much more than the track header controls in the track view.

Here is the documentation on the instruments bundled with CbB. TTS-1 is part of the core install The Studio Instrument Suite has a separate installer available from the "Install Add-ons..." menu option

Session Drummer 3 is not part of CbB.

CbB includes a time-limited trial version of Melodyne (I believe Editor 4 but it could be Studio 4). Once expired the editor stops working but monophonic audio-to-MIDI and tempo detection continue to work. This demo does not require creating a Celemony account. SONAR X3 Studio/Producer and SONAR Professional/Platinum included a license for the regular commercial version Melodyne 2 or 4 Essential. One license for Melodyne was issued. Those upgrading from X3 Studio/Producer to SONAR Professional/Platinum did not receive a second license. Since it was the regular commercial version of Melodyne Essential, users were required to create a Celemony account to register the product. When Celemony released Melodyne 4 the upgrade from Essential 2 to 4 was free. CbB supports ARA2 (not Aria). This is the technology behind Region FXs.

Video View Note: this view is not part of the Basic Workspace. To use the Video View change the workspace to Advanced, create a custom workspace or set workspaces to None.

SI Drums has a single stereo output. To break the kit out into separate audio tracks requires either: separate instances of the synth for the kit pieces that should be on separate tracks or bouncing the MIDI data separately adding audio tracks for each bounce. The MIDI data could be in one track or multiple tracks. When using a single MIDI track a drum map allows mapping the MIDI data to multiple synths or muting/soloing the notes to play.

Aim Assist If the shortcut "X" is a problem set it to "Do Nothing" in preferences

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Dialogs1.21.html

The audio issue is separate from the MIDI issue. To resolve the audio issue start with an audio clip. Review the audio settings in preferences http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x20075 http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B17 http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B19 posting images of these screens may help in diagnosing your audio setup issues. The MS GS wavetable synth does not rely on any audio mode in the the DAW as it is an external hardware synth. Sending MIDI data to it should make sound. If it is not making sound then either the MIDI data is not making it to the chip or the problem is outside of the DAW. Trying to interactively play a controller through either a soft or hardware synth requires enabling input echo, the button to the right of the record button in the track header. Soundfonts do not load natively in the DAW, to use soundfonts requires a plug-in to host them. Once the DAW plays audio as expected, consider opening a MIDI file as described in my first post. Most of what you seem to be dealing with fall outside the realm of software errors so I would not expect any error messages from the software.

The ASIO driver for Realtek is not very good. Removing this driver is not a bad idea. Even leaving it installed using one of the WASAPI driver modes may work better. Importing a MIDI performance is not a good idea. Importing MIDI files strips some data from the file and is intended for use with MIDI clips. For a MIDI performance, try File > Open If there is no MIDI output device specified in preferences, Cakewalk automatically sets up TTS-1 to play the MIDI file. This is usually a better solution than relying on the MS GS wavetable synth. No joke.

less 20% using the discount code 20PERCENT published on the site.

A VST plug-in must include at least one dll binary file or there is nothing for the VST scanner to scan or the DAW to load as a plug-in. A collection of wav files is just that...a collection of audio clips. Audio clips may be added directly to audio tracks, loaded into the Matrix view or loading into a sample playing plug-in such as the ones mentioned in this thread

The SONAR 8.5 upgrade was the first available as a download. In order to reduce the size of the file, an accommodation made for slow internet access, the files common to SONAR 8 were not part of the download. As a result, the downloadable SONAR 8.5 upgrade relies on an existing SONAR 8 install. All download versions after SONAR 8.5 were the full retail product. I do not recall if X1 shipped on disk or not (I believe there were disks for it). It is the first version I purchased as a download but it was also the first time I waited until several updates were released. In fact, I did not purchase X1 until Producer Expanded was released a little after the X1e update. On the subject of the OP, V-Vocal is a DX format plug-in but it is not implemented as a regular plug-in intended for use in the FX Rack. This is why Cronus is on the Exclude list. The plug-in was bundled as part of the SONAR core. This means V-Vocal normally requires installing the DAW to get the plug-in. There is a drop down on the Advanced Install pick list providing for a "Minimal Installation". This option creates the smallest footprint for a functional DAW including V-Vocal. V-Vocal was bundled with SONAR 5 Producer through X2 Producer (thanks to @abacab for compiling the SONAR plug-in spreadsheet).

By default when the scanner is running a toast message appears in the lower right of the screen. This may be suppressed by disabling Show Notifications. It may be hanging on a plug-in. Make sure "Scan in Sandbox" is enabled. When running the scanner shows up in the Windows Task Manager. It may be killed from there. Try the following: Set the scanner to manual scan in preferences. Reboot. Run CbB. Run a VST Reset from preferences with "Scan in Sandbox" and "Generate Scan Log" enabled. If the scan completes, reset the scan frequency to your preferred setting

If using the internal sound chip do not use the RealTek ASIO driver. It is not suitable for DAW use.

Install older SONAR DAWs out of order at your peril. It can result in shared folders being overwritten. The fix for this is re-installing CbB. Installing plug-ins either using the separate Platinum installers or advanced install options is relatively safe. Although it is possible to overwrite newer plug-ins with older versions. While not a great idea, it is not the problem old shared folders can be.

Directory junctions are easy. They rely on a command line tool called mklink.exe For example, I use a directory junction to relocate the default "Cakewalk Projects" folder. This lets me leave the default paths for Cakewalk projects and the global audio folder but physically relocate the data. In my case, the projects are located on the D drive. To do this, after installation I moved "C:\Cakewalk Projects" to "D:\Cakewak Projects" using Windows Explorer Open a command window as administrator and typed mklink /j "C:\Cakewalk Projects" "D:\Cakewak Projects" Now the DAWs still use the original default paths on the C drive but the data is physically written to the D drive. If you need specific help on moving parts of your installation or questions about the process, I am sure the forum will help. Directory junctions are am OS feature worth leaning.

The owner believes the software should be free and has stated so on multiple occasions. Here is some info about BandLab Technologies and their businesses.

The link points to the old Cakewalk site. Cakewalk went out of business in 2017. None of their products are available for sale. In 2018 BandLab purchased Cakewalk IP from Gibson and released a free DAW called Cakewalk by BandLab (CbB) based on the SONAR Platinum code. The old site is running (courtesy of BandLab) to provide access to the current Cakewalk and old SONAR documentation, old forum. old knowledge base and customer accounts. The old Cakewalk activation servers are running too. The CbB website is https://www.bandlab.com/products/cakewalk CbB installs as an upgrade to SONAR. It updates the "Shared" folders and adds new folders for the DAW. After installing CbB botk X3 and CbB will be available.

Just one more mention of directory junctions. They are the safest way to move data. It is very hard to lose data or create something that cannot be undone. I suggest if you have the space, install everything using defaults and use directory junctions to free up space as needed. A 400GB system drive is plenty big enough for the foreseeable future. Skipping the tutorials and demo project significantly reduces the footprint of SONAR installs especially for X-series and Platinum. I would not perform full installs of anything older than X2.

Keep in mind, VST plug-ins do not take up much space. Samples used by plug-ins do. Also few VST3 plug-ins offer an install path. The spec recommends a path on the C drive and most manufacturers follow the recommendation. Some DAWs require VST3 plug-ins go into the spec'd path. Most plug-in installers provide a way to relocate samples. For those that lack this feature, directory junctions are a good way to move data from one physical location to another without having to reinstall. This also avoids changing config files and registry changes. That said - the clean install instructions are here https://help.cakewalk.com/hc/en-us/articles/360034066393-Clean-Install-Cakewalk-by-BandLab Be aware that step 9 Deletes everything in the default VST folder "C:\Program Files\Cakewalk\Vstplugins" Whether you want to do this or not depends on how much third party stuff was installed there and how much you want to re-install. Third party re-install may be avoided by temporarily moving this folder before deleting the Cakewalk folder and putting it back after the deletion. Of course, if the area has been trashed by previous attempts to free space, it may be the case that everything needs to be reinstalled anyway. As far as installing old Cakewalk products see this thread (it links to others but I am try to save some typing).

Are you really stuck using MME. It is the worst performing option. In Win10, the WASAPI modes should work fine with the Realtek chip. Or you might want to try ASIO4All. At least until you can afford a purpose build audio interface for DAW use (then retire the USB microphone for one that works with the new audio interface).

Not sure if that is what the OP had in mind.

It depends on whether the instrument mix coming from the Kentron is all that is needed or if some additional processing is planned. The Kentron SD2 labels its two audio outputs as L and R so presumably the audio is in stereo. So, it does not matter how many channels of MIDI data are sent to the device the output is stereo. One stereo track is enough to capture the audio signal from the Kentron SD2. However, in order to keep the instruments separate, one would need to record each MIDI track one at a time and create separate audio tracks for each MIDI track.