guavadude Posted May 11, 2022 Share Posted May 11, 2022 Just fired up my new Studio Max and now when I hover over a plugin to get its latency in ms, it shows for example 419 samples=0 sec. every reading is =0 sec. I need to try a limiter and see what that says but other plugins I know were 5ms on my Trashcan at 256 buffer now show 0 sec. On my Max set at 64 buffer, I can’t tell if there’s just so much less plugin latency, which would be great or if Logic is now only showing in seconds and not ms which wouldn’t be great. I’ll do more tests. Does plugin induced latency change with buffer settings? With different processors? Quote Link to comment Share on other sites More sharing options...
des99 Posted May 11, 2022 Share Posted May 11, 2022 Yes, this is a known issue that affects Logic running on Monterey, in the main... It looks to just be a display issue with the rounding of numbers into seconds (which is obviously not useful...) 1 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted May 11, 2022 Share Posted May 11, 2022 A few others have reported it and as des99 said it's tied to Monterey. 1 Quote Link to comment Share on other sites More sharing options...
guavadude Posted May 11, 2022 Author Share Posted May 11, 2022 Bummer. Well I guess a workaround would be to set the low latency threshold low and use the LL mode to see which plugins are over that amount. 2 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted May 11, 2022 Share Posted May 11, 2022 Yes indeed that's a workaround. Hopefully this bug will soon be squashed! Quote Link to comment Share on other sites More sharing options...
JBberg Posted August 26, 2023 Share Posted August 26, 2023 I'm on Ventura and have the same issue. All plugin latency shows as x amount samples and 0 seconds. Annoying. The samples also do not change when changing for example a lookahead time. 1 Quote Link to comment Share on other sites More sharing options...
Easy Velvet Posted February 1 Share Posted February 1 Hi there, thx you all for all thoses years of chatting around Logic, i've learn a lot here. Same issue still there on OS Ventura 13.6.3 / Logic 10.8.1 / M1 Would be great to have the equivalence in ms from the latency sample numbers, And even more... for each track or bus: A SUM OF THE LATENCY caused by the plugins on that track or bus! At least, would could see on which track all the other ones are lignin up. Quote Link to comment Share on other sites More sharing options...
thesheep Posted March 27 Share Posted March 27 Yeah still like this for me after almost 2 years. I guess if we know the sample rate (e.g. 48kHz) then we could just calculate it by dividing the number of samples of latency by the sample rate? So if a plugin has latency of 200 samples then that would be 200/48000 = about 4ms? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.