Glenn Stanton

i only wanted to support your comment on oversampling as there is the potential for bit depth expansion in some cases as well - e.g. 32-bit float processing then truncated to 24-bit whilst performing the oversampling process as well.

the mouse wheel is your friend: shift+wheel = left <> right; crtl+wheel = up <> down; crtl+alt+wheel = enlarge <> shrink audio waveform; and alt+wheel = zoom centered on pointer. once you let those 4 methods become second nature then moving to where you need to, and zooming in and out becomes really fast,

oversampling is different than bit depth -- but both can impact the quality of what you hear. i think bit depth is more important for most people (24-bit vs 16-bit). sample rate after a certain point (imho 96Khz) is less detectable to most people, and definitely more storage space consuming. https://www.izotope.com/en/learn/digital-audio-basics-sample-rate-and-bit-depth.html ?

one more cool thing (at least with the AAS Strum GS-2) - if you have multiple sections -- same chords / notes -- but want to use program bank changes or CC to switch between keyboard, guitar and loop, you can "stack" the articulations and the corresponding parts play when put into the given mode (because they're mutually exclusive in accepting the switches...). ?

if you're not using them for something else, then yes. i did on my system as i don't use them for anything.

# of samples in a given instrument, and the range at which the sample player can interpret and apply velocity levels, can impact the levels available - so if i have 2 samples per note - one loud, one half that, then setting the level any where below the trigger velocity for that sample will always be pretty the same. having the instrument with 16 sample levels / note type will be much more flexible, and if the sampler app playing it can respond to velocity in smaller increments, then the sky is the limit.

i use them to create different rhythmic patterns with my guitar VI - if they don't have a native one, i simply create one - effectively similar to the key switching but with some extra features on how they're applied and packaged nicely and reusable.

it should be something you can set up in any modern DAW - i have a few "listen" busses - a "-12db" (quiet mix checking - pre-fader off master) and "master" (feeds room monitoring & basic 2-track bits), a "NX / VSX / Sound ID" for room simulation in headphones (also pre-fader send), and a "print" buss pre-fade off the master for final export.

the dither adds a noise component (not detail) to the LSBs (avoiding a "quantinization error" when truncating digital values) when you convert from (say) 24-bit to 16-bit (i.e. dropping the bottom 8 bits). if you're doing final mix in prep for mastering - leave dithering off and send in same resolution you are mixing in. if you're trying to produce an MP3 (etc) directly off the mix, then pick one of the POW dithering options. note: the results will not be as good as say the Ozone or WaveLab etc dither options. S1 vs CW vs etc may likely have different dithering options and aliasing filters. it is interesting that no matter what we do - noise is always going to be part of audio ? some reference: What Is Dithering in Audio? (izotope.com) https://www.izotope.com/en/learn/what-is-dithering-in-audio.html

one caveat for clip gain - it can impact how effects behave - so things like compression and saturation (or guitar amp sims etc) can end up behaving differently so consider you may have to do some compensation on those to accommodate the changes in clip gain. one reason to do the clip gain automation (sort of dynamic equalisation) before inserting and setting up any effects which can be impacted by those changes.

here's one not so obvious - but i think was installed recently during one of the MS Edge updates - "Realtek audio effects" in "software components" - before: random clicks and glitches, after disabling: clean again. drove me nuts for a couple of days.

+1 on the install -- also - i keep all my Spitfire content on my content drive under a single folder -- this way whatever login is used, the content is the same for all users.

and you downloaded the latest LABS app / Spitfire manager? when you contact Spitfire support - did they give you any suggestions?

thanks!

a simpler solution is use anti-spam filters & rules - new users need to wait 8 hours before posting or read the "rules before posting" sticky and click "like" etc would likely prevent a lot of spamming.

if they're wall warts, you're likely better off replacing them with a properly made power supply which has the correct ground, chassis ground etc. to reduce/prevent hum and provide stable voltage (although in some cases, a variable supply option can be useful to "stress" the electronics to get some additional bandwidth on the effects or some additional smoothing to the saturation.

works fine on my CBB on Windows 11. not using an older version of CW so no option to test it

well, high caffeine tea, red bull, etc all can work when the brain is thinking correctly and the hands type out dumb*ss stuff... ?

apologies - monday before coffee...

... ignore me - too little brain hand coordination this morning before coffee...

remember to do a MIDI export as well to capture tempo (if any) changes etc

as long as they're on and active when you start CW, you should see the same list each time. i know for me (like just now) if i forget to turn on my Komplete Kontrol S49, it's missing from my list ? if i exit CW, turn on my S49, open CW, it's all good again.

+1 -- a means of viewing detailed project information esp on plugins... not necessarily all the settings (very nice to have though) but at least the plugin and patch name, or for CW plugins, the settings as well ? generally speaking when i make enough changes to a preset or from scratch, i save it as a preset of it's own - either for generic re-use, or if project specific - then a project "abbreviation" added to its name and/or saved to the project folder if its an option.

actually the latest version is 2.66 ?

you could use Waves Studio Rack to create parallel also... but sometimes having the plugins serialized is the end goal... then again, when you have 16 cores and 11 are used at any one time -- is that a problem? ?