FX-MAX.com

[Niko]

It'll be nice to input the buffer size manual (e.g. double-clicking on the latency value opens an input field). In my projects I'm working with a global "latency compensation subgroup" that delays all non-latency channels by the current buffer size to compensate the latency-affected channels (they're routed straight to the master aside this group). So the easiest way to handle FXT latency is to set the wrappers buffer to the same as the ASIO buffer and route them direct to master. But when the automatic detection sets a buffer of 2048 I can't set it to 4096 ('cause the slider ends up on 4000).
I did the settings finally via RegEdit but an easy manual input would be much more comfortable.

[max]

Thanks for idea

[Steve Rees]

This is actually a really good idea.

If you are running multiple instances of multiple plugins on a server, the network latency detector sometimes needs to be run several times before moving the latency far enough out for everything to be stable (when running many plugs, I've come across instances where latency for a particular plug on a server needs to be in excess of 20,000 for everything to work OK, and I might have had to run the automatic network latency detection routine 10 or so times for it to reach this conclusion).

It would be nice to be able to set the latency manually in excess of the 4,000 samples provided by the current slider, so that you could set the latency of all plugins to a very large figure to ensure total stability on playback, and on doing any audio exporting. With a host like Cubase SX2.01 with plugin delay compensation, this would work very well.

Steve

[max]

Thanks Steve,
I got it. BTW audio exporting should work OK with any latency, even zero (provided you are running under host which indicates processing mode - like SX or Nuendo - or pressed 'process' button on tool window)

[Firestorrmm]

Hi AWR,

Id like to put in a request for the latency settings to be available per report. For instance if you have a massive report and want it to run slower with more delays, you have to change the global preference settings every time assuming you have other smaller reports that do not use as much of a delay. With scheduling, one has to manually switch this setting within the global settings every time. Hence it would make sense to have the delay setting available and customizable per report.

Thanks

-Bill