[alsa-devel] [PATCH - Intervals v2 1/1] interval: Interpret (x x+1] correctly and return x+1

Takashi Iwai tiwai at suse.de
Wed Oct 24 09:06:21 CEST 2018


On Mon, 22 Oct 2018 09:19:28 +0200,
Timo Wischer wrote:
> 
> On 10/18/18 20:57, Takashi Iwai wrote:
> > But how can it be at the first place?  (352 353) is already empty as
> > the frames.  The time could be kept in this representation, but the
> > frames must be integer.
> >
> > Which order of calls did it result in so?
> >
> > We know that some order of calls make the selection impossible like
> > the above, especially when both time and bytes/frames are mixed.
> 
> 
> I have used the following ALSA configuration:
> 
> pcm.test_rate {
>     type rate
>         slave.pcm hw:gmdcard
>         slave.rate 48000
> }

And which driver is gmdcard?


Takashi


More information about the Alsa-devel mailing list