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 9, 2008 7:50 AM in response to jnashguitar

jnashguitar wrote:
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.


I never got this problem... I'm usually do many Punch-in/out when recording Voice and I always need to select the best result with change left/right region corners for extend or reduce the length...
I also use to overlap the region because this is not a problem with logic (its play always the following region)...
but if i need to use closer regions without overlaping for "fade-in/out" I do it without any disappearing problems

your issue seems to be related with Graphic card refreshing... or, if not, I suggest you to delete logic preferences and system preference... if the problem persist, I'm afraid that you need a fresh installation of your system

Are you sure to have the correct driver installed for your Graphic Card?
(some people run 10.4.11 on the new 8core machines... I suggest to search for it on the forum)

......

May 9, 2008 8:06 AM in response to jnashguitar

jnashguitar wrote:
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...


I make serious production every day with Logic 8.0.1 and 10.4.11 or 10.5.2 as well...
LP8 works as professional DAW... there are no editing bugs, but if you comes from another software you need to learn HOW to obtein the result that you need...
you cannot use the same way like as your previous Audio software!!!

... And, about editing... I'd like to advise you to use Soundtrack Pro that comes with many extra features... with a very fast learning curve for the new Logic Users!

I suggest you to don't force Logic to work like as another DAW.... 🙂

G

May 10, 2008 12:37 AM in response to Community User

Thanks for the input!

I had a backup system handy, so I tried installing Logic on it for the first time (fresh install). Didn't solve the problem. I experienced the same bugs with region length changes (the disappearing/jumping problem doesn't happen all the time, but it still does happen with my freshly-installed version of Logic).

What I did discover, though, is that while I see buggy behavior sometimes when I move the left or right edge of a region on top of another region (with "no overlap" selected), I DON'T experience any bugs when I use the "Junction pointer" (see p.313 of the Logic manual). Since most of the time I can accomplish the same thing with the Junction pointer as I'd accomplish with the Resize pointer, that's an easy workaround to avoid the editing bugs.

I'm guessing maybe the reason why some others experience this bug, while many do not, is that maybe the Resize/no-overlap feature is actually buggy on everyone's system, but maybe most people don't use it, since the Junction feature is actually more convenient in the majority of cases.

Anyway, thanks for the ideas--this got me looking at editing options a little more closely, and the Junction pointer not only seems to be bug-free, but I actually like the way it works visually better than the way I was editing. You learn something every day...

James

May 10, 2008 3:07 PM in response to jnashguitar

jnashguitar wrote:
What I did discover, though, is that while I see buggy behavior sometimes when I move the left or right edge of a region on top of another region (with "no overlap" selected), I DON'T experience any bugs when I use the "Junction pointer" (see p.313 of the Logic manual). Since most of the time I can accomplish the same thing with the Junction pointer as I'd accomplish with the Resize pointer, that's an easy workaround to avoid the editing bugs.



mmm are you using a 3rd party plugins on the tracks?

I got a similar issue in a track with Auto-tune....

There are some other 3rd party plugs that caused similar issue, but in that case, the problem is not related with Logic.

G

May 12, 2008 12:36 AM in response to steve shadforth1

Yeah...
I'm glad to learn you how to editing with logic....
please, go to my web site and make a donation... 😉
if you will be not satisfied about my lessons... in soma cases 😉 i will refund your donation...

ha ha ha!!!!

:-D

May 12, 2008 2:17 AM in response to steve shadforth1

steve shadforth1 wrote:
yeah, please burn us a version of your LP8, it sounds perfect lol
Steve


it is only a joke... but... feel free to ask and specify one or more editing problems with your Logic version...
I just talk about that: there are many kind of editing that can be used to obtain the same result

e.g. in the case of this thread, you could merge the closer regions

May 12, 2008 6:44 AM in response to Community User

fermusic wrote:
I make serious production every day with Logic 8.0.1 and 10.4.11 or 10.5.2 as well...
LP8 works as professional DAW... *there are no editing bugs*, but if you comes from another software you need to learn HOW to obtein the result that you need...
you cannot use the same way like as your previous Audio software!!!

... And, about editing... I'd like to advise you to use Soundtrack Pro that comes with many extra features... with a very fast learning curve for the new Logic Users!

I suggest you to don't force Logic to work like as another DAW.... 🙂


Wow, what an insulting (and clueless) post. "There are no editing bugs"???? There is no question there are many confirmed editing bugs in Logic, do you really think that because you haven't seen them they don't exist and other users are imagining them? This is absolutely not a question of "coming from another software", there is stuff in Logic that just doesn't function properly. Especially things where doing the exact same action multiple times gives different results.

And Logic should work properly, users shouldn't need to switch to STP (which is horribly buggy, but in different ways).


I've had problem #3 above and a number of similar ones.

5) Crossfades created by overlapping appear in the wrong place, not between the endpoints of the regions.

6) Moving or overlapping regions creates (or removes) crossfades in other regions before and after.

7) Copying a region (via option drag) doesn't copy fadein/fadeout on the region. Sometimes, the copy has the fade, but the fade disappears from the original region. I've seen times where the original has fadein and fadeout, and after copying, the original has one fade and the copy has the other.

I'll try the junction tool, but it looks like it only does splice edits and not crossfades.

Has anyone figured a way to avoid these bugs? Apple really needs to roll up their sleeves and get all of these basic editing bugs out of the app, they make it really hard to get work done sometimes. Is it really so hard to get the basics right in an app that has been around for years?

May 12, 2008 1:59 PM in response to Mike Connelly

Mike Connelly wrote:
fermusic wrote:


I suggest you to don't force Logic to work like as another DAW.... 🙂


I think you do not follow my suggestion 🙂
please.... .:-)

I've had problem #3 above and a number of similar ones.

5) Crossfades created by overlapping appear in the wrong place, not between the endpoints of the regions.

6) Moving or overlapping regions creates (or removes) crossfades in other regions before and after.

7) Copying a region (via option drag) doesn't copy fadein/fadeout on the region. Sometimes, the copy has the fade, but the fade disappears from the original region. I've seen times where the original has fadein and fadeout, and after copying, the original has one fade and the copy has the other.


these yours points, make me sure about the fact that you want to use logic as PT or cubase...

i never used crossfades region by this way with Logic... or better... I use this kind of crosfades rarely...

I know what you are talking about bacause I see many pro tools users that use the crossfades as you described... that is why I said: Don't force Logic to work like other DAWs....

When a need to use the crossfades like your describtion I Always use the Sample editor in a Desctrutive way... or you can use the fantastic function like is "EXPORT REGION AS AUDIO FILE"!

I suggest to set "search zero crossing" in the arrange/audio menu....
if you turn on this setting you will be solve almost of the crossfade needing!

Crossfades are not so important function in my experience and can be solved by using a more faster way....
or, if i need to crossfades regions i suggest to make ALL COPIES that you need crossing the arrange windows BEFORE USE crossfades editing.... or if you need to copy a region in a second times, delete the crossfades and select all the region that you need to edit at the same time!

I think that the crossfades bug has been solved: you can obtain the desiderate result by using a different LOGIC way! 😉

I repeat : DON'T FORCE LOGIC TO WORK LIKE AS OTHER DAWs

Thanks ( sorry for my syntax error and feel free to replay... i will post some screenshots if needed as request)

G

May 12, 2008 2:54 PM in response to Community User

fermusic wrote:
these yours points, make me sure about the fact that you want to use logic as PT or cubase...


I'm trying to use Logic as Logic. Or at least as the manual says Logic is supposed to work. I've never used cubase, and I don't think PT does crossfades by overlapping regions like Logic does.

i never used crossfades region by this way with Logic... or better... I use this kind of crosfades rarely...


Well, that would explain why you think Logic has no bugs - if you never use the buggy features, you won't see the bugs.

I know what you are talking about bacause I see many pro tools users that use the crossfades as you described... that is why I said: Don't force Logic to work like other DAWs....


I'm just trying to use Logic as described in the manual. It sounds a bit like you're defending Logic being broken, you really think a feature like this shouldn't work right?

When a need to use the crossfades like your describtion I Always use the Sample editor in a Desctrutive way... or you can use the fantastic function like is "EXPORT REGION AS AUDIO FILE"!


Wow, that's an absolutely horrible way to work, why would you ever want to do that? I'm assembling a bunch of sounds, it would take ten times as long to do things destructively or export everything. And doing it those ways doesn't leave you the option of going back and changing the crossfade later.

I suggest to set "search zero crossing" in the arrange/audio menu....


I shouldn't have to. You really think crossfading two chunks of audio should require finding the zero crossings? They are two completely different things.

if you turn on this setting you will be solve almost of the crossfade needing!


You have no clue what I'm doing, and yet you think I don't need crossfades? Wow.

Crossfades are not so important function in my experience and can be solved by using a more faster way....


YOU don't think it's important, therefore nobody else should need them, therefore you think it's OK if they're broken? Sure.

Not to mention that these bugs don't just happen with crossfades, they also happen with fading regions in and out. You really think that's an unnecessary feature?

I think that the crossfades bug has been solved: you can obtain the desiderate result by using a different LOGIC way! 😉


Nope. Having a different way that can't be revised later and takes way longer isn't a fix, nor an excuse for the app to be buggy. And with all due respect, it sounds like the way you're working is horribly inefficient - you should really check out some of the other non-destructive ways of working.

I repeat : DON'T FORCE LOGIC TO WORK LIKE AS OTHER DAWs


Quit repeating yourself, that has nothing to do with the problems in logic. Why are you defending the bugs in this app, I just don't get it? Why shouldn't apple just fix the bugs?

May 12, 2008 3:45 PM in response to Mike Connelly

There are bugs in the crossfades in Logic. Repeatable behaviour which is not working as described in the manual.

And although each engineer should work their own way, crossfading destructively is, in my opinion, burning all your bridges. I agree with Mike, that would be, for me, a horrible way to work. Plus, I don't try to use Logic like another DAW. But it does have some bugs to iron out, bugs that us, as users, I think are pretty powerless to address. It needs to come from source with a couple of (or just one) GOOD solid updates.

May 12, 2008 11:25 PM in response to octopi

I remaind you that the region crossfade function is NOT a destructive editing...
so,
cannot be compared with protools function because protooòs do a destructive editing...
on the manual there are many things that do not work as described, but this happen in every high-tech software!!!

I repeat that I work every day in professional studio with Logic.... from many many Years....
I always can do and I was been able to do everythings with Logic!
Logic is the best professional audio software compared to the others

G

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.