Pro Tools 2018.1 low latency monitoring issues

[onbeat]

Same problem as the OP. I am on Windows 10 and have an RME AIO. I read the posts and what works for me is to switch from Quickpunch to normal, then back again. It works until you re-arm the record track on version 2018.7.

[mandal]

One newbie question...
I guess output on the track - must have output "Out 1-2" - and not via a bus (Sub Mix) ?

As long as I have "Out 1-2" on the track - everything seems to work OK in Pro Tools Ultimate 2018.7 - Win10 Home (64-bit)
I'm using hardware Avid Omni & PCIe

[onbeat]

Originally Posted by mandal

One newbie question...
I guess output on the track - must have output "Out 1-2" - and not via a bus (Sub Mix) ?

As long as I have "Out 1-2" on the track - everything seems to work OK in Pro Tools Ultimate 2018.7 - Win10 Home (64-bit)
I'm using hardware Avid Omni & PCIe

They supposedly got rid of that restriction in the latest build. You can use any outputs available with the LLM now.


Sent from my iPad using Tapatalk

[nstu]

Originally Posted by onbeat

Same problem as the OP. I am on Windows 10 and have an RME AIO. I read the posts and what works for me is to switch from Quickpunch to normal, then back again. It works until you re-arm the record track on version 2018.7.

I think that is for now the best work around!
Took me an hour to realize that there is something strange since PT 2018. The last time I recorded was with the 12.7 and there all was fine with my Apollo Setup and Direct Monitoring (and by the way still works with that 12.7. version).

I tried all versions from 2018.1. up to 2018.7 with clean install and deleting prefs - nothing helped.

So is Avid aware that this is a bug inside Pro Tools 2018 or do we all have to open up a support ticket to get a fix on that?

[albee1952]

Well, correct me if I am wrong, but I thought:
#1-LLM only works with Avid hardware
#2-when recording with Apollo, you need to be working within the Apollo mixer window
#3-with any UAD card(internal or external), latency makes tracking with UA plugins impossible(I have a QUAD card internal and every plugin reports at least 1100 samples of plugin latency).
#4-anyone have a chat with the folks at UA on the proper way to make this work?(IOW, I don't think its an Avid issue, I think its a 3rd party hardware issue)

[mandal]

Originally Posted by onbeat

They supposedly got rid of that restriction in the latest build. You can use any outputs available with the LLM now.


Sent from my iPad using Tapatalk

Yes, now it's working...
The trick is:

To maintain (or bypass) sends with Low Latency Monitoring enabled:

Choose Preferences > Mixing and click the Setup tab.
Select (or deselect) the Allow Sends to persist during LLM option.
Click OK.

[onbeat]

Originally Posted by mandal

Yes, now it's working...
The trick is:

To maintain (or bypass) sends with Low Latency Monitoring enabled:

Choose Preferences > Mixing and click the Setup tab.
Select (or deselect) the Allow Sends to persist during LLM option.
Click OK.

That works and it also sticks between sessions and rearming. Thank you!

Edit: Spoke too soon. If you enable the sends, then when you playback to punch in, the armed track will still be muted so you won't hear previous recording.

[michaelevancoe]

Same issues as 2018.1 still not fixed in 2018.7. LLM is completely broken, the armed track is never muted and the new preference option does nothing.

[michaelevancoe]

Originally Posted by Oufti

I tried that but it got worse: with new prefs I have the double signal permanently...
Hopefully I was able to restore the previous prefs (didn't empty the trash) and got back to the previous case

Yup, same thing on my end, resetting prefs has made it so the armed track is never muted at all, the workaround of changing playback engine no longer works.

[Bfrink1971]

I have been working with Avid support with no solution to date. So far the only work around is to toggle Quick Punch on/off. This will resolve the problem until the track(s) are taken out of record.

Avid support had me switch the playback engine to the Pro Tools Aggregate I/O and use the computers internal mic as an input. The problem did not occur when I did this, but returned as soon as I switched the engine back to Apollo Thunderbolt.

I still believe this to be a bug in the software (otherwise, why would toggling quick punch temporarily resolve the issue?).

Hope it gets fixed soon. Posting the above in the hopes that it may give someone with more knowledge than me a clue as to the root of the issue.

Anyone else with an Apollo found a permanent solution?