Pro Tools 11 Recording Timing

[Scott Senchak]

hello,

I have a FireFace UFX. When I hit record in protools everything sound great. There is no latency noticeable while I'm recording. Then when I'd play back what I just recorded everything sounded late. So I thought to test things I would throw a mic next to my monitors and record the click track. Sure enough after recording it there was about a 117600 sample delay.

Does anybody know why this is happening? I don't hear that delay while recording but after recording the wave file seems to have a delay.

Thanks for the help.

[Scott Senchak]

Also, there are no plugins running on any channel. The track isn't going through any bus either.

[Southsidemusic]

Originally Posted by Scott Senchak

Also, there are no plugins running on any channel. The track isn't going through any bus either.

We need more info and nobody will be able to help without details

Read the http://duc.avid.com/showthread.php?t=300050

Best Regards
Chris

[Scott Senchak]

Oops, sorry about that:

Windows 8 Pro 64
Intel Core i7 3930K CPU @ 3.20 Ghz
12 GB installed memory

FireFace UFX through USB

Protools 11

What I did was solo the click track through my Mackie HR824 monitors and record a "test track" through a M Audio Sputnik into a Goldenage Pre 73 and into my FireFace to record the click track. I muted the "test track" to avoid feedback. In Protools 10 the recorded "test track" showed up pretty much inline with the grid in protools 10.

Then, in protools 11 I repeated the same test. In Protools 11, the "test track" showed a significant delay after recording. It was about 411600 samples.

Then I went back to PT 10 and it was less of a delay than Protools 11, but now there was a longer delay than the first try.

Let me know if you need any more info. Thanks

Since

[Scott Senchak]

Then, lastly I am an Ohm studio user. I opened up Ohm and tried the same exercise there and there was very little delay after recording. I don't know how to measure the samples there, but when playing that recorded track with the click track there was no audible delay... unlike the protools exercise where there was a big delay. Hopefully that explains the problem. I'm thinking it is a pro tools issue and not a FireFace UFX issue because Ohm studio didn't have the problem.

Thanks,
Scott

[Southsidemusic]

Originally Posted by Scott Senchak

Then, lastly I am an Ohm studio user. I opened up Ohm and tried the same exercise there and there was very little delay after recording. I don't know how to measure the samples there, but when playing that recorded track with the click track there was no audible delay... unlike the protools exercise where there was a big delay. Hopefully that explains the problem. I'm thinking it is a pro tools issue and not a FireFace UFX issue because Ohm studio didn't have the problem.

Thanks,
Scott

Are you using delay compensation on any of the tracks when you record?

Are you recording via/thru the Totalmix software or just thru the interface into PT?

Firewire or USB2?

[miketeachesclass]

There was a similar bug that happened when PT9 came out. A bunch of us were able to reproduce it by printing a click track and re-recording it onto new audio tracks. The recorded audio always showed up late. If I remember correctly, around 5000 samples.

It would be worth trying to see how reproducible this is.

[alexmac010]

Originally Posted by miketeachesclass

There was a similar bug that happened when PT9 came out. A bunch of us were able to reproduce it by printing a click track and re-recording it onto new audio tracks. The recorded audio always showed up late. If I remember correctly, around 5000 samples.

It would be worth trying to see how reproducible this is.

How was this resolved? Was it a recognised bug or was it a setup thing? I really want support from Avid on this issue - is this forum the best way of getting answers?

[miketeachesclass]

Previously, it was a recognized bug, and avid fixed it. I'm sure you can find an older thread about the original problem if you search.

Also, I'm not saying that this is definitely the issue. I haven't updated to 11, and won't until my current project is complete. At that time, I'll check this as well.

[Scott Senchak]

Yea, I remember reading about this problem before. Hopefully they can help us find a solution. Other than this problem PT11 is pretty great. So much more stable, quicker, and useful than previous versions.