Jump to content

Sluggish UI Performance After Bouncing Comp.


pjl

Recommended Posts

I wonder if anyone else has had this problem.  If I record multiple audio passes into a take folder and swipe a comp everything works well.  However, if I bounce that comp on place then suddenly the GUI responds very sluggishly.  Dragging a region or swiping to change the comp takes 2-4 seconds for the interface to respond.

I'm using version 10.6.3 on Catalina.

Link to comment
Share on other sites

1 hour ago, Atlas007 said:

Have you tried to save your project, and cold your Mac?

Yes, that generally works.  Often I just need to close and restart Logic but it's a nuisance to have to do even that after every audio comp as it takes nearly a minute to close and reload the project.

Link to comment
Share on other sites

  • 2 weeks later...

Well, I can't explain what was going on here.  I had this problem for a week or more.  At first, restarting Logic would solve it until I did the next bounce but sometimes even that didn't work.  I'd record some new takes but the problem would persist.

A couple of days later I recorded some new takes, made some comps and bounced them.  The problem had simply vanished.  Same project, I have no idea what I did differently, if anything.

I can't explain it but something changed things and the sluggishness went away.  I guess I just need to put it down to one of those unexplained behaviours that happen occasionally either by obscure software bug or just plain user ignorance.

Anyway, it all seems to be working as expected now so I can get back to concentrating on the project.

Sincere thanks to Atlas007 for your assistance.

Link to comment
Share on other sites

On 7/21/2022 at 7:57 AM, pjl said:

Dragging a region or swiping to change the comp takes 2-4 seconds for the interface to respond.

When I've experienced that with Logic Pro, this was due to an unusually high number of items somewhere in the Logic Pro projects. Items could be regions (like several hundred regions), undo steps in the undo history, or other things. 

I remember once getting a project sent to me that was very slow to react to anything, until I found out that there were several hundred markers in the marker list. I deleted them all and the project was snappy again.

Hope that helps. 

Link to comment
Share on other sites

There's something we often don't thing about, this is Spotlight. Many applications, like Logic obvioulsy, rely on that to manage the files they need to access. If they have difficulties to find the files everything is slowed down. Sometimes rebuilding the index of Spotlight can help. Either for the main drive and also for the external drives where we usualy have our soundfiles.

Edited by FLH3
Link to comment
Share on other sites

5 minutes ago, FLH3 said:

There's something we often don't thing about, this is Spotlight. Many applications, like Logic obvioulsy, rely on that to manage the files they need to access. If they have difficulties to find the files everything is slowed down. Sometimes rebuilding the index of Spotlight can help. Either for the main drive and also for the external drives where we usualy have our soundfiles.

A spotlight index issue may slow down some processes, but not typical non-destructive edits like dragging regions or swiping a comp, which is processed directly in RAM. 

  • Like 1
Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...