Glenn Stanton

spaces matters ?

i just use the VST version in the PC FX chain works fine. the PC version UI definitely is not very usable... it's a really nice compressor when you need fast transient response - i like to use it when i need to "soften" something a bit. pushing it also adds some nice color.

so, something stripped down? +1 - not quite the HW output but really minimal. would you still want FX and PC available? in this example i used the display settings but this would be an actual "type" (like track, bus, aux etc). definitely this would be useful (for me as well).

main "accurate" monitors and center mono speaker are all self-powered. JBL 5.1 speakers and a stereo pair of 12" 3-way Fishers are JVC RX-7000 powered (100/ch) and the Bose 901 are Audio-Centron 250w/ch PA grade power amp (forgot the model offhand). if you're room is not getting the best balanced response for your listening position, as @bdickens noted - you want to adjust things and treat your room.

i use the PC FX chain to host my effects and save each as a preset. then in my templates i have a baseline set of them in use, but can select other presets - so i have the CW effects as default, then Waves, Slate, etc variations. plus instrument variants: acoustic guitar, electric guitar, rock bass, jazz bass, funk bass, lead guitar, lead vox, back vox, etc. also left and right guitar with some preliminary scooping etc to make LR placement not become big mono, etc. also bus presets for instruments, reverbs, delays, etc. so using the PC works for me as i can see the stack of effects and PC fx in a single pane. the track fx box tends to be too small for me.

agreed. i'm think where the projects are more closely aligned and esp if using the BandLab VST plugin, then really CW would be used for the more granular aspects of tweaking audio / samples / midi before reloading into BL.

and longer term - upload a CW bundle to BL - where the project would have used the BandLab VST to provide the instruments which would then be used in BL edits. one example might be BIAB VST (although a much nicer UI is a must), thus allowing full round trip.

it looks like the staff view has the discrepancy between the "page number" and the "measure number". when you zoom out, you can see all the measures (in my example, 31 measures) but when you view it in normal view, the page 17 view doesn't let you see the last few measures and then the display jumps on the next "page", hiding the last few measure. so, it seems yet another (perhaps already known?) bug in the staff view... or perhaps just a wrong page view vs measure view setting? and a print preview seems to show a similar issue of missing measures...

i don't have unify, and there are some other tools which could do this somewhat. i like the frequency split to do things like high-low treatments. in PC, you can create PC effects which have the macro functionality for grouping controls etc. like stacking a pair of PC FX chains and setting an EQ high and in the other EQ low. followed by whatever effects.

nice to be able to use my Slate plugins in it...

there are several plugin bits that need to load as services - such as the Wave Local Server. so, if you don't have those start up with the OS, then you can see a brief delay while they activate, but as noted, once those are services are loaded, the plugin loading is pretty fast. since my DAW uses iLok and Waves, i keep those related services set to automatically start. so my Slate, Waves, and other iLok depedent plugins load quickly.

that would be handy to perhaps have the revision in the title in the file "Reference Guide - 2022.06" etc... even if the file name remains the same.

is this the PDF reference guide, or the help web site? one thing i noticed is the help pages site does not like HTTPS, and when i click on links from the forum or elsewhere i have to reset it to HTTP in order to see images.

so i've tried s number of Wave plugins which are labeled "stereo" (vs "mono/stereo" or "mono"), and a number of other plugins (delays and reverbs) which aren't marked as to whether they are purely stereo (which for this discussion, i'm assuming we mean two distinct channels which may some some mix/blend options - like the sonitus plugins do), and 100% they all follow the interleave as expected. the only plugins (out of 30 or so) that behave with the interleave change not acknowledged - so far - are the sonitus ones. Will - if you have some other examples of true stereo plugins i'll try them out if i have them (or they're free ? ). this whole interleave thing would be problematic since i have a whole set of CW specific presets with sonitus delay and reverbs that i use frequently...

when i try it, the sonitus reverb behaves as you show in your video - the mono interleave and mono track show the reverb as "stereo". bounce to clip then causes it to behave as "mono". the changing the interleave on the track to stereo and back to mono causes it to go back to the "stereo" mode. however, when i tried H-Reverb and Breverb - they are both "mono" on the track mono interleave, and if i switch the bus to mono and the track to stereo, the output is of the bus is "mono" and the track also (metering) is mono. bounce to clip etc has no change on those two reverbs. only the interleaves. mono track = mono track reverb, stereo track = stereo reverb. so based on this limited testing - it may be the sonitus reverb is not behaving correctly in following the interleave of the track or bus. it should be mono if the track is mono, and changing the interleave to stereo should be stereo. not sure why the bounce to clip triggers it to follow the interleave. the other reverbs do what i would expect. EDIT ok so i tried it with the sonitus delay - making it ping pong for most effect - same issue. the interleave is not followed in the track until the bounce to clip. the h-delay behaved as expected - bounce to clip did not change its behavior when following interleave. so maybe a bug with something in the sonitus plugins not following / listening to the track interleave? if i have some time later i'll try some modulation etc effects.

of course, davie504 is one of the greats...

might be a nice enhancement to have duplicate file names get an appended (###) (number incrementing) so the export doesn't "fail" (e.g. if you copy a file and paste it into the same folder, the file gets an incremented value). although if track # is included, chances are the file will be unique all other values being the same. for people using naming which results in duplicates, they would have to then do something to manage the file naming outside of th export function.

agreed. even a "student" (30" scale or so) can be a guitarists friend as they're usually pretty easy to play and the Ibanez Mikro is decent and cheap enough. i just got a Kala U-BASS for those times when i don't feel like pulling out my full-size P-bass. it's a pretty cool instrument...

the ample bass plugin needs MIDI. you can drag your guitar audio to a MIDI track and it should convert. one thing i do - i apply a HP filter to remove some of the potential noise, and also a LP to remove squeaks etc. then convert (although i have Melodyne studio, if you have the basic Melodyne you should be able to convert it). once you have the MIDI you can do any cleanup on the MIDI (including any quantizing etc). then assign that as the MIDI input to the plugin. this works with SI-BASS, etc. as a note, you might need to transpose it down an octave.

if i flip mono-stereo setting on either the main or aux, there is no change in terms of polarity null testing. the patch point is stereo at all times and doesn't have any processing on it. so if i set the main to mono (+3db from a stereo source file) it just transfers through the PP. selecting a L-R-S from the PP is effectively the same because the source is mono. setting aux to mono, main to stereo, same dealio - the PP is stereo, doesn't care, and there is no summing, so no changes. = -> = -> - = -> = -> = m pp a - -> = -> = - -> = -> - only time i get not-null is panning which does shift the relationship (hence the reason i originally mentioned panning)

yes. and the send inputs seems to be working as expected (for me) on patch points and aux tracks ?

AUX-PP-NULL.cwb this is my test file.

it's silent when i set it up to both main and aux to a master bus with aux set to 180° polarity. mono or stereo. panning all centered. i'm not seeing seeing this except if i pan the main or the aux track, then it varies in the bus. if i set the send to follow the track pan, and reset the pan, then its silent. changing the pan law with the panning impacts the amount passed when not centered. so from my perspective, this seems to be working as expected. as a note i'm using a -20db pink noise calibration file as the source.

as noted in your other thread on this topic you should spend some time to learn how to edit midi - note durations, grid, etc. if you enter a note which is 1/8, and need it to be 1, then stretch it. pretty basic. this is an area where a few minutes of reading the manual and some practice it will become second nature.

you could just create 2 tracks - one with the keys, and one with the click. make the tracks mono - then you can pan one left and one right. export as stereo.