12 May
2010
12 May
'10
1:53 a.m.
On Wed, 2010-05-12 at 00:47 +0200, Fons Adriaensen wrote:
On Tue, May 11, 2010 at 10:08:20AM -0700, Fernando
Lopez-Lezcano wrote:
Yes, I do wonder why users with such cards would want PA to use it in
the first place. JACK is made for these (or these were made for JACK,
depending on how you see it).
For me, its quite simple (and doesn't require removing PA), just turn
off module-udev-detect (auto-hardware-detection) in PA, load up JACK,
and load module-jack-sink/source. Now all your desktop audio pipes
through JACK and to your pro-audio card, and you get full access to any
I/O you want.
On Tue, 2010-05-11 at 17:27 +0200, ailo wrote:
Given that PA aims to be a desktop audio server catering for
the 'standard' formats such as stereo and 5.1, it really can't
be blamed for not knowing what to do with a card that presents
N (N >= 8) identical channels. And I'm somehow surprised if
users of such cards (who probably use Jack anyway) expect PA
to handle this OOTB. The obvious solution for them is to use
the PA<->Jack bridge which is reported to work well.
Ciao,
On 05/11/2010 03:58 PM, Gabriel M. Beddingfield
wrote:
Big multichannel rme cards are also affected (obviously). In those cases
the workaround I have to deltas did not work (too many channels?)
On the other hand, I _think_ (but I'm not positive now that I think
about it) that the 8 channel gina/layla3g worked fine, I would have to
test again.
On Tue, 11 May 2010, ailo wrote:
> How do other multi-channel pro audio cards work with pulseaudio?
> Is only ice1712 affected?
>
> I only have experience with m-audio delta cards.
m-audio delta cards are ice1712 cards.
http://alsa.opensrc.org/index.php/ice1712
To clarify, I meant to ask if chips, other than ice1712 are affected.