From: Takashi Iwai <tiwai@suse.de>
To: Timo Wischer <twischer@de.adit-jv.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH - Intervals v2 1/1] interval: Interpret (x x+1] correctly and return x+1
Date: Wed, 24 Oct 2018 09:06:21 +0200 [thread overview]
Message-ID: <s5hva5rq0wi.wl-tiwai@suse.de> (raw)
In-Reply-To: <811d3dc0-775b-6d71-9aed-b25f53f3ab81@de.adit-jv.com>
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
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2018-10-24 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 11:33 [PATCH - Intervals v2 1/1] interval: Interpret (x x+1] correctly and return x+1 twischer
2018-10-18 12:02 ` Takashi Iwai
2018-10-18 12:28 ` Timo Wischer
2018-10-18 13:19 ` Takashi Iwai
2018-10-18 14:31 ` Timo Wischer
2018-10-18 14:45 ` Takashi Sakamoto
2018-10-18 15:16 ` Timo Wischer
2018-10-18 14:58 ` Takashi Iwai
2018-10-18 15:55 ` Timo Wischer
2018-10-18 18:57 ` Takashi Iwai
2018-10-22 7:19 ` Timo Wischer
2018-10-24 7:06 ` Takashi Iwai [this message]
2018-10-24 7:44 ` Timo Wischer
2018-10-24 7:48 ` Takashi Iwai
2018-10-24 8:05 ` Timo Wischer
2018-10-24 10:15 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hva5rq0wi.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=twischer@de.adit-jv.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox