msmcleod

Can you give more detailed steps? If you can let me know which instrument you tried to insert, and a screen shot of the insert synth dialog that would be great.

It seems to be working fine for me with the Insert Soft Synth dialog. Did you have the "Max Available" checkbox checked? This will grey out the number you typed and create tracks for all available outputs.

No, the Gain control is used to control the signal from the clip going to the fx bin /pro-channel (depending on pre/post pro-channel setting). The gain of the recorded signal is controlled by your audio interface. So when recording, the signal goes as follows: Audio Hardware Gain -> ASIO Input -> recorded clip -> Gain Control -> fx / pro-channel -> Volume The main use of the track gain control is to gain-stage plugin input signal.

This is how I do it: Just remember to do the batch function again within Kontakt after adding any new instruments.

If you're using external sound devices, as opposed to soft synths, you actually have to record the audio of your sound modules in to Cakewalk. I only use VSTi's now, but when I exclusively used sound modules, this is what I did: 1. Connect the audio output of your sound module to an audio input on your audio interface. If like me you had all your synths going through a mixer, solo the channel that that sound module is on. 2. Insert an audio track, set it's audio input to the stereo input on your interface you've connected your sound device to (for the Scarlett, it'll be "Stereo Focusrite USB ASIO Input 1" for inputs 1&2, "Stereo Focusrite USB ASIO Input 3" for inputs 3&4, "Stereo Focusrite USB ASIO Input 5" for inputs 5&6 etc..) 4. Solo your MIDI track, and arm your audio track for record. 5. Rewind to the beginning and start recording. You'll need to do this for each track in turn. When you're done, you can either use the export module, or you can just drag the audio clip from Cakewalk into a folder.

FYI - in the 2020.08 release there's no need to split/re-combine audio & MIDI tracks as instrument tracks can now show both audio and MIDI automation.

IIRC you have to save your project as a standard cwp file before saving as a bundle. This is because all a bundle is, is your project directory zipped up into a single file... if the project doesn't exist, it doesn't know what to zip up.

Have you got CC 64 set as your "SHIFT" key within Keyboard Shortcuts?

This is a known issue with 2020.08 The workaround for the moment is to go into Preferences->Control Surfaces, change one of the MIDI ports (e.g. MIDI IN) and change it back again.

This should be on by default for ALL plugins. If it's not, expect timing issues all over the place.

Personally, I've found JBridge to cope with 32 bit plugins far better than BitBridge... and Cakewalk has native support for JBridge if you have it installed, so you don't have to use JBridger to create separate bridged DLL's. BitBridge is a very basic bridge. It literally wraps up the 32bit DLL and passes all VST API calls from CbB to the plugin DLL. JBridge does the same, but has a bunch more options to cope with the fact that the plugin may have been designed for a much earlier version of windows, or is not completely adhering to the VST spec. You can tweak it on a per-plugin basis.

As a general rule, MME is by far the worst performer out of all of the audio driver models. It's only really there for backwards compatibility with interfaces that have no other option. The drivers to use (in order of preference / performance ) are: ASIO WASPI Exclusive WASPI Shared WDM MME ASIO is generally the best choice, unless your interface hasn't got a native ASIO driver from the manufacturers. ASIO4ALL for example is not a real ASIO driver - it's just a wrapper around the WDM driver. So in most cases, WASAPI will be a better choice than ASIO4ALL. [Edit] - There are some exceptions: Realtek onboard devices have a really buggy ASIO driver, so WASAPI is best here. Some really high end audio interfaces have bad WDM/WASAPI support, so you really need to use their ASIO driver.

ACT only works one way - i.e. it only processes MIDI data from a device. It doesn't send any information back.

Just so you know, there's an issue with the saving of control surface presets in the 2020.08 release. The workaround is: After changing any presets etc a control surface dialog, go to Preferences->Control Surfaces and change one of the MIDI ports... then change it back. This will force a save of everything.

wow - there's a blast from the past. I got the book & DVD a LONG time ago. It's very good. One thing to note tho... if you didn't hate Thomas Dolby's "Blinded by Science" before watching the DVD, you certainly will afterwards....

I choose LibreOffice because it's the original OpenOffice devs working on it. Like most things that were bought up by Oracle, the devs left and started their own fork (like MySQL vs MariaDB). In saying that, OpenOffice is now part of the Apache foundation, so maybe things are different now. By UNIX, I guess you mean Linux.... there's a reason for the hoards of distributions. Linux is the base operating system for SO many devices, it's unreal. The point is, you can fork the main repo and take out or add what you want to suit your application (which in many cases may be a hardware device).

Some process has the file locked. The most common reason I've found for this is virus checkers/cloud sync programs (e.g. OneDrive). Make sure your Cakewalk project files (and your audio folders) are excluded from such programs. They will cause no end of issues if they lock files while Cakewalk is trying to access them.

Assuming any audio files associated with the .wrk file are in your Global Audio path, CbB should be able to open .wrk files without issue. If you're wanting to "upgrade" your .wrk files though, the best way to do this is: 1. Create a new project based on the "Basic" template 2. Drag the .wrk file into Cakewalk from the media browser. That way, you get a master/preview/metronome bus as well as all the pro channels enabled on the tracks.

I'm using Focusrite's as well, and I could take advantage of this too... the main reason I don't is that I tend to use ASIO at relatively low volumes. If I had YouTube running it would blast through my monitors at a crazy level.

I pretty much stick to ASIO, but have both my on-board realtek device and my audio interface going through a Mackie Big Knob passive which has an A/B switch. I never thought a glorified volume knob would be so useful, but it is!

I've had this issue twice. The first time was actually a bad RAM stick, but the second time was just some dirt or corrosion on the DRAM connectors. WD40 and a cloth sorted it out.

Go into Cakewalk Plugin Manager, and find the plugin within VST effects. Then click on Plugin Properties and make sure "Configure as synth" is checked: You'll need to come out of plugin manager completely and re-open it for it to pick up this change.

Just my personal take on this.... but I think its also worth noting that BandLab is a Singapore based company. It's very common for US companies (and a lot of UK/EU companies, although to a lesser extent) to insist that every product or project team is financially sustainable. My previous gig ( a US company) insisted that every product had to make at least $1M per developer working on it... so if it made less than that, either the team would be cut or the product canned. The main problem with this approach, is that some products are actually worth having even if they lose money as they act as advertisement, industry prestige, or an entry point to other more profitable products. In a similar vein, I'm sure many of us have worked for companies who have clients that use up so much of the company's resources, you wonder how they can make any money from them... but the point is, having that client attracts other more profitable ones. Those high profile but unprofitable products or clients may not make you money, but they do add value to the brand... which in turn makes money. BandLab has a family of brands comprising of software (offline & online), audio interfaces, guitar pedals, guitars, a huge music retail chain and some big names in publishing. The brands that make money pay for the ones that don't. Having a fully featured professional DAW such as Cakewalk as part of its portfolio not only adds value to the BandLab brand, it also provides a stepping stone for BandLab's online DAW users to move on to the next step. Personally I see it as no different from what a lot of us hobbyists or semi-pros do... I mean we may do paid music work, but I'll bet a lot of us spend more on gear than we earn from it. So how can we continue? Well, the day job subsidises it.

It looks like a bug in the handling ACT Control surface from within Cakewalk itself. I don't think this is due to the recent changes - it's an older issue, but it has a knock on effect on other control surfaces saving when the ACT Control surface is in your Control Surface list.

Interesting.... we did have an issue with it treating surfaces with a missing MIDI Out as disabled.... maybe that's the key. @azslow3 - can you confirm if the presets are saved if the controller has a MIDI out port set?