public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Mike Ood <jh1ood@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: snd-bebob and PrismSound Orpheus fails with snd_pcm_hw_params_set_channels
Date: Thu, 07 May 2015 22:53:30 +0900	[thread overview]
Message-ID: <554B6E5A.5080907@sakamocchi.jp> (raw)
In-Reply-To: <CAJ0eYfWCoqBBLdXpfitc1KZczZmPYXVy9n4-3YEU2Fw0sTRMNQ@mail.gmail.com>

Hi,

Sorry to be late but I have a short vacation.

On 2015年04月27日 17:34, Mike Ood wrote:
> The results are:
> 
> -------------------
> Local        OK
> Wordclock NG
> DI             NG
> PC DAW    OK
> CSP          OK
> -------------------
> 
> So it seems that if there is no external clock applied,
> when one is expected, Orpheus stops playing rather than
> trying to continue operation by free-running its clock.

In this case, the Windows driver may disturb streaming when detecting
de-synchronization.

>> BridgeCo AG (currently ArchWave AG) produced DM1000/DM1100/DM1500
>> chipset with BeBoB firmware. PrismSound Ltd. utilized the chipset and
>> firmware for streaming functionality of your Orpheus.
> 
>> BeBoB firmware gives common ways to control itself, while the hadware
>> vendor added their own cusomization against it. I don't know exactly the
>> reason because there're few information about your device.
> 
> I do not think I understand what you said here due to the lack of technical
> background, but what do you suggest at this moment to a casual applications
> programmer who wish to use snd-bebob with Orpheus?

Such programmer can help driver developers.


Regards

Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2015-05-07 13:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  8:34 snd-bebob and PrismSound Orpheus fails with snd_pcm_hw_params_set_channels Mike Ood
2015-05-07 13:53 ` Takashi Sakamoto [this message]
2015-05-24 11:40 ` Takashi Sakamoto
  -- strict thread matches above, loose matches on Subject: below --
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-24  0:20 Mike Ood
2015-04-24  8:29 ` Clemens Ladisch
2015-04-24 10:13   ` Takashi Sakamoto
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=554B6E5A.5080907@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=jh1ood@gmail.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