Re: [Alsa-user] Need optic out for VIA VT1708 on pico-itx

2007-12-14 Thread John Stile
I'm concerned because http://alsa.opensrc.org/DigitalOut example shows
'cat /proc/asound/devices' with a unique hw:x,y for the digital audio
playback device, and my output shows:
 16: [ 0- 0]: digital audio playback
 17: [ 0- 1]: digital audio playback
and neither of these work:
  aplay -D plughw:0,0 Track01.wav
  aplay -D hw:0,0 Track01.wav
  aplay -D plughw:0,1 Track01.wav
  aplay -D hw:0,1 Track01.wav
When I get it right should I be able to see a red light coming out of
the optic audio port?
Could this be a problem with my case?

On Thu, 2007-12-13 at 21:05 -0800, John Stile wrote:
 I've found a script for helping to debug.
 REF: http://alsa.opensrc.org/index.php/Aadebug
 
 Am I having a syntax problem with aplay? 
 
 
 Output from script
 -
 ALSA Audio Debug v0.1.0 - Thu Dec 13 20:57:47 PST 2007
 http://alsa.opensrc.org/aadebug
 http://www.gnu.org/licenses/gpl.txt
 
 Kernel 
 Linux pico 2.6.23-gentoo-r3 #12 SMP Wed Dec 12 00:59:23 PST 2007 i686
 VIA Esther processor 1000MHz CentaurHauls GNU/Linux
 
 Loaded Modules 
 snd_pcm_oss33696  0
 snd_mixer_oss  15872  2 snd_pcm_oss
 snd_seq_oss25984  0
 snd_seq_midi_event  7680  1 snd_seq_oss
 snd_seq35536  4 snd_seq_oss,snd_seq_midi_event
 snd_seq_device  8588  2 snd_seq_oss,snd_seq
 snd_hda_intel 216732  1
 snd_pcm47492  2 snd_pcm_oss,snd_hda_intel
 snd_timer  18308  2 snd_seq,snd_pcm
 snd33508  8
 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
 snd_page_alloc 10504  2 snd_hda_intel,snd_pcm
 
 Proc Config ---
 CONFIG_SOUND=y
 CONFIG_SND=m
 CONFIG_SND_TIMER=m
 CONFIG_SND_PCM=m
 CONFIG_SND_HWDEP=m
 CONFIG_SND_RAWMIDI=m
 CONFIG_SND_SEQUENCER=m
 # CONFIG_SND_SEQ_DUMMY is not set
 CONFIG_SND_OSSEMUL=y
 CONFIG_SND_MIXER_OSS=m
 CONFIG_SND_PCM_OSS=m
 CONFIG_SND_PCM_OSS_PLUGINS=y
 CONFIG_SND_SEQUENCER_OSS=y
 CONFIG_SND_RTCTIMER=m
 CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
 # CONFIG_SND_DYNAMIC_MINORS is not set
 CONFIG_SND_SUPPORT_OLD_API=y
 # CONFIG_SND_VERBOSE_PROCFS is not set
 # CONFIG_SND_VERBOSE_PRINTK is not set
 # CONFIG_SND_DEBUG is not set
 CONFIG_SND_MPU401_UART=m
 CONFIG_SND_VX_LIB=m
 CONFIG_SND_AC97_CODEC=m
 # CONFIG_SND_DUMMY is not set
 # CONFIG_SND_VIRMIDI is not set
 # CONFIG_SND_MTPAV is not set
 CONFIG_SND_MTS64=m
 # CONFIG_SND_SERIAL_U16550 is not set
 CONFIG_SND_MPU401=m
 # CONFIG_SND_PORTMAN2X4 is not set
 # CONFIG_SND_ADLIB is not set
 # CONFIG_SND_AD1816A is not set
 # CONFIG_SND_AD1848 is not set
 # CONFIG_SND_ALS100 is not set
 # CONFIG_SND_AZT2320 is not set
 # CONFIG_SND_CMI8330 is not set
 # CONFIG_SND_CS4231 is not set
 # CONFIG_SND_CS4232 is not set
 # CONFIG_SND_CS4236 is not set
 # CONFIG_SND_DT019X is not set
 # CONFIG_SND_ES968 is not set
 # CONFIG_SND_ES1688 is not set
 # CONFIG_SND_ES18XX is not set
 # CONFIG_SND_GUSCLASSIC is not set
 # CONFIG_SND_GUSEXTREME is not set
 # CONFIG_SND_GUSMAX is not set
 # CONFIG_SND_INTERWAVE is not set
 # CONFIG_SND_INTERWAVE_STB is not set
 # CONFIG_SND_OPL3SA2 is not set
 # CONFIG_SND_OPTI92X_AD1848 is not set
 # CONFIG_SND_OPTI92X_CS4231 is not set
 # CONFIG_SND_OPTI93X is not set
 # CONFIG_SND_MIRO is not set
 # CONFIG_SND_SB8 is not set
 # CONFIG_SND_SB16 is not set
 # CONFIG_SND_SBAWE is not set
 # CONFIG_SND_SGALAXY is not set
 # CONFIG_SND_SSCAPE is not set
 # CONFIG_SND_WAVEFRONT is not set
 # CONFIG_SND_AD1889 is not set
 # CONFIG_SND_ALS300 is not set
 # CONFIG_SND_ALS4000 is not set
 # CONFIG_SND_ALI5451 is not set
 # CONFIG_SND_ATIIXP is not set
 # CONFIG_SND_ATIIXP_MODEM is not set
 # CONFIG_SND_AU8810 is not set
 # CONFIG_SND_AU8820 is not set
 # CONFIG_SND_AU8830 is not set
 # CONFIG_SND_AZT3328 is not set
 # CONFIG_SND_BT87X is not set
 # CONFIG_SND_CA0106 is not set
 # CONFIG_SND_CMIPCI is not set
 # CONFIG_SND_CS4281 is not set
 # CONFIG_SND_CS46XX is not set
 # CONFIG_SND_CS5530 is not set
 # CONFIG_SND_CS5535AUDIO is not set
 # CONFIG_SND_DARLA20 is not set
 # CONFIG_SND_GINA20 is not set
 # CONFIG_SND_LAYLA20 is not set
 # CONFIG_SND_DARLA24 is not set
 # CONFIG_SND_GINA24 is not set
 # CONFIG_SND_LAYLA24 is not set
 # CONFIG_SND_MONA is not set
 # CONFIG_SND_MIA is not set
 # CONFIG_SND_ECHO3G is not set
 # CONFIG_SND_INDIGO is not set
 # CONFIG_SND_INDIGOIO is not set
 # CONFIG_SND_INDIGODJ is not set
 # CONFIG_SND_EMU10K1 is not set
 # CONFIG_SND_EMU10K1X is not set
 # CONFIG_SND_ENS1370 is not set
 # CONFIG_SND_ENS1371 is not set
 # CONFIG_SND_ES1938 is not set
 # CONFIG_SND_ES1968 is not set
 # CONFIG_SND_FM801 is not set
 CONFIG_SND_HDA_INTEL=m
 # CONFIG_SND_HDSP is not set
 # CONFIG_SND_HDSPM is not set
 # CONFIG_SND_ICE1712 is not set
 # CONFIG_SND_ICE1724 is not set
 # CONFIG_SND_INTEL8X0 is not set
 # CONFIG_SND_INTEL8X0M is not 

Re: [Alsa-user] Select a Virtual device

2007-12-14 Thread Julien Claassen
Hi!
  These are just ideas, I really don't know for sure. But maybe it helps...
Try wrapping your devices in plug-devices like this:
pcm.plug_player {
  type plug
  slave { pcm audio_player
}

  Or try to remove the ctl-devices. With aplay and other good alsa-programs 
they shouldn't be necessary. At least it says so on the alsa wiki somewhere. 
Or try writing the ctl description like this:
ctl.audio_player {
  type hw
  card 0
}
  Another option is to use the jack-plugin and start jack. So you could use 
the jack-server to interconnect your apps.

pcm.myjack
  type jack
  playback_ports {
0 alsa_pcm:playback_1
1 alsa_pcm:playback_2
  }
  capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
  }
}
  I don't know if you can open this port multiple times at once. If not just 
define a second jack device. To avoid problems, wrap them in plug devices, 
as shown above with your audio_player device.
  HTH.
  Kindest regards
 Julien


Music was my first love and it will be my last (John Miles)

 FIND MY WEB-PROJECT AT: 
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
=== AND MY PERSONAL PAGES AT: ===
http://www.juliencoder.de

-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] alsamixer: function snd_mixer_load failed: Inappropriate ioctl for device

2007-12-14 Thread Clemens Ladisch
Salatiel Filho wrote:
 On 12/13/07, Clemens Ladisch [EMAIL PROTECTED] wrote:
 Salatiel Filho wrote:
  I am having a big trouble to make sound work on my ARM machine.
 
  alsamixer: function snd_mixer_load failed: Inappropriate ioctl for device

 Make sure that the kernel and the userspace tools are compiled with
 exactly the same architecture and other options that can affect structure
 sizes.

 They are. I compiled both.

The size of the respective parameter structures is encoded in the IOCTL
numbers.  Since it is the snd_mixer_load() function that failed, earlier
ioctl calls succeeded, so it's very likely that the reason that
SNDRV_CTL_IOCTL_ELEM_READ is unknown is that the size of struct
snd_ctl_elem_value is different.

Please put a
  printf(struct size: %u\n, sizeof(struct snd_ctl_elem_value));
(or printk) into both alsamixer and some kernel code (for example,
snd_ctl_ioctl() in core/control.c).


Regards,
Clemens

-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


[Alsa-user] [SOLVED] Re: No sound on ThinkPad R60 (ICH7, 82801G)

2007-12-14 Thread Christoph Bier
Christoph Bier schrieb am 09.12.2007 12:12:

 Hello,
 
 on my wife's ThinkPad running Ubuntu Gutsy (7.10) and ALSA 1.0.14 I
 get no sound. But using the Gutsy live CD the sound works (and on my
 desktop with the same sound chip (and Gutsy) but rev 01 instead of
 rev 02 sound works, too)... It's quite strange since I compared
 those files from the live CD and the installed system I thought they
 were worth to:

[...]

 I used alsamixer, the GNOME panel volume control, and
 the volume control buttons of the ThinkPad to turn volume to 100%
 and it's not muted. [...]

But GNOME has its own volume control configuration in the volume
control applet that does not communicate with alsamixer. And there
was PCM muted ...

Best
Christoph
-- 
+++ Typografie-Regeln: http://zvisionwelt.de/downloads.html (1.6)


-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


[Alsa-user] Using dmix/dsnoop/dshare to access individual channels of multichannel codec

2007-12-14 Thread Steve Strobel
I am using a 4-input, 8-output codec (AD1938) in an application 
similar to a live sound mixing
board, where a combination of the input signals get mixed for each 
output.  I can mix four
inputs to four outputs with a command like:

 arecord --file-type raw --channels=4 --format=S32_LE --rate=16000 \
  | crosspoint \
  | aplay  --file-type raw --channels=4 --format=S32_LE --rate=16000

where crosspoint is a simple program that reads from stdin, does some 
mixing, and outputs
to stdout.

My next step is to play and record wave files from the various 
channels, while the crosspoint
is running.  For example, I might need to play message1.wav to 
channel 2 and message2.wav
to channel 3 while recording channel 1 to message3.wav.  I am looking 
for advice about the
best way to accomplish that.

It seems like it should be possible using a combination of dmix, 
snoop, and dshare, as follows:
   - Use dsnoop to split the 4-channel input to the crosspoint and 
another virtual sound input, call it A.
   - Use dshare to split A into four mono sources.  Then can use 
arecord normally to capture wave files.
   - Use dmix and possibly dshare to similarly let the crosspoint 
continue to use the multi-channel
 output while also providing a mono sound device for each channel 
that I can use with aplay.

Am I on the right track, or would I be better off adding 
functionality to the crosspoint application
to read and write wave files?  Thanks for any suggestions.

Steve


---
Steve Strobel
Link Communications, Inc.
1035 Cerise Rd
Billings, MT 59101-7378
(406) 245-5002 ext 102
(406) 245-4889 (fax)
WWW: http://www.link-comm.com
MailTo:[EMAIL PROTECTED]


-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] Need optic out for VIA VT1708 on pico-itx

2007-12-14 Thread John Stile
I think the audio card is working.
The problem is in the way the motherboard and case are wired.

The front digital audio port traces to SPDIF_IN (pin 17 of the 18 pin
Front Audio Pin Connector), which means this can only accept
Optic-Digital-IN.

The only SPDIF_OUT appears on pin 57 of the 80 pin Multimedia
Connector (connector only ~20mm long), which is wried to nothing.

I need to find a mate for the 80 pin Multimedia Connector and solder
it to an fiber optic transmitter to get Optic-Digital-OUT.

I'll beg Via for help in finding a plug to fit that connector.

On Fri, 2007-12-14 at 00:32 -0800, John Stile wrote:
 I'm concerned because http://alsa.opensrc.org/DigitalOut example shows
 'cat /proc/asound/devices' with a unique hw:x,y for the digital audio
 playback device, and my output shows:
  16: [ 0- 0]: digital audio playback
  17: [ 0- 1]: digital audio playback
 and neither of these work:
   aplay -D plughw:0,0 Track01.wav
   aplay -D hw:0,0 Track01.wav
   aplay -D plughw:0,1 Track01.wav
   aplay -D hw:0,1 Track01.wav
 When I get it right should I be able to see a red light coming out of
 the optic audio port?
 Could this be a problem with my case?
 
 On Thu, 2007-12-13 at 21:05 -0800, John Stile wrote:
  I've found a script for helping to debug.
  REF: http://alsa.opensrc.org/index.php/Aadebug
  
  Am I having a syntax problem with aplay? 
  
  
  Output from script
  -
  ALSA Audio Debug v0.1.0 - Thu Dec 13 20:57:47 PST 2007
  http://alsa.opensrc.org/aadebug
  http://www.gnu.org/licenses/gpl.txt
  
  Kernel 
  Linux pico 2.6.23-gentoo-r3 #12 SMP Wed Dec 12 00:59:23 PST 2007 i686
  VIA Esther processor 1000MHz CentaurHauls GNU/Linux
  
  Loaded Modules 
  snd_pcm_oss33696  0
  snd_mixer_oss  15872  2 snd_pcm_oss
  snd_seq_oss25984  0
  snd_seq_midi_event  7680  1 snd_seq_oss
  snd_seq35536  4 snd_seq_oss,snd_seq_midi_event
  snd_seq_device  8588  2 snd_seq_oss,snd_seq
  snd_hda_intel 216732  1
  snd_pcm47492  2 snd_pcm_oss,snd_hda_intel
  snd_timer  18308  2 snd_seq,snd_pcm
  snd33508  8
  snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
  snd_page_alloc 10504  2 snd_hda_intel,snd_pcm
  
  Proc Config ---
  CONFIG_SOUND=y
  CONFIG_SND=m
  CONFIG_SND_TIMER=m
  CONFIG_SND_PCM=m
  CONFIG_SND_HWDEP=m
  CONFIG_SND_RAWMIDI=m
  CONFIG_SND_SEQUENCER=m
  # CONFIG_SND_SEQ_DUMMY is not set
  CONFIG_SND_OSSEMUL=y
  CONFIG_SND_MIXER_OSS=m
  CONFIG_SND_PCM_OSS=m
  CONFIG_SND_PCM_OSS_PLUGINS=y
  CONFIG_SND_SEQUENCER_OSS=y
  CONFIG_SND_RTCTIMER=m
  CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
  # CONFIG_SND_DYNAMIC_MINORS is not set
  CONFIG_SND_SUPPORT_OLD_API=y
  # CONFIG_SND_VERBOSE_PROCFS is not set
  # CONFIG_SND_VERBOSE_PRINTK is not set
  # CONFIG_SND_DEBUG is not set
  CONFIG_SND_MPU401_UART=m
  CONFIG_SND_VX_LIB=m
  CONFIG_SND_AC97_CODEC=m
  # CONFIG_SND_DUMMY is not set
  # CONFIG_SND_VIRMIDI is not set
  # CONFIG_SND_MTPAV is not set
  CONFIG_SND_MTS64=m
  # CONFIG_SND_SERIAL_U16550 is not set
  CONFIG_SND_MPU401=m
  # CONFIG_SND_PORTMAN2X4 is not set
  # CONFIG_SND_ADLIB is not set
  # CONFIG_SND_AD1816A is not set
  # CONFIG_SND_AD1848 is not set
  # CONFIG_SND_ALS100 is not set
  # CONFIG_SND_AZT2320 is not set
  # CONFIG_SND_CMI8330 is not set
  # CONFIG_SND_CS4231 is not set
  # CONFIG_SND_CS4232 is not set
  # CONFIG_SND_CS4236 is not set
  # CONFIG_SND_DT019X is not set
  # CONFIG_SND_ES968 is not set
  # CONFIG_SND_ES1688 is not set
  # CONFIG_SND_ES18XX is not set
  # CONFIG_SND_GUSCLASSIC is not set
  # CONFIG_SND_GUSEXTREME is not set
  # CONFIG_SND_GUSMAX is not set
  # CONFIG_SND_INTERWAVE is not set
  # CONFIG_SND_INTERWAVE_STB is not set
  # CONFIG_SND_OPL3SA2 is not set
  # CONFIG_SND_OPTI92X_AD1848 is not set
  # CONFIG_SND_OPTI92X_CS4231 is not set
  # CONFIG_SND_OPTI93X is not set
  # CONFIG_SND_MIRO is not set
  # CONFIG_SND_SB8 is not set
  # CONFIG_SND_SB16 is not set
  # CONFIG_SND_SBAWE is not set
  # CONFIG_SND_SGALAXY is not set
  # CONFIG_SND_SSCAPE is not set
  # CONFIG_SND_WAVEFRONT is not set
  # CONFIG_SND_AD1889 is not set
  # CONFIG_SND_ALS300 is not set
  # CONFIG_SND_ALS4000 is not set
  # CONFIG_SND_ALI5451 is not set
  # CONFIG_SND_ATIIXP is not set
  # CONFIG_SND_ATIIXP_MODEM is not set
  # CONFIG_SND_AU8810 is not set
  # CONFIG_SND_AU8820 is not set
  # CONFIG_SND_AU8830 is not set
  # CONFIG_SND_AZT3328 is not set
  # CONFIG_SND_BT87X is not set
  # CONFIG_SND_CA0106 is not set
  # CONFIG_SND_CMIPCI is not set
  # CONFIG_SND_CS4281 is not set
  # CONFIG_SND_CS46XX is not set
  # CONFIG_SND_CS5530 is not set
  # CONFIG_SND_CS5535AUDIO is not set
  # CONFIG_SND_DARLA20 is not set
  # CONFIG_SND_GINA20 is not set
  #