ugokcen

I recently noticed that the plugin delay compensation acts funny with the new dual mono option. It works properly when the plugin is active but when you bypass it it still "works" - that is, it throws the tracks out of sync. I was wondering if anybody else has experienced this problem or whether this is a known bug. To replicate what I'm talking about throw two apple loops on two audio tracks and put a linear phase eq on one of them in dual mono mode. It should play in sync when the plugin is active but messes up when you bypass the plugin. If you try inserting the stereo version (rather than dual mono) you don't get this behavior.

Thanks Eric, that was quite a read! I am doing everything ITB for now but I bookmarked it for future reference when I get my hands on some hardware compressors and eqs. So, as I understand this playhead not matching up with the audio is a bug, right? There does not seem to be a solution either Umut

Hi everyone, I noticed some strange behavior in Logic yesterday (maybe it was always like this I don't know) and I'm wondering if anyone else has experienced this issue. I always use plugin delay compensation set to "All" because I group instruments and process them together before sending them to the master out. Now if you have some high latency plugins like linear phase eqs on the buses, the audio plays in sync however the midi notes in the piano roll do not match the playback. This makes it very difficult to fine-tune the timing of midi notes later on in the project - say you are trying the match programmed drums/percussion to recorded drum tracks. It appears that Logic is delaying the audio stream to compensate for the plugin latency however what you see in the arrange page and other editors are kept as they are, hence you hear the sound significantly after the playhead has progressed. You can try this on your own. Just pencil in some short click sounds with ultrabeat in the piano roll in a new project, then set it output to Bus 1 and load up a bunch of linear phase eqs on that bus (4-5 will make it really obvious). When I do this and hit play the notes I see on screen no longer line up with what I'm hearing out of the speakers. So, is there a workaround to this problem? Is there a setting somewhere that I am not aware of? Thanks for the help. Umut

So happy to see the Apple team still taking Logic seriously! I actually sat down and read through the whole list. There are two crucial features (at least for me) buried in there. 1) "Using the Fade tool to set fade-ins on multiple regions in a set of grouped tracks now works reliably." I never edited acoustic drums in Logic because of this. Now I can. Bye bye Pro Tools 2) "Setting a track to Flex Edit mode with the Slicing algorithm no longer processes the track with Flex if no edits have been applied." Again this was an issue that made flex less useful than it could have been. I would always notice artifacts even if I haven't manipulated a slice, so I would end up not using it at all. Glad to see that it is fixed. One question though: Do you think Apple is implying that only the slicing mode is fixed, or that the other modes did not have this bug in the first place? Umut

I tried your suggestion and it works (with some trial and error on the length of the overlap). But it's a bit cumbersome and breaks the workflow of just fixing individual notes in flex view. If I was doing vocals for example it would be a nightmare cutting into individual words and syllables, moving them to a new track, etc. I've been holding off on updating my 32-bit version of auto-tune, but maybe that is the way to go... Or I can wait until the next update of Logic... Thanks again for your help.

Yes. If I make the fade really short then the clicks are still there, if I make the fades longer the clicks go away but then you can hear the edit. It would probably work if I bounced the pitch-corrected regions into a new file and put the fades on those but that seemed like a lot of work. By the way the nondestructive fades in the track area do not work at all. I mean, the fade tool does not fade in or out when applied to a region in the middle of a track. Umut

Alright, after an hour I give up. I can't seem to get rid of the clicks if the regions are back to back. And if I flex the whole track I get some warbly artifacts. I'm going to have to go back to Logic 9 and Auto-tune on this one. I was very optimistic about flex, the interface is lovely but it probably needs more work in the background. It makes no sense to me that it still processes your audio even if you haven't changed a thing. Umut

Working on it!

Well, I have to cut in the middle of the waveform cause it is a straight 8th note pattern with no rests. Maybe if I do a super fast fade in and out of the region it'll work… As much as I hate the Auto-tune interface, at least it doesn't mess with your audio unless you make changes to the pitch graph. I think flex mode should have been designed like that as well. Umut

Thanks for the tip David. Just ran into another problem with flex . I disabled it for the regions I do not want to touch using the inspector as you said, and then did my pitch corrections for the problem areas. Now when I play back the full track I get clicks between the flexed and the un-flexed regions. Is that normal? Umut

Aha found it, thanks! Don't get me wrong I love Logic, but there are just too many ways to access Flex editing which becomes confusing. There is the pink button at the top of the arrange page, then the same button in the track editor which appears to be independent of the first one. Then there is the track inspector and the region inspector with the check boxes for flex. Is there any rhyme and reason to all this? What is your favorite method when "flexing" for example?

Hi guys, I haven't posted in a while, busy recording Now it's edit time and I thought I'd give flex pitch a try. I needed to fix a few bum notes on a bass track so I turned on flex and logic did its analysis. Everything looks good so far, I see the notes in the track editor and all, make the corrections, no artifacts, beautiful! Where I got stuck is I would like to turn off flex pitch for the rest of the track but when I click that button all the regions are affected. In other words, I select a region, click the flex button on the region's track editor, then select another region on the same track and the flex is turned on there as well. If i turn it off, it also goes off for the first (unselected) region. Isn't it possible to turn flex on or off per region? Does it have to be track based? Thanks for the help, Cheers, Umut

I've been having 'snap' problems as well. I read the other thread but I think the situation is even worse I think. Try this: record some audio by punching in at some random point. Open the event editor and take note of the start point of the region. Then click and hold the region as if you were to move it but DON'T, just release it. Logic automatically moves the region to the nearest snap point! Usually that is only a few ticks so you won't hear it probably so that's why I said keep the event window open. You can imagine how this kind of snapping behind your back can ruin your entire recording session! I'm being extremely cautious now of 'touching' any regions. Has anybody noticed this? This can't be a feature, it must be a bug right? Umut

Just wanted to report that the iPad app works great on my system as well. No connection issues, no latency, solidl! Everyone will find different uses for this app I suppose. For me the biggest draw will be to check my mixes at different points inside the room, and even outside the room. You know, go to the kitchen make yourself some coffee and listen/tweak your mix from there. Very sci-fi

Yes, that did it! I would have never thought. Man, this forum is great 8) Umut