Audio Editing Bug

[SansImage]

Anyone noticed this audio editing bug? It's been around at least since DP6.

It's a bug when I'm applying crossfades to track groups. Let's say you have a group of 10 audio tracks - like a drum set, for example - set as an editing group. You're zoomed in real close in the Sequence window to edge-edit, & find a good place to cross-fade. Only 5 of the tracks are showing, the other 5 tracks in the group are below the screen.

Well when I apply the cross-fade like this, It will only apply the cross-fade to the tracks that are displaying on-screen. The other tracks won't be cross-faded, and when I scroll down, the little cross-fade toggle in the top corner of the soundbite is missing. I have to close & re-open the sequence window in order for it to reappear.

The solution? Zoom out vertically before applying crossfades. Still kind of a pain...

[heliarc]

I've experienced this same exact bug in DP 6.1 on a Dual 2.7 Power PC. It's a big pain when editing. Wish they would fix this.

[Don T]

Hello,
I wonder if this is part of the "only edit visible tracks" way that most DAWs operate. If any tracks are in an edit group but not visible then they don't get the edit. Been bit by that more than once in PT and DP.

[Frodo]

[quote="Don T"If any tracks are in an edit group but not visible then they don't get the edit.[/quote]

That's the trade off, isn't it? To edit tracks you can't see... I do understand that if one makes the effort to *select* tracks to be edited that one expects the edits to apply-- but perhaps this was a better-safe-than-sorry sort of decision on the part of MOTU where altering tracks which cannot be seen could present undesirable results as a matter apart. One can always scale down the tracks to be edited to make them visible in on screen, I suppose--- but I fully understanding the enigma.

[Dan Worley]

I've never had that happen. It works fine whether the tacks are visible or not. But now that I know about it it will happen all the time. Thanks a lot!

c-ya,

Dan Worley

[newrigel]

I've experienced this same exact bug in DP 6.1 on a Dual 2.7 Power PC. It's a big pain when editing. Wish they would fix this.

Works fine here!

[Don T]

Hello,
And, doesn't it make a difference if you are using the selection tool in the window or in the time line ruler? How can you be sure that the non visible tracks are still selected? When using the ruler to select, all tracks should be edited except the ones that are hidden not just scrolled out of view. I'm going to go back and check version 5.

In other words, how are you adjusting the selected area while zoomed?

ON Edit: Both dp 5.12 & 7.1 are behaving the same for me. If I select a region over multiple audio tracks, zoom, scroll then edit, all tracks selected are edited including the ones not in view (but not hidden in the view filter). I adjusted the selection boundaries while zoomed using the I beam tool. The selection part in both manuals reads the same.

In summary: I don't seem to have that problem with dp, I must be confusing it with PT.

[Shooshie]

Even when I use the "W" key to edit all visible whatevers, the ones scrolled off screen still are edited properly. The idea being that they are visible, just needing a larger monitor to see them. I haven't seen the problem in question in any version of DP so far.

[newrigel]

Even when I use the "W" key to edit all visible whatevers, the ones scrolled off screen still are edited properly. The idea being that they are visible, just needing a larger monitor to see them. I haven't seen the problem in question in any version of DP so far.

How you guy's remember all those key commands is beyond me...

[Shooshie]

Even when I use the "W" key to edit all visible whatevers, the ones scrolled off screen still are edited properly. The idea being that they are visible, just needing a larger monitor to see them. I haven't seen the problem in question in any version of DP so far.

How you guy's remember all those key commands is beyond me...

For me, many of those commands had to be committed to memory so that I could work fast enough to keep up with the whims of clients, who wanted to be creative without technical obstructions. Basically, I was creating what they wanted, but almost at dictation speeds. It was possible in DP if I used Commands and QuicKeys. Periodically I'd have to tell them to wait, but as often as possible I'd work as fast as they could think, often having entire 8-bar sections done before they told me what they wanted -- simply because I already knew.

Anyway, those commands come in handy when working like that. I find that now that I'm only working for me, I work much, much more slowly, often dwelling on a few little details for hours. Maybe I need to hire myself.

Shoosh