Unable to monitor my voice while recording. I am using pro tools native 8x8x8 hardware. I have 16 in and 16 out via the card. The signal goes into Logic but does not come back out while recording. Does come out in play back.

Question

Level 1

8 points

Unable to monitor my voice while recording. I am using pro tools native 8x8x8 hardware. I have 16 in and 16 out via the card. The signal goes into Logic but does not come back out while recording. Does come out in play back.

Does anyone else have the problem of not being able to monitor what you are recording in Logic X when using pro tools HD native card and box? The signal goes in but does not come out through assigned out put. Will playback as it does in fact record, but can not monitor it. Hardware is fine because it works fine with protools software.

Logic Pro X, OS X Mountain Lion (10.8.5)

Posted on Oct 22, 2013 2:04 AM

Reply

Answer 1

Eriksimon

Level 6

15,416 points

Oct 22, 2013 2:31 AM in response to Marcus6

Have you enabled Software Monitoring? And track input monitoring on the track(s) to be monitored?

Reply

Answer 2

Marcus6 Author

Level 1

8 points

Oct 22, 2013 2:49 AM in response to Eriksimon

Yes I have tried it this way, but there is a big delay in the monitoring. I used logic 6 a long time ago and never used Software monitoring. I have always used the monitoring via my pro tools hardware cards. The monitoring should work, I think the same way as when Im using pro tools 10 software. However the signal goes in ( I can see it on HD box hardware input) but does not go back out through the hardware and into the output I have assigned it to in my desk. I have checked 'core audio' and the i/o assignments are all correct.

Reply

Answer 3

Eriksimon

Level 6

15,416 points

Oct 22, 2013 3:08 AM in response to Marcus6

In my experience there are two main causes for getting (too much) monitoring delay:

1. If you have latency inducing plugins in your signal chain; usually that gives a delay of typically 30-300 ms, (depending of course on which and how many plugins are set to what values). Short, but already unworkable. Solution: remove Latency inducing plugins from your output channel, or engage Low Latency Mode.

2. Switching to another program that uses audio (music players, webbrowsers) can lead to a latency build up in Logic of a whopping and silly two seconds. The solution for that is to restart coreaudio within Logic: go Logic Pro>Preferences>Audio>Devices>Core audio, disable and re-enable coreaudio, click Apply Changes and you'll have cleared the lag.

But, what may well be a (the?) factor here, Digi coreaudio drivers are well known for their issues. Many say they suck.

Reply

Answer 4

kcstudio

Level 4

1,808 points

Oct 22, 2013 10:40 PM in response to Eriksimon

Eriksimon wrote:
..........
Digi coreaudio drivers are well known for their issues. Many say they suck.

+1 Definitely!

Regards

Reply

Answer 5

Pancenter

Level 6

14,644 points

Oct 22, 2013 11:39 PM in response to Marcus6

Marcus, Logic no longer supports the type of hardware monitoring that was available in Logic 6, the options are no longer available in Logic. You're thinking of DAE and TDM that used to be available in the Audio preferences.

Basically... Apple and Avid/Digi are no longer supporting each other, I think Logic 8 was the last version to support PT hardware.

Reply

Answer 6

Pancenter

Level 6

14,644 points

Oct 23, 2013 12:58 AM in response to Marcus6

Marcus, to further clarify.

At this point you're using Avid/Digi's "Core Audio" drivers, previously you used DAE which addressed the hardware directly, just as Protools does.

To get close to the same latency you will have to run the the Digi Core Audio drivers with the I/O Buffer set at 32 or 64. Unfortunately the Core Audio drivers Avid/Digi provides will break down quickly at those buffer sizes.

You're out of luck on this one.

Reply