Interesting occurrance with Slate Trigger.

[Jordon]

So, while tracking drums this weekend, I had something weird going on with Pro Tools and Trigger. I'll try to explain it the best I can.

While tracking drums, I'll usually throw trigger on a duplicate of one of the kick mic tracks to beef the kick up for a bit of "wow factor" for the drummer and to bring a bit more quick definition to things. I've been doing this for a while, but something odd started occurring this past weekend.

Usually I'll take the inside kick mic (a Sennheiser E901), duplicate the track in Pro Tools and slap Trigger on there in live mode with whatever random-ass sample I decide to go with for the sessions. Then I record arm the three kick tracks: Kick In, Kick Out, and Kick Trig. Kick In and Kick Trig are coming from the same input, so they are, theoretically seeing the same signal. This has worked a charm for the longest time, but here's the new strange bit:

They are not recording the same thing.

The Kick In track is just fine. The signal looks as it should.

The Kick Trig track, however, is about 30ms (it varies, and is never consistent) BEHIND the Kick In track, and about 10-15db quieter overall. The signal looks squashed and weird.

The fucked up thing is this: It sounds fine until I deactivate Trigger.

I have delay compensation on "Long," but I have it on "Long" on every session I do, so I'm not sure this is the issue. I'm running PT10, by the way.

Again, when Trigger is active, it sounds fine. So it's not screwing anything up when monitoring or listening back, and when I go to edit, I delete the Trigger track anyway, so it doesn't screw me up there, either. It's just strange, and I'm curious if anyone else has experienced this.

Maybe I'm just slow and haven't noticed it before.

 

[heshian46]

Does it do the same thing if you send the orig. kick track to another track and record its output? (as opposed to just duplicating it)

 

[Jordon]

Does it do the same thing if you send the orig. kick track to another track and record its output? (as opposed to just duplicating it)

Nope. Strange, yea? I always print any samples when it get to the mix stage, but what it's doing right now is just weird. It's like it's somehow going through some sort of weird processing chain before it lays the track....but that would be impossible.

 

[heshian46]

Sounds to me like an interface issue. Like there's somethings up with the internal routing. This never happened w/ the 003 rack you had before correct? And now you have the C24, maybe its the desk?

Just thinking out loud.

 

[Jordon]

Sounds to me like an interface issue. Like there's somethings up with the internal routing. This never happened w/ the 003 rack you had before correct? And now you have the C24, maybe its the desk?

Just thinking out loud.

The desk has no audio routed through it.

It's strange, I did a prepro session with a band a week or so prior to this one and it wasn't happening then. It started with this project. I'll try to post a few screen caps later.

 

[AudioGeekZine]

two tracks with the same input recording simultaneously and the waveforms are different?

 

[Jordon]

Yup. As soon as I get to work, I'll grab some screen caps of it and post 'em up.

 

[Fox Mulder]

That's Avid.
Have you tried putting Trigger on an aux track instead?
Just to be clear, you can record one "kick in" track and do a parallel send to an aux track.

 

[AudioGeekZine]

Trash the disk allocation database. Usually recording/disk related glitches are because of corruption there. I've seen a lot of weird stuff happen.

I've had audiosuite print audio from outside of my selection from different projects.