scook

The setup in CbB is fairly easy. Add the plug-in to an audio track, enable MIDI Output in the drop down above the plug-in UI and the plug-in appears in instrument and MIDI track input drop downs. From there it works just like any MIDI controller. There were a couple of lengthy threads on the old forum about MIDI Guitar starting with when it was released as a beta through v2. How well the software tracks depends on the guitar and playing style. I doubt it will work well with an an acoustic guitar regardless of how the signal is captured but a little time with the demo should answer that question. There is no demo of the plug-in, the demo is the standalone version but that should be adequate to see if the product is for you. The standalone (and the plug-in for that matter) can host soft synths or send MIDI data to the DAW using a virtual MIDI cable.

The BandLab support email is support@bandlab.com The Cakewalk support email is support@cakewalk.com Currently the initial Cakewalk by BandLab download and activation relies on BandLab Assistant

The AUD.ini switch is documented here https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Troubleshooting.07.html The DirectShow engine (VideoEngine=0) allows moving the video on the timeline The Media Foundation Engine does not. But in order for CbB to use the DirectShow engine the video must be in a format the engine recognizes. If CbB cannot play a video with DirectShow it will automatically switch to the Media Foundation engine regardless of the AUD.ini setting. There are quite a few threads on the old forum about this. If you want to read about it use Google to search site:forum.cakewalk.com directshow noel and you will get several threads with Noel's comments about the MF and Directshow video engines.

Re: scripting AFAIK nothing has changed since http://forum.cakewalk.com/tm.aspx?m=3778540&p=3

Until additional MIDI routings are added... One solution currently available for driving multiple MIDI and instrument tracks requires creating a master instrument track using a plug-in capable of passing MIDI data through the plug-in. I use one of the Code FN42 plug-ins (MIDIChFilter, NoteMapper or Veloscaler) but it could be any "synth" plug-in capable of sending data. This "synth" appears in the input drop down of every other instrument and MIDI track in the project. The tracks using the master "synth" as their input need input echo enabled because there no data actually in their tracks. Like aux tracks, because this method relies on input echo instead of actually storing data in the track, to print the track requires recording the data in real time. Alternately one could copy the data from the "master" track into the track echoing the data then use the regular freeze and bounce functions.

If the drop downs are empty - hold down the SHIFT key while starting CbB. This should add any missing files to your CbB user directory including the metronome audio files.

The "duplicates" are threads created and used by BA. This is normal. support@bandlab.com may be able to help.

Selection after single split

Photoshop is fine for modifying images but I doubt you really want to resize images using any editor. The easiest way to update the background image (or any image) depends on whether the user theme is based on Mercury or Tungsten. If it is based on Mercury, deleting the existing image will automatically pick up the new Mercury image. If it is based on Tungsten, open Tungsten in another instance of the Theme Editor, copy and paste the Tungsten image into the new theme. Delete, Copy and Paste are on the context menu shown when right-clicking an image. This will insure the size of the image is exactly what CbB expects. Then modify the texture or color as desired in Photoshop. The Theme Edit lets you add an image editor using the Setup Wizard in the Tools tab.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=WindowManagement.09.html#1260131

Absolutely, as I alluded to and @Colin Nicholls clarified, the objectionable part of the UI you mention is part of a Microsoft library. The theme in the OP, on the other hand, is a functional problem. Parts of the program don't work with that old user theme.

You may want to update the theme. It appears seriously out of date. See and for the parts the need to be updated for the theme to function properly. Of course none of the updates are going to address the MS libraries you are asking to be updated.

May help to know which plug-in(s) are creating the sounds. This could be the result of volume automation. Opening automation lanes in audio and instrument tracks automatically create volume automation. If a track has volume automation the envelope is visible in the main track, there is an indication next to the Volume label in the track header and the automation lane button may be a different color. To get rid of unwanted automation either use the edit filter (the drop down under the track name in the track view) to select the automation or open the automation lanes then right-click on the envelope and using the context menu select "Delete Envelope"

A fine idea that may be outside their budget but that should not stop any enterprising individuals from setting up their own share(s), even if just as a temporary measure until the resources get allocated to the project. CAL has been deprecated for almost 21 years. Don't expect much from Band:Lab on this subject. AFAIK Sitata has no need for articulation maps and the most recent release makes drum maps redundant by implementing the VST2.1 effGetMidiKeyName opcode. Something every drum synth developer needs to do.

Double check the zero controllers setting. This is a per-project setting. Make sure to update the project templates in order that new project have the preferred settings. Also review the data in the Event List view.

Reset is the button called "Reimposta..." above and to the right of the red circle The item in the red circle hides VST 2 plug-ins when a plug-in manufacturer has a VST3 plug-in and the appropriate code is added to the plug-ins indicating it may replace the VST2 plug-in. Deselecting this option shows both VST2 and VST3 plug-ins. At least, that is the intend of the feature. When running a VST reset it is usually a good idea to enable "Generate Scan Log" (Genera log dopo la ricerca). Then if the problem continues, the log will be available.

I have neither plug-in installed. Do the plug-ins appear in the "Sort by" layouts? The "Sort by Category", "Sort by Manufacturer" and "Sort by Type" are built on-the-fly from all available plug-ins. If not, consider running a VST reset from preferences. Do not use the plug-in manager for scanning. The plug-in manager should be used for managing the Exclude list and building custom layouts only.

What suggestion? In this thread?

https://help.cakewalk.com/hc/en-us/articles/360021858293-What-happened-to-Cakewalk-SONAR-What-happens-to-everything-I-paid-for-

If the plug-in plays a MIDI clip then it is routed correctly. The next things to establish are the controller is setup as a MIDI input device in the DAW and the instrument/MIDI track input drop down is set to the controller.

This forum was created for Cakewalk by BandLab the PC-based DAW. The web-based DAW called BandLab is a different product. I do not know of a forum dedicated to this DAW but there is a support team at BandLab. Their address is support@bandlab.com. I believe there is also a Facebook group.

When adding a synth to Cakewalk make sure to use either an instrument track or an audio+MIDI track pair. Maybe reviewing the MIDI tutorials in this video series will help.

Or have the DAW automatically pin them for you. It depends on the Recycle Plug-in Windows settings.

SoundForge Pro occasionally (every year or so) goes on sale for as little as $20 as part of a deal on Humble Bundle. The sales show up in the deals area of this forum. Usually a release behind current but a great deal. Much more than the basic version of SoundForge. There are several free editors that easily handle the basics.

IDK, I have not bothered with more than one PC at a time.