David Baay

The spoken-word clip you shared doesn't seem to fit the description except for the motor-boating sound. The pertinent questions would be: - How did the beat markers line up, and did you correct them if they weren't right? - What tempo was detected, was it right, and how different was it from the project? - How much much did you change the pitch? I just did a quick test with a verbal count-in sample that I happened to have handy, and it worked fine but the Groove Clip algorithm worked better for increasing the tempo than decreasing it which is typical. I got a better result just slip-stretching it to fit the project tempo using the default Elastique algorithm, and then pitch-shifting it - even the DX Pitch Shifter worked okay for that.

I don't think it's a bug, per se, but rather a questionable design choice that the composite of all clips in the parent track is only shown when lanes are showing. MIDI tracks work the same way. I've brought it up with the Bakers a number of times over the years.

I have occasionally had a particular track in a project get 'out of whack' in this way after making several recordings and undoing/redoing/deleting some takes. I'm not sure of the exact sequence of events that can cause this, but it seems the lane-indexing can get mixed up over time and only deleting all lanes will restore the normal take ordering and numbering behavior.

As best I can figure out, CbB/Sonar doesn't like when the start of a note is more than about 64 measures off-screen. At minimum zoom with the PRV at maximum width and no keyboard, I can get 740 measures on-screen, and I can manipulate a note that's 804 measures (740 + 64) long; but as soon as I scroll far enough out to see the end of it, the start is now over 64 measures off screen, and I can no longer edit it in the PRV and have to resort to the Event List or scroll back to nearer the start time.

You need to clarify the project setup and the intent of doubling the cello part and what steps you took to copy the MIDI. Are you saying you have two Instrument tracks (combined MIDI and Synth audio) using two separate instances of Musio Cello inserted in the synth rack? Or is it two MIDI/Audio channels of a multitimbral instrument? The Musio website doesn't even make clear whether the plugin is multitimbral or you use a separat einstance for each sound. As has been explained, MIDI itself does not produce reverb, but there is a MIDI controller (CC 91) that is intended to control the depth/level of reverb produced by a synth, and Cakewalk MIDI tracks (and the MIDI side of Instrument tracks) have a knob for it. Copy-Pasting or drag-copying a MIDI clip from one track to another cannot, by itself, cause an instrument to start producing reverb unless the clip contains CC91 messages or the instrument on the target track is already configured to be producing reverb. If the timing of the MIDI clip is inadvertently shifted by a few ticks it might produce a delay effect that sounds a bit like reverb, but I doubt that's the problem in this case. As and aside, you should be aware that simply doubling an instrument with no change to the timbre of the patch and timing of the MIDI is not going to make the two tracks sound like two separat einstrument; it will just make the cello louder. Most symphonic plugins have 'section' versions of instruments to produce the chorusing effect of multiple musicians playing the same part.

You can lasso controllers just as well but I would probably just do it in the Track View to quickly get all of them.

Cool. Glad to help.

I would guess antivirus scanning. Make sure Cakewalk projects/content and program directories are excluded at a minimum. Watching the Windows Resource Monitor while saving might help confirm that or give another clue. It could also be casued by large zip/archive files left on the Wndows Desktop or other paths the Windows Explorer-based browser might be indexing. This usually affects loading more than saving, but would be something to watch for, especially given you presumably just transferred a lot of data from an old PC to the new one.

I understand stuff can get overlooked in the shuffle, but I did ask, "what instrument and what velocity do the MIDI notes have?" Next place to look is at the meters in the Spitfire UI. If you aren't getting a good level out of the intrument, it has to be either low velocity into the instrument from the MIDI side or some setting in the instrument UI is lowering the output level. I'm not familiar with Spitfire stuff so can't give more detailed guidance. Is the MIDI your own composition/recording, live input from a keyboard, or imported from a 3rd-party? If the latter, check the Event View for controller events that might be effecting the level (especially CC1 Modulation, CC7 Volume, and CC11 Expression) Any FX or Prochannel inserts on the track? The only other thing that comes to mind would be having some other track/bus soloed with Dim Solo enabled, allowing a low level through from the Instrument track. But the default gain for Dim Solo is -12dB so I would still expect more level in that case.

I don't get latency with your project, but I'm missing some plugins. The first suspect I see is: LoudMax - Per the website: "LoudMax is a Look-Ahead Brickwall Loudness Maximizer". It's in an FX Chain in the Prochannel on the DnB bus. Other suspects would be one of the several reverbs that might use convolution. And, as mentioned previously, I don;t have any of the Kilohearts stuff. In general, I would not recommend using such and intensely "pre-populated" template with such convoluted routing and so many plugins.

Drag the pane divider at the far right of the Console view to the left to reveal hardware channel faders.

Do you mean in the Master bus meter, or the Volume control level? If the Volume control is at -36dB that would explain it. If the Volume control is also at 0dB, what instrument and what velocity do the MIDI notes have? Or are you just playing live on a keyboard? Possibly there is a negative velocity offset (MIDI Gain) on the track? Or there's a problem with the analog ouput level to your monitors as Glenn suggested.

Edit > Select by Time operates on tracks selected in the track view which can be more than just the one you have enabled for editing in the PRV, depending on how you switched views. When I want to select a time range in PRV, I usually just right-click and drag to lasso with or without snap enabled which will limit the selection to the the track that currently has focus in the PRV.

I think he just means many tracks.

Not happening here - only notes in the highlighted track get selected for me when selecting in the timeline - but can't immediately think of a setting that would cause it to behave differently for you.

Other parts of the Mercury themes not dark enough for you?

Ripple Edit superceded delete hole. It works reliably to create or remove space.

How about just attach the template file?

I suggest freezing tracks one at a time and listening for changes on playback after each freeze. If you haven't heard anything significant by the time you get everything frozen, bounce the Master bus to a track that goes direct to Main Outs, solo it and group the solo button in opposition with the Master bus solo. A/B and listen for issues. Then invert the phase, cancel the grouping, un-solo and see if it nulls (which it should if all tracks are frozen and there isn't something random going on with live FX on the Master bus).

Agreed. The OP stated it didn't matter what MIDI input assignments he made, but I think he must be overlooking something. Ideally they should all be set to a single channel of a hardware controller if not specifically intended to be receiving input from a MIDI-generating VST. One other possibility would be that some synth input assignments on the audio side of Instrument tracks have gotten crossed up which has been known to happen when hardware ports come and go from the system and/or when certain sequences of undo/redo/insert/replace synth are executed.

+1 Great idea! I, too, had a ton of stuff pinned in CbB for different reasons/purposes, too many for one window. Tabs would be really helpful. And I'm hoping/expecting the Bakers will introduce a "compact" listing mode without project icons as well as a return if the "tiles" view where the project thumbnails are usefully large.

It could be a lot of things, all of which are more likely than that there's an inherent flaw in Cakewalk's mix engine that could be resolved simply by moving to a different DAW with everything else being equal, and that hasn't been noticed by people who have done many, many dense mixes with CW over the years like Lord Tim.

Processing load alone will not increase latency. Latency will remain the same as you start getting more and more crackles from late buffers until eventually the audioe engine drops out. I posted early on about Plugin Delay Compensation and that is still the most likely cause, but it doesn't seem you've thoroughly investigated that by removing/bypassing plugins or archiving tracks.

Pics or it didn't happen, i.e. please share a project that manifests this.

Just like exporting with no selection exports everything in the project, quick-grouping without a selection used to assume you wanted to affect every track when you held Ctrl. But users were occasionally getting themselves in trouble with it, so the behavior was changed to require a deliberate selection.