Glenn Stanton

you can also see the 32 or 64 bit in the FX browser. and i also use the VST Inventory program to periodically collect the plugins registered with CW

i've found ASIO4ALL useful - however - i cleaned up all my other "ASIO" drivers and generally cleaned out any extraneous audio drivers. so now i have my Intel non-ASIO drivers, IMC ASIO, and ASIO4ALL. mostly use the WASAPI shared or exclusive modes. some VI require an "even boundary on 8" sample setting, and the WASAPI modes often fall on odd numbers (e.g. 441 vs 384 or 512). this is where the ASIO4ALL is handy - i can set it on an even boundary (it defaults to those), get my VI work completed, render to audio, then go back to my regular drivers. and then, unless i'm really in love with the VI, i'll relegate it to "do not use unless necessary", and a few VI were so annoying with the sample settings, i uninstalled them. edit: forgot i have the Tascam DX ASIO driver as well for when i use my DX for recording. that one works really well and has never given me a problem (then again, the UMC ASIO driver is pretty solid as well)

all 70+ tracks have clips playing at the same time?

also - more curiosity - is the reason for manipulating so many tracks gain due to a) too hot a record level? b) too low a record level? c) using a VI but not using the VI volume control? for me, i tend to check inbound client files for volume levels, noise, etc are part of prep, or if they're my own sourced files / clips - making sure the peak levels are min -12db or more likely -18db. so i seldom have to touch gain controls unless i want the track to be a bit more hot going into the FX.

it took me a few times to finally get the main variations in the export dialog understood. then i discovered "tasks". so being lazy, i set up a few tasks which default to "mix" based on my "print" buss (a buss defined to take the master output). and a "tracks" tasks which outputs the tracks - full length all - to an "audio export\tracks" folder (which i create on my recording projects). saved into my record and mix templates. then, in a project, i "recall" the settings, tweak some of the selections and the time length, "update", and then run tasks. now i get my mix and my tracks exported together or one or the other. otoh - i think the UI is good for me as i'm often using complex export/import functionality for my drafting and rendering work, but if you're not used to a complex I/O UI + the idea that a) "entire mix" is somewhat ambiguous and maybe calling it/adding "hardware output"? b) the module and the dialog have some conflicting concepts (?) which need to be rationalised...

hopefully in your walk-in subzero refrigerator set at 5% humidity

any reason you chose to use plugins instead of the native gain control? curious.

@Victor Flores check your notification settings on the sub-forum - the "following" settings let you choose how you want to be notified (or not).

does the BlueCat gain plugin probably doesn't support the ctrl-move like the native gain control. also, if you have any automation enabled, this can cause the level to snap to what value was set using the automation. if you do have automation enabled, you can use the ctrl key on that track to make the change - ie.e say you're set at 0db, holding the ctrl key while dragging the volume down should let you change the value.

i've been using the export feature to dump all the tracks from a MIDI/VI only project then importing and placing on my audio mix template project. similar to how i would do it if a client sent me files. since my record template has the same naming and ordering as the mix template, and then the export conveniently names all my tracks. couple of things - set the output name as {trackname} (unless you need more complexity - like raw vs FX printed), set to follow source (stereo / mono), 24-bit (or more), and turn off the dithering. i can then grab all the files and drag them into my project and then drag them to their respective tracks (all to zero). if you need to have them position themselves on the timeline - export as broadcast WAV. and then use shift when moving to keep them aligned. but @57Gregy has it correct - if you're copying from one open project to another - make sure the location and track are selected before pasting. i generally will ensure my clips are trimmed to minimise the leads and tails so i have a clear space to paste into ? ---------------------------------------- as a note: since deciding to separate the "recording" process from the "mixing" process - i.e. get a good set of tracks recorded and all reasonably balanced - whether live or VI performances - really makes my mixing process much easier if i'm not tempted to touch the VI settings or just not having the overhead, so much smoother. and if i need to "re-record" a VI, easy enough to go to the recording project, tweak, re-export/import that track (or 2 || 3 etc.) using the same techniques for printed FX vs "DI" instrument tracks etc. and since i'm still using a very under powered laptop at the moment, the reduction in overhead from not having VI in the mix project means i have more headroom for the stuff that matters to the mix... anyhoos my 2¢

yeah, i was thinking it could get "too granular" if you factor in automation changes expressed in a csv ?, but in general -- per track / bus metadata + media + fx + general settings on them (if an option to extract) would likely answer most people's desire for project details sufficient to recreate the majority of it from scratch.

hmmmm. do you have a lot of software installations going on as well? i've found something my runtime get out of sync (even when they're supposed to be the same and backwards compatible) because of other products. so, once i done updates on my software (MS, audio and drafting products etc), i re-run the CbB runtimes and my Sketchup runtimes, then install the CbB and SU updates. generally they are then stable against interference from other products. sometimes renaming the cakewalk.ini to .old also helps in case an update needs new entries and somehow they didn't mesh correctly...

that would be amazingly handy.

^^^^ yeah, my laptop is not very powerful so when using effects or VI i like to limit them and just take "completed" audio over. makes the overall mix process lighter. so i'll setup my MIDI-only tracks in its own "record template", tweak, and then export the audio tracks. then import into my "mix template". essentially, following the same mix process is if a client sent me a bunch of tracks...

if you find your track levels are fairly consistent for the duration - you can set your fader to say -6db, then adjust gain to about -18db to -12db on your meter. this way most of your levels are in a good range for mixing. and you'll get some more consistency on plugins. this works decently for live situations as well - get your monitoring set, then (on small gigs) bring up FOH to blend, or large gigs to whatever levels you've contracted for... ? and you have plenty of room to adjust individual performances and keep the monitoring stable...

one thing i've been doing lately - create a 2-track export of the main project - only what i need for the vocal performance, then create a project with that export on one track and then do all of the vocals and edits. then when i've got the vocals mostly comped etc i can then export those tracks and import into the main project. this keeps things fairly clean and then i can go back to editing the main project without overloading it with lots of additional vocal / take lanes tracks and edit-effects. reduces the overall size versus copying the entire main file (e.g. my main file might have 2.5GB of track audio, whereas the export might only be 50mb)

i'm a fan of AI - so long as it works offline as well as online... i like the idea of letting computers do a lot of work for me....

where does it go next. a matching keyboard lol https://cosmomusic.ca/products/pianoarc-brock360-circular-keyboard

cancelling guitar... the reviews are in: The Friendly Angle: "George Harrison is turning over in his grave" The National Conant: "Seriously, you need help, but it is kinda cool" The NY Times: "We're going to hunt you down and end you" Mom: "What the f*** is wrong with you! i didn't raise you like this!" really it started by playing around with the LABS voices thingie and it sounded neat as a harmony part... and it just went from there.

i went through my apps first - find all of the ones listed as ASIO. then go through the registry and finding all references to those or others not listed in the apps. then rechecking to see if any more were cropping up and hunting those down. and lastly, finding all the program files and removing those (most are in directories, some were individual files)

i have a few generators i use like scaler, chordz, ripchord, and a few more more i can't remember but they let me create arpeggios / sequences etc which i feed to the plugin via MIDI... but i see - you have an arpeggiator on the plugin want that to be output as MIDI... so if you check the plugin settings in the plugin manager plug-in properties -> details -- it needs to support event output = yes in this example - chordz is a generator, that's its job... maybe there is a way to "drag" the sequence onto a MIDI track. Scaler and a few other generators work like that.

very very slow (on my laptop) but the extraction of the bass, drums, and vocals was impressive. it created an "others.wav" which was a combination of organ, rhythm guitar and lead guitar tracks (a 7 tracks total song - took about 20 minutes) - loads of reverb (which was preserved with each track!) the drums had both the drums and the congas. there are a couple of songs i wanted to remix for a bit but lost the source tracks or are live stereo recordings of a 4-piece band so it will be interesting to see how that works for enabling the remixes. but the quality is very high, and for a source mp3 - quality was really clean. the fact it had the reverb intact with just the instrument was shocking. very cool program.

definitely staying away from this one ... ?

i went through and removed every ASIO driver that various software had installed: ASIO4ALL, Generic Low Latency ASIO, MAGIX 2016, etc... even my UMC driver. i think 8 total. then i reinstalled my UMC, and the ASIO4ALL (2015 release). oddly enough, most of the amp sims (TONEX, TH-U, Guitar Rig, and the older (32-bit) standalone keyboard apps all play very nicely with low latency on the ASIO4ALL and are worse on the UMC and the WASAPI. long buffer delays (even when trying to set them low), stuttering, crackling. but then, when i play them through CbB - ASIO4ALL - not bad but not great latency, WASAPI exclusive - nice, better latency, WASAPI shared - pretty much the same as exclusive, and UMC - best. low latency, no stuttering and crackling. generally speaking i've seldom used the ASIO4ALL but when using my standalone apps, i've made it the default for those.

of course it helps if you're a recording/mixing/producing genius like Steve...