msmcleod

If you need an effect post fader, either create a post fader send to an Aux track, or set the track output to an aux track, then continue the processing in the aux track. It's kind of an odd thing to do though. If you really need a fader in between two insert effects, put an empty FX chain in there.

The most common reason for this I've seen over the years is when your hardware output is not set to unity gain and/or you're routing directly to the hardware output rather than through a master bus. If the hardware output level is set to less than unity, your export will appear louder.

You'll need to convert it to a step sequencer clip first by right clicking it, and selecting "Convert MIDI Clip(s) to Step Sequencer "

Yes, this is the case. However you should be aware that sending multiple articulation switches in quick succession could confuse the VSTi (obviously dependent on the VSTi in question). Also, clicking a "trigger event" articulation will send the articulation out immediately, so if you are experiencing issues, you can use this method to force a particular articulation.

The way articulations chase is depends on the chase mode, the type of articulation (i.e. latched notes / duration based notes / cc ), and the implementation of the articulation within the VSTi itself. Duration based note articulations require the trigger note to be held down for the duration of the whole articulation, whereas latching key-switches generally require a short note to engage the articulation, and then they retain their state. Whether it's duration or latched is dictated by the VSTi, so it's up to you to make sure the articulation is set up to match that - if they're mismatched then the behaviour you describe (or similar) is likely to occur. CC articulations normally behave like latching key-switches - i.e. you set them, and they retain their state until something else changes them. The above is true for triggered event type articulations. Transform articulations always need their duration cover the notes you want to affect.

FWIW their tape emulator is one of the best I've heard, and also one of the cheapest on the market. Gain staging is vital with this one, but once you get it right the results are awesome.

That's half of the issue. The other half is that the tracks are not routed to the master bus. So: 1. Route your tracks to the master bus 2. Route your master bus to the Focusrite stereo output

How are you exporting it? If the source category is Tracks when exporting, then that might be the issue. Try using "Tracks Through Entire Mix" instead.

I'm almost certain sysex isn't supported for VST's in CbB - I know it doesn't support receiving it, so it's doubtful it'll support sending it either.

It depends on the synth. Some synths allow the same note to be triggered multiple times, in which case this technique won't work. For others, this will work fine.

Right click on the gain knob, and select "Remote Control" - you can assign a CC to control it there. You're correct however - you can't automate it using automation.

You've not said exactly which UAD plugin it is - so you'll need to check their website. If it is VST3 only though, there's nothing that will make it work in Sonar X1.

Two things to bear in mind: 1. Sonar X1 pre-dates the VST3 format. 2. A few years ago, Steinberg revoked the license for releasing new VST2 plugins - essentially forcing vendors to release VST3 only versions (unless a VST2 version of the plugin was already released before the license revocation). So if this plugin is a VST3 only plugin, it won't appear in Sonar X1.

Both are great sounding VSTi's and well worth the money.

I rarely use presets for VST's (vs VSTi's), but if I do have a particular one I like, I save it inside an FX chain. If you hold SHIFT when dragging from the browser to the FX bin, it automatically removes it from the FX chain with all the settings intact.

IIRC I had to re-install the VC++ redistributables after I last installed the AIR stuff - maybe not for the synths, but definitely for the effects stuff. You may also want to re-install the iLok software. Whoever wrote the original installers didn't think to check for newer versions of the components, and just blasted over it with the ancient stuff in their installer.

Most likely a corrupt ctrlsurface.dat. Before you launch Cakewalk, rename ctrlsurface.dat to ctrlsurface.old within %APPDATA%\Cakewalk\Cakewalk Core - then start Cakewalk. You'll most likely have to set up your control surfaces again within preferences.

There's also "Fit Improvisation". Basic usage: 1. Add a MIDI track, and arm it 2. Start recording and tap the same key for each beat through the song until the end 3. Select the MIDI clip you just recorded, then Process->Fit Improvisation. A tempo map will be created from what you recorded.

One other thing you could try... I've found that having lots of small MIDI clips on a track eats up way more CPU than a single MIDI clip on the track. If you've got lots of smallish MIDI clips, try consolidating them into one by selecting them and "Bounce to Clip(s)".

Linux is an OS. The advantages for hardware is that it's a powerful and very reliable OS that makes development much easier. The downside is the start-up time.

Personally, I think Linux as an operating system rocks. However, as a DAW platform (certainly on desktop), it has these two major issues: 1. Lack of audio driver support for professional interfaces 2. Lack of native Linux VST plugins (2) can be worked around by using a wrapper, but this increases CPU usage. I don't know Presonus's motives behind this move, but it may be to allow some of Studio One's features in a hardware product at some point (total speculation here!!). Korg already uses the Raspberry Pi as the basis for a lot of their hardware synths, so likewise, Presonus may be looking to re-use Studio One's technology in a linux-based hardware product at some point - maybe as part of their StudioLive series? Having the fully-fledged DAW out there in the wild being effectively tested by users may help to iron out issues before they commit to shipping it in a hardware form.

If you're likely to want to freeze/unfreeze regularly to edit parts, then I'd recommend using multiple instances of Kontakt. The CPU usage is around the same for a single instance/multiple instances (assuming you've got the multi-processor options set correctly within Kontakt). The amount of time to freeze everything is around the same, however with multiple instances you have the option of unfreezing one of the instances in isolation - with a single instance, it's all or nothing. Re-freezing that single instance in a multiple instance scenario is much quicker than re-freezing everything. However, if you don't regularly edit parts and just want to freeze to allow you continue with the rest of the composition, then a single instance might be more convenient as it's a single click. As an alternative to freezing, you could consider bouncing to a stereo track then archiving your original tracks. I use this method when I need to re-record something later on in the mixing process and I need latency as low as possible. If you've got lots of tracks that need freezing, this method is often much quicker as it only requires one mix-down, rather than one per track (or one per synth). Obviously when it comes to mix-down, you'll need to mute this track and freeze the individual tracks in order to get more granular control, but it can be useful while you're still editing/adding tracks to the project.

I've got the FaderPort 16, and @Jonathan Sasor has the FaderPort 8 - both work perfectly with CbB. The only exception is lack of access to the Synth Rack - unfortunately this feature was added after the FaderPorts were released, and because the FaderPort fakes multiple MCU button presses, it's not easy to work around (I did try, but it got messy). IMO this isn't a big deal, as most synths have too many parameters to make editing parameters feasible with a Mackie Device in any case. For the single fader version, you could try setting it to Universal Mode or Cubase Mode within the Mackie Control Surface dialog.

I've got the TC Helicon Voice Prism and also the VoiceWorks plus. Normally I don't use the harmony features, just the voice modelling, but it's just an extra connection. 1. First make sure Perform VK MIDI Out is checked in preferences. 2. Set the MIDI Output of your MIDI harmony control track to Perform VK MIDI Out. 3. Connect the L/R outputs of the TC Helicon to inputs 3/4 of the focusrite 4. Connect the 3/4 outputs of the Focusrite to the inputs of the TC Helicon 5. On your vocal track, insert a send to a new Aux Track - this is where your harmonies will live. Ensure Input Echo is enabled on the Aux track. 6. On the Aux track, insert an External Insert effect within the effects bin. 7. Set the Send of the External Insert to Focusrite Line Out 3/4 and the Return to Focusrite Line Input 3/4 - click the button under the Delay - once calculated, it should read something other than "*0ms, 0 samples". Once this is done you've got a couple options: 1. Let the TC Helicon do the processing in real time until final mixdown. In this scenario, just make sure input echo stays active on the Aux track. 2. Record the harmonies as audio If you've pre-recorded your main vocal, arm ONLY the Aux track, rewind to the beginning of the project (or where your vocals start), then record. If you've not recorded your main vocal yet, arm BOTH the Aux track and your main vocal, then record. Once the vocals are recorded, I normally copy the recorded audio to a new track, then archive the Aux track. If I need to re-record the harmonies, I unarchive, re-arm, and re-record.

There is no need to have a split instrument track - just select the region on the track (or tracks), and "Bounce to Track(s)":