Protools 12.5.2 repeatable crash when selecting midi region

[john1192]

Originally Posted by Stereo Missile

Thanks John,

Unfortunately I can't post the session because it's a commercial job that I can't release publicly (I do corporate and advertising stuff).

If I get a session which is just a muck around session to do it I will post it for sure.

copy that ...

[holler]

This has happened to me as well! I find that most crashes happen when I work "too fast" for Pro tools to handle. Like I've started doing something before the previous process has completely finished

[Stereo Missile]

Originally Posted by holler

This has happened to me as well! I find that most crashes happen when I work "too fast" for Pro tools to handle. Like I've started doing something before the previous process has completely finished

Yes exactly.

[AlexLakis]

Originally Posted by holler

This has happened to me as well! I find that most crashes happen when I work "too fast" for Pro tools to handle. Like I've started doing something before the previous process has completely finished

Pro Tools stability has always been affected by "fast clicking". I remember when I was working out in Los Angeles, our normally stable HD and Mix rigs would sometimes be plagued with errors depending on which producer was working on them at the time. The term "crazy clicker" was thrown around a lot.

For example, if you try to bounce immediately after you save (IE the save command is still "completing" while you press the key command for bounce-to-disk) sometimes the currently selected region will be DELETED!

Pro Tools has always had "a rhythm".

[john1192]

Originally Posted by AlexLakis

Pro Tools stability has always been affected by "fast clicking". I remember when I was working out in Los Angeles, our normally stable HD and Mix rigs would sometimes be plagued with errors depending on which producer was working on them at the time. The term "crazy clicker" was thrown around a lot.

Pro Tools has always had "a rhythm".

change your internal personal Grid Value !!! Quantize yourself into the Box .. i have experienced as well over the years ... have told many mixers that used my systems .. slow down bro !! LOL ..

[nbot]

I am also experiencing this problem.
Avid can't seem to help me.

It seems that it's not so much if I'm working fast.

From what I can tell, I start a new session, work in it, everything is fine.
Then I if I close the session and reopen it, some randomly chosen MIDI region (or a few even) creates the crash. It crashes on the first click even, not the double click. Spinning ball.

A workaround, a terribly inconvenient one, is to select the area around the region and consolidate it. That SEEMS to keep the problem at bay, but it's a real hassle.

With a midi track count up near the track limit, I either have to wait for the crash to find the culprit(s) , or just consolidate everything and then deal with a zillion regions, most of them blank. Can't offer a real solution but I've been looking for weeks for even someone else with the same nightmarish problem and it looks like you and I are the only two.

I write music for film and TV and this is really slowing me down.

Is it a graphical problem? A random, unconsolidated MIDI region being clicked or half-clicked, causes it. It's crazy.

It started when I upgraded my OS. I did a full reinstall and now I'm back to the old OS, pretty much a clean install. Problem was still there.

and yes I've trashed the prefs. Believe me. Trashed em good.

[Stereo Missile]

Originally Posted by nbot

I am also experiencing this problem.
Avid can't seem to help me.

It seems that it's not so much if I'm working fast.

From what I can tell, I start a new session, work in it, everything is fine.
Then I if I close the session and reopen it, some randomly chosen MIDI region (or a few even) creates the crash. It crashes on the first click even, not the double click. Spinning ball.

A workaround, a terribly inconvenient one, is to select the area around the region and consolidate it. That SEEMS to keep the problem at bay, but it's a real hassle.

With a midi track count up near the track limit, I either have to wait for the crash to find the culprit(s) , or just consolidate everything and then deal with a zillion regions, most of them blank. Can't offer a real solution but I've been looking for weeks for even someone else with the same nightmarish problem and it looks like you and I are the only two.

I write music for film and TV and this is really slowing me down.

Is it a graphical problem? A random, unconsolidated MIDI region being clicked or half-clicked, causes it. It's crazy.

It started when I upgraded my OS. I did a full reinstall and now I'm back to the old OS, pretty much a clean install. Problem was still there.

and yes I've trashed the prefs. Believe me. Trashed em good.

Yes my impression is that this is not an issue related to preferences, it seems like a bug.

[Hanswurstlsepp]

Originally Posted by Stereo Missile

Yes my impression is that this is not an issue related to preferences, it seems like a bug.

To me it seems like a bug, too. I found no way how to reproduce.
It is related to selecting midi regions.
Got about 4 crashes per day when working with midi in PT.
After committing InstrumentTracks all is fine - so "I think" it only happens when selecting a MidiRegion/Clip.

[travisrex]

I've done a screen recording of the bug for anyone who's interested



Note: The Quicktime Screen recorder doesn't show the Beachball. You can see in the quit window when Pro Tools is hanging.

I was selecting a VSL Instruments PRO VI (Violins) to bring up the Midi Editor when Pro Tools started hanging.

I'm using
PT12.5.2
OSX 10.11.2
Mac Pro 6.1 12 Core 32 GB RAM

[Hanswurstlsepp]

Originally Posted by travisrex

I've done a screen recording of the bug for anyone who's interested



Note: The Quicktime Screen recorder doesn't show the Beachball. You can see in the quit window when Pro Tools is hanging.

I was selecting a VSL Instruments PRO VI (Violins) to bring up the Midi Editor when Pro Tools started hanging.

I'm using
PT12.5.2
OSX 10.11.2
Mac Pro 6.1 12 Core 32 GB RAM

Cool, so is this reproducable with your session ?