From: Clemens Ladisch <clemens@ladisch.de>
To: Mike Ood <jh1ood@gmail.com>, alsa-devel@alsa-project.org
Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Subject: Re: snd-bebob and PrismSound Orpheus fails with snd_pcm_hw_params_set_channels
Date: Fri, 24 Apr 2015 10:29:00 +0200 [thread overview]
Message-ID: <5539FECC.8050609@ladisch.de> (raw)
In-Reply-To: <CAJ0eYfXCX_0C-v0cGOwieDDCOn6q4Mt9JvBG7CxA51yOrALSpw@mail.gmail.com>
Mike Ood wrote:
> Clemens wrote:
>> Any error message in the system log?
>
> this is just after % aplay -D plughw:2,0 test.wav
> ...
> [ 110.580310] firewire_core 0000:08:00.0: created device fw1: GUID 00119800010001f9, S400
> [ 113.660273] snd-bebob fw1.0: Detect discontinuity of CIP: 00 08
> [ 128.010593] snd-bebob fw1.0: Detect discontinuity of CIP: 00 08
> [ 133.416998] snd-bebob fw1.0: Detect discontinuity of CIP: 00 08
> [ 136.275142] snd-bebob fw1.0: Detect discontinuity of CIP: 50 70
> [ 137.654178] snd-bebob fw1.0: Detect discontinuity of CIP: 70 90
This means that some packet to be received from the device is (or
appears to be) missing. In theory, this is supposed to happen only when
noise on the cable has corrupted the signal, but this might be a problem
with this device's firmware.
Does this device (with this cable) work in Windows or OS X?
At the moment, a missing packet results in the driver just stopping the
stream. There would be better ways to handle this, but I haven't yet
found the time to implement this.
Regards,
Clemens
next prev parent reply other threads:[~2015-04-24 8:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 0:20 snd-bebob and PrismSound Orpheus fails with snd_pcm_hw_params_set_channels Mike Ood
2015-04-24 8:29 ` Clemens Ladisch [this message]
2015-04-24 10:13 ` Takashi Sakamoto
-- strict thread matches above, loose matches on Subject: below --
2015-04-27 8:34 Mike Ood
2015-05-07 13:53 ` Takashi Sakamoto
2015-05-24 11:40 ` Takashi Sakamoto
2015-04-25 13:44 Mike Ood
2015-04-25 11:53 Mike Ood
2015-04-24 12:27 Mike Ood
2015-04-25 12:01 ` Takashi Sakamoto
2015-04-24 10:58 Mike Ood
2015-04-24 7:30 Mike Ood
2015-04-23 13:06 Mike Ood
2015-04-23 14:39 ` Clemens Ladisch
2015-04-23 12:45 Mike Ood
2015-04-23 12:48 ` Clemens Ladisch
2015-04-23 12:13 Mike Ood
2015-04-23 12:22 ` Clemens Ladisch
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=5539FECC.8050609@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=jh1ood@gmail.com \
--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