msmcleod

Your VST DLL's are in C:\Program Files\VstPlugins\Toontrack.

The path you've added is C:\Program Files\toontrack.

The only path you need for it to be found is:  C:\Program Files\VstPlugins   - all subdirectories, including the toontrack subdirectory will be found automatically.

11 hours ago, sjoens said:

Very rare and maybe project specific.  Along with the uneven L&R mono track meter.

Most likely your meter settings are different between the track view and inspector view.  The meter settings can be set separately for Track View, Console View and Inspector.

Setting one to pre fader and the other to post fader will almost certainly give this result.

By default the MIDI input for the active track will be "Omni" - change the input MIDI on that track to ONLY your footpedal MIDI device.
 

Some general tips to avoid unexpected dropouts (in addition to the ones mentioned above):

Outside of Cakewalk:

1. Ensure all of your Cakewalk project directories, and any "content" directories (e.g. where plugins load their samples from) are excluded from virus checkers.
2. Turn off any cloud-sync applications/services while Cakewalk is running.
3. Make sure Windows is up to date before you run Cakewalk.  If Windows starts downloading/preparing updates in the background it'll kill your audio performance. It's not always obvious Windows is doing this, so I still get caught out by this one, wasting hours troubleshooting!  The best thing to do is check for updates and allow them to finish before you open Cakewalk.
4. If you're using a laptop, consider disabling your WiFi adapter - some are known to interfere with audio performance.  You can always turn it on momentarily to allow plugins to "phone home" if necessary.

Within your project:

1. Avoid using lookahead plugins (e.g. linear phase) during tracking.  Some linear phase plugins have an option to switch the linear phase part off - do this while tracking, and don't turn it back on until mixing time.
2. Consider sharing high CPU plugins such as reverbs by putting them on a bus
3. Some plugins, especially mastering plugins really eat up CPU.  Consider creating a new project for mastering with just the stereo mixdown in it, and only use the mastering plugins there rather than on your "mix" project.
4. Either commit changes regularly (i.e. bounce to clips) and/or freeze tracks when you think they're in a stable state.  If bouncing regularly, bounce without effects - but freeze with effects to free up resources.

On 12/25/2023 at 5:49 PM, Dave Maffris said:

Latest update, it’s working for a lot of things now. Still can’t get a track to be set for write automation, though. I have the Lexar template for Sonar, I can disable read automation globally, can’t set read or write per track and there is no button for global write automation, only read. Would be nice to be able to arm the automation from the Mackie control surface, perhaps I can map it manually,  I do t have a manual, but have looked online a bit.

Are you following the instructions in the Mackie Control Surface help?  You can get to it by pressing F1 from the dialog in the previous post.

The "Automating the Mackie Control" chapter covers all those scenarios, apart from global write automation enable - AFAIK the only way to do this is CTRL + A, then CTRL + click the enable write automation on one of the tracks, i.e. quick group the write enable.  You should be able to assign "Clear All Automation Write Enables" to one of the Mackie function keys.

10 minutes ago, Nio Sebez said:

I can't find that option. Is it on the screen I put?

 

It's here:

Check out MIDI Guitar 2 by Jam Origin

For it to work reliably, you'll need to set your sample rate to 48Khz and have an ASIO buffer of at least 128.

Expect some latency when recording - especially with lower notes.

Something to bear in mind: When you apply gain, you're applying gain to the clip. The meters however show the output of the track post fader.

So anything that is happening on the track - e.g: Track Input Gain, FX in the Pro Channel or FX Bin, or Volume / Volume automation will affect what you see in the meter.

Also, be clear what "Apply Effect->Gain"  by -6 is actually doing:  it's reducing the volume of the clip by -6db.   This is not the same as "setting" it to -6db.  The only time this would be the case, would be if the complete clip was at 0db.

The easiest way to do this is:

1. From the main menu:  Project -> Insert Time/Measures
2. Ensure "At Time" is 1:01:000, "Insert" is set to 2, and Measures  is checked - make sure all the other checkboxes under "Slide" are also checked.
3. Click OK.

6 hours ago, DeeringAmps said:

But in what order? The order they were installed? What is the criteria that CbB uses?

@norfolkmasteringdelete your aud.ini file. Then delete the drivers. Then reinstall the drivers in the order that you want them. Of course you may want to wait on msmcleod’s answer.  It may be that CbB sets up the list on some criteria that can’t be changed. 
There is no need to reinstall CbB. 

t

The order the driver presents them.

If you're using ASIO with ASIO drivers that support multiple interfaces, the order of installation is unlikely to be a factor.  The ASIO driver presents the ports in a particular order, and that's the order CbB uses.

As far as I know, the audio ports are always listed in driver order.  This is by design.

So the short answer is, no, you can't do this as it stands.

The only thing I can suggest is to use friendly names, and perhaps prefix those ports with an asterisk or some other character that might make it stand out more in the list.

24 minutes ago, rfssongs said:

3) Changing the Arranger so that when you Commit an arrangement that all arranger tracks are preserved.

I don't really get this one... surely once you've committed an arrangement, all of your existing sections are all in the wrong place?

Or rather than preserve, do you mean "arrange" the sections in the other arranger tracks too?

On 11/30/2023 at 2:33 AM, Herky Acuff said:

Ability to Increase the font size, even just a little?

I do have two large monitors, but still, that only helps a wee bit... I know I can go into Windows display settings and make everything bigger - but that brings other issues.

The new Sonar will fully support the scale size you set in Windows - so if you set scale to 125% or 150%, the fonts within Cakewalk will adjust accordingly.

11 hours ago, David Webb said:

The ability to use 3rd party console emulations and fx plugins as modules (like or in place of Pro Channel) would also be nice...

You can already do this using FX chains:

To create them:

My PC has been sluggish all day... then it became apparent why... the latest windows 2023/12 update had been doing it's thing in the background, and when I finished up for the day was telling me to restart to complete the update.

I can't count how many times this has caught me out.

Before troubleshooting all your audio settings / cakewalk config etc... check Windows update - it could be the cause of the slowdown and memory usage. 

Some day I'll remember my own advice myself!

On 12/10/2023 at 11:20 PM, FreeEarCandy said:

IMO it would have been a good idea to program the DAW to look in the global audio location specified in preference if the audio cannot be located in the per project location before asking the user where the files are. If they are also not found in the global audio file, then ask the user where the files are, saving  the user a step. But it is what it is.

I hope this clears up the confusion.  

 

This is exactly what happens.

You can set your global audio folder in Preferences under File->Audio Data.

On 12/11/2023 at 3:43 AM, Roger W said:

One roadblock that's prevented me from understanding how to set up multiple instruments in Kontakt7 was that my Cakewalk GUI setup did not display the MIDI Ch control that normally appears at the bottom of the horizontal track strip controls. If I understand you correctly, this is the "forced MIDI channel" control that you were referring to. Somehow my Cakewalk was not configured to show that.

I've now enabled it:

Up to that point, the only MIDI Ch settings I knew about were at the bottom of the Track strip in the Inspector and the Console:

So in your previous post, you said that if the forced MIDI Ch setting is changed after setting Kontakt up with the "Per-Output Track functionality", then problems arise. In other words, this a bug?

Anyway, after receiving your and others' advice here, I was doing OK when I set up one instance of Kontakt with multiple instruments. But later, when I decided to delete one instrument in the list and replace it with another, strange things happened.

I started with 5 instruments, and all worked well. I could record and play back with no difficulty.
Then I deleted one of the instruments.
I re-Batched. All instruments would sound when playing back the song. However, when I attempted to Solo some of the tracks, some would sound in Solo, while others would go dead.
Having discovered the new-to-me MIDI ch control, I attempted to get all the inputs and outputs synced up so playback would work  correctly, but I failed.

Was this a case of me running into the problem (bug?) that you described that results from forcing a channel?
If that is the case, how does one get it to work after deleting an instrument from the list ?
Or is the only solution to completely start over and set up the instruments again?

 

Roger

There is no clever interaction between Kontakt (or any other multi-timbral VSTi) and Cakewalk.  No special notifications are sent to Cakewalk when you delete a library from Kontakt, so Cakewalk has no way of knowing you've pulled the rug from under it.

Re-running the batch-script in Kontakt after deleting a library after all the tracks have been created in Cakewalk is a bad idea.  All the MIDI / audio port mapping is going to change.

If you do need to delete a library in Kontakt (unless it's the last one)
-   don't run the batch script
-   be prepared to manually set the MIDI / Audio channel outputs in both Cakewalk and Kontakt.

Note - it's fine to delete a library, then add a new one to the end and continue to use "Append Instrument Track" as long as the MIDI Channel / Audio Port continues to ascend.  Just make sure you don't change the MIDI channels / Audio ports for any existing libraries.

If deleting libraries is a common part of your workflow, consider using simple instrument tracks and having separate instances of Kontakt for each track.  For Kontakt at least, the difference in CPU/Memory usage is minimal.

You can't use the same MIDI port for both Mackie Control and normal MIDI input.  The Mackie Control takes sole ownership of the MIDI port.

Devices that support Mackie Control will expose extra ports specifically for that purpose.

FYI - some electronic pianos support more than one pedal value.  My old Yamaha PF80 used to send four different values of "on" depending on how far the pedal was pushed down. 

How synths / VSTi pianos react to that is up to how they are programmed - i.e. some will see anything other than zero as on, for others it'll be 64 and above, and others will support a range of values adjusting the sustain accordingly.

2 hours ago, John Vere said:

FYI. Cakewalk by Bandlab has just been discontinued so tutorials will be obsolete very soon. Sonar will be similar but the whole look will change so CbB videos will  look wrong to new users. 

Not yet it hasn't.  The download links for Cakewalk by BandLab on www.cakewalk.com are still active.

8 hours ago, carlne said:

Thanks 
Unfortunately, even after performing a clean install, the issue persists.

anyone has additional suggestions.

Even after renaming CW130Auto.dll in C:\Program Files\Cakewalk\Shared Utilities ?

1 hour ago, John Vere said:

@msmcleod I read the info about the VST and it only talks about how the hardware devices were multi timbral It doesn’t really ever say the VST is. 

I guess easy to test by inserting the VST and see if there’s options for separate output tracks. 

If not then no point in using it as multi instrument anyway. 

Just tried it - the Korg Triton VSTi is indeed mono-timbral.  Makes sense, as both the VSTi versions of the M1 & Wavestation are mono-timbral too.

9 hours ago, Byron Dickens said:

That is incorrect. Korg's Combination mode is NOT multitimbral. It is for combining patches together to do things like making splits and layers.

I'll need to check out the Triton's implementation, but certainly on the Korg X series, combinations could be multi-timbral - you'd simply set the MIDI channel of the different patches within the combi to different channels.  I use this technique on my X5D (live use)/ X5DR (studio), simply because there's 100 combi's that are easily saved and only one Multi... and the multi is a pain to set up.

[EDIT] - looks like Korg removed the ability to set different Combi part receive channels in the N series.  Pity... it was very useful for live use.

Right click on the curve and change it to a jump.

FYI - that particular video was a very early beta (from around the beginning of Sep).  We're still unsure as to how it got out.

It's really not representative of how Sonar is looking now - and work is still ongoing.