For Logic(or ex) Logic users only.. Does the PDC automation/visual timing issue bother you?

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic

Does Logic's PDC related automation/visual timing issues bother you?

Yes it bothers me, but I am sticking with Logic
2
10%
I am aware of the issue but am happy the way it is
4
20%
Yes, so I avoid using any very latent plugins in Logic as a workaround
1
5%
Yes, so I am now migrating or have migrated to an alternative DAW
2
10%
I have never noticed this issue
11
55%
 
Total votes: 20

RELATED
PRODUCTS

Post

[DELETED]
Last edited by ObsoleteAcc99 on Mon Feb 29, 2016 4:32 pm, edited 2 times in total.

Post

I've only noticed this on Logic 9.x on Mavericks, and it's a bug specific to the EQ plugin using the analyzer. It's severe, where everything in the UI stops responding to user actions, while playing. It eventually catches up, but it can take almost a minute.

As for the kind of latency you're describing, I guess I don't use enough latency-causing plugins. Can you describe a setup that causes this?
- dysamoria.com
my music @ SoundCloud

Post

I personally would say the GUI lag is annoying however user settings can cause this to be much more laggy. Make sure your using a high buffer size if your not recording audio (what I do, is if I decide to record audio go into setting and turn buffer down as low as 128, but right after recording I'll go back up to 1024.)

Also make sure you have compensation for volume pan and plug in parameters. At default logic doesn't include plugin parameters and you have to enable it via drop down.

But even if you are doing everything right, there is still some annoying lag

I think we can expect the logic team to accomplish this soon enough. They know they need to change make a real time audio engine, and we can only hope automation timing would be another thing they check off the list while fixing the audio engines lag.
Bitwig 6 • Diva, Dune, Serum, and UVI Falcon are my Daily Drivers • Drum Machines • Harrison 32c + DSM 3 + American Class A Enjoyer • Apple M4 Max • Apollo User • DJ • Dance Music is life

Post

[DELETED]

Post

Well... The buffer size def helps with my Latent UAD plugs..

just repeating because you quickly dismissed it.
Bitwig 6 • Diva, Dune, Serum, and UVI Falcon are my Daily Drivers • Drum Machines • Harrison 32c + DSM 3 + American Class A Enjoyer • Apple M4 Max • Apollo User • DJ • Dance Music is life

Post

[DELETED]

Post

Found this old thread and want to say I 100% agree with you. It makes doing any sort of precise hand/drawn automation based on hearing (not visually) impossible, not to mention the problems that happen when scoring to film. I use a lot of UAD plugins, and quickly made the connection that if I wanted to avoid the visuals no longer lining up with what I was hearing, I had to stop using them. Its one of the reasons I switched to Cubase last year. Though cubase has its fair share of annoyances, overall I'm finding less major show stopping issues like these.
My progressive rock band - free demos here!! (and if you do listen please let me know what you think!) http://www.aeonsatori.com/news/free-downloads

Post

[DELETED]

Post

I don't use (or rarely) plugins that induce enough latency, so for me it's not an issue.
If I did use those plugins, I'm sure it would annoy the crap out of me.
My other host is Bruce Forsyth

Post

[DELETED]

Post

TheoM wrote:
spaceman wrote:I don't use (or rarely) plugins that induce enough latency, so for me it's not an issue.
If I did use those plugins, I'm sure it would annoy the crap out of me.
yeah that's the way around it.. avoid dsp powered plugins, nebula, and linear phase eqs/multi band comps, and you will never ever notice it.. having a few plugins in a project with a few samples latency here and there will not affect automation timing in any perceptive way, not even in heavily quantized EDM.

The other thing is that it only happens in a certain order.. i.e you have to be trying to automate the latent plug itself, on an audio track OR instrument track (you can automate a latent plugin with perfect timing on a bus believe it or not), or you have to be trying to automate a "normal", non latent or very low latency plugin that is placed in the chain *before* a latent plugin, then the automation of the NON latent plugin is thrown out by the latency of the LATENT plugin after it. Even all the pro DAW video course gurus have confirmed this issue and created entire workshops on how to work around it. Yet people in this topic dispute it like it doesn't exist (again, they don't understand the issue Yves, thankfully you and a couple others do).

For someone like me whose entire project's FX plugins are 95% DSP, it is a nightmare with no real work around at all. If i hadn't gone to UAD, i wouldn't have really left logic I guess. But the quality of my mixes have improved so much simply because i can get much better results mixing with uad plugins, that they are a must have for me. You also have to be careful even using stuff like ozone advanced because all it's modules have a fair bit of latency, same with things like waves tune, izotope nectar, breath controllers (700ms latency), etc. Or don't automate plugins in the same signal path as the latent ones, if they are placed before them. So try and work around and make the routing suit the automation timing. And so on.

or just use cubase or PT, which just work no matter what you have anywhere.
I'd be pretty pissed off if I had to deal with that when using (rather expensive) DSP plugins.
And it baffles me that Apple have still not fixed this.
My other host is Bruce Forsyth

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”