[alsa-devel] snd-bebob and PrismSound Orpheus fails with	snd_pcm_hw_params_set_channels
    Takashi Sakamoto 
    o-takashi at sakamocchi.jp
       
    Thu May  7 15:53:30 CEST 2015
    
    
  
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
    
    
More information about the Alsa-devel
mailing list