I'm getting tired of this "There is a recording offset". There is a "Latency compensation" slider (actually, two of these) that you can use to get rid of exactly this recording offset. This is even mentioned in the manual, FFS. Stop spreading misleading information!Sascha Franck wrote:Usually, the ASIO4All driver will introduce quite some recording offset when recording audio (i.e. the audio is late).
Traktion 2 end-to-end latency issue...
-
- KVRist
- 284 posts since 8 Nov, 2004
-
- KVRist
- 488 posts since 2 Mar, 2004
I don't think he's providing any mislesding information. Regarding asio4all, I have the same experience. I cannot get the same latncy using asio4all as I can get with native asio drivers.wuschel wrote:I'm getting tired of this "There is a recording offset". There is a "Latency compensation" slider (actually, two of these) that you can use to get rid of exactly this recording offset. This is even mentioned in the manual, FFS. Stop spreading misleading information!Sascha Franck wrote:Usually, the ASIO4All driver will introduce quite some recording offset when recording audio (i.e. the audio is late).
And sure there is a latency compensation with Tracktion, but it doesn't do a heck of alot when when recording with end to end monitoring and latency is high. If you can't get your latency than use the direct monitoring function. Latency compensation only helps in your playback of recorded material.
-
- KVRist
- 284 posts since 8 Nov, 2004
This is an entirely different issue and depends largely on the quality of the WDM drivers.darcyb62 wrote:Regarding asio4all, I have the same experience. I cannot get the same latncy using asio4all as I can get with native asio drivers.
There is. But I was rather referring to the latency compensation that can be adjusted within asio4all. IOW, if you see a significant recording offset, this means that asio4all is not properly configured and not that this is inherent to asio4all in any way.darcyb62 wrote:And sure there is a latency compensation with Tracktion,
-
- KVRAF
- 13445 posts since 14 Nov, 2000 from Hannover / Germany
Whoops!wuschel wrote:I'm getting tired of this "There is a recording offset". There is a "Latency compensation" slider (actually, two of these) that you can use to get rid of exactly this recording offset. This is even mentioned in the manual, FFS. Stop spreading misleading information!
Sorry, seems I was still referring to an older version which didn't have that.
Will defenitely give it a try right now.
My sincere apologies!
There are 3 kinds of people:
Those who can do maths and those who can't.
Those who can do maths and those who can't.
-
- KVRAF
- 13445 posts since 14 Nov, 2000 from Hannover / Germany
Shit. Must apologize even more!
Just tried running Guitar Rig in standalone mode, using Rig Kontrol 2, but driven through ASIO4ALL (2.6). And guess what? It's performing BETTER than with the ASIO drivers coming with the Rig Kontrol!
Now, this is freaking amazing!!
But, no matter how you put it, there's still a slight recording offset. Not sure what this is related to, might as well be the Rig Kontrol, but I'm gonna try with a whole bunch of cards later on.
Anyways, for standalone operation of GR2 this is allready kickass.
Just tried running Guitar Rig in standalone mode, using Rig Kontrol 2, but driven through ASIO4ALL (2.6). And guess what? It's performing BETTER than with the ASIO drivers coming with the Rig Kontrol!
Now, this is freaking amazing!!
But, no matter how you put it, there's still a slight recording offset. Not sure what this is related to, might as well be the Rig Kontrol, but I'm gonna try with a whole bunch of cards later on.
Anyways, for standalone operation of GR2 this is allready kickass.
There are 3 kinds of people:
Those who can do maths and those who can't.
Those who can do maths and those who can't.
-
- KVRist
- 488 posts since 2 Mar, 2004
Thanks for the clarification and apologies if I misunderstood. The latency compensation in asio4all never seemed to do anything for me. I'll have to take another look at this based on your comments and Sascha's findings when I have some time.wuschel wrote:This is an entirely different issue and depends largely on the quality of the WDM drivers.darcyb62 wrote:Regarding asio4all, I have the same experience. I cannot get the same latncy using asio4all as I can get with native asio drivers.There is. But I was rather referring to the latency compensation that can be adjusted within asio4all. IOW, if you see a significant recording offset, this means that asio4all is not properly configured and not that this is inherent to asio4all in any way.darcyb62 wrote:And sure there is a latency compensation with Tracktion,
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
The bell just rang to let school in, so I don't have time to read. Apologies if this is covered; however:
Stick to the TonePort drivers. Set your buffer at a reasonable level. Tracktion will compensate automatically, so forget about the compensation slider. Ditch the ASIO4All and use the TP as your main soundcard, or if you REALLY must use the other one for some stuff, use a cheap mixer (saw a pic posted, so I'm guessing it's been suggested) to mediate between your 2 cards and your speakers.
I'll check back in later; I use a TP UX2 and also my Audiophile at times, so I have it all going on.
Greg
Stick to the TonePort drivers. Set your buffer at a reasonable level. Tracktion will compensate automatically, so forget about the compensation slider. Ditch the ASIO4All and use the TP as your main soundcard, or if you REALLY must use the other one for some stuff, use a cheap mixer (saw a pic posted, so I'm guessing it's been suggested) to mediate between your 2 cards and your speakers.
I'll check back in later; I use a TP UX2 and also my Audiophile at times, so I have it all going on.
Greg
