The list of Talend Components presents all components and connectors, describes their function, and presents a compatibility matrix with the different versions of Talend Open Studio. Download drivers, software, firmware and manuals for your Canon product and get access to online technical support resources and troubleshooting. We use cookies to provide you with the best possible experience in your interactions with Canon and on our website.
![]()
Hi all!I'm a composer and I work every day in Logic Pro, and have been using it for the last several years. About two weeks ago, I installed Logic Pro 10.1.1 at the Mac Store's prompting. I'm running a MacBook Pro 2.4 GHz with 8Gb RAM, and Yosemite 10.10.3. Since starting to use the new version of Logic, I've noticed that the user interface starts off fine (I've been using it for a long time, and I would very quickly notice if the UI was more sluggish than the previous version, and initially at least, it is good), but fairly quickly, typically within 20-30 minutes, things begin to slow down - clicking in the piano roll display (which is where I spend a significant amount of my time) becomes sluggish, with it sometimes taking several seconds to recognize a mouse down, and frequent appearances of the spinning beachball. It seems as though Logic has to 'catch its breath' after any actions, and during this period, nothing (not even scrolling the window, or clicking on a menu item in the menu bar) is recognized. It's during this period that the spinning beachball usually appears.
This constant pausing makes working in the piano roll display very tedious, and the pauses become progressively longer over time. Interestingly, working with tracks in the standard track view (the top half of the window, in my layout), doesn't seem to have the same issues, only the piano roll. I haven't checked any of the other views (Score view was a bit flaky even in the last version, so I haven't had the courage yet to go in there. Although at certain stages of a project, I will spend 90% of my time in the score editor). In any case, once the 'pausing' gets to a certain point of annoyance, I will save and quit Logic Pro, and then re-open it, and everything is fine again for about half an hour.
While I appreciate Apple's attempts to get me away from my computer and get some exercise, it's truly a big annoyance when under deadline for a project!Does anyone else have this experience with the latest version of Logic Pro?Any ideas for troubleshooting?Steve. First thoughts upon looking through the report.1) SoundFlower. Any of these audio routers (Other examples being Jack and Dante) seems to affect the performance of Logic. Especially under Yosemite.
It's usually the first thing I look for when people report such issues and sure enough, you have an audio router installed. And loaded up.2) socketfilterfw - This is part of OS X's Firewall routine and for some odd reason on occasion it will east up resources. If you note, in your report its using 8% CPU which is way above normal for it. Switch off the firewall and turn it back on again to fix this as a temp measure.
Hopefully a OS X update will resolve this in the near future.3) Note the CPU resource diagnostic from earlier on the 19th. In the Diagnostics Information center. This can indicate that something maybe went 'postal' with your CPU which would cause spinning beachballs etc in other applications. Maybe a check through that log to see what was the cause, would help.4) There are a few reports about Cobook having a memory leak. As that's running in the background that could be another source of the issues.5) You have a lot of 'clutter' for want of a better word.
Loaded/running in the background. This is never that good for a Mac running a time sensitive/CPU grabbing app like Logic. Especially these days when the recent OS X's themselves are becoming more and more CPU/GPU/Memory hungry. So disabling/removing/putting them into a different account, is often worthwhile. Such things as Axel.
(Id really get rid of that!). The Juniper access stuff. Preventing all these apps/routines from loading up in the background when using Logic, by whatever means. Can only be a good thing ™Apart from Cobook, I really don't see anything that I would describe as having a memory leak. But my best guess at the culprit to your issues would be either that or more likely, based on past reports made here and elsewhere by other users, SoundFlower. Im not seeing this behavior Steve.So, you might want to try the following.Please download Etrecheck from here.and then launch Logic ProNow run Etrecheck and either look through the report yourself and/or post up the full report here.That could identify the culprit if it's something else going on with your system (Adware.
Wayward apps running in the background)Also it could be a plugin issue. I had a similar problem with a previous version of the Kontakt 5 plugin. And a small memory leak that got fixed in v5.4.3. It only truly manifested itself when I had about 20+ instances of K5 running when the leak truly become noticeable.Nigel. Thanks Nigel! That Etrecheck is a neat little tool! I've looked over the report (which is pasted at the end of this message), and can't really see anything that jumps out at me, possibly the ' com.AmbrosiaSW.AudioSupport' which was a recent install, but it didn't work (which is why I'm assuming it says 'not loaded'), and possibly the SoundFlower KEXT, ' com.Cycling74.driver.Soundflower', which is also fairly recently installed, but it is intended to redirect the Mac's audio output to a file, and if it was doing anything, I wouldn't be able to hear my project in my headphones.
So I know it's not running. The Logic Pro project I had open when I ran this doesn't use these instruments, but I do have 2 instruments that I purchased from NativeInstruments, that uses Kontakt 4. As of yet, I haven't gotten any indication from them that there has been any upgrades (to Kontakt 5, for example). First thoughts upon looking through the report.1) SoundFlower. Any of these audio routers (Other examples being Jack and Dante) seems to affect the performance of Logic.
Especially under Yosemite. It's usually the first thing I look for when people report such issues and sure enough, you have an audio router installed. And loaded up.2) socketfilterfw - This is part of OS X's Firewall routine and for some odd reason on occasion it will east up resources. If you note, in your report its using 8% CPU which is way above normal for it.
Switch off the firewall and turn it back on again to fix this as a temp measure. Hopefully a OS X update will resolve this in the near future.3) Note the CPU resource diagnostic from earlier on the 19th. In the Diagnostics Information center. This can indicate that something maybe went 'postal' with your CPU which would cause spinning beachballs etc in other applications. Maybe a check through that log to see what was the cause, would help.4) There are a few reports about Cobook having a memory leak.
As that's running in the background that could be another source of the issues.5) You have a lot of 'clutter' for want of a better word. Loaded/running in the background. This is never that good for a Mac running a time sensitive/CPU grabbing app like Logic.
Especially these days when the recent OS X's themselves are becoming more and more CPU/GPU/Memory hungry. So disabling/removing/putting them into a different account, is often worthwhile. Such things as Axel.
(Id really get rid of that!). The Juniper access stuff. Preventing all these apps/routines from loading up in the background when using Logic, by whatever means. Can only be a good thing ™Apart from Cobook, I really don't see anything that I would describe as having a memory leak. But my best guess at the culprit to your issues would be either that or more likely, based on past reports made here and elsewhere by other users, SoundFlower. Ourson wrote:Nigel, I'll remove SoundFlower and see what that does - I've been a Macintosh developer for 20+ years, and it's just too convenient that I installed SoundFlower and started having issues with Logic. I'll report back if it sorts out the issues!
Thanks so much for your response!I know what you mean Steve. There are coincidences. And then there are.
You are welcome. And yes, please keep us updated.Are you using Kontakt in your projects?I suspect the reason for Pancenter's good question is to ensure you have turned off Kontakt's Memory Server as that can lead to weird behavior too. With memory related issues.However I did notice you also said earlier.However, having said that, I.am. experiencing the slowdown that I talked about with this project, which does not have either of the Kontakt instruments in it.But it's worth bearing in mind to make sure its kept off whenever you do actually use Kontakt given the memory server isn't needed and will likely conflict with other memory management systems. If it's left on.As an aside, (and thanks to Pancenter. For nudging my memory about this too) it's worth upgrading Kontakt to v5 as K4 is known to have issues under modern OS X versions. And if you are using Kontakt Player rather than the full version.
It's a free upgrade.Cheers.Nigel. Hi Nigel & Pancenter!So, I uninstalled SoundFlower, and so far today, after a few hours, no repeat of the slow-down behaviour I was seeing previously!
So cautiously optimistic at this point!The Kontakt question, 90% of the projects I work on utilize both of the instruments I have from NativeInstruments, and from what I recall, it's possible that I switched to the project which did NOT have the instruments in them, after working on the project which DID. And doesn't Logic keep instruments around between projects, so it doesn't have to re-load them? Just a thought. I have checked in Kontakt 4 (which I will upgrade shortly), and the 'memory server' option was turned off.
I'll make sure it stays that way when I upgrade to 5.Thanks so much for all your help, it seems at least initially that it was SoundFlower that was causing the problem. I'll let you know if that's not the case! It's possible that I switched to the project which did NOT have the instruments in them, after working on the project which DID.
And doesn't Logic keep instruments around between projects, so it doesn't have to re-load them?No, Logic doesn't keep libraries in Kontakt when you switch between projects. That use the same libs because Kontakt as a plugin, has to close. And then reopen. Therefore, as far as Logic is concerned, those libs have to be reloaded by Kontakt.
Note: Logic does remember which libs and lib settings. Per project.But, libs do seem to load faster the second time around.so I suspect they remain in memory (or in a buffer?) and Kontakt sees that and doesn't have to fully reload them, hence it seems faster.That's just a guess however. Maybe one of the more techie people here might have a better, more accurate explanation for the apparent speed up.Anyhow, glad to hear that removing SoundFlower seems to have resolved your issue.
![]()
That turned out to be the simplest fix of the various possibilities. If it pans out to be so.Fingers crossed it remains that way ?Cheers.Nigel.
Apple Footer.This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |