Logic still plagued by serious region start/end adjust and crossfade bugs

Wow... it had been a while since I used Logic for serious audio editing (I primarily use it for composing, and for virtual instruments/effects/mixing onstage)... what an amazingly frustrating experience.

I spent all day today using Logic to overdub album tracks, using autopunch extensively. The tracking went fairly smoothly, but the simple task of fine-tuning the edit points and crossfading turned into a nightmare:

1) The Region-Disappearing Bug: when there are two audio regions touching, and I extend the length of the left region over the right region (with "no overlap" set), sometimes this works just as at should. But sometimes the right region simply disappears. The solution is to use Undo, then try again... sometimes I had to move the transition point five or six times, with the right region disappearing every time, until suddenly it worked.

2) The Region-Jumping Bug: same scenario: two audio regions touching, but not overlapping. Extend one of the regions to move the transition point, and sometimes the right region jumps slightly in time (not a large amount, but enough that it's visible when zoomed-in... maybe 50 samples or so). Same solution: Undo, then try again (or use "Move audio to original record position," then try again). Same deal... sometimes I performed the same edit five or six times in a row before it suddenly and inexplicably worked.

3) The Crossfade-Doesn't-Work Bug: self-explanatory... sometimes, two regions simply won't crossfade... no explanation. Trying this over and over doesn't tend to solve the problem. When this happens, the only way I've found to solve the problem is to remove the surrounding crossfades (the fades on the other sides of the regions I'm trying to fade), then recreate all three crossfades. That usually works, although sometimes it takes several tries.

4) The Crossfade-Causes-Region-To-Disappear-Or-Jump Bug: this is a combination of crossfading and bugs #1 and #2 above... performing a crossfade sometimes causes the same problems as moving an edit point: the region to the right sometimes disappears or jumps around in time.

I really want to believe that Logic is ready to compete in the world of professional audio, but the occasional times that I've tried to use it for serious production work, I've been shocked by these editing bugs. I love writing in Logic, and it continues to work flawlessly running plug-ins live on stage, but my experience has ben that these audio editing bugs currently render it essentially useless for production work, especially when clients are watching...

Does anyone have any advice on how to avoid these bugs ? Is it possible that upgrading to OS 10.5 would solve any of these problems ? I've avoided upgrading so far because of the unfavorable reports posted on this forum.

Thanks for any advice!

James

MacPro 2.66, MacBook 2GHz, Mac OS X (10.4.11), Logic 7.2.3, 8.0.1

Posted on May 8, 2008 9:04 PM

Reply
43 replies

May 14, 2008 1:26 PM in response to jnashguitar

I've just started having a related problem: when I mouse over the end or beginning of a region, the mouse cursor changes for an instant to the proper tool (crossfade, loop, region size tool, grabber, etc. and then suddenly changes back to the pointer, instead of showing the proper tool while I hover over the region start/end/splice. This just started happening out of the blue.

The correct tool function still works, but it is a bit disconcerting to see this behavior.

Has anyone seen this and reported it to Apple?

May 14, 2008 1:27 PM in response to Community User

fermusic wrote:
can you tell me what are the other DAWs that comes with no-destructive crossfade function???
This is another of the great unique features of Logic.... (you just correct me about PT crossfades) 🙂


ProTools, Digital Performer, Cubase, Nuendo, Logic (of course)... all of these DAWs have a non-destructive crossfade function. Correct me if I'm wrong, but I don't know of any DAW that does not offer a non-destructive crossfade.

Maybe you have a very unique way of working, fermusic... I have NEVER worked in a DAW-based studio that didn't perform dozens/hundreds/even thousands of non-destructive crossfades on a daily basis.

James

May 14, 2008 1:32 PM in response to Mike Connelly

Mike Connelly wrote:
James, which mode do you have the drag option set to? Are you using no overlap or xfade?

From what I've seen, it looks like xfade is extremely buggy while the others seem better. And unfortunately, it looks like if you create some crossfades by overlapping, it screws up the track, and those bugs will be present regardless of what mode you are in.


Thanks, Mike. I work almost exclusively in "no overlap" mode, so I guess I'm avoiding these xfade bugs...

The primary bug that slows down my work is when I adjust a region boundary and it causes adjoining regions to disappear. Most of the time, when I do this, I can't see the region that disappears until I zoom out, but I have tried this with all regions visible, and it still happens: the only highlighted region is the one I'm editing, and the un-highlighted region next to it mysteriously disappears (and it's really gone--confirmed by playback--not just a screen redraw issue).

James

May 15, 2008 7:44 AM in response to jnashguitar

The crossfade function in Logic is strictly related to the size of the region!
Logic cannot replace the adio region track by creating a new one like PT!!!

Crossfade function on the audio region works in a different way from the other DAWs!

thats why you must "tie region size" before using crossofade IN/OUT function... if your region exceed the size (overlap to the following region) the crossfade editing should be not correct because the following regions will start in PLAY before the crossfade point!

I hope to be clear...
I'm sorry but english is not my native language... so please, be patience and take my words in a positive way.

Thanks

PS: this is the Logic DNA...
Logic is different from others similar applications and requires a open mind 😉

May 22, 2008 5:34 AM in response to jnashguitar

With 8.0.2 it looks like #6 and #7 listed above may be fixed (at least they have worked so far).

Unfortunately #5 still is broken, creating crossfades by overlapping regions doesn't put the crossfade between the overlapped part of the regions. I'll be reporting that to apple as soon as they update their feedback page to include 8.0.2. At least it's a step in the right direction, although I'm disappointed they left in such a blatant bug.

James, are any of your issues improved?

May 22, 2008 12:09 PM in response to Ed Egned

Ed Egned wrote:
That's funny,how you can get "xfade" with no overlaped regions- thats not possible, you can gen only "fade in" and "fade out"- not "xfade" !



Strange, but this is actually not true. Logic will sometimes allow a crossfade between two regions that are not overlapping--I haven't bothered to try to figure out exactly what determines this, but if you want to try, zoom in and put two regions very close, but not precisely touching... the crossfade tool will still work.

I did test once to see what happens... Logic acts as if the the regions are touching, so you get a smooth fade even in the section of the timeline where it appears on the screen that there is NO region present.

James

May 22, 2008 1:09 PM in response to jnashguitar

You don't even have to have a small gap between the regions - you can create a crossfade between two regions that are far apart. The crossfade appears even though there's a huge gap in the middle.

I'm not sure why anyone would want to do that, and I wouldn't consider the result to be a crossfade. I assume it's just a bug.

Let us know how things go, I'd like to hear if your issues have been fixed or not. Thanks for checking.

Jun 5, 2008 1:35 AM in response to Mike Connelly

Mike Connelly wrote:
Let us know how things go, I'd like to hear if your issues have been fixed or not. Thanks for checking.


Hey, Mike,

8.0.2 has solved a lot of problems for me, and I'm especially happy with the way swipe comping is working now.

But, unfortunately, I'm still experiencing the "disappearing region" bug (#1) when moving around region boundaries using either the resize or junction pointer. Have you experienced this bug, Mike ? This is the main bug that plagues me day-to-day... I can't move the junction between two regions without checking to make sure the next region over is still there... if this were fixed, most of my work in Logic would be bug-free!

I went so far as to install a fresh system in hopes this bug would go away... it didn't... kinda strange more people aren't complaining about it, though... possible this is some unique problem with my system, or are others having the same problem ?

James

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Logic still plagued by serious region start/end adjust and crossfade bugs

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.