From: FFADO <ffa...@ff...> - 2012-04-13 00:18:11
|
#216: Unhandled XRUN ---------------------------+------------------------------------------------ Reporter: j.silvestre | Owner: Type: bug | Status: reopened Priority: major | Milestone: FFADO 2.1 Component: | Version: FFADO SVN (2.0 branch) Resolution: | Keywords: Device_name: | ---------------------------+------------------------------------------------ Comment (by jwoithe): In relation to buffer sizes, there's a trade-off: the larger the buffer size the lower the rate of interrupts and therefore potentially there's CPU load savings to be had. On the other hand, if the buffers are too large it can be difficult to keep the device synced because of the way the various protocols function (with some devices being more prone to problems than others). I've seen numbers of 256, 512 and 1024 being mentioned in the context of "medium-sized". You reported that with a buffer size of 1024 you managed to get an xrun. In a way that's good because it obviously didn't take too long to trigger; I suspect it should be fairly easy for this test to be replicated to recreate the accidently lost log file. This is probably valuable since it may give us an indication as to what went wrong (that is, whether there is a problem lurking within FFADO, or if it's due to some as-yet-unidentified local issue). As far as testing for stability, it would then be interesting to try with buffer sizes of 512 and/or 256 and see if that improves things in any way. -- Ticket URL: <http://subversion.ffado.org/ticket/216#comment:37> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |