alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Need expert's advice - Fast Track Ultra (8R) dropping samples
Date: Wed, 13 Oct 2010 14:48:13 +0200	[thread overview]
Message-ID: <20101013124813.GL7159@buzzloop.caiaq.de> (raw)
In-Reply-To: <4CB56401.60508@showlabor.de>

On Wed, Oct 13, 2010 at 09:47:13AM +0200, Felix Homann wrote:
> Am 12.10.2010 12:26, schrieb Daniel Mack:
> >If that doesn't work, try debugging the value returned by
> >urb.c:snd_usb_audio_next_packet_size(). For your device, you should end
> >up in the "subs->stream->implicit_feedback" branch.
> 
> I've tested your patch. Unfortunately I don't get any sound.
> snd_usb_audio_next_packet_size() returns from the
> "subs->stream->implicit_feedback" branch. But the return value is
> always 0. ('frames' is returned, not the  0 from the if
> (WARN_ONCE...) statement).

Hmm, ok. That means that the capture stream doesn't see any data.

> Any ideas how to proceed?

Sure :) Can you check whether the capture URBs are started when the
playback stream is kicked off? It should be, and the 'retire' callbacks
should increase the substream's frame counter. Due to the special case I
added, the frames should now always be parsed for this very purpose,
even if the record stream is not in use. You should trace why this
doesn't happen. And once the capture stream sees data,
snd_usb_audio_next_packet_size() will return more reasonable values, and
the playback should also start.

Let me know what you find :)

Daniel

  reply	other threads:[~2010-10-13 12:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  9:57 Need expert's advice - Fast Track Ultra (8R) dropping samples Felix Homann
2010-10-01 11:00 ` Felix Homann
2010-10-01 16:29   ` Clemens Ladisch
2010-10-03 11:50     ` Felix Homann
2010-10-03 12:00       ` Daniel Mack
2010-10-05  7:21       ` Clemens Ladisch
2010-10-06 13:57         ` Felix Homann
2010-10-06 14:38           ` Clemens Ladisch
2010-10-06 16:31             ` Felix Homann
2010-10-07  6:37               ` Clemens Ladisch
2010-10-07  8:10                 ` Daniel Mack
2010-10-07  8:50                   ` Felix Homann
2010-10-07 11:35                   ` Felix Homann
2010-10-08  6:26                     ` Clemens Ladisch
2010-10-12  7:18                       ` Daniel Mack
2010-10-12  8:18                         ` Felix Homann
2010-10-12 10:26                           ` Daniel Mack
2010-10-13  7:47                             ` Felix Homann
2010-10-13 12:48                               ` Daniel Mack [this message]
2010-10-15  7:23                             ` Clemens Ladisch
2010-10-15  8:59                               ` Daniel Mack
2010-10-15 11:08                                 ` Felix Homann
2010-10-15 14:21                                 ` Clemens Ladisch
2010-10-03 10:02 ` Daniel Mack

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=20101013124813.GL7159@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linuxaudio@showlabor.de \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).