mettelus

Also check an inadvertant fade in on the clip. That would also produce what you are seeing.

Hehe... regular intervals of beeping, white noise, or dropouts are more often indications of something in demo mode (with the transport running (usually)). One that can easily confuse folks is iZotope's Vinyl... that inserts noise (its job function) even with the transport stopped, so can easily make you think your audio interface just crapped the bed when you re-open a project you've used it in.

You also have to be mindful of subtle clues with bands. "Flaccid Flatulents" may sound like a cool alliteration, but is a poor choice for a band name.

Her slip slipped S.L.I.P.... but luckily at the 55 second mark it magically recovered when they spliced the performance together.

Mark summed it up. Sample rate conversion (SRC) is also pretty transparent between the two as well, so you do not need to be overly concerned about starting in the wrong one. You may find an app that specifies one (say 48K for video), but it is more common to see SRC on import (as SONAR/CbB has always done under the hood).

This may or may not help. How close is the note to the beginning of the project? Scooting tracks to all start on measure 2 or 3 was common years ago for similar issues, and many of us still carry that workflow forward out of habit. Although not a solution, it may help, since it gives time for the audio engine to be up and running before processing audio.

Quick clarification. Did setting input to the left channel resolve this? The more important aspect is that routing is accurate for what you are doing. Trying to resolve ”stereo” working may be moot, since there is no visibility to what the plug-in is doing. Different modules and patches may respond differently to mono inputs, so some of the issue also lies in TH's handling of a mono input when it is told it is stereo. Another quick check would be to take a track with issues on stereo, and bounce that mono track to a new stereo track, then ctrl-drag TH into that truly stereo track and see what happens.

Beautifully done, on all fronts. An excellent testament to honor Dina's memory.

Touch pads can be a nuisance. I am not sure how customizable they are these days, but I have met several people (including myself) who inadvertently trigger them just by proximity. Every person generates a different body potential, so they are not "one size fits all." Just the fact that you have to reach across it to use the keyboard can cause issues if your potential is high. I was told once during some ESD training years ago that they had clocked someone at roughly 50,000V (can't validate it, but that is way high)... while the focus was protection of un-shunted parts, that comment suddenly made me think, "Maybe spontaneous combustion isn't a sham after all."

I think a big part of that is system dependent. Are you using the same audio interface on both systems? I seem to recall getting both signal attenuation and a feedback situation on different occasions when the stereo input was used, and IIRC was between TH2 and TH3. I also shifted system, but not interface, in that period.

Very nicely done gentlemen! This is a very powerful piece full of expression. Simple and elegant. You actually got several more listens than just me for this one (got a couple of group listens in here). I have an aspiring pianist visiting and have been struggling to convey the power of expression via variation in volume and timing, so this was a perfect example for her (thanks Simeon).

Or keyboard... the special function keys are what always got first on mine, specifically the CTRL key, which makes for interesting troubleshooting when it fails. The mouse would make more sense for what you are seeing, since as the contacts go it is common to suddenly get "double-clicks" when you think you have only done one. You could test that in the Windows mouse options and see if single clicks are triggering the double-click folder; but if that is the root cause, you would also be seeing it anywhere you use the mouse (that takes double click inputs).

As the OP uses synths in composition, this is something to be very aware of. In general, reverb benefits most to add "room space" to something close-mic'd and dry. Ironically, recording practice has become "strip all environmental effects, then add them back during mixing." Most synth presets are loud, wide, and dripping with reverb (to make them sound great solo), so those are things to address early on in your mixing chain. It is easy to over do FX on synths specifically because of this.

+1.... Win10 will even allow you to scroll through a non-focused app if the mouse is over it. Scrolling through some lists with those little up/down arrows is just painful. It seems like CbB is carrying forward internal scripting rather than leveraging newer APIs.

Ouch... that just reminded me of the need for mouse scrolling in the menu lists (there was another thread recently on that). Unless RX Connect is one of the last 5 FX used, scrolling through iZotope to get to RX is a PITA.

Both of these threads should be stickies... for NEW users, one of the first things they are gonna want to know is "What are the most-liked free VST(i)s for CbB." Managing it for the OP could become a nightmare, but a link in the OP to an external webpage might be simplest. There are often a lot of golden nuggets dropped by folks in these forums, but not everyone has time to mine for them.

This is an important point. When first starting out, the input echo allows the soft synth to be heard from the controller. Since you will most likely be building songs by overdubbing, leaving that setting to default will let you leave your controller assigned to the same channel and get your work recorded. When input echo is off, the soft synth will respond to notes in the track. Some soft synths allow "MIDI through," which is something to be aware of... sending a MIDI note to them will pass through (to other tracks), so if you get a "weird" instance of driving one synth, but hearing a second respond to your controller.... check 1) input echo is off on the second synth and 2) MIDI through is off on the soft synth you are using. Channels are something also to be aware of, but starting out what Bob mentioned is easiest... input to Omni, and automatically echo the selected track (default behavior). Side note: A cool feature of CbB is that if you have NO MIDI outputs enabled in preferences (highly recommended), when you open a MIDI file with CbB (right click and "open with..." if you didn't automatically assign MIDI files to CbB during installation), CbB will automatically insert the TTS-1 GM synth and route all instruments/channels for you. This is a nice feature if you want to play with MIDI files downloaded from the internet.

I only had experience with one. I do remember it being rather warm, but it wasn't hot enough to deter me from shaking a friend's until it was a perfect homogeneous solution. She said it took a month to separate back out and wasn't ever quite the same again. I told her NEVER tempt engineers with odd toys... they will either tear it apart, or stress test it till it breaks (and then probably waste hours fixing it).

I just put a Crucial MX500 1TB from the offering a couple months back in my machine as a sample drive. It maxed out write speed and stayed there for the most part moving 463GB of Kontakt libraries from my Samsung 970 NVMe m.2 (X4) (also 1TB, and I wanted the Kontakt libraries off of that one). First Crucial I have owned, no issues noted, and the MX500s seem to be rated nicely.

When TH3 is re-installed, it will reset, and default to "stereo" under the master controls (the "Master" button to the left of the tuner). That has caused issues in the past for me, so make sure that the "In source" is set to the proper mono channel there.

There are quite a few freebies on Patch Arena, and nicely sorted. The Muz3uM for Z3ta+ is at this link (download is in the upper right of the OP).

Jeremy Soule did some of the Elder Scrolls scores and I believe he is exclusive to Guild Wars, but definitely no amateur, since he "has been described as the 'John Williams of video game music'" https://wiki.guildwars2.com/wiki/Jeremy_Soule [Just read that through and he signed an exclusivity agreement with EverQuest... found that odd.]

The advice above regarding programming synth sounds is worth considering... There will be times when you will want to commit ideas quickly so you can move on, and tweaking something will end up being far faster than searching presets.

That statement can be applied to far too many applications! I am hesitant to suggest certain things to people because a follow-on sentence could easily be "invest X hours into it and you might get useful results with it." Have to step back when it is going to come across as "Get this, you'll never really use it." ?

Nothing to add, but wanted to comment on how nicely presented the OP was.