David Baay

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.

What path does the "Missing Audio" dialog indicate it's looking in?

Actually, no. I never encountered that problem. I just thought I might solve it for you by docking them. All you have to do (if you can get them to open undocked) is drag them to the bottom of the screen where a blue overlay/shadow appears indicating that they will drop into the Multidock when released. Most views, including the Console, open as tabs in Mutlidock by default. They can be undocked by right-clicking the tab, and you can also dock FX GUIs by right-clicking the title bar.

Sounds like the UIs have somehow gotten moved off-screen. They open as expected for me in your project, but I noticed the Multidock was undocked and minimized. I'm attaching a copy of the project in which I've re-docked the Multidock, and docked some of the synth UIs in it. If you undock them from there, possibly their screen coordinates will be corrected. I had to re-direct where it was looking for audio files since it was apparently using the Global Audio folder on F: so you'll have to re-reference that folder when it prompts for missing files. I highly recommend you switch to using per-project audio. Phil's project - Synth UIs in Multidock.cwp

If you have the metronome set to Audio, the clock will be forced to Audio. Likewise if the project has any soft synth or any audio track with input echo enabled. To use 'Internal', the project has to have only MIDI tracks and MIDI metronome. But that's not what you want anyway.

On the contrary it's a highly useful feature in many contexts such as when editing drum parts in which case you are likely to want to select all the notes on a given note number to change their velocity/timing or drag them to a different note number to switch instruments/articulations. It's also useful for grabbing all the notes across a range of pitches (e.g. bass or melody notes) to cut/copy and paste them to different track to be played or coubled by a different instrument or transposed up or down an octave. I don't draw my music to start with so I seldom have a need to preview a pitch by clicking in the keyboard, but I would recommend you just draw a new note to hear it. If it's not the right pitch, you can drag it where it needs to be or right-click to delete it. Or get in the habit of immediately clicking an empty area of the PRV after clicking a key to deselect everything. You can also Ctrl+click the same note to de-select.

Yes, USB. The PC version of the hardware actually shipped with a chip that you had to swap out to make the port compatible with Wintel USB. But, you're right to question as I realize I was off by a decade. It must have been early 2000s when I got my first laptop that needed external MIDI.

It got tossed (actually just hidden initially) because it was only designed to offset the MIDI tempo and Pro Audio/SONAR did not initially have audio-stretching capabilities. You can now get the same effect using Tempo Offset by percent, but you have to enable Audiosnap Clip Follows Project in Autostretch mode on any audio in the project as Promidi mentioned in the first response. And it's not as easily done temporarily because it's destructive to the tempo map and percentages have to be whole numbers so it's not easy to get a perfectly reversible ratio other than 80% and 125%.

No, you actually have to jump through some hoops to get CbB to change pitch corresponding to the change in playback speed, and it's unlikely to have fewer artifacts because it's two separate DSP operations. If Live is just re-sampling the audio at a lower rate with fewer total samples to make it play back more quickly at the interface clock rate, I believe that would tend to produce the cleanest result other than the slight alteration of pitch formants (chupmunk effect) that shouldn't be a probem with small changes in tempo.

Personally, I think it's n urban myth that MOTU don't know how to write good drivers for Windows. They've been shipping Windows-compatible hardware and drivers since the early '90s. I have a MOTU MIDI Express XT interface from that era that still works fine under windows 10, and my MOTU PCIe-424/2408mkii interface runs great at 64 samples and even 32 if the project is light. Where interfaces mainly differ is in how much hardware/firmware/bus latency is added to the buffer latency, and that's where the MOTU shines because it's PCIe instead of USB. Pops/clicks/dropouts are all about whether the DAW application can get the buffer of audio processed before the interface driver requests it and Windows responding in a timely manner to the interrupt request to fill the buffer (that's where the Deferred Procedure Call latency - what LatencyMon measures - comes into the picture), and that's where you need start diagnosing problems with streaming performance . No doubt there are some dodgy ASIO drivers out there, but they're not coming from companies with the expertise and reputation of MOTU.

Most people would find the latency with that buffer size troubling. I generally run a 64-sample buffer while recording, and never more than 128, especially when input-monitoring hardware synths. But you mentioned sync problems on the order of "a few seconds" which is a lot even for a PDC problem. The only thing I know of that has ever caused that much of a problem is some interface drivers not playing nice with Metronome Count-in enabled. Try recording without it. If it makes a difference and you have not had this issue before, a reboot might cure it. Also make sure to zero out any Timing Offset you might have tried in Sync and Caching (not to be confused with the Manual Offset for audio record latency compensation).