scook

There is no point is capturing the whole screen when the error message is a tiny window in the middle of the screen. Just capture the error message and post it. With the error message in focus, ALT+Printscreen and paste into Paint or any image editor and save. The result looks something like this: or edit the full screen down to the error message before posting. It is much easier to read this way. Thanks. Also may want to use meaning subjects when posting. Instead of "Error Message" something like "Audio Setup Help needed" or "Audio Playback Decide Not Found" would make more sense. What audio interface, driver and drive mode (ASIO, WASAPI Shared/Exclusive, WDM, MME) are you using?

They do the same thing at different points in the signal flow. See the signal flow diagram The gain lowers the signal before the FX rack and ProChannel. The volume lowers the signal after the FX rack and ProChannel. That said, I usually leave the volume at unity and adjust the input gain or make the adjustments at the bus/track level before the signal even hits the master.

Yes, see page 3 of https://dl.two-notes.net/downloads/QSG_CABM_+.pdf The mini-USB port on the device is for the Control Unit software NOT for sending audio to the PC see page 2 and 4 of the same pdf.

It does not matter if adding a track template or adding the drum map to an existing project or project template. The Out Port assignments are all made following the same rule. Out Ports in a drum map are dynamically assigned to the track based on the MIDI output it is replacing. If there is no prior MIDI output assignment or the Out Port assignments become invalid, the DAW adjusts them so that the data has somewhere to go. IOW, the design requires a valid Out Port assignment, if possible, in drum maps used by a project. This is similar to the dynamic assignment of Omni when input echo is enabled on tracks that have no input assignment. Could there be a different way to handle this...yes. Is the current process inconsistent...no. That said, there most definitely is room for improvement in how MIDI data routes and PRV note pane labels are created, maintained and applied to projects. AFAIK, this has been on the to-do list for some time.

Have you tried changing the Polyphony setting the elements loaded by the programs? This is a per-program, per-element setting so make sure to change all the elements as needed

I doubt it. but support@cakewalk.com could supply the definitive answer. There was a time before Cakewalk was shutdown that they offered the unlock code for free. However, when the company went out of business, so did the offers for upgrading their products. As noted above, the current Cakewalk by BandLab does have the same integrated mp3 encoder used in the later versions of SONAR Platinum. The encoder like the DAW is free to use.

The Out Port assignments of a drum map are set using the existing output routing for the MIDI track. If there is no routing, the DAW makes the assignment, if possible, to insure the data does somewhere. The same thing happens if a routing becomes invalid (ex. the synth in the Out Port assignments is deleted). Fortunately, should the assignment need changing, it can be done with a few keystrokes SHIFT+select the range of mappings to change CTRL+SHIFT+click the drop down to reassign the selected ports Or, after adding the new synth delete the old drum map, make sure the track is routed to the new synth then add a new drum map.

Yes. However, they have big ramifications in the PRV when working on tracks use a drum map. Without one assigned, you don't get drum names in the Drum Pane. I'm advocating for a more intuitive connection between the two. For instance: you have an active MIDI track in the PRV. Right click in the blank space at the left of the Drum Pane and access the presets and DMM from there, and have the map assigned to the active track. Or maybe from the PRV Track List. Just somewhere the user can find it in the PRV. Personally, I think the drum pane is redundant. The functionality could be folded into the Note pane. But suggesting changes was not the point of my post. It was offered as an explanation of why instrument tracks appear as they do. I can understand the confusion WRT the MIDI output drop down. I suspect is it called a "New Drum Map" because it is a new object being added to the project. Drum maps like articulation maps are stored in the project. They may be created on the fly using the tools provided or loaded from files. Once loaded they are stored in the project and no longer have anything to do with the presets stored on disk.

I suspect they agree and it is on the list of things to do. It may seem strange that drum map presets and the Drum Map Manager are at Drum maps predate the track inspector and instrument tracks. Drum Maps are a MIDI track output setting. All MIDI tracks have access to drum map presets and the Drum Map Manager. The MIDI track output drop down assigns a new drum map preset to the track. The drum map manager is available in the output drop down to create a new drum map for the track, modify the existing drum map or save a new drum map preset. Instrument tracks are a simplified presentation of the MIDI track's input and an audio track's output. The MIDI track output and audio track input default to the synth used while creating the instrument track. These controls are not visible on the track view header strip. Since an Instrument track may need a drum map, the MIDI track output is exposed on the MIDI tabs of the track inspector. Without the track inspector, instrument tracks would need to be split to access the underlying MIDI output drop down.

There are a lot of ways to do this. Note (re)assignment may occur in the hardware or software. In software it may be done before the DAW in something like MIDI OX. Cakewalk has the ability to create translation tables in the Transpose MFX and Drum Map Manager. Superior Drummer has a tool built in to maintain its own tables separate from the DAW. First determine what data the hardware is sending. This may be done by recording a few notes in Cakewalk and looking at the data in the event list view.

Cakewalk includes seven sample project templates. ALL of them route everything (all other tracks and buses) through a master bus. This is the model I follow. The only deviation from this layout that I like to add is an additional bus between the master and the main hardware out. This lets me leave the master at unity and still have a way to make adjustments for monitoring purposes, such as a headphone EQ after the mix. Without routing everything through a single bus, it is very difficult to

Is it possible the plug-in was not installed. The Concrete Limiter was never bundled with SONAR, It has a separate installer. The installer should be in your old Cakewalk account.

I find it easier to set the Properties dropdown to ignore the data. But I cannot tell from the images supplied if the routing is correct. Also may want to insure the notes are in the playable range for SI-Bass. Most of the SI-Bass programs start at MIDI note 36.

It is kind of hard to follow this post The first image shows creating a new instance of a synth with a MIDI source track and the first synth audio output. The only parts needed for SI-Bass is the Audio Track because the MIDI track (Track 1) is going to be the MIDI Source. But the extra MIDI track while not needed does not cause any problems. The next image Shows activity on Track 1 with its output set to an instance of SI-Bass. If this is the only instance of SI-Bass in the project then I suspect the problem is data related and my first post about 3rd party MIDI data is needed. The last image shows Track 1 routed back to TTS-1.

Yes, there is that too. Did too fast a read of the OP. A complete routing includes the MIDI source track and a target audio track (or an instrument track with is a combination of both MIDI and audio tracks in a single track presentation). In this case, MIDI for the Bass already exists in its own track so all that is needed is the synth and an audio track. Adding the synth with the options shown in the image above will automatically add the requisite audio track properly routed to the synth. Then all that is needed to change the output on the Bass MIDI track to SI-Bass to complete the routing.

Common problem with Cakewalk sfz engine synths and 3rd party MIDI files. See this thread

When running Win10 and using the internal sound chip, start with the WASAPI driver modes using the preference screen in the last image. WASAPI Shared allows other software to use the audio chip while the DAW is running. Latency cannot be adjusted in WASAPI Shared mode. WASAPI Exclusive prevents other software from using the audio chip while the DAW is running. Latency is adjustable in this mode. After selecting the driver mode, make sure the devices are selected in Preferences > Devices. You may also want to deselect the MS GS Wavetable Synth in MIDI > Devices output and get used to the TTS-1 synth bundled with Cakewalk. With no MIDI output devices selected in preferences, opening a MIDI file automatically sets up TTS-1 to play the file.

It goes back well before CbB, at least through the X series (although from the looks of it probably back to SONAR 1).

TTS-1 is a GM synth and maps pitched instruments across all 128 MIDI notes. Most soft synths do not do this. It is not unusual for soft synth to restrict the playable range of the instrument. This is especially true for sample-based synths like the Studio Instrument Suite (note: SampleTank and Kontakt fall into this category too). SI-Bass note range is determined by the sfz files used in the programs. Most of them start at MIDI note 36. The range may be extending by modifying the sfz files. Extreme modification may require additional samples.

the path is set in preferences

The drum kit image like the keyboard at the bottom of some plug-in UIs is for audition purposes only. There are a variety of ways to add MIDI data to an instrument or MIDI track. Here is a post that may help There are several videos linked in this thread starting with that may help with basic MIDI concepts

Copying dlls is not a substitute for running the installer. Installers do a lot more than copy files, They setup the environment for the software. As a rule, if software comes with an installer, the best course of action is add the software to the PC using the manufacturer supplied installer. The Studio Instrument Suite will not run by simply copying the files whether they are in the exact location or not.

Old 32bit plug-ins should be avoided, There are plenty of free 64bit plug-ins. The cause of this problem is a combination of old plug-in design and security changes the OS. Installing these plug-ins in a folder that everyone may write into often solves the problem IOW, do not install these plug-in in "Program Files" or "Program Files (x86)." While adding these plug-ins to a folder that everyone can read and write may be the best solution, running the DAW as administrator will overcome the permissions problem too.

That's a start and suggests an issue with one or more plug-ins.

Check the Windows Event Log See if there are any dumps in %appdata%\Cakewalk\Cakewalk Core\MiniDumps Run the project in safe-mode (hold down the SHIFT key while loading the project). It may be enough to load in safe-mode. If not, it may be plug-in related. Safe-mode allows control over loading each plug-in instance.