Panu Pentikäinen

Yes, Duckbar adds solo button to the QuadEQ as well as the Reset button.

My 0,05 €: Cakewalk interface beats Studio One. S1 font size is too small (not tweakable?) and colors can't be adjusted enough to suit my taste (more contrast, please). S1 is modern and in many ways it operates smoother than CbB but its interface is too ugly and small printed. Skylight interface is OK. Freely scalable interface would be cool but I doubt it would be too expensive project to carry out for Cakewalk at this time.

I did some maintenance work for Duckbar to make it CbB compatible. I just leave this here... Many of the new forum users don't know what Duckbar is and the rest have forgotten... In short, Duckbar is an utility which improves missing features to CbB/SONAR and improves some others. Now there is official Theme Editor available but Duckbar offers an alternative, more powerful way to batch handle resources. There is also powerful Color Scheme editor (found in Preferences / Colors). Other features include new buttons added to Piano Roll, Staff View, QuadEQ (for example "Reset settings") etc. Duckbar also includes improved versions of internal metronome sounds and it stores the last fade curve settings globally (Cakewalk does this per project basis only). Want to see if automatic crossfades are enabled? Duckbar adds button in Track View to show and toggle that, too. Tools menu editor is included, too - of course. And instantly ready-to-use Tap Tempo with delay times calculator. Duckbar also warns if waveform cache is getting full and it can delete all but the newest cache files. Of course Duckbar also has its built-in scripting language but that's another story... Q: Download link? Availability? ETA? A: Not available yet. Not available yet. 2019.

I have 28 inputs and outputs but they have to be named only once and after that it would always be easier to see input (and output) channels in the TV. But like I said: Stero track naming in its current state is not good because only the first letter of the actual name is shown. However, I won't hold by breath while waiting for the improvement; I sent feature request of this very same thing 7-8 years ago but nothing happened... Maybe this time?

In track view it's called "Insert Instrument" but in Synth rack it's "Insert Synth". Insert Instrument opens "Add track" window while Insert Synth opens directly list of available synths.

In track view there is very little room for the input channel text. Example: for a left (and right) channel, only 6 characters are shown of the channel name while the rest are reserved for the word "Left". Stereo channels: Only the first (!) letter of the channel name is shown. Suggestions: A) Replace words Left, Right and Stereo with L, R and St (or stereo symbol). B) Increase width of the input channel widget. There is much more screen estate on modern displays than decade or two ago when this widget was designed. C) Enable friendly names for mono input channels.

Superb tip! That helped! THANK YOU!!!

I've got a little problem... Browser window does not appear anymore on the screen, not with keyboard shortcut nor from the main menu. There are two displays in the system. Recently I changed the other to be the primary display. Now the Browser window may be located outside the visible area. Does somebody know where in the registry Cakewalk stores last window positions?

When ripple editing, remember that clips locked in time will are not affected by ripple editing. This should be obvious but at least I forget to unlock all clips every now and then before ripple editing only to find later that I have messed the project. This happens more often if the project is long there are locked clips outside the visible area of the track view.

@Noel BorthwickI sent it to Jon!

Well, Ripple Edit caused unexpected result: it crashed Cakewalk. I forgot to turn off Ripple Edit All and deleted some audio clips during playback. Then I noticed that too many clips were deleted (before remembering it was on). I hit Ctrl-Z to undo and deleted clip again. This time Cakewalk crashed. Advice: do not ripple edit when playback is on!

CbB version 2019.03: Ripple Edit moves automation and tempo map, too.

According to CbB documentation: "Caution: Ripple editing can cause unexpected results when editing multiple tracks, so use caution and check the results before you proceed with additional edits." Source: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.22.html Recently I have used ripple editing to edit 4 track podcasts but not so much to cut sections of bigger projects. Everyting seems to work perfectly but the documentation hints of possible problems. What's your experience with ripple editing? Can you trust it without checking results and making backups every time? How does it deal with varying time signatures and tempo maps, stretched clips, audiosnap enabled tracks, frozen tracks etc.?

I have only m.2 and SSD drives on my new DAW. There's no way ever going back to HDDs! Disks are even faster than what CbB and plugins can utilize.

Noel's explanation makes sense and it confirms there's nothing fundamentally wrong on my system settings. Render times are not even a real problem. On my new system Cakewalk renders 4 min song made of 50+ audio tracks with 50+ FX in 30 seconds. Finally it feels like being in the future.

Are you sure? Disk usage shows barely 3%. Audio files are on SSDs.

Disabling plug-ins (additive): Disable Waves CLADrums - 41% Disable ValhallaPlate => CPU usage 41% Disable 5 FabFilter Pro-R instances => 41-42% Disable FabFilter Pro-MB => 42% Disable FabFilter Pro-L2 => 46% Disable three more FabFilter Pro-L2 => 51-52% Disable 5 FabFilter-Q3 => 48-53% Disable FabFilter Pro-DS => 47% Disable one more FabFilter Pro-R => 46% Disable FabFilter Pro-L2, DS, Q3, Q3, C2, C2, Q2, Q3, Q3, Q3 => 54% Disable FabFilter Pro-C2, Sonitus:Delay, Sonitus:Gate, Sonitus:Compressor, Q2, C2, C2, => 63% Disable Sonitus:Gate, Sonitus:Gate, Q3, Cakewalk Channel Tools, Cakewalk Channel Tools, Q2, C2, Q3 => 57% Conclusion: Plug-ins are the throttleneck, especially the old Sonitus DirectX plugins [in thist very project at least]. Conclusion 2: I'm a big fan of FabFilter plug-ins! L2, DS, Q3, C2 and Pro-R are my goto tools now.

I tested some settings to see if I could increase CPU utilization. - Cakewalk always restarted after making changes to settings. - Same project in every test. BounceBufSizeMsec=250 CPU utilization dropped from 41 % to 34 %. Increase audio interface buffer 128 => 512. CPU usage: 38 %. Enable Plug-in Load Balancing CPU usage: 38 %. Disable Plug-in Load Balancing ThreadSchedulingModel from 1 to 2. CPU usage: 38 %. Close all open 5 FabFilter plugin GUIs. CPU usage: 28%. (Weird.) FabFilter plugins open again. ThreadSchedulingModel from 2 to 1. ExtraPluginBufs=5 CPU usage: 38 %. ThreadSchedulingModel=1 Set EnableSetThreadIdealProcessor=False ExtraPluginBufs=5 CPU usage: 41-42 %. Set EnableSetThreadIdealProcessor=False MixThreadCount=8 ExtraPluginBufs=5 CPU usage: 40% Set EnableSetThreadIdealProcessor=False MixThreadCount=4 ExtraPluginBufs=5 CPU usage: 32% Set EnableSetThreadIdealProcessor=False MixThreadCount=32 ExtraPluginBufs=5 CPU usage: 38-39 %, peaking to 55% every few seconds Summary: Best settings found so far for this very project: EnableSetThreadIdealProcessor=False MixThreadCount=8 ExtraPluginBufs=5 MixThreadCount=32 was not bad either because it created some CPU bursts. To be continued...

Just wondering why Cakewalk does not utilize 100 % CPU or Disk when exporting a mix with Fast Bounce setting on. Is there something to tweak in the Preferences to get the most of the system? For example, in the screen capture I was mixing a typical small project with only 32 tracks, and 20 FX. CPU usage is 41% while disk usage is barely 3%. For comparison, Premiere and AE in the same machine keep system 100% utilized during rendering.

EDIT: removed duplicate post.

This should help: https://www.laptopmag.com/articles/use-maximum-cpu-power-windows-10

Have you possibly customized VocalSync graphics? I remember changing size of the background only to see that it did not work.

Some modern i7, for example Intel Core i7-8700 3,2 GHz LGA1151, should be enough for DAW use for years to come. i9-9900k is expensive. I recommend it if you edit videos, too.

I hope this helps...