I think I have re-enabled pulse and I am able to replicate the
problem.

with openal, alsa:
[EMAIL PROTECTED]:~/defence-pyg$ env | grep "PYGLET"
PYGLET_DEBUG_MEDIA=1
[EMAIL PROTECTED]:~/defence-pyg$ python soundtest.py
E: thread-posix.c: Assertion 'pthread_setspecific(t->key, userdata) ==
0' failed at pulsecore/thread-posix.c:194, function pa_tls_set().
Aborting.
Aborted
[EMAIL PROTECTED]:~/defence-pyg$

with alsa, openal:
[EMAIL PROTECTED]:~/defence-pyg$ env | grep "PYGLET"
PYGLET_DEBUG_MEDIA=1
[EMAIL PROTECTED]:~/defence-pyg$ python soundtest.py
<pyglet.media.drivers.openal.OpenALAudioPlayer object at 0xb7c43a6c>
underrun: reducing update period to 0.04
<pyglet.media.drivers.openal.OpenALAudioPlayer object at 0xb7c43a6c>
underrun: reducing update period to 0.03
<pyglet.media.drivers.openal.OpenALAudioPlayer object at 0xb7c43a6c>
underrun: reducing update period to 0.02
[EMAIL PROTECTED]:~/defence-pyg$

I notice that it's mentioning openal here, but I thought seeing as the
alsa driver is first it would use that. Trying again I got the same
problem, but no output about underrun this time. Trying again I got
this:
<pyglet.media.drivers.openal.OpenALAudioPlayer object at 0xb7cc4a6c>
underrun: reducing update period to 0.04
E: thread-posix.c: Assertion 'pthread_setspecific(t->key, userdata) ==
0' failed at pulsecore/thread-posix.c:194, function pa_tls_set().
Aborting.
Aborted

Again with openal, alsa: E: thread-posix.c: Assertion
'pthread_setspecific(t->key, userdata) == 0' failed at pulsecore/
thread-posix.c:194, function pa_tls_set(). Aborting.
Aborted

I don't know where to find alsa.log, could you help me find where it's
located?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to