[Bluez-users] Re: snd-bluez-sco

[Bluez-users] Re: snd-bluez-sco

[Rainer Jochem]

[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]


Okies. 

Meanwhile I've played around a little bit more - here's some 
additional information I've produced (dunno if it's useful, but
here it is):

root@marvin:# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Audigy [Sound Blaster Audigy], device 0: emu10k1 [EMU10K1]
  Subdevices: 31/32
  Subdevice #0: subdevice #0
[...lots of other subdevices...]
  Subdevice #31: subdevice #31
card 0: Audigy [Sound Blaster Audigy], device 3: emu10k1 [EMU10K1
FX8010]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
[...]
  Subdevice #7: subdevice #7
**** List of PLAYBACK Hardware Devices ****
card 1: V8233Pre [VIA 8233-Pre], device 0: VIA 8233-Pre [VIA 8233-Pre]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
[...]
  Subdevice #3: subdevice #3
card 1: V8233Pre [VIA 8233-Pre], device 1: VIA 8233-Pre [VIA 8233-Pre]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
**** List of PLAYBACK Hardware Devices ****
card 2: Headset [Bluez Headset], device 0: Bluez SCO PCM [Bluez SCO
PCM]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


root@marvin:# alsaplayer -d plughw:Headset /home/rainer/tmp/rootbeer.pcm 
error on set_period_size (1024)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: [8000 8192000]
PERIOD_SIZE: (352 361268)
PERIOD_BYTES: (1408 1445072)
PERIODS: (0 1027)
BUFFER_TIME: (7981 8191996)
BUFFER_SIZE: [352 361267]
BUFFER_BYTES: [1408 1445068]
TICK_TIME: 10000
error on set_period_size (1024)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: [8000 8192000]
PERIOD_SIZE: (352 361268)
PERIOD_BYTES: (1408 1445072)
PERIODS: (0 1027)
BUFFER_TIME: (7981 8191996)
BUFFER_SIZE: [352 361267]
BUFFER_BYTES: [1408 1445068]
TICK_TIME: 10000
failed to configure output device...trying OSS


 
> Perhaps you could try adding some debugging printf()s to the
> find_hwdep_device() function to try to identify whether it is finding the
> snd-bluez-sco device, and if so, what hwdep interface type it is
> reporting.

Hmm... I'll try it. 

> I haven't yet tried the code against alsa 0.9.7, so it's possible there
> may be some incompatabilities.

Might be possible too.


-- 
http://graphics.cs.uni-sb.de/~rainer/



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[Bluez-users] Re: snd-bluez-sco

[Jonathan Paisley]

On Sat, 27 Sep 2003 1:34pm +0200, Rainer Jochem wrote:

> then I do:
> root@marvin:# bluezsco  xx:xx:xx:xx:xx:xx 6
> Error: control open (hw:2): No such device
> Error: Can't find device. Bail

This error is coming from the bluezsco tool, when it's trying to open
hwdep ALSA interface for the snd-bluez-sco driver.

It cycles through the ALSA devices (hw:0, hw:1, hw:2, etc) trying to
identify a device which has an hwdep interface of type
SND_HWDEP_IFACE_BLUEZ_SCO. The error you're seeing is the loop bailing
because it didn't find the device, and you only have ALSA device hw:0 and
hw:1 (presumably your real audio card and the snd-bluez-sco driver).

Perhaps you could try adding some debugging printf()s to the
find_hwdep_device() function to try to identify whether it is finding the
snd-bluez-sco device, and if so, what hwdep interface type it is
reporting.

I haven't yet tried the code against alsa 0.9.7, so it's possible there
may be some incompatabilities.

Thanks.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users