STRIKE! Dropping Styles And Changing Kits On The Fly?

[LightWing]

I've been using STRIKE since the 1.0 days. Weird thing has hapened to a STYLE I have been using for years. It will run fine and then about 1:45 into a track it SWITCHES Styles and Kits and the Intensity goes from 78% to ZERO!

If I double click on the STYLE it restores itself for a short period and then does it again....Wash, Rinse, Repeat!

If I use a different Kit the same the happens.

Trashed the DBs and Prefs too...same thing happens.

Buffers? Doesn't matter...set from 64 thru 512 and it does the same thing.

Deinstalled PT back to 10.3.6...same thing. Reinstalled PT 10.3.7...same thing.

A sample song where this happens has TWO tracks...EZ Keys Piano and Strike for Drums and both are Stereo Instrument tracks so this is not a resource issue.

I'm using a Quad Core Xeon machine, 8GB RAM, Win 7 64-Bit SP1, plenty of disk space too.

Both Drives have been Defragged.

Everything is up to date. PT 10.3.7, Strike 1.5.1.15293, Delta 66 interface up to date as well as Midi Sport Drivers.

I am also using Axiom 49 for trigger the Strike patterns. I use Strike in Latch mode and Content is set for >400MB

Any ideas?

[sunburst79]

Originally Posted by LightWing

I've been using STRIKE since the 1.0 days. Weird thing has hapened to a STYLE I have been using for years. It will run fine and then about 1:45 into a track it SWITCHES Styles and Kits and the Intensity goes from 78% to ZERO!

If I double click on the STYLE it restores itself for a short period and then does it again....Wash, Rinse, Repeat!

If I use a different Kit the same the happens.

Trashed the DBs and Prefs too...same thing happens.

Buffers? Doesn't matter...set from 64 thru 512 and it does the same thing.

Deinstalled PT back to 10.3.6...same thing. Reinstalled PT 10.3.7...same thing.

A sample song where this happens has TWO tracks...EZ Keys Piano and Strike for Drums and both are Stereo Instrument tracks so this is not a resource issue.

I'm using a Quad Core Xeon machine, 8GB RAM, Win 7 64-Bit SP1, plenty of disk space too.

Both Drives have been Defragged.

Everything is up to date. PT 10.3.7, Strike 1.5.1.15293, Delta 66 interface up to date as well as Midi Sport Drivers.

I am also using Axiom 49 for trigger the Strike patterns. I use Strike in Latch mode and Content is set for >400MB

Any ideas?

Any automation present? What happens if you export the MIDI to a a new session?

Frankly I haven't seen this and Strike has always taken a fairly long time to load kits here. So the idea of it switching kit mid song seems strange.

Does the kit or style change happen at the same time as a note or MIDI event? Is it possible that somehow you triggered this change on a previous pass and the data got recorded with the track? Or even some type of MIDI corruption issue. Importing the tracks into a new session may help determine this.

[LightWing]

No automation at all...BUT...now that you mentioned Midi Corruption...

Went into the Midi Event List just before this starts and sure enough....4 or 5 occurances of what appeared to be the Intensity parameter nosediving to ZERO!

Deleted them out and there you have it...FIXED!

Weirdest thing I've ever seen or had happen using STRIKE!

Thank you so much SB79.

[LightWing]

As an update I went back into the Midi Events list and cleaned out ALOT of trash that seemed to get generated. I only want keyboard notes to trigger the STRIKE patterns and nothing else...runs sweet! :)