Re: latest CVS commit
Jeremy Hall <jhall <at> maoz.com>
2003-04-01 23:41:06 GMT
In the new year, Kai Vehmanen wrote:
> On Sat, 22 Mar 2003, Martijn Sipkema wrote:
>
> It's not really significant. With 2ms engine period/buffersize, and 1ms
> interrupt interval, the additional wakeup latency is max 1ms. You'd of
> course have to utilize a three-period driver buffer between the driver and
> the clients (-> 6ms of driver/device buffering).
>
Please understand I am taking this out of context, as I haven't fully
digested this thread, but these words by themselves aren't going to cut it
for me. It is not acceptable to me to have to endure 6ms latency. I
think we should be able to run 64 frames_per_cycle and deal with the
constraints. I personally would like to see 96khz at 64 frames_per_cycle
reliably, and since I use multiple applications at once with jack, my
understanding is they need to be OOP clients. My understanding is ardour
must for other reasons, although we have discussed that before, so for me
that means that every cycle counts.
My understanding is that the HDSP might help me with some regards, but if
I need to run a compressor, I MUST process in software, unless somehow the
hardware can be given an asm program that does the same things the host
processing would do, i.e. the ladspa plugins etc gets pushed down into the
hardware somehow.
_J
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
(Continue reading)