Glenn Stanton

it's the VST3 fault, not CbB nor Sonar. the removing the .vst3 folder extension is a workaround for a faulty implementation of the VST3. i have probabyl 6 or 7 which needed this "fix", but then after the dev folks were alerted to the issue (and likely from any number of people), most of them updated correctly and now work fine with the .vst3 extension on the folder.

whenever i see this in a "blank" section, i split and delete out the section. then i may at some some point bounce the clip, but it never reappears after that as it's pure silence (which seems to be different than nearly silent). not sure if imaybe there is some noise sample or DC (or both) which is very very very low (and massively zooming in appears flat) but is something the waveform drawing process decides to display. in most cases, i'm slicing out long sections (workflow thingie) anyways to ensure no possible noises as a habit, and i just ignore it unless it's something in and amongst audio i'm keeping (and in which case is usually some noise - pick, electronic spike, mouth click etc).

you can connect additional units if they're all using the same driver. i have the UMC 202 HD and the UMC 1820 and can connect and access both because they use the same driver. but - for expanding the 1820 unit directly - your best bet is the optical route.

true but for me, this works well vs the track manager only (which i do use as well) as i also want different views like console or not, inspector or not, etc. and this captures it quickly and easily. just my workflow input on the subject.

i have a view preset "WIP" work in progess - which is "disposable" in the sense i can overwrite it at will to reflect how i want things arranged. and then i can always just select my custom mix/record etc views to go back to a fuller view.

i know. i have it preset in my templates so it's all set up. still not the same as "None". maybe switch the text to "Omni" instead of "None" to remove new folks confusion.

sadly, the "none" = "omni all possible MIDI on the entire planet welcome here" has been around forever. possibly one of the best changes that could be made in the immediate future -> "none" = "none" (i don't want to receive MIDI from anyone). 🙂

there is an FX2 as well as FX. the version 2 synth included the FX component. unfortunately they're 32-bit and don't seem to load correct in Sonar (probably need to set them up with my jbridge etc)

i don't often use it within Sonar, but it's been reliable - except when i try to use two instances sync'd, then it may or may not work as expected - but generally works in standlone mode. then again, keeping up with the Scaler forum, there are a lot of things behaving weirdly across OSes and DAW, and the fix is promised for 3.0 😉

besides the usual directory / file name restrictions, things like "~" and "!" also have meanings in many search syntax. https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file

it's definitely broken.

it's definitely broken.

Channel Tools

and this years grammy for best mix goes to Microsoft! yay!

back in the bad old analog days, you ran hot to overcome systemic noise and ensure a good level on the tape. now with digital mostly have a noise floor below -100db, running hot will lead to digital clipping which is a problem unless you like that sound... from the IO unit - most A/D converters are 24-bit - so you need to ensure you're hardware is running low enough to prevent peaks from clipping (or preface the IO with a manual volume control movements / compressor / limiter etc). the DAW will take that input (and presuming it's not clipping) will write that to the file (24-bit or 32-bit). reading from that file (clip), you need to consider the summing of all tracks (into buss(es) or your hardware output). decibels are ratios and logrithmic. if you have a single track (say a stereo live recording) you might just set it to -6db before exporting it for a mastering step. if you have 10 tracks, you might set each to -18db and set the master buss to -6db. and possibly tweak each track gain to reliable and as evenly hit those values before adjusting the volume of each. ultimately adjusting levels depending on the material and export target. i would just use the builting metering of CbB / Sonar as it has enough options for those types of decisions.

Is NPU better than GPU? It depends on what context you are comparing a Neural Processing Unit (NPU) against a Graphics Processing Unit (GPU) since both are integral parts of a computer's processing abilities. GPUs are specifically designed to render complex imagery to handle tasks like video editing and gaming. However, NPUs are designed to work faster with AI tasks, reducing some GPU loads so a system can work more efficiently. The thing is, NPUs tend to be more limited to small, repetitive tasks, whereas GPUs can handle larger and new tasks better. The important thing is that both processors work together to improve a system's overall performance, like in a laptop. What can I use an NPU for? A Neural Processing Unit (NPU) can accelerate AI machine learning tasks such as speech recognition, background blurring in video calls, and photo or video editing processes like object detection. my question is: what is an AI task? i can imagine your Copilot+ PC stopping you to ask all kinds of questions like the software Copilot will tend to do -- "how can i help you now?" stuff... LOL. it will be interesting when someone creates valid benchmarks...

not sure how much "public domain" hip hop and trap music for training is available given the length of time a copyright persists. it's one of those things that the legal system will end up deciding WRT AI training on copyrighted materials.

32-bit files, not 32-bit OS 🙂 (i hope)

reboot the PC?

the Ozone Maximizer (esp the new Ozone 11 version) is very nice esp coupled with the Insight loudness metering. you can set the Maximizer to have a constant level either in or out so you can compare the effect. i usually also add a touch of gentle EQ before the Maximizer to remove a bit of low mids, or push a bit more higher end. i use this on the master buss and not on the monitoring or print busses. if i am sending to mastering, once i have tweaked things here, i'll turn it off and then print about from 26LUFS to -18LUFS (depending on targets) so the engineer has room. i'll also print my "mastered" version as a reference as well. i don't really use the Ozone FX on tracks as i find my other FX typically do what i need. i may on real problem mixes run the Neutron to identify masking issues. e.g. https://www.izotope.com/en/learn/unmasking-your-mix-with-neutron.html

second test - still works on Sonar used stereo interleave on all tracks added PC EQ w/ boost on ~1200hz turned on solo on source tracks used Sonitus EQ on buss A with a couple of boosts

quick test in Sonar - two tracks hard panned, out to buss A, plus sends to an Aux track as well, stereo as expected. with or without the Sonitus EQ. for me it seems to be working as expected. each source track was set to mono interleave with a mono clip. buss = stereo interleave, aux = stereo interleave no FX, no PC on any tracks or buss no solo settings latest Sonar

so tagging someone like @Noel Borthwick would possibly work - Noel - any thoughts on enabling multiple stackable or otherwise floating console views?

pan law settings? corrupt audio file?

search?