carsontm18

What I'm really looking for is to be able to trigger the LFO Tool's sidechaining capabilities via a MIDI track. I know I can automate the amount of sidechaining the plug does via an aux track in the arrangement. I also buss my instruments in layers as you do with snares/claps going to an aux and then that routing to a drum bus. I was talking about taking those already bussed instruments and routing their aux tracks to another aux for the sidechaining. In my experience I have found that this final layer seems to introduce some noticeable latency in the chain whereas before adding the final routing the latency wasn't noticeable. I was hoping there would be some way to easily replicate my sidechaining setup I had before. Basically I would use a VI to trigger my sidechaining. This way I can easily determine when I wanted to sidechain by just editing the midi track.

I know. That is what I want to avoid. I am wondering if there are any methods to bypass this. Maybe something routed through the Environment? I know that initially using the environment may be more hassle but the idea is that I would have it set up so that I can avoid this problem in the future.

I've been using Xfer's LFO Tool for a substitute to sidechain compression. However, I still haven't been able to figure out a way to easily automate LFO Tool's volume automation. I know that I could just automate the plug's bypass in Logic however I want to avoid this since I am using the plug on aux channels and want to avoid cluttering my arrangement. I've also considered creating dedicated aux tracks for my sidechaining, so I can then just buss multiple tracks to the sidechain channels following their respective processing chains. The problem with this is latency... I buss all of my individual tracks to auxiliary tracks to take advantage of applying effects and processing to multiple tracks at once. So to then have those aux tracks bussed to another aux would introduce unwanted latency... and I make sure that plug-in latency compensation is set to all. There are many benefits to volume automation (as LFO tool does) as compared to sidechain compression, so I really would like to keep using this plug. Can anyone think of any ideas as to how I can automate this LFO sidechaining so that I can control when it is activated in a straightforward manner?

Well, then I won't be able to run Sylenth1. I ran the same project with 4 instances of Spire (similar to Sylenth1) with the same MIDI and no 32 Lives... http://s30.postimg.org/c1dmbcylt/Screen_Shot_2014_07_12_at_6_22_03_PM.png image post And here is a screenshot of the Actitivty Monitor with Sylenth1 running through 32 Lives... http://s30.postimg.org/dilr12g4x/Screen_Shot_2014_07_12_at_6_27_56_PM.png host image And the the fourth thread is very unsteady... it spikes from just below where it is on the screenshot to near max randomly.

I have been using Logic 9 for about 4 years and decided to make the jump to Logic X recently. However, since switching to Logic X, my audio output from the program has been crackling and fizzling out consistently. If it's bad enough I will then get the error sync message with a weird sample rate detection. I have ruled out my interface's drivers (M-Audio Profire 610) because it does the same thing for Built-in Audio. The problem doesn't seem to be the core audio engine, rather the CPU usage of Logic X. The crackling only occurs for certain VI's (like Sylenth1 - running via SoundRadix 32 Lives), but not for others (Massive, stock Logic plugins, etc.). And I can minimize the effects by reducing the number of VI's. I can also increase the I/O buffer but that is not ideal since it only helps if I increase to a ridiculous amount like 1024 samples (in Logic 9 I can get away with 70 VI's mostly Sylenth1 and Massive at 128 samples and run smoothly). Here is a screenshot of the thread distribution with only four instances of sylenth1 running and playing the same MIDI... http://s24.postimg.org/bmgmuhxd1/Screen_Shot_2014_07_12_at_5_50_52_PM.png image hoster Now, I have had my fair share of CPU/audio,midi sync problems in the past with Logic 9. I typically work with a large number of VI's that use a considerable amount of CPU. I have adapted my workflow to bouncing regions with these VI's in order to save CPU in Logic 9 and it has worked well for me. However, in Logic X I am experiencing issues with audio quality with only a couple of instances of one of my least CPU hungry VI's. I have not had any System Overload messages yet, but regardless this is unacceptable and makes it impossible to work on my tracks. The weird thing is that Activity Monitor shows Logic X as using less CPU than Logic 9 for the same project. However, in Logic, the CPU meters read higher in X than in 9. I've read through countless of these threads but haven't seen anyone else who has encountered this particular problem. Could it possibly be 32 Lives? Or something else?

n6smith, I have a MBP model 6,2 (mid 2010) so I don't have a Thunderbolt port. triplets, I har started looking at FW 800 drives and I found an ideal drive but it looks like I'm going to have to get a FW400:FW800 adapter (Like you said). I was wondering are there any FW800 drives with just multiple FW800 ports? Also, won't I still be, in a sense, daisy chaining the audio interface if I'm going to run it off of the FW800 drive, which runs from the main FW800 port on my MBP?

I'm running 64 bit for my OS. I also checked up on the RAM and found that my MBP supports up to 8GB, so I'm gonna go for that as soon as I have some cash... Do you know of any good types of RAM? Like manufacturers? I don't know much about RAM and I don't wanna throw away my money on bad RAM. And for the external drive, I currently have a USB backup drive but am looking to invest in a 2 TB FW800 external drive soon (I just need to figure out how I'm going to configure my setup since I currently am running an M-Audio Profire 610 Audio Interface through my one FW800 port on my MBP).

Ok, thank you for the quick replies

Ok, I'm running Logic in 64-bit now, it seems Logic is using a little less CPU (using 150-180% compared to 200-220%). As for the RAM, what would be a good amount of for me to get? Just to put it in perspective, most of my projects are and will be pretty similar to the one I described in my first post. Should I get 6GB? 8BG?

First off, I know there are many posts relating to this topic. I have read most of those posts and have read te article on CPU usage in Logic. I am posting this because I have tried many things and still am having CPU issues. I also want to find out if I actually need more RAM before I spend any money. I've looked up a lot on System Overload Errors so far (actually for about two days now) and have found that there are tons of situations that could lead to CPU spikes from Logic. And to be clear, I am having CPU spikes, not HD spikes, I've checked using Activity Monitor. As for my current project, I am running several instances of Massive and EXS24. I don't have many CPU hungry plug-ins besides those two as of now (I've been trying to use the built-in effects in Massive). I'm running about 55 active tracks in my project as of right now, but I'm still writing so there will probably be more... I also am EXTENSIVELY using busses, because I know they are a good way to drop CPU loads in Logic. Also, when I run Logic I typically am ONLY running Logic, I quit all programs besides Logic. Also, I have already read the link you have posted (about 10 times at least). I am using all of the tips that the article says to do and still I am getting CPU overloads. I have reduced the number of voices on all of my instruments to the minimal amount, I have increased the I/O Buffer Size to "1024", set the Process Buffer Range to "Large," I use "Virtual Memory" with my EXS24. I have tried freezing tracks, BUT it's extremely taxing on my workflow because I'm still writing portions of my project. Also, when I do freeze tracks, i tend to just get a heavy load on my HD and then I run into a whole new set of problems. Oh and a BIG issue, through out all of the forums I've been to, I haven't found anybody with this issue: When I run Logic, even when I run it by itself, I find that Logic is using up to 200% of my CPU! (found using Activity Monitor) Personally I didn't think this was even possible. Does this mean that I need to invest in more RAM? Thank you in advance for any answers or tips

Ok, well someone on this forum has to know... should I start a new thread? I really need some answers because my workflow is seriously hindered because of the System Overload Errors.

I've heard a lot of people say the same thing, Dave... But have you ever seen Logic use 200+% of CPU before? I have heard of other apps that take away from Logics CPU but never of extreme CPU usages of 200+% BY Logic. I just want to make sure I'm not frying my processors on my MacBook Pro. Also, could this mean I need more processing power?

I just found that sample relocation isn't helping (in my situation) because I am using a USB drive for my external drive, which is just bottle-necking the flow and increasing CPU load. I've looked up a lot on System Overload Errors so far (actually for about two days now) and have found that there are tons of situations that could lead to CPU spikes from Logic. And to be clear, I am having CPU spikes, not HD spikes, I've checked. As for my current project, I am running several instances of Massive and EXS24. I don't have many CPU hungry plug-ins besides those two as of now (I've been trying to use the built-in effects in Massive). I'm running about 55 active tracks in my project as of right now, but I'm still writing so there will probably be more... I also am EXTENSIVELY using busses, because I know they are a good way to drop CPU loads in Logic. Also, when I run Logic I typically am ONLY running Logic, I quit all programs besides Logic. Also, I have already read the link you have posted (about 10 times at least). I am using all of the tips that the article says to do and still I am getting CPU overloads. I have reduced the number of voices on all of my instruments to the minimal amount, I have increased the I/O Buffer Size to "1024", set the Process Buffer Range to "Large," I use "Virtual Memory" with my EXS24. I have tried freezing tracks, BUT it's extremely taxing on my workflow because I'm still writing portions of my project. Also, when I do freeze tracks, i tend to just get a heavy load on my HD and then I run into a whole new set of problems. Oh and a BIG issue, through out all of the forums I've been to, I haven't found anybody with this issue: When I run Logic, even when I run it by itself, I find that Logic is using up to 200% of my CPU! (found using Activity Monitor) Personally I didn't think this was even possible. Does this mean that I need to invest in more RAM?

It worked! I've moved all of my samples over to my external drive now and I checked it out and the majority of them check out ok. But, I'm still getting System Overload Errors, so that's incredibly annoying. Thanks for the help

Please any advice would be great... I want to transfer these samples to my external drive so I can use Logic without getting a System Overload Error. But I don't want to risk losing all of my EXS24 instruments made with the samples (the ones I want to relocate).