msmcleod

Good suggestion for quantise... in the meantime, you can use "Apply Trimming" on the clip after quantising. Your second point, use CTRL + D to duplicate. This does exactly what you're wanting.

I suspect your ASIO output issue is not to do with Cakewalk, but instead a routing setup with your Mixer. I've not used the A&H QU16 specifically, but normally mixers of this type let you decide whether each channel is coming from the audio inputs, or from USB. You need to designate a stereo pair on the mixer that is fed from USB, and ensure that it is "hearing" the output from Cakewalk via the ASIO driver.

It's not ASIO not being in focus, it's CAKEWALK not being in focus. So when this setting is checked, if you bring another application to the foreground, Cakewalk will stop its audio engine. If you need Cakewalk to play while it's in the background, then don't use this setting. What I don't understand is why you need WDM for playback. Cakewalk will NOT be using WDM for playback, it'll be using ASIO. The A&H ASIO Driver supports 32 channels of audio via ASIO in BOTH directions. If you're playing back using another Windows application, then it may be using WDM. What I do personally, is use my onboard sound card for Windows (a Realtek device), and run both my audio interface and onboard sound-card through a mixer (actually a Mackie Big Knob) - this way I can easily switch between the two.

It sounds like the A&H drivers don't support access via ASIO & WDM at the same time. Cakewalk will be using ASIO for both recording & playback, whereas (as you've pointed out) Windows uses WDM/WASAPI. If you check "Suspend Audio Engine When Cakewalk Is Not in Focus" within Preferences->Audio->Playback and Recording, then Cakewalk will release the ASIO driver while it is not in focus. This will allow Windows to use the WDM driver.

This definitely shouldn't be happening. To give you an idea of what is happening in the freeze: 1. Instrument tracks are made up of two tracks: an audio track, and a MIDI track. 2. When the track is frozen, all that happens is the bounced down audio is stored against the audio track, and the MIDI track hidden. 3. When you unfreeze, the audio is deleted from the audio track - the MIDI track data should remain unchanged. Can you confirm that the MIDI data has actually disappeared, or that it's a cropping issue? In other words, if you extend the beginning of the clip back from bar 13 to 1 is the MIDI data restored? [Edit] - Can you also confirm which version of CbB was used (a) to Freeze the track, and (b) to Unfreeze the track.

I've found & fixed the issue. It's down to a combination of per output instrument tracks, auto-track zoom & showing the synth properties. If either of those were off, it would work fine. The fix will be in the next release.

Essentially everything except Per Output Instrument Tracks will ignore the track limit. In the next version, these will be greyed out if you pick any other option.

@Vernon Barnes - looks like an AutoZoom issue. Do you have this switched on? If you switch it off, does it insert the tracks successfully?

@scook - I took a look at the dump, and I've fixed that problem... basically now you must select one or the other, and the issue it caused (a divide by zero error) has also been fixed. @Vernon Barnes - thank's for the info... I'll look into it further. The options on the dialog work fine for me with Kontakt, so there must be something else happening here.

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 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.