1. Didja accidentally blow through the whole, "We're using our real names" thing on registration? No problem, just send me (Mike) a Conversation message and I'll get you sorted, by which I mean hammered-into-obedient-line because I'm SO about having a lot of individuality-destroying, oppressive shit all over my forum.
    Dismiss Notice
  2. You're only as good as the harshest criticism you're willing to hear.
    Dismiss Notice

Microphones when Writing vs. Bouncing

Discussion in 'Tips, Tricks & Talk' started by John Mears, Jul 9, 2017.

  1. Big thanks to Mike for the new community. A main problem I feel I run into is when a library doesn't offer a mic mix option- for instance Hollywood Strings, but then another does for instance Berlin WW. Would the recommended workflow involve only composing with TREE mics? If you later add close mics for definition do you then back off the level of the entire track to compensate for added volume of the additional mic. I jack up my levels each time I finish a tune and start dicking around with mics. I noticed Mike said he works with HWS and BWW, so I was just wondering!

    Thanks-
    JOHN
     
  2. I just use Decca Tree Mics when writing. My template would fall over otherwise. I also think Decca sounds great. Then at the end, when I have finished writing a track/cue I switch on other Mics to suit and therefore have enough RAM to be able to cope with it! ;)
     
    John Mears likes this.
  3. I'm with ya on using the Tree mics while writing and dialing in the others when going to mixdown.

    There's a really fast way of doing it, maybe you already know this. Most libs allow the mix sliders / purge buttons to be CC mapped. I then drop a ReaControlMIDI (I work in Reaper) on a separate which lets me assign its faders to a specific MIDI CC number and then control them with the mouse or using automation. I assign the faders accordingly for the specific library's mic sliders, and then send the track MIDI in "omni" to the track(s) that the Kontakt is on. That way I can control the entire mix for all the different instruments from one library with one slider.

    If I need slider automation to adjust mic volumes throughout the mix, rather than automating the ReaControlMIDI sliders, I would save a preset for ReaControlMIDI inside Reaper for different mic mixes, then drop a MIDI clip on the track that ReaControlMIDI resides on and dial in a Program Change which triggers different presets, which change the mic mixes.

    I find this incredibly useful and fast when experimenting especially with drums as I can create different "takes" of a midi clip, each with its own program change and switch between different RCM presets/mic mixes (closer and more dry, or "bigger" and more wet, etc.) with one shortcut for changing takes, which is "T" on my keyboard. Awesome for A/B-ing without having to bounce or have duplicate instruments.

    While this is for Reaper, I figure all bigger DAWs have their own ways of doing this sort of thing.
     
    Krzysztof Fokow likes this.
  4. Yeah I have all Mic positions assigned to physical faders on my Fadermaster Pro. It's a godsend!
     
  5. Same here....on my Launch Control XL. Saves a lot of time.
     
  6. So technically does this mean there is a CC# assigned to the fader? So i.e. cc33 is assigned to your hardware fader, then in KONTAKT you manually assign cc33 to close microphones in Albion, etc???
     
  7. The faster way for me was to change the CC# of a knob on my Launch Control to the default CC for Spitfire mic faders (I forgot the actual CC#s). This way, if I want to change the complexion of an entire piece, I can grab all of the Spitfire midi tracks, tweak two knobs and get a completely different sound.
     
    Noam Levy likes this.

Share This Page