Gordon Scott wrote:
> On 21/07/17 08:18, Clemens Ladisch wrote:
>> What latency you can reach depends on how much other
>> applications and drivers interfere with the scheduling; on the Pi,
>> typical culprits are WiFi, ethernet, or USB.
>
> Indeed. Any serial and/or packetising interface will
On 21/07/17 08:18, Clemens Ladisch wrote:
What latency you can reach depends on how much other
applications and drivers interfere with the scheduling; on the Pi,
typical culprits are WiFi, ethernet, or USB.
Indeed. Any serial and/or packetising interface will certainly add
_some_ latency.
Robert Bielik wrote:
> I want to route input to output with minimal possible latency, this
> will run on a Raspberry Pi, and the latency should be < 1 ms.
This is easiest to do if the hardware already has this routing built in.
Otherwise, you have to do the capture and playback in software. See
Dear Clemens,
Thank you so much for the alsaloop tip, I just ran it with:
> chrt -rr 70 alsaloop -f S32_LE -C plughw:0 -P plug:ladspa -l 48
And it works perfectly, exactly what I needed!
Regards
/Robert
> -Original Message-
> From: Robert Bielik [mailto:robert.bie...@dirac.com]
>
Hello Clemens,
> Otherwise, you have to do the capture and playback in software. See the
> alsaloop tool. What latency you can reach depends on how much other
> applications and drivers interfere with the scheduling; on the Pi, typical
> culprits are WiFi, ethernet, or USB.
> Also see
Robert Bielik wrote:
> using the alsaloop tool and setting a latency, what does that mean
> exactly ? If I set latency to 48 frames (like below), does it mean 48
> frames per capture/playback, i.e. so total latency is 96 frames ? Or
> is 48 the total latency ?
As far as I can see, the buffer size
