DP9.13 Crash after delete-key-editing a region of audio...

[npj]

Hi all,

Wondering if anyone else is experiencing this bug...

I'm getting a crash ('application has unexpectedly quit' dialogue) when I try to create fades (via dragging the top corner of the region), after editing the region using the delete key, for any region of audio for which had pre-existing fades (before the delete key edit).

In other words...
- Start with an audio region that has fade ins/outs already applied.
- Select any portion of the region and hit the delete key.
- For any these new regions, adjust the fade in/out point via clicking and dragging.
- Crash.

This also happens when cutting instead of deleting part of the region.

This is happening on two different Macs running DP 9.13.

Wondering if anyone else is experiencing this. I've made a TechLink on MOTU.com.

I've moved back to DP 9.12 for now. It's really hard to not edit regions using the delete key!

[robinsky]

Same here!!
It seems crashes only appear when clicking and dragging the fade. Create fade through only clicking or marking and hitting ctrl-f are ok!

[MIDI Life Crisis]

Thanks for that warning! I've yet to install 9.13 but it sounds like a fix is already in order for something like that, especially if it is widely repeatable.

Anyone else?

[npj]

Same here!!
It seems crashes only appear when clicking and dragging the fade. Create fade through only clicking or marking and hitting ctrl-f are ok!

Good to know... Yes, you need to use the delete key for editing... Then you need to attempt to create (or adjust) a fade by dragging.

I was testing with mono audio... I assume it happens with stereo audio too...

It's a pretty common thing for me to do... So back to 9.12 for me...

[cuttime]

Just confirmed this here, too.

[MIDI Life Crisis]

How'd THAT ONE get past the testers? I adjust fades a lot in my audio work. Guess I did good by not updating too soon.

[npj]

How'd THAT ONE get past the testers? I adjust fades a lot in my audio work. Guess I did good by not updating too soon.

Yep, a little concerning that none of the testers found it... I was only using 9.13 for a day or two before I noticed...

MOTU said (via my TechLink) they're aware of the problem and are working on it. Hopefully we'll get a 9.14 update soon.

[terrybritton]

Egadszookums!

[MIDI Life Crisis]

That's pretty serious. I hope it was something that happened during compilation and can be fixed. Wait, I have NO IDEA what I am talking about, do I? LOL

[cuttime]

Hey Terry! Perhaps you con confirm that this is a Mac or Windows issue...

Perhaps someone can chime in, too- If DP automatically submits a crash report, is it necessary to file a TechLink?

[terrybritton]

Hey Terry! Perhaps you con confirm that this is a Mac or Windows issue...

I'll test on the Windows version later tonight after dinner.

Terry

[Robert Randolph]

Happens 100% on both of my macOS machines.

[terrybritton]

Yes, it crashes in Windows when I actually follow the instructions (having pre-existing fades, deleting, making new fade). (This is an edit - sorry if you got your hopes up from my original.) It also crashes if I delete ONE side having a fade-out and try to adjust the next fade in.

Let me know if you need me to try anything else.

Terry

[npj]

Egadszookums!

Precisely.

Minor update: This only happens when the delete-key-edit-of-an-audio-region is done in the Sequence window. If you delete in the Tracks window, then dragging the fades in the Sequence window works successfully.

[ronsaltmarsh]

Any word on a fix? Crashing consistantly here too.