mettelus

Not installed 1903 yet, so making a quick comment to find this thread for when that time comes.

My apologies if I threw a wrench in the thread, but I'll freely admit that given your modest needs that throwing a DAW solution out would probably not fix all of your issues (especially system ones). It would be worth getting ”Bandlab Assistant" and then the newest CbB release to kick the tires on it and get any system issues addressed. CbB also introduced WASAPI driver mode that would allow you to troubleshoot sans interface for things like DPC latency issues. There are plenty of folks here that will stick with you to iron things out if you are willing to give that a go.

Have you tried the new CbB release? I am more curious as to the issues you are having "making it work." For a few tracks with minimum plugins, just about any DAW *should* work, but each one has its own quirks. I have only tried a few others, and Samplitude "seemed" closest, but I couldn't get myself to like it. I use Studio One mostly these days, but again that falls into familiarity with the work flow and trade offs to other things. The few things I do miss most (track templates, Set Measure Beat at Now, Audio Editor integration) have workarounds or partial fixes. I have yet to install the new CbB, but it includes a lot of updates. If you are more familiar/comfortable with CbB's work flow, it might be more beneficial from a time perspective to get help with the issues that you have. Samplitude/Studio One it seems you have already used/tried, and I cannot really speak to more.

FX do not care what they take in nor what they pass on, so always be mindful of the signal you are sending from one FX to the next. A compressed signal is harder to EQ if it has unwanted content (like roll-off's mentioned above), and there is nothing limiting you from multiple steps (where more transparent changes can be made). Mild compression in -> EQ the proper content (for the instrument) -> compressing again to fit the mix is not uncommon.

Very nice piece Dave. I saw the "MIDI editing cheat" comment, but when started listening it became a "who cares?" for me. This quote gave me a smile. I have a classmate who used to play keyboards, got married, and then a grand piano. She has had zero interest in DAWs or mic'ing it... she just plays (20 years and counting...).

Ozone is also a bit CPU heavy and you cannot use modules separately without the advanced version. iZotope has done a lot of work to split their functionality apart since the Alloy days.

I see what you mean now. I renamed a .mid to .midi, and double clicking it launched CbB, but you are correct that the open dialog box does not recognize the .midi extension (it is not visible). That is a bug as far as I am concerned, since CbB can definitely open them.

How did you perform this? Reason I ask is twofold. First, many programs link to computer ID, so shifting hardware and OS could require a reinstall and/or reauthorization of those apps (Waves could be one, but I do not own any). Second, the VSTscan is a shared component, did you install an earlier SONAR version at any point after your shift to Win10?

That is cool that it got posted for future downloads. New folks can still apprectiate what it can do. That release is totally unlocked, so I am not sure if there is any issue with just sharing it with others.

Thanks for the response Craig. In concept it makes sense (the article reference in the OP); but for the price tag, I get concerned for a couple of reasons (pun intended), especially to new users: There are a lot of free (or cheap) VSTis out there; and while many users start with tweaking presets, there are also a lot of "sonic manipulation" tools (in the same price range) that can morph things into uncharted territory. For $400, someone with patience could rack up quite an arsenal of instruments and tools for use with CbB (or any DAW). In a similar vein, while the point is to take advantage of tools which do not have recording capability, that same $400 could buy a DAW which most certainly can and also includes adequate VSTis already. That would undermine the point of the article. New users are the my primary concern, since they really want 1) easy setup, 2) intuitive workflow, 3) not to have to invest large amounts just to get up and running. *IF* someone had those tools on hand, ReWire would make sense, but I am always hesitant to suggest a solution with a large price tag to folks needing help.

This will probably spin around and bite me in the butt down the road. I have stayed on a FireWire interface because it is dedicated and not managed by Windows as USB is. When the day comes that I switch to a USB interface, I will probably forget reading this advice.

I am not familiar with Reason, so had to look up the cost for an end user, and rewire has been a can of worms for me as well. Does the Reason Intro version include those features (full blown Reason is not cheap)? If not, some third party programs or even DAWs have these functions integrated under the hood which makes them simpler (and get fixes more readily). Being unfamiliar with rewire, I would be interested to hear the argument for a new user, since learning two DAWs is not as beneficial as sticking with one which already does what they need.

Wow, thank you for posting this. Resolve is one hard-core program. The initial setup even asks you what workflow you are used to so it will customize the layout to something familiar. I was tempted to say Premiere Pro, but then just chose Resolve's default. 2937 page manual... OMG, but it is nicely bookmarked and thorough that I can tell (and they even apologize for it being so big). I ran it enough to kick the tires a bit and the engine in it was smooth as silk for scrubbing, so I just added more and more till I got bored with effects. I hit the play backwards button by accident at one point (never seen one before), and that just gave me a chuckle. Now wondering why I never picked up on this existing. I downloaded the 16 Beta, and it didn't ask anything other than info prior to downloading... not sure if there is anything more to it after the fact?

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).