B4 II Causing PT8 to Crash

[holden]

Does anybody have any info on this?

Everytime I try to use B4 II it causes PT8 to crash. I have tried reinstalling B4 II (latest version) a number of times. I've run the ProTools Pref and Database Helper (for 10.5) a number of times. I've confirmed that all my plugs are up to date. I've repaired permissions, etc..

I am using 96K/24b sessions and run OS 10.5.5.

I have an inactive channel in my session containing B4 II. When I activate it and click on the B4 II plug to open it, it consistently causes PT to crash.

As a workaround to that I have tried deleting the track containing B4 II from the session. I've also tried opening a fresh B4 II on a new aux track. Sometimes this works for a couple of minutes, but then I'll click on something and PT crashes again.

Can anyone help me on this? It costs so much time every time I have to restart PT that I'm about to give up and remove B4 II altogether. Hate to do it since it is the best of its type that I have heard.

Thanks.

[WernerF]

I use it in 8 all of the time and have had not a single problem. I don't ever work at 96K though. Always at 44.1. The higher sample rate might be involved in the issue. You might wanna try it at 44.1 just to troubleshoot. Who knows.

[holden]

Evidently it is not B4 II that is the problem. I stripped it from my session and tried to use the Digi organ sim, DB-33 and had the same problem.

Thanks anyway for letting me know it works for you.

[the dude]

It is most likely that B4 II is not the issue but most likely that B4II has a conflict with another plugin(s)

try having only B4II and the Digirack Plugins in the plugins folder - relaunch PT and see if it is the problem
if not add the others a few at a time

[Craig F]

might want to check the permissions on your plug-ins (Permission Repair does nothing here) I find that sometimes plugs get installed as read only

[the dude]

I find that sometimes plugs get installed as read only

Having a plugin as read only will not be a problem since these files ( plugins ) are not modified by pro tools at all and are all essentially read only
In fact some plugins are installed as read only for the Admin user and with root / system user access only
the Phoenix plugin for example is just one among many others

[holden]

Originally Posted by the dude

It is most likely that B4 II is not the issue but most likely that B4II has a conflict with another plugin(s)

try having only B4II and the Digirack Plugins in the plugins folder - relaunch PT and see if it is the problem
if not add the others a few at a time

I've now tried to open my session with no plug-ins in the plug-ins folder other than Stereo Mixer.dpm and B4 II.dpm. PT still crashes when I activate the track that has B4 II as its only insert.

Evidently the problem is not with compatibility with other plug-ins, unless Stereo Mixer is the problem in which case I'm screwed.


Any other ideas? I suspect there is something wrong with the session, but I have tried Save Copy In ... and that has not helped.

[holden]

I got the session to work by opening a new blank session and importing the tracks from the session that was crashing.

Interestingly, and with typical Pro Tools opacity, when I imported everything in one shot (all channels, audio, markers, Tempo/Meter Map, Key Sig/Chord Map, Markers/Mem locations, Mic PRE settings) the resulting session crashed as before. But when I imported all the channels and audio first, then imported the maps, locations and PRE settings, the session worked fine.

I've now squandered a couple of days of work on this problem with the final result being no more than a workaround. Given the endless stream of problems provided on the DUC, the lack of diagnostic tools in Pro Tools is truely appalling. Do Logic users have these problems?

[allstaar]

Yes, sorry to hear you had your time wasted by this. I know how frustrating that is.

BUT, on the bright side, finding out about the import session data procedure when dealing with corrupt sessions is worthwhile. I'm sure you'll run into a corrupt session again sooner or later and now you'll know what to do without wasting too much time.
By the way, once you've imported tracks into a fresh session and got it working the problems rarely occur again.

Not sure if that's optimistic or pessimistic

[holden]

Originally Posted by allstaar

Not sure if that's optimistic or pessimistic

It is optimistic and appreciated.

Thanks.