Bugs and crashes with Btt 4.12 on Pro Tools 11

Hi, I´m getting lots of "Pro Tools unexpectedly quit" when I try to open Sessions with more than one Instance of Battery 4.
Also the inputs of the separate Instrument tracks change, when I reopen a session (which I can only do by creating a new session
and importing the one that crashes, if I try to open it the usual way). The separate inputs change between the Battery instances, if you understand what I mean, i.e. when I have Instance 1 for Beat No.1 and instance 2 for Beat No.2, and 5 separate Stereo-Instrument-Inputs for each instance, after saving and reopening a session the BassDrum from instance 1 will be heard on the snareDrum-Input of instance 2 and so on. Since I sometimes have 8 to 10 instances of Battery running one can imagine the confusion.
Any help is much appreciated.

 

No problems with the Battery updater here in PT11.1.2. That leads me to ask why do you have more than a single instance of Battery 4 in a PT session, and for that matter why 8 or 10?
What do you mean by 'opening the session in the usual way'? Do you open PT11 via the program icon or double clicking the session? Double clicking the session can have problems especially if you have PT10 co-installed on your computer. For that matter what computer platform and operating system are you using? That kind of info will help.
Lastly - have you asked about this over on the DUC?

 

We´re trying out different Beats that I programmed on different tracks. Sometimes we want to try 10 different programmed beats on one song.

Pro Tools menu-File-open session

Mac Pro 2,4 GHz 12-Core Intel Xeon (Westmere) 32 GB RAM, OSX 10.8.5,/ PT 11.1.2

Yes

 

Where on the DUC did you post about this? I hang out there on a regular basis and haven't seen it lately.

The way you're going about this all wrong. Assuming you're using the same kit all the way through just do this: have Battery 4 on an Aux track in PT. Have as many MIDI PT tracks as you need. Then one at a time route the output of each MIDI track to the instance of Battery you have. Another way this would work is to route each MIDI track to the Battery 4 instance on the Aux track but to a different MIDI channel and mute all but the MIDI track you want to hear. There might even be a way to do this with playlists but I'm not sure about that.

 

Just because you don´t understand the way I work doesn´t mean I´m doing anything wrong. I know what you´re trying to say, but it doesn´t apply to my problem at all. I´m not using the same kit, each instance has its own kit, and I´ve been working like this for decades and don´t need any advice on how to work with Battery.

 

Well excuuuuuuuuse me for trying to help. You couldn't possibly have been working this way for decades with BFD. The thing you fail to realize is the way that you're working might just be the root of the problem. So each instance has it's own kit - are they each different kits? If not then the way I outlined would be the way to go. If you don't need any advice on working with battery then why are you posting here?

 

Facepalm..Of course they are all different kits, and no, you were not trying to help at all. I wasn't "asking for advice on working with Battery", I reported a bug and crashes and was asking for help with that.

 

You never said until now they were all different kits. You really were asking for help in working with Battery4 because you were/are having crashes. Can't provide a cure without trying to fix the symptoms and it might not be that the PT update is the cause of your problems but the way you are working with Battery 4. I provided a way to try and diagnose your problem. Pare things down to the simplest of ways of working and go from there. It's called basic troubleshooting.

Would you mind providing the link to the DUC where you asked about this? I'd like to see the responses you got if any.

 

I think you'll find mhmh stated on post #5 that they were different kits.

It seems a perfectly normal way to work when experimenting with different drum tracks to have multiple instance of Battery each with their own kit.

Unfortunately I don't work with PT so cannot offer any advice either, but Cubase has a similar confusion, where each instance of Battery is called "Battery", so that also gets really confusing with multiple instance of any plug in, I assume you are struggling with the same issue.

Though that is Cubase/PT issue, not the plug in itself. Though Cubase does not crash, it just leaves the user confused, it sounds like PT is also getting confused as well.

 

Thank you Andyjh, and you've got a good point there. Other VIs like Structure name their instances x-1, x-2 and so on, so there's no confusion.
This could be a hint and a feature request for the NI developers.