Let me try this again... Latency

[Kang]

Does Tracktion automatically account for latency. If I'm recording with 60ms latency will it move it back for me? (using asio drivers)? Or do I need to fill in the value?

I know this is easy to test out, but I have, and most the time it seemed like it did, but then later it seemed like it wasn't so I'm confused. Sorry for the dumb question.

Thanks

[valley]

Tracktion *should* automatically account for latency.

You need to run the autodetect feature though to get everything properly snapped in time IIRC.

[Kang]

How do I get that to work? Do I need to run a tone through it or something. I've tried doing it and it doesn't work, or gives me like 5 latency values.

Thanks

[valley]

no, what you do is run a cable from your output to your input and then hit the test button.

Tracktion sends a signal and measures the round loop time.

Once done, you should be properly synced for playback, and record.

[Kang]

Thanks a lot.

One more quick question though. If I do this, should I monitor through tracktion now, via ' enable end to end' on the tracks I'm recording?

Normally I'm monitoring my inputs through a mixer for o latency monitoring, (otherwise I'll hear the delay) and turning end to end off.

Hope that makes sense.

[valley]

when you do the test, you don't need to worry about end-end. Just run a cable from out to in on your soundcard, and hit the 'auto-detect' button.

Once you've done that Tracktion should be able to adjust for whatever you are trying to do.

[bassport]

Where is thist "test" button? That'd be good to know, because I never heard of this function you're referring to...

[valley]

[bassport]

Thank you!

I'm gonna try that.

Would'nt it be sufficient to just fill in the latency there?

I know this must be in the manual somewhere, but what exactly does this "time adjusting" do? It can't record something in advance that isn't even playing yet now, can it?

[djsubject]

not quite yet its just to get yr line in's to be in time 4 playback 4 any thing u record

[valley]

Would'nt it be sufficient to just fill in the latency there?

If you know it. It isn't likely to be what you are expecting though. The latency due to ASIO buffers is only one aspect of overall end to end latency.

I know this must be in the manual somewhere, but what exactly does this "time adjusting" do? It can't record something in advance that isn't even playing yet now, can it?

No. The point is not to fix the take when you are recording, but to correct the offset when you have finished. IE, if your card delays incoming audio by 5.9ms, anything you record will be reaching Tracktion 5.9ms later than the currently playing audio, so to correct that Tracktion just needs to timestamp the incoming recording as if it had happened 5.9ms earlier. That's basically what it does.

[bassport]

Alright, thanks!

[Lunch Money]

One more quick question though. If I do this, should I monitor through tracktion now, via ' enable end to end' on the tracks I'm recording?

Not if your latency is actually 60ms. Anything longer than (for me, mileage may vary) 10 ms and the slap-back echo effect is too much to handle in realtime.

[Kang]

yeah I figured that out, I just thought that after I did the auto detect thing it might delay the playback to match the latency so I could monitor with no slapback, but I realized this isn't the case, as 0.02ms latency was found, and I actually am using 56 ms of latecy on my card.

Thanks for the help, I'm pretty sure I have everything figured out now.