Skip navigation

Input monitoring not working

751 Views 7 Replies Latest reply: Dec 6, 2012 6:23 PM by Pancenter RSS
the-design-guy Level 1 Level 1 (0 points)
Currently Being Moderated
Dec 4, 2012 6:08 PM

I had a couple of guys over for a recording session today and ran into a problem with the Independent Input Monitoring function. I had both "Software Monitoring" and "Independent Input Monitoring" checked in Preferences > Audio > Core Audio, and Auto Input Monitoring checked under the Options > Audio menu.

 

When I record-enabled tracks, the fader had NO effect on the monitoring level. One keyboard track was so loud, I had to cut the input level unacceptably low just so the other players could hear themselves. Am I missing something here? I don't recall having this problem in the past. I'm not sure what settings might have changed.

 

I have recently added a Mackie Onyx Blackbird to my TC StudioKonnekt to get some more input channels, but I don't see why this would affect the software monitoring. I just created a new file to see if there might have been some problem with the file I recorded earlier. No luck. Same problem.

 

******BREAK******

 

After writing that last paragraph, I did some additional testing and verified that the channels that aren't affected by the fader are the ones that are being input through the Blackbird (which is connected via ADAT lightpipe to my TC Studio Konnekt). Meaning, I guess, I have to adjust the monitor levels of the channels hooked up to the Blackbird using the Blackbird Control software mixer (which, as far as I can tell is as unstable as the TC Near software that came with the Studio Konnekt). Hopefully this will solve the problem, but thought I'd post this anyway in case others had the same issue. I guess another option is to create an Aggregate audio device with the TC and the Blackbird. That'll be my next waste of an hour or two...

 

 

Using Logic Pro 9.1.8, System 10.8.2, on a mid-2007 iMac 2.8 GHz

iMac, OS X Mountain Lion (10.8.2), 2.8 GHz, Core 2 Duo
  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Dec 5, 2012 12:29 PM (in response to the-design-guy)

    Just curious as to your final results.

     

    Since you're using ADAT into the TC unit do you have The Onyx as the Master digital clock and the TC set to slave to incoming digital clock on the ADAT line?

  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Dec 5, 2012 4:40 PM (in response to the-design-guy)

    Thanks for the reply, If I remember correctly they still recommend syncing the two units together by digital clock. s/pdif or optical.

     

    http://support.apple.com/kb/HT1215

     

    They show wordclock in the aggregate tutorial but you could use the Onyx as master clock and the TC as slave.

    The first unit in a digital link setup is almost always (if not always) the master clock.

     

    However, if it's working without dropouts or digital hash at random intervals, why change!  :-)

     

    Unfortunately, an aggregate device will never give you the ability to software monitor at low latency

  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Dec 5, 2012 6:05 PM (in response to the-design-guy)

    Thanks for posting the pic and info.

     

    I'd appreciate it if you would post back what you come up with regarding powering up the units and any other issues you might have.

  • Pancenter Level 5 Level 5 (7,505 points)
    Currently Being Moderated
    Dec 6, 2012 6:23 PM (in response to the-design-guy)

    Thanks for getting back...

     

    Having installed digital patchbays in a couple of studios I can confirm the way you now have digital clock is the correct and most trouble free method, that's why I mentioned it earlier. The first unit in a digital chain (the Onyx in this case) is always the master, at least in all scenarios I've worked with.

     

    Good luck-

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.