All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arve Knudsen" <aknuds-1@broadpark.no>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Problem writing to PCM plugin
Date: Wed, 11 Aug 2004 15:33:45 +0200	[thread overview]
Message-ID: <opscklaj0ufmr65f@mail.broadpark.no> (raw)

I'm currently trying to implement support for user defined pcm plugins in  
PortAudio ALSA (ALSA-lib 1.05), and I've got as far as discovering the  
pcms. In order to test I defined a routing plugin, which moves data from  
channel 0/1 to 16/17 (S/PDIF) on my Hammerfall Lite. With aplay this  
plugin works just fine, but when I open it with PortAudio the same way as  
with any hardware device, the output is simply silent (I can't listen to  
any of the ADAT channels since I lack ADAT gear). Defining a simple plugin  
which does nothing but drive my onboard nForce2 (routing fails with this  
assertion: 'pcm_plug.c:363: snd_pcm_plug_change_channels: Assertion  
`snd_pcm_format_linear(slv->format)' failed') works the same as if I open  
the hw device.

The obvious difference to aplay I can think of is that we use floating  
point format in the PortAudio tests, so there is an intermediate  
conversion before the audio gets to the routing plugin. Could this be the  
cause of the problem? If you wish I can provide output from snd_pcm_dump.

Thanks

Arve Knudsen


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

             reply	other threads:[~2004-08-11 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 13:33 Arve Knudsen [this message]
2004-08-11 13:36 ` Problem writing to PCM plugin Jaroslav Kysela
2004-08-11 13:53   ` Arve Knudsen
2004-08-11 13:45 ` Clemens Ladisch
2004-08-11 14:00   ` Arve Knudsen
2004-08-11 15:06   ` Arve Knudsen
2004-08-11 15:03     ` Jaroslav Kysela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=opscklaj0ufmr65f@mail.broadpark.no \
    --to=aknuds-1@broadpark.no \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.