Re: Ardour using a bluetooth headset

> 
> Does the bluetooth device show up as hardware when you run
> 
>   aplay -l
> 
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
gunter@Marius:~$

> 
> While playing with mplayer, can you run
> 
> cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash
> ./adevices.sh
> 
========================================
Part I: ALSA
Advanced Linux Sound Architecture Driver Version
k4.15.0-041500rc7-lowlatency.

Card 0 (PCH):
  * Playback Device 0 (ALC271X Analog):
    - Subdevice 0 (hw:PCH,0,0):
      closed

  * Playback Device 3 (HDMI 0):
    - Subdevice 0 (hw:PCH,3,0):
      closed

  * Recording Device 0 (ALC271X Analog):
    - Subdevice 0 (hw:PCH,0,0):
      closed

========================================
Part II: jack processes


If I turn off my headset while playing audio using mplayer I get the
following error message:

[AO_ALSA] pcm pause error: File descriptor in bad state
[AO_ALSA] pcm resume error: File descriptor in bad state

Can it be that mplayer uses alsa to write to a pipe or do something else
which is weird?
Anyway.. Seems like the fact that mplayer when instructed to use alsa
finds my headset doesn't indicate that the headset is actually supported
by alsa => will find me a wired headset and apologize for the additional
work I have caused.


Kind regards,

     Gunter.
_______________________________________________
Ardour-Users mailing list
[email protected]
To unsubscribe  or change your mailing preferences please visit:
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org