On Sat, Feb 06, 2016 at 12:20:38PM +0100, Fokke de Jong wrote:
> That, helped thanks.
> Unfortunately I’m still getting the same huge latency as before..
Looks like a driver problem then...
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream,
On Wed, Feb 03, 2016 at 10:41:06PM +0100, Markus Seeber wrote:
> The buffersize can confuse applications which assume, that the
> buffersize is variable and is always (buffersize = framesize * periods)
> but I guess that this is not an assumption that should be made in the
> first place.
On Wed, Feb 03, 2016 at 10:41:06PM +0100, Markus Seeber wrote:
> Was the driver already included in mainline? I saw the patch on
> alsa-devel but kind of lost track of it.
No. Takashi had some feedback, and I had neither the time nor hardware
to work on it.
I can do the cosmetics, but rewriting
On Sat, Feb 06, 2016 at 04:12:39PM +, Fons Adriaensen wrote:
> > That, helped thanks.
> > Unfortunately I’m still getting the same huge latency as before..
>
> Looks like a driver problem then...
Not impossible, but I fail to see how. Here is the relevant driver side:
On Sat, Feb 06, 2016 at 06:30:16PM +0100, Fokke de Jong wrote:
> Ok, just to be clear: I *am* able to get the expected latency using jack
> (around 3.5ms with a period=32 and nperiods=256).
> but using my own alsa wrapper (and also using zita-alsa-pcmi) the latency is
> >170ms
You probably
On 02/06/16 18:54, Fons Adriaensen wrote:
Ok, just to be clear: I *am* able to get the expected latency using
jack (around 3.5ms with a period=32 and nperiods=256).
but using my own alsa wrapper (and also using zita-alsa-pcmi) the
latency is >170ms
You probably mean nperiods = 2 ???
Well,
Ok, just to be clear: I *am* able to get the expected latency using jack
(around 3.5ms with a period=32 and nperiods=256).
but using my own alsa wrapper (and also using zita-alsa-pcmi) the latency is
>170ms
here’s the output from hw_params:
Device: hw (type: HW)
Access types: MMAP_COMPLEX
That, helped thanks.
Unfortunately I’m still getting the same huge latency as before..
cheers,
Fokke
> On Feb 4, 2016, at 21:51 , Fons Adriaensen wrote:
>
> On Thu, Feb 04, 2016 at 04:07:30PM +0100, Fokke de Jong wrote:
>
>> I tried the alsa_loopback example:
>>
>>