msmcleod

At present there are three options: 1. Export as OMF - assuming the target DAW supports this (note you'll have to do MIDI separately); or 2. Export your tracks individually as .WAV files / .MID files and import them into the other DAW. 3. Export to a BandLab project - you can then manipulate it in BandLab and export the tracks as you see fit (there's a 12 track limit though). Personally, at the moment, I'd say that option 2 is by far the most universal option. Export to AAF is on the future road map, but your MIDI tracks will still have to be done separately even when this feature is available. Of course if you're exporting to Reaper, then @azslow3 's ReaCWP is an excellent tool: http://www.azslow.com/index.php/board,13.0.html. It covers far more than just audio/midi - it also does plugins & envelopes.

@dahjah - The alt behaviour for scissors depends on where the mouse cursor is relative to the clip. If the mouse cursor is in the the bottom half of the clip, only the current clip is split; if it's in the top half, then all the tracks in the selection are split:

It might also be worth checking these values in your configuration:

I find the phone camera so useful when doing electronics repairs - the writing on IC's nowadays is so small, it's impossible to read without taking a picture & zooming in.

One solution for this may be to define a screenset which has the control bar, inspector & browser collapsed - that way you can flip between the two using keys 1 & 2. To do this: Press "2" to activate screenset 2. Maximise the height of the console view Press "C" to collapse the control bar Press "1" to go back to your first screen set Now pressing "2" will show the console view in full; pressing "1" will go back to your standard screenset. [Edit] - just realised, control bar state isn't saved as part of the screenset.... you can always use "C" to toggle it on/off.

AFAIK, if you're still in the trial period of Melodyne, you'll get full polyphonic conversion as it's effectively a trial version of the Studio edition. It reverts back to monophonic when your trial period is ended. Both Melodyne Editor & Studio editions support polyphonic conversion.

I'm pretty sure it was a rule - the only entries in the moderator history was by me, approving the post.

Looks like the link posting rules have become a bit more strict, requiring moderator intervention... I've unhidden the topic.

As an alternative.... https://www.arturia.com/products/software-effects/preamps-bundle/trida-pre it's €49 until March 4th...

@_Will_ - unfortunately this didn't quite make the 2020.01 hotfix, but it'll definitely be in the next release.

Are you sure the data wasn't just in another lane? MIDI tracks, unlike audio tracks, don't "merge" the events from multiple lanes in their comp track. Why it decided to paste it into another lane is another question though... although it could be related to paste special settings.

FWIW that's the way I've always done it too. I write the music in Cakewalk, then print out the notation if someone needs it.

Even though the waveform is blank, does it actually play back the audio? If the audio plays back ok, it may be that your picture folder is full. It's pretty safe to delete the files in the picture folder, as they'll be re-created when you next open a project. Here's a thread on the old forum that goes into more detail: http://forum.cakewalk.com/Picture-Cache-HUGE-m2217459.aspx

Probably not, according to the Presonus website: https://support.presonus.com/hc/en-us/articles/210046773-Can-I-use-my-StudioLive-as-a-control-surface- Although, as you say, they've added Logic & ProTools support. I suggest contacting PreSonus and asking them whether it supports a Mackie DAW mode.

I've just tried this and it worked for me. Does archiving each track individually work? My guess is there's a plugin on one of the tracks that doesn't like being archived, but we'd need to have access to the project to be sure. The best thing is to upload your project somewhere and raise a ticket with support: support@cakewalk.com

Yup, I pretty much did the same. My main interface is a 1st gen Focusrite 18i20, which I bought new, but I've got the older Mackie MCU + XT + C4. Apart from the looks, the only difference between the old MCU and the MCU Pro is: The older MCU uses P&G Faders powered by string (really - it's like a fishing rod mechanism inside); the MCU Pro uses belt driven Alps faders. The older MCU requires a MIDI interface, whereas the MCU pro has a USB MIDI interface with 2 x extra ports to for expanders (e.g. 2 x XT's or XT + C4 ) It's worth mentioning that if you do go for the older MCU, the cheap USB "cable" MIDI interfaces will not work. You'll need a decent branded interface such as M-Audio or MidiFace. Oh, and if you see spare faders for them buy them - they're easy to replace, but very hard to come by nowadays. Finally, be aware that the MCU / MCU Pro are large units - they WILL take up a lot of desk space. If this is a concern, take a look at the FaderPort or the X-Touch.

I would recommend adding SynthMaster & Omnisphere to your list, especially with regard to your interest in 70's prog (synthmaster) and soundscapes (omnisphere).

The Mackie ProFX is limited to 2 inputs/ 4 outputs at the Cakewalk side, and there's no remote control of Cakewalk via it's faders - it's literally an analog mixer with its stereo out routed to USB. The RME Fireface UFX II on the other hand, is (in my opinion anyhow) one of the best (if not the best) audio interface on the market, and the Mackie MCU is the most comprehensive DAW controller for Cakewalk available. The two options you've given are pretty much the extremes of the home-studio market here... there are plenty of other options in between, e.g.: If you want an analog mixer, I'd take a look at the Tascam Model 12, 16 or 24 : You get a full analog mixer, plus multiple audio channels (e.g. the Model 24 is 24 in/24 out over USB 2.0) - but no DAW control. If you don't need the 30 inputs/outputs of the UFX II, take a look at the Focusrite, Tascam, MOTU range of interfaces which range from 2 in/out to 20 in/18 out. There's no doubt the MCU Pro is the most comprehensive controller, however there are other options: Non-motorized faders: Look at the Korg nanoKONTROL Studio Motorized faders: - Presonus FaderPort 8/16 (the 16 has almost the same physical footprint as the MCU Pro, but with twice the number of faders) - Behringer X-Touch

For Kontakt, the process is a little more involved. The easiest way to do this is to create a default output profile for the VST Plugin instance of Kontakt: You may also want to enable multi-core support for Kontakt. This ensures that Kontakt's CPU usage is spread across all your CPU cores: To assign an instrument to an output:

For Omnipshere, the procedure is as follows:

The 2020.01 release saw the introduction of Per-Output Instrument Tracks, which allows you to create multiple Simple Instrument Tracks routed to a single instance of a VSTi. In order to use this feature however, you must map the MIDI channels within your VSTi to the relevant output. This must be done inside the VSTi itself, and each VSTi handles this differently. For example, to do this in TTS-1:

Try using WASAPI instead of ASIO within CbB's audio preferences.

WASAPI is built in to Windows. You shouldn't need to install any drivers, just swap to WASAPI within audio preferences within CbB.

@Robert Bone - The fact that plugins aren't picked up within C:\Program Files (x86)\ by Cakewalk Plugin Manager, but they are within SONAR to me sounds like it could a permissions issue (possibly caused by a Windows update?). If you run the scan from directly within CbB's Preferences->VST Settings does it pick it up? Follow-up: - I've just tried scanning a 32 bit plugin in C:\Program Files (x86)\vstplugins using Cakewalk Plugin Manager. It appeared to scan it, but was no where to be found. I then removed the plugin, and re-scanned using CbB's Preferences page. I put the plugin back into C:\Program Files (x86)\vstplugins, and scanned again using CbB's Preferences page. This time it was picked up. So it does look like there might be an issue with Plugin Manager and scanning C:\Program Files (x86)\ (however, I did notice I had other files in my directory which could be causing the issue). My recommendation would be to always use CbB's Preferences page to do your scans, if nothing else but for the fact it does a sandbox scan which prevents the scan from aborting should it encounter an issue - but at least do it this way for the meantime until the problem within Cakewalk Plugin Manager is identified/resolved.