Glenn Stanton

one more thing to add: ask someone you can count on for objective listening to give a listen when you think you've made progress as sometimes the things you thought should be at one level or another, when someone else is listening, they may have a different opinion on that... a second set of ears can really help to focus and get your mixes to improve.

you could use the fxchain PC module and create your own set of plugins. then save as a track template, or PC preset, or as part of a larger overall template.

have you gone to Behringer | Downloads https://www.behringer.com/downloads.html and checked for the latest drivers for each device? also - turn off caps lock. it's not helpful for reading and implies shouting. as far as the bundled software, you should go to that product site and make sure you have their latest software. lastly, if you're running older versions of Windows or haven't been keeping up on patching, that can also cause issues. also, trying to install old software (and many times the "free software" is 7+ years out of date which is why they're giving it away), will also often fail for a variety of reasons. so: step one - calm down. no caps lock, no repeat postings. step two - make sure your profile is filled out with all your technical equipment details, Cakewalk version, etc so people have a sense of your systems step three - when in doubt, reach out to Behringer support since this problem doesn't seem to be a BandLab issue.

actually that ability has been around for quite some time. i generally don't use it since i have my nudge keys setup and they only work on whole clips (although i admin to not testing that on the clip edit content)

i set mine to -3 (after calibrating on unity), on real hw mixers i find this gives me a bit more (psychological) room to push a given track volume.

anti-virus is disabled for cakewalk?

the update to the program cause the revert to wide strips on the default workspaces, os i create my own mix and record etc workspaces so the updates don't change them. also set up my templates with narrow strips. almost never go to the full strip, just use the inspector side for it

as a note, the shift key works on most of the controls (sliders, knobs etc) to enable more granular settings by effectively "slowing down" the change speed - e.g. volume, eq, etc - you can quickly switch from "large" moves to "small" moves with the shift key.

hey! don't be knockin' those rockin' old folks! ?

my Sequential Circuits Pro One was the rock-solid clock source for the rest of the devices (keyboards, drum machines etc) so one dial to turn for tempo ?

a lot of early sequencers used precision (0.5% tolerance) thermisters (thermal resisters) and capacitor type "clocking" on some form of crystal master clock. the slow degrading of these devices eventually overcome any thermal stability afforded by the high tolerance components... so over time the stability and relative settings drift... i just fixed 4 synths and machines last year by replacing these components to get them mainly back in order...

it might happen if you have pre-fade sends? but then again mute should mean mute ?

you can route directly to the hardware outputs (which is what is seems like you're original project settings were). however, if adding a master bus changed things - you might need to check that all tracks AND all SENDS etc and all BUSSES are also going to the master buss. otherwise you may be missing tracks, effects, etc etc which are currently routed to the hardware and the results are now a skewed output.

also, they have a free music theory e-book which some folks may find useful if they don't already have a good understanding of music theory. https://welcome.online.berklee.edu/download-berklee-online-music-theory-handbook.html

maybe re-install it and re-scan it? or you're using a preset which has the volume off? ? i haven't tried the PC version of it, but assume that is a VST2.

i'm on build 2022.02 039. seems to be working. i have both the vst2 and vst3 installed - although override to use vst3 is set in preferences.

definitely try them out. currently, i'm routing via speaker switching and some direct outs on the I/O - my main monitors + sub, an active cube, Bose 901+sub, Fisher 12" speakers (full range setup), and 5.1 via optical out to JVC receiver and 5 JBL speakers + the sub. and occasionally a few bluetooth speakers (Jambox, Bose, and some no-name brand), headphones (Dr Dre, a couple of AT headphones, SA headphones, a Samsung earbud, and some no-name light earphones), and lastly sometimes via my phone speaker. i don't go through all possible options for my stuff (maybe 30% of the non-switched outputs), but with other peoples mixes i'll do probably 90% of those before thinking its ready. i found my old PC speakers w/ sub (the Altec setup they were handing out with Dell back in, erm mid 1990...) so i may connect those soon as they have a completely different operation than the other speakers and are easy to switch too, and are unforgiving... ?

yeah, i was looking at the 8200 as well to expand my 1820 but saw a number of reviews about issues with this pairing, and since the 8200 is only slightly cheaper, i just got the second 1820. the monitoring outs go into my mixer and then to the speaker switch as set #2, and normal out on first 1820 as #1. so a bit of extra work there but overall behaving nicely... 16 xlr in + preamps. but easier to connect and sync...

i found this in my inbox a few days ago. it's a nice course which gets you thinking about how orchestration should use "color" instead of "range" when select instruments. https://welcome.online.berklee.edu/Orchestration-Techniques-Course.html

i thought your Jag could hit 12K RPM before it begins to act up... ?

the latter as who could object to the former? ?

a blues song about the plethora of underwear and general undress in advertisement today... ?

from my test electronics days - we'd consider anything 5Hz and under to effectively be DC so blocking anything below 10Hz was fairly standard to avoid issues with the DACS. from a musicality standpoint, unless you're doing something with large pipe organs, cutting anything below 20Hz would likely solve this. for VLF "effect" like gaming and theater effects - i'd put those on a separate "effects" track and ultimately route to the appropriate effects channel (if there is one).

2¢ more - any time you are "stacking" multiple selections on a single control (like output or input) you run the risk of these being hidden from general view and could result in people having problems with changes or troubleshooting... i like the idea of "MIDI sends" for when you want to assign the output to something else specifically and when looking at the track can see it (unless you have lots of them so they're hidden). or a "patch point" (as a send and/or output assignment) where any track can select it as an input (or really any MIDI input on a synth or track). for me, an "aux" track is just a convenience to setup a patch point + related track so that would be consistent with the audio side of things. these two approaches would seem intuitive and not result in (too many) "hidden" connections and provide folks with "absolute" routing paths when desired. on the sends it would be nice to have filtering options (like we have volume and pan) like notes or CC, ranges, etc. on patch points - i'd keep it simple - the consumer manages the content they get from it. this avoids possible man-in-the-middle complexities like when you're trying to tweak something at 4am and end up pulling hair out trying to remember why the wrong stuff is happening when everything seems to be set ok... ?

that is what i usually do - select multiple ones then the target, however it would be nice for the one-offs to return to the uncategorized list rather than the target list and the resulting scrolling...