Plug latency even when using analog output ???s

[mkline]

Don't get this one, I have all my outs set to analog out (1+2), and the plug is still reporting to the host 3968 samples delay ???

[7G]

Specs please...
Audio Card,sequencer,buffer size???

[mkline]

Don't see what it has to do with my specs...
If the plug reports a delay (latency) the host will trigger the midi earlier (in this case about 90 msec) to compensate. As I'm not using the usb for audio, this delay is too big.
When using the analogs out, the plug shouldn't report any latency, at least not that much.

[Hell Yeh]

The Virus|Control plug-in, itself, has an enormous amount of plug-in delay/latency. All DAW applications except for Pro Tools LE/M-Powered automatically compensate for this. However, plug-in delay is different from the latency you experience when recording through analog inputs. You will experience that no matter what unless your DAW or audio interface has some kind of direct monitoring feature that will allow you to hear the analog inputs without any latency. The best way to get around your problem is to reduce your hardware buffer to the lowest setting whenever you record or monitor your Virus' inputs.

[mkline]

Well I do monitor directly the analogs out (hardware mixer).

But as the virus plug shows such big delay to the host, this one will compensate and start to play the midi earlier, which is fine when using the audio from the plug thru usb, but is far too early when direct monitoring the analogs out.

I also tried to send the midi directly to the usb midi port or the standard midi port of the ti, but no luck, once the vst plug is used there is no other way to send the midi to the ti.

Anyway, for now I removed the plug as it's more trouble than fun (midi delay, clock out of sync, loud noises trying to destroy your ears, though this one may be related to the ti itself )

[marc]

Originally Posted by mkline

Well I do monitor directly the analogs out (hardware mixer).

But as the virus plug shows such big delay to the host, this one will compensate and start to play the midi earlier, which is fine when using the audio from the plug thru usb, but is far too early when direct monitoring the analogs out.

I also tried to send the midi directly to the usb midi port or the standard midi port of the ti, but no luck, once the vst plug is used there is no other way to send the midi to the ti.

Anyway, for now I removed the plug as it's more trouble than fun (midi delay, clock out of sync, loud noises trying to destroy your ears, though this one may be related to the ti itself )

the analog outs were never in time when using total integration. this has been discussed here and elsewhere many times. the delay has nothing to do with the latency compensation settings of the plug-in and cannot be overcome unless the sequencer provides a certain information. we are working with pretty much all sequencer manufacturers to improve this.

marc
access music

[mkline]

Then why not let the user be able to set the delay reported to the host.

I could compensate by setting a delay on the track itself (most host let's you do that). But it would be easier to do it on the plug itself.

Currently my routing is ti analog outs to mixer (audio doesn't go thru the host).
But if I want to record the analogs outs of the ti, the latency won't be the same anymore, as this time it goes thru my audio card, so I would have to re-adjust each track again.
By letting the user set the delay reported to the host, this would require a single setting change (on the plug).

[marc]

Originally Posted by mkline

Then why not let the user be able to set the delay reported to the host.

I could compensate by setting a delay on the track itself (most host let's you do that). But it would be easier to do it on the plug itself.

Currently my routing is ti analog outs to mixer (audio doesn't go thru the host).
But if I want to record the analogs outs of the ti, the latency won't be the same anymore, as this time it goes thru my audio card, so I would have to re-adjust each track again.
By letting the user set the delay reported to the host, this would require a single setting change (on the plug).

it is not that easy. the latency reported to the host has nothing to do with the problem. if there would be an easy solution to all that which doesn't require work on the hosts as well, we would have made use of it.

best, marc

[mkline]

Originally Posted by marc

[..]the latency reported to the host has nothing to do with the problem[..]

Hmm, then how do you explain this:

This is the audio received from the ti analog outs thru my rme 96/32 (using 128 buffer sample + the 32 "safety" buffer).

The first track doesn't use live mode, the ti reports about 3000 samples delay to the host (C4). (note that we have much less than 3000 samples, could be due to a cubase limit ??).
In the second track, Live mode is this time enabled and the ti plug reports 512 samples to the host.
For the third track I removed the plug and sended the midi directly to the ti driver.

In this case, when using the plug, it would be nice to set manualy the delay to report to the host, no need to set up each track.

[marc]

mike,

i appreciate your effort in showing us how things look in terms of latency. i know that all - since years. if there would be an obvious and easy solution, you might imagine that we would have implemented it by now. unfortunately, to explain to you in deep why your idea doesn't work, would require me to give away intellectual property which we prefer to stay with access only.

best, marc