11 Mar
2006
11 Mar
'06
11:38 a.m.
hi!
I bought a MAYA 44 Audiotrak USB soundcard and now I'm trying to set it up.
I can see it when I do "cat /proc/asound/cards"
0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
Intel 82801DB-ICH4 with AD1981B at 0xd0100c00, irq 11
1 [USB ]: USB-Audio - MAYA44 USB
AUDIOTRAK MAYA44 USB at usb-0000:00:1d.7-4.2, full speed
2 [mate ]: USB-Audio - XP MIDI mate
Ego Systems Inc XP MIDI mate at
usb-0000:00:1d.7-4.3, full speed
I use qjackctl and when I set it to use hw:1 as the audio interface and I get
this:
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:1|hw:1|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Note: audio device hw:1 doesn't support a 32bit sample format so JACK
will try a 24bit format instead
Note: audio device hw:1 doesn't support a 24bit sample format so JACK
will try a 16bit format instead
nperiods = 2 for capture
Note: audio device hw:1 doesn't support a 32bit sample format so JACK
will try a 24bit format instead
Note: audio device hw:1 doesn't support a 24bit sample format so JACK
will try a 16bit format instead
nperiods = 2 for playback
ALSA: cannot set hardware parameters for playback
ALSA: cannot configure playback channel
cannot load driver module alsa
and jack won't start. What else do I have to configure for the second
soundcard. When I start an audio player, like xmms and tell it to use
hw:1 as a playback device it tells me that it cannot open audio.
I suppose the driver is loaded fine but I misconfigured something.
Please help,
Hiram.
--
"I happen to think that computers are the most important thing to
happen to musicians since the invention of cat-gut which was a long
time ago. "
Robert Moog
11 Mar
11 Mar
3:07 p.m.
Hello Hiram,
Saturday, March 11, 2006, 4:38:40 PM, you wrote:
HA> I use qjackctl and when I set it to use hw:1 as the audio interface and I get
HA> this:
HA> loading driver ..
HA> apparent rate = 48000
HA> creating alsa driver ...
HA> hw:1|hw:1|1024|2|48000|0|0|nomon|swmeter|-|32bit
HA> control device hw:1
HA> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
HA> Note: audio device hw:1 doesn't support a 32bit sample format so JACK
HA> will try a 24bit format instead
HA> Note: audio device hw:1 doesn't support a 24bit sample format so JACK
HA> will try a 16bit format instead
HA> nperiods = 2 for capture
HA> Note: audio device hw:1 doesn't support a 32bit sample format so JACK
HA> will try a 24bit format instead
HA> Note: audio device hw:1 doesn't support a 24bit sample format so JACK
HA> will try a 16bit format instead
HA> nperiods = 2 for playback
HA> ALSA: cannot set hardware parameters for playback
HA> ALSA: cannot configure playback channel
HA> cannot load driver module alsa
try nperiods=3
sincerely,
Marije
3:23 p.m.
Quoting nescivi <nescivi(a)gmail.com>om>:
Hello Hiram,
hi Marije. :)
try nperiods=3
I tried setting the buffer to 3 but I still get the same error messages.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:1|hw:1|1024|3|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 1024 frames, buffer = 3 periods
Note: audio device hw:1 doesn't support a 32bit sample format so JACK
will try a 24bit format instead
Note: audio device hw:1 doesn't support a 24bit sample format so JACK
will try a 16bit format instead
nperiods = 3 for capture
Note: audio device hw:1 doesn't support a 32bit sample format so JACK
will try a 24bit format instead
Note: audio device hw:1 doesn't support a 24bit sample format so JACK
will try a 16bit format instead
nperiods = 3 for playback
ALSA: cannot set hardware parameters for playback
ALSA: cannot configure playback channel
cannot load driver module alsa
The Maya USB soundcard has 4 analog inputs and 4 outputs.
I can change volume no problem from alsamixer for hw:1 (Maya 44USB).
I tried disabling the laptop's audiocard in BIOS hoping that
Maya will become the default soundcard but unfortunately
there is no option in my BIOS for this.
What else could I do, please advise.
Respect,
Hiram.
--
"I happen to think that computers are the most important thing to
happen to musicians since the invention of cat-gut which was a long
time ago. "
Robert Moog
6:29 p.m.
Hallo,
Hiram Abiff hat gesagt: // Hiram Abiff wrote:
I tried setting the buffer to 3 but I still get the
same error messages.
What else could I do, please advise.
Does "aplay -D plughw:1 some.wav" work?
What ybout "jackd -d alsa -d plughw:1"?
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
6:49 p.m.
Quoting Frank Barknecht <fbar(a)footils.org>rg>:
Hallo,
Hiram Abiff hat gesagt: // Hiram Abiff wrote:
Nope. It says:
Playing WAVE
'/home/hiram/mp3/egoboobits/AeSqe__pinhead_ost_07_mother.wav' : Signed
24 bit Little Endian in 3bytes, Rate 44100 Hz, Stereo
aplay: set_params:935: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S24_3LE
SUBFORMAT: STD
SAMPLE_BITS: 24
FRAME_BITS: 48
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 33078
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 132300
TICK_TIME: 1000
I tried setting the buffer to 3 but I still get
the same error messages.
What else could I do, please advise.
Does "aplay -D plughw:1 some.wav" work?
What ybout "jackd -d alsa -d plughw:1"?
Negative, chief. The ALSA software "plug" layer doesn't work.
Whatever that is. jackd says:
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ...
plughw:1|plughw:1|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a hardware device
instead rather than using the plug layer. Usually the name of the
hardware device that corresponds to the first soun
nperiods = 2 for capture
You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a hardware device
instead rather than using the plug layer. Usually the name of the
hardware device that corresponds to the first soun
nperiods = 2 for playback
ALSA: cannot set hardware parameters for playback
ALSA: cannot configure playback channel
cannot load driver module alsa
no message buffer overruns
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
Respect
Hiram
--
http://www.egoboobits.net/HiramAbiff
6:57 p.m.
Hallo,
Hiram Abiff hat gesagt: // Hiram Abiff wrote:
Quoting Frank Barknecht <fbar(a)footils.org>rg>:
Yes, if aplay doesn't work, nothing else will work, and you actually
don't need to continue testing other software, until aplay works.
However aplay should work, when using the plug-layer so I'm a bit
puzzled by the error message you got.
Are you on a PowerPC-system?
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
Does "aplay -D plughw:1 some.wav" work?
Nope. It says:
Playing WAVE
'/home/hiram/mp3/egoboobits/AeSqe__pinhead_ost_07_mother.wav' : Signed
24 bit Little Endian in 3bytes, Rate 44100 Hz, Stereo
aplay: set_params:935: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S24_3LE
SUBFORMAT: STD
SAMPLE_BITS: 24
FRAME_BITS: 48
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 33078
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 132300
TICK_TIME: 1000
What ybout "jackd -d alsa -d plughw:1"?
Negative, chief. The ALSA software "plug" layer doesn't work.
6:59 p.m.
Hallo,
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
Yes, if aplay doesn't work, nothing else will
work, and you actually
don't need to continue testing other software, until aplay works.
However aplay should work, when using the plug-layer so I'm a bit
puzzled by the error message you got.
Oh, and another thing: is your Maya card still "card1"? plughw:1 will
access the second card in your system. If you have the Maya as first
card, that is as card0, you need to use plughw:0 in the aplay test.
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
7:37 p.m.
Quoting Frank Barknecht <fbar(a)footils.org>rg>:
Hallo,
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
It is card1, acording to /proc/asound/cards.
--
http://www.egoboobits.net/HiramAbiff
Yes, if aplay doesn't work, nothing else will
work, and you actually
don't need to continue testing other software, until aplay works.
However aplay should work, when using the plug-layer so I'm a bit
puzzled by the error message you got.
Oh, and another thing: is your Maya card still "card1"? plughw:1 will
access the second card in your system. If you have the Maya as first
card, that is as card0, you need to use plughw:0 in the aplay test.
7:34 p.m.
Quoting Frank Barknecht <fbar(a)footils.org>rg>:
Hallo,
Hiram Abiff hat gesagt: // Hiram Abiff wrote:
Negative. On an Intel Centrino. Slackware 10.2, a 2.6.15 kernel.
Hiram.
--
http://www.egoboobits.net/HiramAbiff
Quoting Frank Barknecht
<fbar(a)footils.org>rg>:
Yes, if aplay doesn't work, nothing else will work, and you actually
don't need to continue testing other software, until aplay works.
However aplay should work, when using the plug-layer so I'm a bit
puzzled by the error message you got.
Are you on a PowerPC-system?
Does "aplay -D plughw:1 some.wav" work?
Nope. It says:
Playing WAVE
'/home/hiram/mp3/egoboobits/AeSqe__pinhead_ost_07_mother.wav' : Signed
24 bit Little Endian in 3bytes, Rate 44100 Hz, Stereo
aplay: set_params:935: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S24_3LE
SUBFORMAT: STD
SAMPLE_BITS: 24
FRAME_BITS: 48
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 33078
PERIODS: (3 4)
BUFFER_TIME: 500000
BUFFER_SIZE: 22050
BUFFER_BYTES: 132300
TICK_TIME: 1000
What ybout "jackd -d alsa -d plughw:1"?
Negative, chief. The ALSA software "plug" layer doesn't work. 
7:55 p.m.
Hiram Abiff wrote:
Negative. On an Intel Centrino. Slackware 10.2, a
2.6.15 kernel.
Could it be the exact same thing that Frank helped me with yesterday? A
big in usb audio in 2.6.15. I solved it by upgrading to 2.6.15.6, which
also can be patched my the rt21 patch...
Worth a try...
--
peace, love & harmony
Atte
http://www.atte.dk
8:31 p.m.
Quoting Atte André Jensen <atte.jensen(a)gmail.com>om>:
Hiram Abiff wrote:
I read your yesterday's posts. You wrote that aplay works, for exapmle.
I can get 0 apps to work with my USB card. I don't think we have the
same problem.
--
http://www.egoboobits.net/HiramAbiff
Negative. On an Intel Centrino. Slackware 10.2, a
2.6.15 kernel.
Could it be the exact same thing that Frank helped me with yesterday?
A big in usb audio in 2.6.15. I solved it by upgrading to 2.6.15.6,
which also can be patched my the rt21 patch...
Worth a try...
8:37 p.m.
Quoting Hiram Abiff <domain.admin(a)online.ie>ie>:
Quoting Atte André Jensen
<atte.jensen(a)gmail.com>om>:
I forgot to mention that I didn't compile ALSA in the kernel I
downloaded it separately and compiled from the ALSA website.
--
http://www.egoboobits.net/HiramAbiff
Hiram Abiff wrote:
Negative. On an Intel Centrino. Slackware 10.2, a
2.6.15 kernel.
Could it be the exact same thing that Frank helped me with
yesterday? A big in usb audio in 2.6.15. I solved it by upgrading to
2.6.15.6, which also can be patched my the rt21 patch...
Worth a try...
8:15 a.m.
Quoting Christoph Eckert <ce(a)christeck.de>de>:
I compiled them out of the kernel so I can upgrade ALSA separately and
don't have to recompile the whole kernel just for ALSA.
--
http://www.egoboobits.net/HiramAbiff
I forgot to mention that I didn't compile
ALSA in the kernel I
downloaded it separately and compiled from the ALSA website.
I had never problems using the in-kernel ALSA drivers (while alsa lib is
an external package, of course).
11:59 a.m.
Quoting Christoph Eckert <ce(a)christeck.de>de>:
I just read the long troubles of Lukas Zapletal who owns the same
card and posted to this list earlier. I tried everything you guys
told him to, none of it works. He stopped posting but I don't intend to
give up as I have no other choice.
So, now I have a patche 2.6.15.6 kernel, after which my cards list
has been rearranged and now it looks like this:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 2: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel
82801DB-ICH4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: I82801DBICH4 [Intel 82801DB-ICH4], device 4: Intel ICH - IEC958
[Intel 82801DB-ICH4 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: USB [MAYA44 USB], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
I tried with plughw:3 and hw:3 but everytime I get the message:
"Cannot set hardware parameters for playback"
I am puzzled.
--
http://www.egoboobits.net/HiramAbiff
I forgot to mention that I didn't compile
ALSA in the kernel I
downloaded it separately and compiled from the ALSA website.
I had never problems using the in-kernel ALSA drivers (while alsa lib is
an external package, of course).
12:02 p.m.
Quoting Christoph Eckert <ce(a)christeck.de>de>:
I also found a post from Luke Yelavich at audioslack.com who says:
I forgot to mention that I didn't compile
ALSA in the kernel I
downloaded it separately and compiled from the ALSA website.
I had never problems using the in-kernel ALSA drivers (while alsa lib is
an external package, of course).
Anyone ever run the maya 44 ?
not listed on the alsa page so prob not a goody...
"If you are referring to the Maya 44 USB, this device works well as of=20
alsa driver version 1.0.7. I have one of these, and helped in getting it=20
working correctly."
I myself use ALSA ver 1.0.10rc3 so this shouldn't be a problem.
--
http://www.egoboobits.net/HiramAbiff
1:28 p.m.
I also found a post from Luke Yelavich at
audioslack.com who says:
> Anyone ever run the maya 44 ?
> not listed on the alsa page so prob not a goody...
I did not run a Maya, but I have a Terratec Aureon 5.1 USB which seems
to be very similar and it ran without any problems (I'm now using an
Edirol card).
Best regards
ce
1:46 p.m.
Quoting Christoph Eckert <ce(a)christeck.de>de>:
Drat. Well now I have to deal with this. I found something interesting.
I connected a drum machine's audio output to the input of the Maya 44
and I could hear sound coming from maya's output no problem, LED's are
flashing for both input/output stereo channels.
I can also adjust the volume level from alsamixer for the Maya playback.
I recon I must adjust the playback parameters differently if this
input stuff seems to be working fine.
--
http://www.egoboobits.net/HiramAbiff
I also found a post from Luke Yelavich at
audioslack.com who says:
> Anyone ever run the maya 44 ?
> not listed on the alsa page so prob not a goody...
I did not run a Maya, but I have a Terratec Aureon 5.1 USB which seems
to be very similar and it ran without any problems (I'm now using an
Edirol card).
2:32 p.m.
Drat. Well now I have to deal with this. I found
something
interesting. I connected a drum machine's audio output to the input
of the Maya 44 and I could hear sound coming from maya's output no
problem, LED's are flashing for both input/output stereo channels.
I guess it's the hardware monitor channel, so audio doesn't go through
your PC or even ALSA.
Best regards,
ce
2:58 p.m.
Quoting Christoph Eckert <ce(a)christeck.de>de>:
That would explain it. I must say I am clueless at this point.
I really don't know what to try next. I urge anyone who knows
anything that could help to please share their knowledge.
Thnx
Hiram
--
http://www.egoboobits.net/HiramAbiff
Drat. Well now I have to deal with this. I found
something
interesting. I connected a drum machine's audio output to the input
of the Maya 44 and I could hear sound coming from maya's output no
problem, LED's are flashing for both input/output stereo channels.
I guess it's the hardware monitor channel, so audio doesn't go through
your PC or even ALSA.
3:09 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I own a Maya44USB and it works perfectly under Gentoo 2.6.13. The only
thing a had to do was modprobing snd-usb-audio.
Have you tried to restart alsa? There should be an init script somewhere
in /etc/init.d/.
Can you re-plug the card and post the output of dmesg?
Markus Herhoffer
Hiram Abiff wrote:
Quoting Christoph Eckert <ce(a)christeck.de>de>:
That would explain it. I must say I am clueless at this point.
I really don't know what to try next. I urge anyone who knows
anything that could help to please share their knowledge.
Thnx
Hiram
Drat. Well now I have to deal with this. I found
something
interesting. I connected a drum machine's audio output to the input
of the Maya 44 and I could hear sound coming from maya's output no
problem, LED's are flashing for both input/output stereo channels.
I guess it's the hardware monitor channel, so audio doesn't go through
your PC or even ALSA.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEFIT1uXdsp50C0vMRAvOhAKCQk/MzkiGid+vf5lTvmgMM95Y5dgCePy7c
xvq4nrKVykybFhRre0BzHG8=
=7kM8
-----END PGP SIGNATURE-----
3:19 p.m.
Quoting Markus Herhoffer <markus(a)herhoffer.net>et>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I own a Maya44USB and it works perfectly under Gentoo 2.6.13. The only
thing a had to do was modprobing snd-usb-audio.
snd-usb-audio is loaded. lsmod says:
snd_seq_midi 7008 3 snd_seq_midi_event 5952 1 snd_seq_midi
snd_seq 50512 14 snd_seq_midi,snd_seq_midi_event
snd_pcm_oss 49056 0 snd_mixer_oss 17216 3 snd_pcm_oss
snd_usb_audio 74816 3 snd_usb_lib 14592 1 snd_usb_audio
snd_rawmidi 20640 2 snd_seq_midi,snd_usb_lib
snd_seq_device 7116 3 snd_seq_midi,snd_seq,snd_rawmidi
snd_hwdep 7264 1 snd_usb_audio
Have you tried to restart alsa? There should be an
init script somewhere
in /etc/init.d/.
Yes, I did. I tried rebooting as well. I also patched my kernel
to v2.6.15.6. I have a script called /etc/rc.d/rc.alsa for ALSA control.
I use Slackware 10.2.
Can you re-plug the card and post the output of
dmesg?
Ofcourse. Here goes:
dmesg:
---
usb 1-4.3: new full speed USB device using ehci_hcd and address 7
HID device not claimed by input or hiddev
---
hmmm....what does this line mean:
"HID device not claimed by input or hiddev"? Looks relevant.
Also here is the output of "tail -f /var/log/messages":
---
Mar 12 20:16:03 guybrush kernel: usb 1-4.3: new full speed USB device
using ehci_hc and address 7
Mar 12 20:16:04 guybrush udev[4715]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 32 applied,
'pcmC1D0p' becomes 'snd/%k'
Mar 12 20:16:04 guybrush udev[4715]: creating device node '/dev/snd/pcmC1D0p'
Mar 12 20:16:04 guybrush udev[4716]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 32 applied,
'pcmC1D0c' becomes 'snd/%k'
Mar 12 20:16:04 guybrush udev[4716]: creating device node '/dev/snd/pcmC1D0c'
Mar 12 20:16:04 guybrush udev[4717]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 86 applied,
added symlink '%k'
Mar 12 20:16:04 guybrush udev[4717]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 86 applied,
'dsp1' becomes 'sound/%k'
Mar 12 20:16:04 guybrush udev[4717]: creating device node '/dev/sound/dsp1'
Mar 12 20:16:04 guybrush udev[4718]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 84 applied,
added symlink '%k'
Mar 12 20:16:04 guybrush udev[4718]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 84 applied,
'audio1' becomes 'sound/%k'
Mar 12 20:16:04 guybrush udev[4718]: creating device node '/dev/sound/audio1'
Mar 12 20:16:04 guybrush udev[4719]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 30 applied,
'controlC1' becomes 'snd/%k'
Mar 12 20:16:04 guybrush udev[4719]: creating device node '/dev/snd/controlC1'
Mar 12 20:16:04 guybrush udev[4720]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 88 applied,
added symlink '%k'
Mar 12 20:16:04 guybrush udev[4720]: configured rule in
'/etc/udev/rules.d/udev.rul s' at line 88 applied,
'mixer1' becomes 'sound/%k'
Mar 12 20:16:04 guybrush udev[4720]: creating device node '/dev/sound/mixer1'
Mar 12 20:16:04 guybrush udev[4742]: creating device node '/dev/usbdev1.7'
---
Everything seems fine from these entries.
--
http://www.egoboobits.net/HiramAbiff
3:58 p.m.
Quoting Christoph Eckert <ce(a)christeck.de>de>:
I'm not sure I understand. You say that it DOES register on the BUS,
but this output says that the device is NOT claimed by input.
But all the other messages about creating devices seem fine and I see
my Maya card in /proc/asound/cards. hmmm....
--
http://www.egoboobits.net/HiramAbiff
"HID device not claimed by input or
hiddev"? Looks relevant.
It means that the Maya does register on the USB bus as human input
device; nothing wrong with that, the Aureon does at well.
4:06 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have the same output with the Maya USB. It's all right with that:
usb 2-1: USB disconnect, address 4
usb 2-1: new full speed USB device using ohci_hcd and address 5
HID device not claimed by input or hiddev
Can you try:
# cat /dev/urandom > /dev/dsp
(Turn down the volume of your speakers and abort with Ctrl+C very quickly)
This should produce a white noise completly independent from alsa. If
you hear the noise you can be shure that there's all right on the device
layer.
Markus
Hiram Abiff wrote:
Quoting Christoph Eckert <ce(a)christeck.de>de>:
I'm not sure I understand. You say that it DOES register on the BUS,
but this output says that the device is NOT claimed by input.
But all the other messages about creating devices seem fine and I see my
Maya card in /proc/asound/cards. hmmm....
"HID device not claimed by input or
hiddev"? Looks relevant.
It means that the Maya does register on the USB bus as human input
device; nothing wrong with that, the Aureon does at well.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEFJJFuXdsp50C0vMRAn2yAJ4+60OJ6xWTFNLN2kd+9xX2g1uL8wCgnEIt
VRFcN4jJhnU7zfVwwOxUq10=
=y5ni
-----END PGP SIGNATURE-----
4:28 p.m.
Quoting Markus Herhoffer <markus(a)herhoffer.net>et>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have the same output with the Maya USB. It's all right with that:
Well, tried it and I got sound coming from my laptop speakers so I
suppose /dev/dsp is used by my laptop's integrated soundcard.
I also have a /dev/dsp1. I tried redirecting urandom to it and got this:
cat /dev/urandom > dsp1
cat: write error: Broken pipe
/dev/dsp and /dev/dsp1 area actually symbolic links to /dev/sound/dsp
and /dev/sound/dsp1, respectively.
Here are the contents of my /dev/sound directory:
crw-rw--w- 1 root audio 14, 12 2006-03-12 18:14 adsp
crw-rw--w- 1 root audio 14, 4 2006-03-12 18:14 audio
crw-rw--w- 1 root audio 14, 20 2006-03-12 21:19 audio1
crw-rw--w- 1 root audio 14, 3 2006-03-12 18:14 dsp
crw-rw--w- 1 root audio 14, 19 2006-03-12 21:19 dsp1
crw-rw--w- 1 root audio 14, 0 2006-03-12 18:14 mixer
crw-rw--w- 1 root audio 14, 16 2006-03-12 21:19 mixer1
crw-rw--w- 1 root audio 14, 32 2006-03-12 18:14 mixer2
crw-rw--w- 1 root audio 14, 48 2006-03-12 18:48 mixer3
--
http://www.egoboobits.net/HiramAbiff
usb 2-1: USB disconnect, address 4
usb 2-1: new full speed USB device using ohci_hcd and address 5
HID device not claimed by input or hiddev
Can you try:
# cat /dev/urandom > /dev/dsp
(Turn down the volume of your speakers and abort with Ctrl+C very quickly)
This should produce a white noise completly independent from alsa. If
you hear the noise you can be shure that there's all right on the device
layer.
Markus
5:07 p.m.
On Sun, 2006-03-12 at 21:27 +0000, Markus Herhoffer wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have the same output with the Maya USB. It's all right with that:
This doscussion should really move to the ALSA lists, it's clearly a
driver bug. It's possible that the vendor changed the device in an
incompatible way (would not be the first time).
BTW Markus, your public key is invalid - I can't find it in the MIT key
server, the only one that comes up for you is 0x159D79D1 which expired.
Lee
usb 2-1: USB disconnect, address 4
usb 2-1: new full speed USB device using ohci_hcd and address 5
HID device not claimed by input or hiddev
Can you try:
# cat /dev/urandom > /dev/dsp
(Turn down the volume of your speakers and abort with Ctrl+C very quickly)
This should produce a white noise completly independent from alsa. If
you hear the noise you can be shure that there's all right on the device
layer.
5:13 p.m.
Quoting Lee Revell <rlrevell(a)joe-job.com>om>:
This doscussion should really move to the ALSA lists,
it's clearly a
driver bug. It's possible that the vendor changed the device in an
incompatible way (would not be the first time).
Yes, it's been dragging along for a while now. Will try there also, again.
Dammit.
Thanks for all the help guys and tips and your time. I appreciate it.
Respect,
Hiram.
--
http://www.egoboobits.net/HiramAbiff
2:13 a.m.
Hiram Abiff wrote:
I read your yesterday's posts. You wrote that
aplay works, for exapmle.
I can get 0 apps to work with my USB card. I don't think we have the
same problem.
I know it's not the same problem. But it might be worthwhile to try
another kernel.
I at least wouldn't run usb audio on a kernel with known usb audio
issues, when an upgrade is free :-)
--
peace, love & harmony
Atte
http://www.atte.dk
11:23 a.m.
Quoting Atte André Jensen <atte.jensen(a)gmail.com>om>:
Hiram Abiff wrote:
I just patched my kernel and I still have the same problem.
It was worth a try. Thnx, Andre.
--
http://www.egoboobits.net/HiramAbiff
I read your yesterday's posts. You wrote that
aplay works, for exapmle.
I can get 0 apps to work with my USB card. I don't think we have the
same problem.
I know it's not the same problem. But it might be worthwhile to try
another kernel.
I at least wouldn't run usb audio on a kernel with known usb audio
issues, when an upgrade is free :-)
6778
days inactive
6779
days old
linux-audio-user@lists.linuxaudio.org
30 comments
7 participants
participants (7)
-
Atte André Jensen -
Christoph Eckert -
Frank Barknecht -
Hiram Abiff -
Lee Revell -
Markus Herhoffer -
nescivi