msmcleod

You should see a progress bar on the arrangement section that is playing in the inspector.

This is how you should use Melodyne: More details here:

The VST3 standard allows for multiple MIDI event buses, each with 16 MIDI channels. Very few support it though, with the Vienna Symphonic Library (VSL) being a notable exception. I suspect Kontakt might support it once they move to VST3.

well spotted @scook

Claves?

I use ScreenToGif : https://www.screentogif.com/

You want to decide on a directory where your plugin dll's live, and copy your plugins into that directory. The most common ones are: 64 bit: C:\Program Files\VSTPlugins C:\Program Files\Steinberg\VSTPlugins 32 bit: C:\Program Files (x86)\VSTPlugins C:\Program Files (x86)\Steinberg\VSTPlugins If you're using very old 32 bit plugins, I'd recommend putting them somewhere else to avoid having to run as admin, e.g.: C:\32BitVST\ Next, make sure these paths are in your VST Scan Paths, then click the Scan button:

There's also the SQ8L, but it's 32 bit: https://www.kvraudio.com/product/sq8l_sq8x_by_siegfried_kullmann

There were no XT's for the HUI - it was a stand alone 8 track device. You can't use XT's when the main MCU is working in HUI mode. If you've got a real MCU, then run it in MCU mode.

I've used Linux in my professional career for nearly 30 years, and I can honestly say it's a FAR better OS than Windows for anything other than desktop apps. You can literally let a Linux server run for years without touching it. Security updates are only needed if they're directly connected to the internet, which a lot aren't as they're behind a proxy server, which is in turn firewalled. I'll never forget back in 2000 when Oracle released their own Linux version - it ran 9 times faster than Windows on the same hardware. Linux (well, Unix actually) got the security model right from the beginning. Windows has been trying to retrofit a security model on to an OS that was never designed for it for the past 20 years, whilst still trying to maintain backwards compatibility. Personally, I think given the circumstances they've done a great job, but it's a nightmare when it goes wrong and you've got to check various conflicting settings that are duplicated 4-5 times around the system. But the main stumbling point for running a DAW under Linux is the drivers. Audio interface manufacturers just don't have any incentive to write drivers for Linux. It's a catch 22 - no-one uses Linux because there's no drivers, and manufacturers won't write Linux drivers because not enough people use Linux. Exactly the same goes for plugins. Linux will never win the desktop war as it was never really meant for the home market. Ubuntu does a pretty good job, but you soon get caught up with having to deal with driver issues at some point.

This would need access to Cubase's internal code for dealing with the MCU, which I don't have - and even if I did, it would likely be a conflict of interest at least for me! The best you could hope for with the MCU route would be to get something that pretended it was an MCU, but even then you'd be limited to the first 8 vpots.

@u-man - I was going to suggest you tried using the C4 with the Commander Software, but I see this what you're already doing. Unless Steinberg implement something themselves (unlikely since the C4 is EoL), this is the only thing you really can do, unless you write something that emulates some other protocol such as the Akai Advance/VIP or Native Instruments Komplete Kontrol protocols.

These are common ones to add to your scan path: C:\Program Files\Steinberg\VSTPlugins C:\Program Files\VSTPlugins and if you've got any NI stuff (e.g. Kontakt) C:\Program Files\Native Instruments\VSTPlugins 64 bit

https://www.bandlab.com/products/cakewalk

This is just how the driver reports the names to Windows, which is displayed by Cakewalk. First make sure "Show Mono Outputs" is checked: Now when you pick an input / output device within a track you'll see something like the following for inputs: And something like this for outputs:

The CA-2A's frequency control is between the Limit/Compress and the Gain knob:

You should also make sure your running the correct drivers for your motherboard. For example, the network card / ATAPI drivers are showing high usage - this could be down to your PC using the Microsoft generic drivers rather than the Intel ones. You can download the drivers for your motherboard here (note there's no Win 10 drivers, but Win 8.1 drivers should work ok) https://support.hp.com/gb-en/drivers/selfservice/hp-compaq-elite-8300-small-form-factor-pc/5232852

This: CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 3392 MHz Measured CPU speed: 10 MHz (approx.) Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. First I'd make sure your power settings are set to "High Performance". I normally edit this plan and make sure nothing is set to go to sleep, e.g. USB, drives, screen etc, and make sure the CPU is set to 100% all the time. But also take LatencyMon's advice and disable Intel Speed Step in the BIOS.

Have you got a look-ahead plugin in that project (e.g. LP EQ or LP MB) ?

From what I remember, the C4 protocol is similar to the MCU protocol, but obviously different as it's a different device with different buttons, rotaries etc. Also, IIRC the C4 is pretty dumb - in other words the UI and behaviour is provided by the DAW integration and not internal to the C4. You should be able to get the technical docs from Mackie, but how you'd go about interfacing that with Cubase is another matter.

I'm pretty sure this is ok, but I'd have to try it out. All of my changes are now in Cakewalk's standard MackieControl control surfaces, so just add "Mackie Control C4" as your control surface within Preferences->Midi->Control Surfaces. Technically, you don't need to edit the MackieControl.ini as it will present each parameter on the C4 in the order they're defined in each plugin. However, you probably want to download my C4Mapper tool to arrange them into a more sensible order and/or edit the parameter names: http://msmcleod.co.uk/cakewalk/C4Mapper.zip You need to run this as admin for it to update MackieControl.ini Note that the plugin parameters are taken from %APPDATA%\Cakewalk\ACT Data\genericpluginparams.xml , which is only populated for each plugin when: You've added a control surface defined You've opened that plugin with a control surface defined So once you've added your C4, you may have to go through adding your plugins to an audio track for it to populate genericpluginparams.xml. Don't do too many plugins at once, and restart Cakewalk regularly during this process (genericpluginparams.xml gets written when Cakewalk closes). Holding down the Track button on the C4 will give you access to the menu, from which you can choose what to edit (e.g. track parameters, Eq, dynamics, synth rack etc).

MAutoPitch is free, and pretty good - it's part of their free fx bundle: https://www.meldaproduction.com/MFreeFXBundle

That's the BandLab website - not BandLab Assistant. You can download BandLab assistant here: https://www.bandlab.com/products/cakewalk

Thought I'd check - the apps tab definitely doesn't appear on the Mac version

If you've got the Melodyne installed, either the trial version (installed under "Addons" in BandLab Assistant) or any of the licensed versions, you can simply drag the audio track to the time ruler and it'll create a tempo map for you. If you'd prefer to use the Audio Snap Palette, the keyboard shortcut is now ALT + A.