Glenn Stanton

thanks! i actually did have more on it originally but i liked it a bit dryer, made it feel "closer"

the cache will be replenished when you install plugins but it can be greatly reduced by clearing old stuff first ? i think mine is 980MB

check out some CAL scripts to strip out the majority of notes - i've used the "lowest note only" script (i'll have to see if i can remember the exact name) to strip out the chord info and leave only the bottom notes which then if transpose as needed for the strumming mode. lately i just play the single note on the guitar or keyboard to get the strumming. i've found the Session Guitarist very nice but you tend to have to play it differently than GS-2 because the SG are using sampled playing and the strums don't always end once the note is off - a good thing in many cases, whereas GS-2 is synthetic all the way so it's more responsive. key switching is also important to consider. i tend to do the key switching as i play it out on my keyboard rather than waiting for later. depends of course on what my source is - if existing or already performed strumming - CAL script or manual edits, otherwise i just play it intending to use a virtual instrument.

yeah, my Waves folder is about the @ 9.6GB (after clearing cache and using on v11/v12 plugins), Slate @ 7.7GB, CbB @ 3.5GB (Dim Pro, etc), Kontakt libraries @ 15GB total - but they're all on the D drive where i have content and project files. within the Waves folder are all kinds of file types which are the working bits and only the shell DLL are in the VST and VST3 directories.

just another love song

just in case we're losing track of the testing effort here ?

i don't recall having issues in v8 ( i started using CW in v3) but maybe this will help: http://www.cakewalk.com/Documentation?product=SONAR&language=3&help=Playback.27.html it seems like the compatibility setting is more for correcting things from a previous version... Pan Law compatibility mode When using a non-default pan law with floating point or 24-bit audio, Cakewalk would previously apply the pan law twice; once at the clip level and once more at the track level. In SONAR 8.5.2 and later, pan laws are only applied once at the track level and only for mono tracks. Any clip pan envelopes will continue to work, but behave strictly as a balance control. If you have existing projects that use a non-default pan law (i.e. other than 0dB center sin/cos taper), the mix might sound louder in Cakewalk.

brillant! i thought there was something like this as well, but being a context menu guy, i was looking for it under a context menu option...

yeah, for some reason i find a bunch of stuff hiding in the (x86) including 32-bit apps when i'm pretty specific about 64-bit versions only... thanks for the link to the treesize, i'll give it a try.

i use the WinDirStat app periodically to find folders that are "heavy" - Waves, and a number of products including Slate, any number of virtual instruments etc often install some large libraries and supporting files into the ProgramFiles and Documents folders as well as Program Files folders. i think at this point i have about 30 links to move this stuff off my C:/ drive on onto my contents drive.

my apologies - i mixed up some responses you made in another thread with @msmcleod

agreed - bouncing down was something done to handle track limits. and there are pros and cons to it - one pro - you're forced to make mix decisions early ? cons - if your early mix decisions are wrong you need to re-assemble all the tracks, copy overs, etc to get back... lot's of "imperfections" from the old days, but then again, great song writing conquers all... for me - my default template uses tracks -> sub-mix busses -> stem busses -> master mix busses. so i can pick which level of granularity i want to change things, and exporting parts, stems, or mixes are reasonably obtainable within my normal workflow. i can solo "stem" sections to see vocals vs low end vs instruments etc and make changes on the sub-mix or tracks as needed. and adding additional stem busses if needed. some projects i do for other folks they may want 6-8 stems for the mastering process - vox up/down, solos up/down, etc type of things.

sorry - i though t to add it to your suggestion, and in case you didn't know about it.

@scook there is also a feature called "Flatten Comp" which creates a new take lane composed of all the other (comped) takes and then solos it (in take lane, not track). the take shows an "unlock" icon which indicates the "clip data" is locked - it's not (apparently) a destructive operation as the takes are in one WAV file and the new one is in another WAV file.

that would be a handy feature - i'd caveat by saying it might be nice to have something like this as a "bounce to clip" function where i could select a number of tracks and do a fast bounce to a new clip/new track with the source track effects etc being applied. something much faster than a "record" activity.

correct, you cannot create a link if a conflicting name exists - so copy the original folder first, "x out" the old dir, then do the mklink. this way the old directory is still there as a backup, as well as the copy you made (the new target). if it all checks out, then delete the x'd out folder. Copy C:\Users\MyName\OldDir -> D:\Settings\Product\OldDir C:\Users\MyName\OldDir -> C:\Users\MyName\OldDir.X mklink /J "C:\Users\MyName\OldDir" "D:\Settings\Product\OldDir"

one thing to note: if you can hear them, they can hear you ? so all your impact noises, music, speaking, chair dragging, etc. the proper solution will require several things: you need to add additional mass and preferably some damping to the floor above - and depending on the actual framing etc structure there will be limits due to weight as well as door openings etc. as a general rule, the quieter you make certain sections the more other sections will appear louder - so best to plan on extensive coverage rather than spot coverage. one option is mass loaded vinyl under concrete board, covered with underlayment and carpet - you'll be raising the floor about 30mm and this not going to be as effective compared to changing the ceiling below to prevent sound coming up. the upper stairs floor mass, if doing the suspended ceiling, can be added between the joists along with insulation to fill the cavities. and you need to put in a suspended (or otherwise decoupled) ceiling downstairs. this is best accomplished with spring isolators, hat channel, and 2x drywall layers.

you should use the junction /J setting as this creates a hard link to the directory Creates a symbolic link. MKLINK [[/D] | [/H] | [/J]] Link Target /D Creates a directory symbolic link. Default is a file symbolic link. /H Creates a hard link instead of a symbolic link. /J Creates a Directory Junction. Link Specifies the new symbolic link name. Target Specifies the path (relative or absolute) that the new link refers to.

what happens if you bounce to clip first? it seems likely that a clip not bounced (effectively locked) could be prone to errors if there is some offsets in the audio being stretched.

or remap it via mklink command - this way you can put all your presets onto another drive / location and the app thinks its the original

i just downloaded today - lot's of warnings from Microsoft - ultimately it's the MS "reputation check" settings interfering with downloads. the AV scans showed nothing untoward, so i installed and played around with it. seems good here.

i'm using the fabulous Minimalistic Orange Faders by Brian Walton

excellent, i didn't notice it and i was looking all over, and boom, there it is!

i could just put the MIDI on the instrument track. but i found that i can reuse the same midi track on other instruments to see how it works without having to move it around. and once i go into mixing mode, i just hide all muted tracks so it gets simpler pretty quickly. and i'm in the "buss" side of the equation so it's about 12 channels of instruments (if using all) and 4-5 ambience busses, and 3-4 stem busses. the latter i don't really change until i think the mix is overall balanced, then the stems are the final check and adjust - vocals up/down (in my case mostly down ? ) lows up/down, etc. lastly a noise injection test maybe some slight tweaks on the sub-mix busses, a quick "mastering simulation check" by engaging a -6db limiter threshold and a tilt EQ - see if things are still ok at the increased volume - levels, harshness, etc. the template with all 15 soft-synths, and another ~50 effects (mainly the PC EQ, a few reverbs and compressors) across 48 tracks, and 20 or busses, i think a new project from the template takes maybe 25-30 seconds to load up. most of the soft-synth and effects are turned off and/or muted so loading is fairly low esp during recording (i'll set the ASIO down to 5ms - about 240 samples) and then during mix up to 2048 samples to reduce load when engaging/adding the effects.

is this some configuration setting i'm missing?