Crashes, 96K recording

[Shifted Music]

I've had several crashes in the last couple days. several were when in a session and doing some recording and then recording on another track, then hitting "I" to input monitor on another (3rd) track or back to the first and get a beach ball.

This has happened about 4 times the last few days. Trashing refs doesn't seem to work. making a fresh session and importing session data does though.

not a busy session, pretty limited plug ins.

just did Sierra fresh install earlier in the week, so latest plug ins (not all I own are even in yet, just my main ones.). airport off, and or on.

MCdsp Filterbank, compressor bank, mc2000
Soundtoys v5
Plug in alliance, VSC-2, DSM2, BX-Digital, BX-Meter
Air plug ins Strike, structure, loom, hybrid 3 vacuum pro ect...
Dp Meter
Fabfilter Pro L
Avid classic compressors
Azoptope Delay, Neutron
Melodyne
MJUC
Acon Digital Verberate, Multiply
Sonnox Oxford, all plus de buzz, de click, de noise
The Glue
Waveshell 9.6 hybrid compressor and delay
Synthmaster
Nexus 2

Very few of these actually used in a session...

if anyone else has experience this similar issue we can coordinate more info to try and track something down...

Its not something I can seem to reproduce so not much I can do with tea support.

Ideas?

[jeam25]

Hi Jay !!

Guessing here ...

Are all plugins updated to their lastest version ?

Did you try launching PT with no plugins at all ?

And are all your OS optimizations done ?

http://avid.force.com/pkb/articles/t...Optimize-10-12

What version of PT and what interface ?

You have the lastest installer for your interface ?

[JFreak]

Remember that all plugins in a plugin folder are loaded into memory when PT starts, no matter if you use them in a session or not. Sadly it only takes one badly behaving plugin to crash the system.

[Shifted Music]

Originally Posted by jeam25

Hi Jay !!

Are all plugins updated to their lastest version ?

Did you try launching PT with no plugins at all ?

And are all your OS optimizations done ?

http://avid.force.com/pkb/articles/t...Optimize-10-12

What version of PT and what interface ?

You have the lastest installer for your interface ?

All plug ins recent downloads and installed, fresh OS install and fresh PT install as in from scratch re downloading latest installers for them all.

I did not try launching pt with no plugs ins because its not reproducible, as in its not every time. I will remove a MCDSP plug in that was def in an offending session and monitor everything today as I do more recording with in the same bunch of sessions.

OS optimizations were done, I just now turned off auto update in App Store prefs, but all the others were done. and pretty sure the crash happened both with and without airport on, just fyi..

PT 12.7.1. Mbox 3 Pro. latest drivers for interface.

All of these suggestions are my Normal operating procedure after 14 years daily pro tools usage, as yourself and its frustrating when this level of diligence still incites these errors...

is it a plug in? PT big, combo. just seems so hard now days to track these type of things down.

The do this and then crash every time stuff is easy to find and thus fixable in most cases but things that happen sometime are so frustrating.

if I get it today I will trash prefs, reopen pt and create new session and import session dates that has helped so far this week.

but as most of us I have work to do today with musicians in and out of the studio so cant very well TRY stuff to trouble shoot, I need to work around em...

We shouldn't have to do that. we used to not to very often in pro tools.. :-(

[jeam25]

Hi i understand the frustration .

Luanching PT without plugins is very important . In that process your gonna find if is a plugin the culprit . Just do it and run it a few times to see if it happen . If no then start adding the plugins by manufacturer ( my suggestion ) or 1 by 1 until you see the issue again .

Hope you find it friend !

[JFreak]

Originally Posted by Shifted Music

is it a plug in?

Easy to find out. Move all 3rd party plugins to unused folder and if the problem goes away, then some of the plugins cause the issue. Then just add plugins back, for example one manufacturer a time, until the problem comes back. Then you know which one it is.

[Shifted Music]

I removed all plug ins and was able to work the rest of the afternoon, although it was only on one session so I really don't know if I solved the actual problem...

this last week I saw the issue after opening and closing several sessions and then as I said recording or input monitoring a track then going to another one.

later in the week I will try and see if I can recreate it with a specific plug in.

at first I thought maybe it was mcdsp mc2000, but I had already removed that before the most recent crash I got this afternoon.

[jeam25]

Ok great ! Let us know

[Shifted Music]

Update.

Finished recording, stock plug ins only. Didn't get another freeze when hitting rec or input monitor.

I did put BX-meter back in then experienced these issues below and DID not get any further issues actually recording though. (I have yet to be able to test this particular thing below without BX Meter...FYI)

Then while listening back and messing about I used a eq7. sweeping a frequency on the hi mid band cause a crash.. twice..


then after several rounds of pref trading and restarts and what not I tried with channel strip thinking probably gonna be better..

Also got another crash.

So I can't believe that I'm the only one looking for offending frequencies with these two plug ins adding a decent amount of gain and sweeping around...

so I assume its something on my end.

which is pretty crazy when I've removed all 3rd party stuff (bx meter excluded for this test), done optimizations and did a clean fresh install...

Baffled.

[jeam25]

Hi ! bx plugins are known to cause strange behaviors specially with older versions . Beleive me i have at least 6 plugins of them running perfectly fine now .
Be shure to have installed the lastest version of them .

If you didnt have any issue without any 3rd party plugin as i understood then one of them is giving you trouble , maybe then is the bx meter ( my best bet ) without knowing what others plugins you have :-/ .

btw check for the lastest version update on every 3rd party plug you have .