12 May
2010
12 May
'10
9:02 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 12.05.2010 00:47, schrieb Fons Adriaensen:
On Tue, May 11, 2010 at 10:08:20AM -0700, Fernando
Lopez-Lezcano wrote:
So would it not be the most easy and non-obtrusive solution for
everybody involved, if PA just treats every card, that does not follow
"desktop-standards" as a simple stereo-device?
Desktop-audio/legacy-stuff would go to the first 2 ports of such a card
via PA (using its JACK-sink if JACK is running and switching to it as
JACK ist started) and everything else would be handeled by JACK on the
users behest.
Thus PA would not be seen as a trouble-maker, but as a solution most
welcome.
And the PA-people would not need to add handling of drivers for
un-desktopish hardware to their to-do lists.
Everybody could be happy :-)
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. 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. The obvious solution for them is to use
the PA<->Jack bridge which is reported to work well.
Ciao,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkvqUo4ACgkQ1Aecwva1SWMiMQCfTnFQgOIwR3cb+rlBEEHxDCNx
7hYAnjJJWvIWMRJJ5DDYeBztT+dIfrOs
=1Cyc
-----END PGP SIGNATURE-----