[Bug 29294] No sound with ALSA loopback devices
wine-bugs at winehq.org
wine-bugs at winehq.org
Sun Feb 26 18:54:21 CST 2012
http://bugs.winehq.org/show_bug.cgi?id=29294
--- Comment #9 from Antonio López <amlopezalonso at gmail.com> 2012-02-26 18:54:21 CST ---
>
> plughw:0,1 is the device that got used for most tests. Is that the Jack one?
> Why are other ones busy? Is that a case where a device remains open for a
> couple of seconds, preventing access to the low-level device? I believe that
> an inaccessible "default" caused no sound in past versions of Wine.
I don't know why the other devices seem to be busy. I have no other issues with
audio apps except with Amarok but probably for other reasons.
>
> As "default" is the first device accessed, this must have another reason. Why
> is default=dmix+dsnoop not accessible on your system? Does speaker-test
> -Ddefault work for you?
speaker-test -Ddefault works fine.
>
> Is this all because dmix wants to use hw:0 which is inaccessible too because
> Jackd sits on it? Shouldn't dmix go through Jack too?
>
I don't know about the nuts and bolts of the loopback devices. But I can tell
you I'm just using the generic asoundrc file shown in
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge just
below the "asoundrc definition" entry.
The only difference I made was in the loop2jack script: I modified the two
lines for system microphone as follows:
jack_connect system:capture_1 ploop:playback_1
jack_connect system:capture_2 ploop:playback_2
> >../../../tools/runtest -q -P wine ...
> Please supersede the log (make the old one obsolete) with:
> ../../../tools/runtest -i -v -P wine -M mmdevapi.dll -T ../../.. -p
> mmdevapi_test.exe.so render.c >/tmp/render.log 2&>1
> Does it stutter?
This test finishes with no output at all (no sound and an empty render.log).
>
> >trace:alsa:alsa_write_data pad: 184
> >warn:alsa:alsa_write_best_effort writei failed, recovering: -32 (Tubería rota)
> >ALSA lib ../../../src/pcm/pcm.c:7316:(snd_pcm_recover) underrun occurred
> I'd say this is a symptom of clock skew because CreateTimerQueue callback get
> more and more late. You'll certainly hear random crackling/choppy sound from
> the interactive test, thus from all w7 apps that use XAudio2. What about the
> patch from bug #28723, comment #130?
>
Applied the patch, recompiled and reinstalled git wine and the stuttering is
still there.
Regards,
Antonio
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the wine-bugs
mailing list