Benjamin

There are no special requirements - just a normal client context. For the PulseAudio backend, the application name will only appear in the PulseAudio monitor when a source is actively...

The PulseAudio backend works OK on my Arch systems, as well as in some Debian VMs I have. If no errors appear from the pyglet side, it would seem that...

I tried the MX-19.4_x64.iso, and sound played fine with PulseAudio. I used the `soundscape` example in the pyglet repository.

In your event loop, you might also need to call `pyglet.app.platform_event_loop.dispatch_posted_events()` I had a look at the code, and PulseAudio is posting `on_write_needed` events there, as opposed to the Application...

I made a small change to the FFmpegDecoder that may aleviate the stuttering.

The PulseAudio driver seems to be really sensitive to timing. Assuming this works with the standard pyglet event loop, for a test you can try ticking everything much faster. The...

I like this idea. It would be quite useful.

Over on the Discord server we recently came up with a hack using tkinter. It runs in another process, so it won't cause any conflicts. Results are pyglet events. I...

Sorry to just jump in here, but I've been following glooey for a while, and think it's a great project. One of dislikes, however, is the number of external dependencies....

Ah, sorry I completely missed the from_x_tuple methods in your Color class. About dependencies, I actually do agree with you. It's only for libraries that I make an exception, because...