[pulseaudio-tickets] [PulseAudio] #941: No sound from Ice1712 chipsets - can help so it can maybee work

[PulseAudio]

#941: No sound from Ice1712 chipsets - can help so it can maybee work
---------------------+------------------------------------------------------
  Reporter:  mith    |       Owner:  lennart                                                                                                                                                                                                                                                                                                 
      Type:  defect  |      Status:  new                                                                                                                                                                                                                                                                                                     
 Milestone:          |   Component:  module-alsa-*                                                                                                                                                                                                                                                                                           
Resolution:          |    Keywords:  Digigram VX442 Hoontech Soundtrack Audio DSP 24 IC Ensemble Generic device  M-Audio Midiman MAudio Delta 44  66  410  1010  1010LT  1010-LT  Audiophile 2496  DiO 2496     Seasound Solo     Sonorus Medi/o     Terratec EWS88D  EWS88MT  EWX24/96  DMX 6Fire     Event Electronics EZ8  ALSA Pulseaudio
---------------------+------------------------------------------------------

Comment(by tanuk):

 Replying to [ticket:941 mith]:
 > I have reported this bug to Ubuntu team on theirs Launchpad site but
 with no luck resolving this as an permanet fix.

 Could you provide a link to the Launchpad bug, so that the same things
 won't have to discussed again in this bug?

 > As I have understand, You develop Pulseaudio and not Ubuntu as I first
 believed (im new to Linux) and I think its more important to report the
 bug here so it can be fixed. And if it gets fixed here, it will apply to
 all Linux distros using Pulseaudio/Alsa.
 >
 >
 > Actually Ice 1712 chipsets are on a lot of soundcards so if this will
 get fixed A LOT of soundcards and their users will get working sound.
 >
 >
 > Ive managed to follow some guides when ive searched myself over the net
 how to get audio working with this card and it worked.
 >
 > Now im reporting this so it can be implemented so it can be working
 again with all soundcards using Ice 1712 chipset (now date I know about 17
 soundcards that will work if this will be fixed - thats some!)
 >
 > I myself are an soundtechnican and musican doing music on the computer
 so I have knowledge in how to set the default mixer for best results and
 also some tips about setting the right latency.

 For doing music on the computer you will want to use Jack instead of
 Pulseaudio. With new enough Jack and Pulseaudio they should (I have no
 personal experience) be able to cooperate so that when Jack starts,
 Pulseaudio automatically releases the sound card, so hopefully you would
 be able to easily use Pulseaudio for "normal" tasks and Jack when doing
 music.

 > As I have discovered it can get to work but with audio glitches, have
 you ever thought of increasing the buffer size that the soundcard uses? If
 its to low, of course the sound will glitch.

 Now I'm losing track of what you're doing. I thought you didn't get any
 sound? But now you're saying that you get some sound, but with glitches?

 > I would recommend the following: If you only uses the computer not in
 making music etc, you can set a high buffer for the soundcard.
 >
 > Its only when you are making music you are in need of a low-latency
 responsive system. otherwise you can set the buffer size to 512, 768 or
 1024.
 >
 > The slower the computer and older, the better to have an high latency
 value. Because if the computer is to slow the audio will glitch. Therefore
 its good? to set a high value like 512 to have older computers able to
 playback sound.

 You're right. But this is already taken care of - Pulseaudio will use 2
 second buffers if the sound card driver is able to provide that big
 buffers (otherwise the maximum is used). For giving good interactivity,
 the buffer is rewritten when something happens that requires immediate
 reaction (volume change, stream pause, stream creation and so on).

 > I can contribute to this in order to try making it work if you help me
 what to do so you can use it later in future Pulse audio releases that
 many Linux distrubitations use so many can get some sound..

 I'm a bit confused because you said that you actually did get it to work,
 but anyway... my initial guess is that because the sound card is aimed at
 professional audio work and not as an audio interface for entertainment
 playback, the sound card driver doesn't provide any device identifiers
 with known semantics (like "surround71").

 But guessing is a bad substitute for knowledge, so could you provide the
 Pulseaudio startup log at verbose logging level? The way to get the log is
 the following:

 1. You'll want to stop the running Pulseaudio instance, but by default, in
 most systems, Pulseaudio will restart automatically. To disable the
 automatic restart, put this to ~/.pulse/client.conf:

 {{{
 autospawn = no
 }}}

 2. Now you can stop pulseaudio, so run this in a terminal:

 {{{
 pulseaudio -k
 }}}

 3. And restart it:

 {{{
 pulseaudio -vvvvv > log.txt 2>&1
 }}}

 4. Wait for a while for the startup to complete (something like 10 seconds
 should be enough).

 5. Stop pulseaudio by pressing Ctrl-C.

 Now you should have the startup log in the file log.txt, and you can
 attach that to this bug.

-- 
Ticket URL: <http://pulseaudio.org/ticket/941#comment:2>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server