I changed line 1332 to 'raise', but that produces an error for both drivers: AttributeError: 'module' object has no attribute 'oledll'. What are right changes to make to __init__.py to discover the errors?
On Sep 2, 11:58 am, "Alex Holkner" <[EMAIL PROTECTED]> wrote: > On Tue, Sep 2, 2008 at 8:54 PM, Ragzouken <[EMAIL PROTECTED]> wrote: > > > 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? > > It's created in your working directory when the alsa driver is > initialised, which it sounds like it isn't -- you probably don't have > the ALSA user lib, or pyglet is having errors importing it (you can > discover these, if you're interested, with some simple hacks to the > driver imports in pyglet/media/__init__.py to reraise the import > exception instead of falling back on the next driver). > > Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
