zosoaudo007

I don't think that applies that much to a sound of this nature. It's a synthetic drone after all. J. My rule of thumb is that time stretching, to correct timing issues, should be avoided where other options exist. As a correction tool, it can work, but I think it's better to not use it if you can work around it. Using it as a sound design tool is another point. That said, there are certainly contexts where it performs perfectly fine. However, it sounds like the OP has even stumbled across the issue with time stretching....the artifacts involved. Especially with extreme stretching. It's always a judgement call with this kind of stuff, and to be fair, I haven't listened to the OP's audio example he posted. So, you could be more on point than me. If it works, great. If not, he should try cross fading.

Try copying it over to the right, cut it up and crossfade it with itself. That's usually the best way to do it. It'll take some patience to get it to work. Just like what Matt said. Time stretching should be a last resort for corrections that need to be made.

That did the trick. Thx.

It's driving me bonkers. A custom template I set up months ago suddenly has some funky Marquee tool behavior married to it. It won't go away. It is constantly appearing and then switching to the regular cursor tool randomly. Holding and release the Apple key doesn't resolve it. I don't know what to do!

Thx David. I did already know that. Its an ok workaround, but requires too much precision IMO. I use Cubase at work and it actually has an option for this behavior. Hoping Logic did too...... Any other ideas?

Is there an option to have the playhead jump to a location by clicking on the background of the arrange page? This is driving me nuts. I know I can play from the Marquee position, but that can be a little finnicky (specifically when I select a new region). Thx

Weird..... Something was up with it yesterday, but today it seems to be working fine. All is well. Thanks guys!

Yea, all I'm changing is the output from stereo 1-2 to a bus. The track is panned hard left or right. Then I set a stereo Aux's input to that bus. At this point, the panning that I should be hearing is lost. The sound always gets centered. The original track is still properly set to its hard pan, but what I hear does not have the hard pan when it is coming through the stereo Aux track. Makes cents?

So, I have been trying to figure this out in Logic without much success. I have two guitar tracks playing the same part. One is panned left and one is panned right. I would like to set the output of both of these to one Aux track while retaining the pan. This issue occurs with all mono tracks I use. As soon as I change the output of a track and send it to an Aux, all my pan information is lost. It immediately becomes centered again. In Pro Tools, if I have two mono guitar tracks, I can pan them left and right and set their track output to a bus to bring up on an Aux track. This is awesome to do in Pro Tools and works extremely well. I can add EQ and compression to both while still retaining the pan information. Can this be done in Logic? Do I need to use a plugin to achieve this as opposed to the pan knob? Help is much appreciated.

i still get the dry signal through the track with the plugin. if i want it to not play, i have to mute either the track or the send. it absolutely does pass the dry signal through. any thoughts?

Happening on my end too. 12-core Mac Pro. Western Digital sample drives. 16 gb of RAM. Crazy annoying issue. Never had one problem like this with my 2009 MBP. Hyperthreading issue, mayhaps?

I actually have bought this thing and love it. However, after a dozen times of use, I'm getting the dry signal through the plug. Extremely annoying. I have it set-up on an instrument track and have my sound sent to a bus and the side-chain set for that bus. It's definitely coming through the plug-in. Very confused.... Anyone know how to stop the dry signal from going through the plug-in, when gestures aren't being played?

It is working extremely well with Logic. I upgraded from a Core 2 Duo laptop, and the difference is tremendous. Since Logic is capable of only handling 16 virtual/real cores at this point, I'm uncertain if you would notice any sort of performance boost from your 8/16 core system. I don't know what your current clock speed is, but even if 2.93 is faster than what you currently have, the difference may be negligible. In Pro Tools 9 - since Avid is pushing forward with native processing - the 12 cores make a huge difference here. I am able to select all 24 virtual cores while using PT9. I run a lot of instances of East West's Play engine, and the largest session I have run with this contained 20 tracks of Play. I did not come anywhere near maxing out the CPU. RAM is a different story... Anyway, if you have an 8 core system, you already have the number of cores which Logic can handle. And your clock speed may already be faster than mine. I know that turbo boost technology doesn't work unless there are a few cores doing all the work (which is rarely the case in my sessions). Hope its helpful.

Try some compression and EQ on them.

I recently made the incredibly time-consuming, financially straining, EXCELLENT decision to upgrade from a dual core laptop (MBP 08) I used from my college days at Berklee. Now that I am out and running a business, I was faced with a difficult decision of having to upgrade. Laptops are great for mobile productions. But I don't DJ that much, and I do more producing, and composing than anything else. On to my question, Logic is only capable of handling 16 virtual/real cores even if you have a dual 6-core system (12 cores plus the 12 virtual totally 24). Is Logic capable of handling turbo boost technology on these new processors? I have allocated 14 cores for Logic in the preferences pane and two is enough to leave for OSX. My main area of interest is in how I could accurately test the turbo boost technology and post some results here and we could talk about that. I always love reading about interesting hardware optimization topics and now is my chance to give back. Step one: Any recommendations for a great CPU utility program that will run on OSX? I have been using Activity Monitors toolset, but doesn't give values for the cores. I'm up for suggestions on how to best test this. Thanks