David Baay

The best manual tool is Set Measure/Beat at Now. Set the Now time at a transient, Shift+M, and enter the measure and beat (or fraction of a beat) that transient should be hitting. CbB will modify the previous tempo to make it happen and enter matching one at that point to act as an "anchor" for the next Set. If the first downbeat isn't at 1:01:000, more steps are required to get started. I have a single key bound to it since I use it a lot and Shift+M is awkward. Take advantage of Tab/Shift+Tab to transient and other keyboard shortcuts for navigating the timeline, and you can move through a piece pretty quickly. I recommend snapping downbeats every 4-8 measures to start. Then you can go back and Set more points as necessary to tighten things up further.

Is this a new installation of CbB with no changes to default settings? Does it happen if you freeze the synth? The symptoms sound like you have a non-zero Fade On Start set in Preferences > Audio > Playback and Recording.

True if you want to bounce to a different track, but the OP's question implied he wants to render a section of audio "in-situ" in which case you need to split the instrument track to make the synth audio side of it available as a target for the bounce. And assuming you don't want track Volume/Pan "baked in" to the rendered audio, you have to record the synth in real time to capture the raw output, and then mute the rendered part of the MIDI so it doesn't get doubled on playback.

Not all plugins are compatible with Plug-in Load Balancing. In general I leave it off unless a project is heavily loading the first core, and enabling load-balancing clearly helps. In projects where the load is already pretty well-distributed and I'm not having to greatly increase the ASIO buffer to get it to play cleanly, I've found it can actually be detrimental. I'm not able to repro your crash on closing multiple folders.

I'm afraid you are near the first if not THE first to report this. Is this something that just showed up recently or you're just starting to use CbB and encountered it right away? In any case, I'd suggest you try getting as clean a boot as possible using msconfig or Task Manager > Startup Apps, depending on your Windows version, and/or use LatencyMon to see what might be spiking your DPC latency: https://www.resplendence.com/latencymon

"To play the virtual steel tongues use your MIDI keyboard from the note C3, C#3, D3, D#3, E3, F3, F#3, G3" Disappointing they sampled an instrument with only 8 pitches (13-15 is not uncommon), and a very weird choice not to map them to their corresponding positions on a keyboard.

Had a look at some posts on the old forum to refresh my memory. Good to hear from you , but I have to agree "doomed product" and "hanging in, trying to make it all work" doesn't really capture the lived experience of those of us who have continued to make lots of good music using CW without any significant issues over years and decades. There has never been any actual disruption in CW's serviceability through all the ownership transitions or even the Gibson "shutdown", just a lot of needless hand-wringing as there is now with the transition from free to paid product. The king is dead! Long live the king! Cheers, Dave (the user formerly known as brundlefly)

Hmmm... sounds odd, not sure what could cause that. I'd probably need to get hands on with a copy of the project to see if the problem reproduces on my system and investigate further if it did. FWIW here's a process you might want to try if this isn't close that what you did:

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.

Shirley you jest.

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.