Jim Blokland:

Hey Isaac:

Thanks for this.  Removed all levels, effects, keyframes from the sequence.  Rolled a whole bunch of bits around – audio, video, slides, etc – no crashes.

Of course, as you're no doubt aware, I need all those things in my sequence...and in all previous version of the software, was able to trim with no issues.

Thanks for troubleshooting.  Let me know if there's anything else you need.

Best, JIM. 

Jim and Iassac

I updated the case and told support this bug was confirmed and attached info and screen shots.

Thanks for the added help on this one.

Marianna

Thanks Marianna!  Really appreciate it.  Hope they can issue a quick patch soon.  I'd rather not roll back, if possible.  Other than this bug, 2018.10 seems pretty solid.

Best, JIM.

Good to know. I havent had any issue until I tried yours so thats my first bugaboo too

marianna

Marianna:

Good to know. I havent had any issue until I tried yours so thats my first bugaboo too

marianna

Since this is pretty serious, may I assume that a fix will be released asap? Like when 2018.7 was released and it would not even do a decent video playback on Macs, and a 2018.7.1 was made available within a week?

Trim with audio-scrub is a basic function as well. It's a real handicap to suddenly not have it.

Arnoud

This is happening to me too. Sometimes I get the segmentation error, and sometimes it just pinwheels forever. I just found this thread so haven't tested it with/without audio dissolves, but it happens more than half the time I try to trim.

I've just been inserting filler and extending edits as a workaround, but often end up trimming before I can remember not to.

MC 2018.10, MacBook Pro mid 2012, 2.6 GHz i7, Mac OS 10.13.6

Tim

+1 since I upgraded to 2018.10

I have the exact same problem. Just rolled back to 2018.09 since I couldn't unlearn my fingers not to trim ;-)

I really look forward to the fix of this bug bacause 2018.10 seemed A LOT more responsive when working in the timeline overall which was a big relieve coming from .09

Kind regards Per

I rolled back to 2018.09 too and haven't crashed since. Good call. I had a few other new factors which I thought might be making things unstable (new big project on this fairly old computer, new audio hardware), but that did it.

I love Avid for keeping past versions available!

Tim

Has this been fixed in 2010.11?

Yes, in AvidMC v2018.11 Win/MacOS trimming with mouse works well.

In my experience 2018.11 is extremely stable. Current project is pretty straightforward (almost no FX) but I have had problems using previous versions even with basic timelines. So try 2018.11!