David Baay

Quantizing multi-tracked drums properly is a pretty involved process. Trial and error is not likely to get a good result. Are you sure it was good from start to finish at some point or possibly you hadn't listened to the whole track previously and are just discovering problems that were there all along?

The usual cause of a synth UI not opening would be that it's disconnected. Are there parentheses around Sitala in the Rack? If so, open the Settings menu at the top of the Rack with Sitala selected, and choose Synth Connected to re-connect it.

That wouldn't surprise me, but for me the last time was just the the second time I re-booted after disabling it. I only got one clean start-up without it.

Yeah, that's a good bet. Also along the lines of connections getting oxidized, you may find some ribbon cables inside that should be unplugged/re-plugged.

"Exercising" analog volume knob(s)/fader(s) on the keyboard while playing back some dense, sustained MIDI chords so there's a strong signal level might help clean up the ozidized contacts which can cause distortion in neglected hardware. If you can get the distortion issue resolved, standard operating procedure for using a keyboard synth with any DAW is to route its audio outputs into your audio interface and set up an audio track to echo it out to your monitors. Then disable Local Control so the onboard sound module doesn't respond directly to its keyboard (or pedal input), but only to MIDI echoed from the keyboard through a MIDI track in CbB and back to the keyboard synth. Basically you're treating the keyboard synth as a separate controller keyboard and sound module.

A quick search found an ancient (2014) post on KVR that said "The audio effect "tool" does this. The phase buttons for left and right are above the amplitude knob." Other hits also mentioned "Tool", so it seems that's the only way.

If you bind Tracks | Wipe Track(s) in Track View section of Shortcuts to a single key, you can simplify the process of clearing the track for a new take.

Go to the Groove Clip section in the Clip Properties tab in the Track Inspector and correct the Beats in Clip value. 8:01 to 19:01 is 11 measures which is 44 beats in 4/4. EDIT: I just noticed "18:05" which indicates you're not working in 4/4. Groove Clip Looping doesn't handle odd time signatures well. You might need to double the length of the clip so there's an even number of beats in the clip. Or just use Copy-Paste instead of looping.

Except for the guy with SPF 25000 slathered all over his face.

A tempo track node way out in the timeline will also cause this, in which case Ripple All helps ensure the node is included.

Yes, I mentioned in another thread that this generally only happens to me when using Realtek in WASAPI mode in which case there really isn't an option to power-cycle the interface. But if it happens with a peripheral interface for any reason (e.g. after a crash), this will often do the trick.

I believe this is caused by the audio hardware/driver not responding as expected when CbB releases the ports. It happens on my laptop, but only when using Realtek in WASAPI mode. I've never seen it after a normal exit using ASIO drivers on any machine, and it doesn't happen using WASAPI on my Desktop PC, so it seems to be hardware/driver-specific. If it's happening with an ASIO driver, you should report it to the Bakers with details of your PC/Interface configuration.

You lie Youlean! Nothing crashes in Reaper, and nothing crashes on a Mac. Doubly impossible!

The metronome only follows what's in the Meter/Key View and reflected in the project Timeline. And Audiosnap only really cares about beats per minute. The Beats Per Measure setting in the clip map is just a convenience for you to keep track of where the downbeats are when setting markers. In any case, the answer is no, it's not possible to set different meters in the Clip Tempo Map. You would need to split up the clip at downbeats where the meter changes. I would suggest you first go through the whole recording and enter all the meter changes; the project tempo doesn't have to be following the clip to do this. Then, rather than using Audiosnap, use Set Measure/Beat at Now to manually align the timeline to the clip as needed.

Never seen anything like that. Would be interested in seeing a project or steps to create one that reproduces it.

Kontakt has options for managing how much of the sample set loads that might help. SD3 is pretty light and I'm seeing no delay with it, loading several projects I hadn't opened for years. I wouldn't pay to much attention to other threads about slow-loading unless the symptoms are near identical to yours and they ultimately found a solution that you might try. There can be many different causes, and most of us are not experiencing abnormally long load times. Check your Windows performance monitor in Task Manager to see what it's working on when the load "hangs". You might need to get familiar with Microsoft Process Explorer or Process Monitor to get a better handle on it.

I'll have to look into that because I've "disabled" the Connect service several times in different ways, and it always seems to "revive" itself at some point.

Numeric Peak indicators hold whatever peak level is reached until they're reset or playback is restarted. If you're looking at the same track in the TV and CV, and only starting/stopping playback with no other change in the project state, it's hard to imagine how they would get out of sync. But if any sends or buses are involved, switching mute/solo/send/interleave states or gain/volume during playback could get things out of sync depending on the routing. Arming a track or otherwise changing where the meter is picking up the signal (i.e. pre/post-fader) can also produce unexpected results. Regarding the change in metering overnight, I would be inclined to think you were simply mistaken about the state of the project when you saved iand/or what you were looking at, and what you're seeing now is accurately reflecting the current stae of the bounced audio and metering settings But it's also possible that some FX plugin was reset to initial conditions on being reloaded and isn't producing the same result it was before because it's not linear phase or something like that. You might get a better idea of what happened by importing the three generations of clips (as-recorded, after applying gain, after bouncing together) from the audio folder into separate tracks of a new project and seeing how they compare. This is a case where the problem would need to be captured on video or by sharing steps to reproduce it in a new project in order to fully understand what's happening. All I know is that just about every time I've encountered a situation in which levels were unexpected, it turned out I was misunderstanding something about the routing or looking at the wrong meter. It happens easily.

I haven't set up or used a control surface for a long time so I'm not the one to give detailed guidance; I just wanted to check that the basics were right which sounds like they are. All I know is that when a keyboard stops working as a basic MIDI performance controller, it's often because ACT has taken over the port as a control surface.

Or just drag/slide/nudge the MIDI track out two measures, and Ripple All should take care of it.

Are the keyboards using independent USB MIDI connections and the Mackie is plugged into a seprate interface port so nothing is daisy-chained? Then did you set up theMackie as a control surface in ACT, and were the other ports possibly included inadvertently.

In the mean time, if you know what the offender is, you can just move the .dll so CW can't load it, open the project normally, and remove the "missing" plugin instance(s).

Record both outputs to a stereo track and zoom the waveforms. Any meaningful true-stereo difference should be obvious. I'm not familiar with these synths, but if they have onboard FX some of those might manufacture stereo content that isn't in the raw audio from the synth section.

What if you try that setup in standalone Kontakt or in another VSTi host?

Oops. I hate it when that happens. ;^) But, yes, the OP needs to determine whether the Hammer 88 is outputting the full range, and if not, why not.