scook

"Downloads " points to your Documents\BandLab folder where sounds are download from BA and data exchange happens between BandLab and CbB. "System Folder" points to %appdata%\bandlab-assistant\Downloads where BA downloads itself and CbB updates.

AFAIK, all Cakewalk products may still be installed and activated, including products released after SONAR 8.5. Do you know differently?

Chances are you do not own any software you purchased. Most software companies sell licenses to use their software. They do not sell their software outright. BandLab purchased IP from Gibson. That IP included the code for SONAR and other Cakewalk products. BandLab developed a new product based on that code and provide licenses to use that software free of change.

The activation scheme is similar to last version of SONAR without the ability to activate offline. The thread containing Noel's quote posted above is still active.

It is not a conspiracy theory when one misquotes another users and then uses the misquote out of context.

Referring to the software in general as "leased" (or rented) is misleading as most users do not understand IT terminology (especially without providing the context in which the term was used) and would think the lease is a contract involving the exchange of money for goods and services. In this case lease refers to the time a token is valid for an authentication process. IOW, it is a technical term with a specific context and using the term outside of that context to describe the software is incorrect.

If no one provides a solution, I'll try to make some time later to take a look at this. In the mean time, for auto-panning take a look at Sonitus Surround.

Documentation usually takes a little longer to update

or click on What's New? in the CbB help menu

updated for 2019.01

updated for 2019.01

updated for 2019.01

I appreciate Azslow's effort but as an aging Tcler, it would get a lot more use by if it used a Tcl engine instead of Lua. Don't have anything against Lua, I know it is an extremely popular scripting language just have my own preferences. Now if Variorum want's a challenge, create an MFX wrapper for Tcl. One that takes advantage of the TK graphical toolkit.

Cakewalk will break up MIDI data entered in the PRV based on the space between notes. I have no idea where the clip was copied or how the tracks in the project are setup. There are a variety of video tutorials on basic operations. Most of them are for older Cakewalk products but a lot information still applies. Some tutorials on an older Cakewalk product targeted for beginners are here Here are more tutorials feature a product more like current Cakewalk product. Some users have created their own tutorials and there are quite a few on Youtube. Cakewalk has quite a learning curve and it may take some time and a little study to get up to speed.

What you want to do is export the clip. There are several ways to export clips. Drag and drop to a folder in Windows Explorer or a folder in the Media Browser (you may recall I provided a link to the Media browser in your other thread) may be your best options. Both do the same thing - create MIDI clips as files on the hard drive. As far as naming the clip, this can be done in clip properties in the inspector or once the file is created.

similar to https://discuss.cakewalk.com/index.php?/topic/767-midi-hearing-piano-and-drums-in-my-drum-track

Yes, ALT+click on the bus number will select the tracks sending to it. Sends have a pre/post fader switch. The output is post fader. Functionally a post fader send is the same as routing the output to a bus. Pre-fader sends are useful for sidechains. Sending tracks to another track using a patch point or an aux track can serve the same function as a bus except the it is located in the track area. Some like to see "buses" next to the tracks. Some prefer the have buses in the bus area.

Just installed. The original and MK II were installed and activated.

Bit depth does not matter. ASIO bit depth is disabled because the driver works at one value. This is normal. Given the sample rates are the same. this is not the problem. Are you using another product that uses an ASIO driver? If so, make sure its sample rate is set the same. Most Widows software does not use ASIO. In addition to DAWs, audio/video editing software typically can use ASIO.

No, the plug-ins included with CbB are listed here.

If this is the default Windows audio device make sure Windows and CbB are set to the same sample rate. Sample rate in Windows is set on the Advanced Tab in the Properties of the default Playback and Recording devices in the Sound control panel.

Thanks for this Eventide is one of the worst when it comes to letting users know about updates. This plug-in is free for Anthology X and XI users. Downloading Anthology XI 2.1.1 now.

For audio clips, you can change the pitch and tempo of the clip but you cannot go into the clip and change a major to a minor. At least not without additional software. This can be done with tools like Melodyne Editor and Studio (the lesser versions cannot work with polyphonic data) and in real time with products like Zynaptic Pitchmap. For this type of application MIDI is much more flexible.

Creating MIDI loops for chords will work. Use the Media Browser to store them in a folder in the MIDI Groove Clips (a predefined area in the Content Location menu) or anywhere you like. You can extend the Media Browser as you see fit, add folders, create new entries in the Content Location menu, drag and drop MIDI and audio clips from your project into folders.... Ultimately if you spend any amount of time in the Piano Roll View, you will get a keyboard controller for data entry. Does not have to be expensive, have a lot of keys or control options, Just something to bang in the notes. Of course, if you play keyboards the size and feel are issues. If not practically anything beats using a PC keyboard, mouse and copying loops when entering data in the PRV.

That is a good idea. Having Always Echo Current MIDI Track enabled is part of the problem. When this feature is enabled, any track that has its input set to None will have the input changed to Omni when the track has focus because input must be set to echo something. Having the track set to Omni will pick up all MIDI data at its input. This will include the controller and any plug-in with "Enable MIDI Output" selected. Any synth that can send/generate MIDI data will have "Enable MIDI Output" selected by default. "Enable MIDI Output" for a plug-in instance is available on the Soft Synth Options dialog when adding the plug-in and the VST2/3 drop down in the standard header (scroll down to be bottom of the page for the description and image) after the plug-in is added to the project. A good practice is only "Enable MIDI Output" when needed. This along with manual control of input echo should take care of unexpected MIDI data hitting instrument and MIDI track inputs.