OutrageProductions

In all my years of experience there have been two unassailable assets regarding production of a record. And none of it (after the recording phase anyway) has anything to do with the actual gear. All things being relevant and subjective, it doesn't depend on the recording media, or the console, or the room, or the outboard gear, or the DAW, or the plugins, etc. It all depends, ironically, on the mixing engineer and the mastering engineer, and their ears.

Check in the help system. Highlight a clip, RMB, context menu towards the top. CW is much more complex program than most noobs suspect. I've been with it since '92, and just learned something new today that I didn't know was possible.

That's strange. Do you have the clips locked in track view?

@Neil If you clik on the D# piano key in the PRV (for ex) do all of the closed hat notes highlight? And if so when you then hover directly over the velo tail in the bottom pane for one of the highlighted notes, does the cursor change to an up/down arrow? If so you should be able to drag them up or down from there.

Which Tool is assigned to your cursor in the PRV? <Keyboard Shortcut = T> Maybe post a screen shot of a couple of bars so that we can see what might be wrong.

I never knew this either! And I rely on artmaps for nearly everything I print.

Shhhhhh.... you might wake the trolls.?

Why should we ruin the surprise?

Install and run MIDI OX and monitor when everything is at idle. That will tell you what is being triggered.

Much easier way is to put the Master (mix) bus into mono instead of stereo interleave.

Every DAW has a different algorithm for summation and export to file; so backgrounding, buffer addressing to the chip set, and file maintenance will be slightly different. The same operation in my Cubase 12P took 4.25 seconds, and in Nuendo took 6.4 seconds. I have PT available as well, but hate using it. But a "fast-bounce" that, in essence, equates to "real time" is beyond question wrong, for whatever reasons.

You guys both have something funky running in the background. Have you fed the processor gerbils lately? Here on my machine, I just did the same operation as @Bruno de Souza Lino mentioned on a 48k/24bit stereo Wav file from 2:27 to 4:54 (twice as long), and it took 3.27 seconds to complete. Interestingly enough, on the exact SAME mix printed as an MP3 at 192k and imported into CW in a 48k/24 session, the same process took 4.02 seconds to stretch 200%.

In the 'hardware output' section of the console view, I have enough actual physical outputs that I have configured a stereo out to headphones, a stereo out to a pair of nearfield loudspeakers, and 6 channels out to my mains in 5.1 Surround (LRCSLsRs) and it is saved in every one of my starting project templates. [I have an outboard monitoring rig that allows me to switch between them] In the bus section, all of my project templates also start with (obviously) a Master (Mix), a Reverb, and sometimes a Drum bus. They are very flexible indeed!

Also consider disabling any services that may not be necessary. Things like Search Indexing and background virus/malware scans can really chew up CPU time slices. Consider excluding your Cakewalk program & audio storage drive locations from the virus scan path.

The concept is simple, but you may be slightly confused by terminology. Busses just operate as a summing fader. You can add as many busses as needed and use them to 'group' things like drums, percussion, guitars, keyboards, vocals, reverb, etc. Each of those 'groups' can have overall EFX treatment if desired, and then all of those busses can be sent to a Master (aka 'Mix') buss, then the Master feeds your audio outputs. A lot of folks will (if they have enough horsepower) insert some "mastering & monitoring" tools on the Master buss for listening (and sometimes printing) an output file.

Can you play the project all the way through from head to tail? If so, try to export with <render in real time> and <audio bounce> engaged. And maybe change the output file destination just to see if it's a write permissions issue. BTW the latest version is commonly referred to as 2022.11.

+1 for installing latest version of CbB! I left SONAR X3 on my machine, installed CbB, migrated setting and plugins, then used Win P&F ctrl panel to uninstall only the SONAR application after I was happy with everything. All my old bundled plugs stayed installed and running.

Try to increase your driver latency in CW (or in the ASIO ctrl panel) to just less than 30ms round trip (approx 128 samples) and see if it helps. Then back it down until the crackle appears again and you'll know just how fast your rig can respond. I've learned to use headphones and play just a bit in front of the beat, then iron it out in post. Do this without the TH2 engaged first. Edit/preferences/audio/driver settings/mixing latency/buffer size. [Some ASIO devices require this to be set in the ASIO device control panel, if such exists.]

I have examined the minidump files when CW very occasionally quits unexpectedly on big projects on me, and 99% of the time it is because I tried to do something (like freeze or expel a large VSTi, or cancel an Export) and move on to the next operation before the program has had a chance to properly flush and reallocate RAM. I just go get a fresh cupper and in 7 minutes it clears out of the Task Manager and I can relaunch and continue. I'm used to it happening about once a month. But I also only reboot the machine if required by Win updates about once a month also. In between big sessions I flush the Standby and Working Sets of RAM with a batch file I wrote in the CMD window. Never fails to make things continue to work more or less seamlessly.

I've been using a KK S61 Mk1 for 5+ years. It works seamlessly altho it does not have the 'auto track focus' that is integrated into Cubase & Nuendo (that's on CbB, not NI). And using Mackie Control surface, the transport controls on the hardware work; rec, stop, play as normal, loop turns an existing loop marked on/off, ff & rw move now time by 1 measure. Do not know if the 'mixer' knobs on Mk2 will integrate as ctrl surface. I've heard of too many hardware failures with the Mk2 for me to have to upgrade. That's all I need. Integration in Cubase is deeper like automatic track/instrument focus from hardware, but I just work around that.

I would bet that both the oscillator and the oscilloscope were MODELED on some existing piece of hardware and the resulting algorithm inherently includes the anomalies found in 'real-world' impulse responses. If they were strictly developed on a purely mathematical basis, I imagine you would see a more geometrically square wave without artifacts. Which would probably phreak out anyone with a minimal electronics background. Sinusoidal responses, and their derivatives, are found to be generally symmetrical in the normal world. Aside from cardiac infarction, obviously. ?

With the Scarbee basses, the samples from 101 to 127 velo range are all the same dynamic range, so it's an increase in volume only. In my Indiginus instruments (and especially in ISW Shreddage instruments) it can get you in serious trouble with velo scaled articulations.

Seriously trying to ask about someone's favorite DAW (and why) is like herding cats in a rainstorm. BTW, my favorite color is the smell of the number nine... but only in the vacuum of space. ?

That was a stickler fer sure, but it controls the relative (I guess you could say 'unity') gain of the note velocity from the MIDI channel. Sort of increases the dynamic velocity curve, if you will. For example; in NI Scarbee Jay Bass (and IIRC) Pre Bass, I have to bump the MIDI volume from 101 to 127 before recording so that I can get a reasonable (-6 to 0db) level on the instrument for input monitoring. (yeah, yeah, I know there are ways to do it in the VSTi and save it, but it gets overwritten every update). I found some really cool long evolving drones, risers, and soundscapes that I really like in things like NI Reaktor and Absynth, but they are extremely stochastic. Play it one time and I love it; next pass... not so much.

We're just here to observe how real nerds turn a dead horse into glue by beating it to a pulp.