alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Paul Argudo <jpa@argudo.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] snd-bebob : from kernel 4.13 to 5.3.19 and .20
Date: Wed, 30 Oct 2019 10:40:18 +0100	[thread overview]
Message-ID: <ad6f8c036538aa755017efe976ac223bb7c90be3.camel@argudo.org> (raw)
In-Reply-To: <20191030091540.GA1856@workstation>

Dear Takashi,

Le mercredi 30 octobre 2019 à 18:15 +0900, Takashi Sakamoto a écrit :
> [...]
> > 
> > First, I hope I report this the best way, really not sure here.
> 
>  
> This list is for this purpose. Thanks for your report and I apologize
> your inconvenience.

Don't apologize, bugs happens. 

I thank you very much for this fast answer.

> 
> > If not, please tell me what to bring (files? logs?) and where (on
> > this
> > list? elsewhere?).
> > 
> > I have spare time to investigate anything that could help here.
> 
> The messages in syslog means that your Focusrite Saffire LE
> transfers isochronous packet to your system with discontinued
> sequence number.

OK.

> But subtraction of the counter (e.g. 0x20 and 0x60 in the
> last line) always results 0x40. The former(=0x20) is expected
> but the isochronous packet includes the latter(=0x60). I think
> it's any possible bug of ALSA IEC 61883-1/6 packet streaming
> engine and check it. 

OK.

> I'll install Eoan kernel and test my devices.
> (but I don't have Saffire and Saffire LE...) I'd like you to wait
> for my test report.

What I can say is that with kernel 4.13 under Ubunto Disco everything
was fine :-(

I can say too I never had to plug external power, the power by the
firewire cable has allways been enough for it. And this is still
working on Windows 10 (I have dualboot on my computer, but only do
audio things on linux, mostly with Ardour).

> 
> Thanks

Thanks to you !!

I'll be waiting for your tests. Be sure to ping my anytime you need
info, log files or whatever. 

I'm "jpa" on irc.freenode.net, connected worktime (~9am ~8pm UTC+1)

Cheers, 


> 
> Takashi Sakamoto

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-10-30  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  8:10 [alsa-devel] snd-bebob : from kernel 4.13 to 5.3.19 and .20 Jean-Paul Argudo
2019-10-30  9:15 ` Takashi Sakamoto
2019-10-30  9:40   ` Jean-Paul Argudo [this message]
     [not found]     ` <c4b792255de178094fd53d80a25fc75b795e3acb.camel@argudo.org>
2019-10-30 11:50       ` Takashi Sakamoto
2019-10-30 14:40         ` Jean-Paul Argudo
2019-11-09 12:36           ` Takashi Sakamoto
2019-11-10 20:26             ` Michael Beer
2019-12-05 13:13             ` Jean-Paul Argudo

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=ad6f8c036538aa755017efe976ac223bb7c90be3.camel@argudo.org \
    --to=jpa@argudo.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=o-takashi@sakamocchi.jp \
    /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).