-
Posts
6,762 -
Joined
-
Last visited
-
Days Won
33
Everything posted by msmcleod
-
For vocals, you probably want some compression, EQ and either delay or reverb (or both if you want!). Generic settings are unlikely to be of any use as every vocal is different. As far as stock plugins go, you have the choice of using the ProChannel compression / EQ / reverb, or using the Sonitus plugins in the FX rack. You can also use the Sonitus plugins in the ProChannel if you add them into an FX Chain. Here's a couple of guides that will help:
-
I had a bunch of issues with OneDrive - especially with multiple computers, I'd change something on one machine and only to find it'd be overwritten by a change on another. And of course there's the issue you've been having where OneDrive is hijacking files while they're in use. You've got two choices - either: 1. Disable OneDrive completely 2. Configure the directories you want OneDrive to backup so that it's not including your Cakewalk ones: https://support.microsoft.com/en-gb/office/choose-which-onedrive-folders-to-sync-to-your-computer-98b8b011-8b94-419b-aa95-a14ff2415e85 There's a third option, which I use with Mega, but it'll work with OneDrive too... I've got a batch file that copies my projects from my Cakewalk Projects folder to a backup folder, and it's the backup folder that gets sync'd to the cloud.
-
You could use an arranger track to mark each song as a separate arranger section, then export the arranger sections. Each arranger section will be exported as a separate file.
-
MCU Question Regarding EQ/Plugin Functions
msmcleod replied to minminmusic's topic in Cakewalk by BandLab
I'm using Cakewalk with a Mackie Control Universal (MCU), Mackie Control Extender (XT) and Mackie Control C4. I literally have zero problems and it works exactly as it should. I have control to all tracks / buses / mains, all plugins, and all synths in the synth rack. My main workflow is to use the MCU/XT for fader & pan controls, and the C4 for all plugin duties as it has 32 rotary controls. It's far more likely that the iCon isn't behaving like a real MCU than a Cakewalk issue. -
Several New Instrument and Plugin Updates no longer work as VST3s
msmcleod replied to Steve Patrick's topic in Cakewalk Sonar
Once you've copied it to the Shared Utilities folder, you may also need to unblock it - right click, properties then click "Unblock". -
-
Several New Instrument and Plugin Updates no longer work as VST3s
msmcleod replied to Steve Patrick's topic in Cakewalk Sonar
ok - it should say 6.0.7.0 , and the date should be 11th July 2024 (ignore my version number - it's one that was built locally). I've asked the guys to double check the installers. -
Several New Instrument and Plugin Updates no longer work as VST3s
msmcleod replied to Steve Patrick's topic in Cakewalk Sonar
What version is it showing? -
Several New Instrument and Plugin Updates no longer work as VST3s
msmcleod replied to Steve Patrick's topic in Cakewalk Sonar
All I can say is, it's working here. Are you definitely running the latest version of Cakewalk with the newest VST scanner? The error message would indicate it's looking for the VST in the wrong place - which was exactly the issue that the latest VST scanner fixes. FYI - the latest version of Cakewalk is 2024.07 build 108. You can check if you've got the latest version of VstScan.exe, by right clicking on it and choosing properties. The Details tab on the properties dialog will show you the version: -
See my post here:
-
Several New Instrument and Plugin Updates no longer work as VST3s
msmcleod replied to Steve Patrick's topic in Cakewalk Sonar
It looks like either your MODO BASS 2 install has not worked, or you failed to do a VST Scan after updating. The correct location for the latest MODO BASS 2 should be: C:\Program Files\Common Files\VST3\MODO BASS 2.vst3\Contents\x86_64-win\MODO BASS 2.vst3 Also, make sure you're running the very latest version of CbB / Sonar - earlier versions do not correctly recognise the new VST3 standard of having .vst3 in the directory name. -
Modo Bass v.2.0.3 working fine here with both Sonar and CbB.
-
In cakewalk , using MSuper looper with multiple output / input
msmcleod replied to Riccoboni's topic in Cakewalk by BandLab
It will be in Cakewalk Sonar only. I'm not sure about Cakewalk Next. -
Help! Some projects take a long time to close.
msmcleod replied to Scott Mallard's topic in Cakewalk Sonar
This is most likely due to plugins freeing up their memory before closing - like you say, the more memory that is being used, the longer this will take. VSTi's such as Kontakt have a "purge" option to remove all samples - you could try using this before closing. You could also try setting sample based synthesisers to load samples on demand and/or limit the amount of memory they can use for samples. Not only will this speed up the closing of projects, it may also speed up project load. The only downside is possible delays in loading the samples on first playback (unless you have very fast RAM / SSD), but it is only on first playback - subsequent plays should be fine. -
In cakewalk , using MSuper looper with multiple output / input
msmcleod replied to Riccoboni's topic in Cakewalk by BandLab
Ah... of course, yes - apologies. Unfortunately, Cakewalk doesn't support multi-output effects - only synths. I'm not sure if it's actually in our to do list yet, but it's been discussed as a future feature in Sonar. -
The RockGuy pack is awesome - models of the Rockman compressor/distortion and chorus/delay mini racks.
-
In cakewalk , using MSuper looper with multiple output / input
msmcleod replied to Riccoboni's topic in Cakewalk by BandLab
Use per-output instrument tracks. -
You could use a software loopback device such as loopBe or LoopMIDI to send to multiple plugins. Once installed, they look like hardware MIDI devices. The track sending the MIDI would send to "loopBe MIDI OUT #1". The receiving tracks would all have their input set to "loopBe MIDI IN #1".
-
Melodyne 5 with Cakewalk Sonar isn't smooth...
msmcleod replied to Jaime Ramírez's topic in Cakewalk Sonar
Not seeing any cursor difference between Sonar & CbB with Melodyne 5 here - mind you, I'm running at 1080P / 100%. -
You don't need to select the track, only focus it. Clicking anywhere in the track header apart from the track number (e.g. the track name) will set the track to be the active/focused track. Clicking the track number will select the track and all its events If you need to set the active track in the PRV, expand the PRV Track Pane by clicking the expand button in the top right hand corner of the PRV. You can then choose which tracks to edit directly from the PRV.
-
Have you changed CbB to run as Administrator? This would certainly explain the drag & drop issue, and could be contributing to the other issues.
-
When using the Mackie MCU protocol / Mackie Control Surface it needs exclusive access to the MIDI ports assigned to it, which means you can't use them for normal MIDI keyboard events. I would make no sense to allow both on the same MIDI device in any case, as button presses on the MCU are actually sent out as note events. Keyboards that support the MCU protocol normally expose more than one set of MIDI ports, one set for the keyboard and one for the MCU.
-
I had a look at the UF8 user guide, and it looks like it should work with CbB/Sonar as follows: Set the UF8 to Cubase using the MCU protocol Add the UF8 as a Mackie Control Surface Go to Utilities->Mackie Control 1 and set the protocol to "Cubase Mode"