It seems like that might not be necessary. After your recent threaded locking commit, it started working. I tested it with a generic wave file loaded from disk, as well as some audio created from pyglet.media.procedural. All seems OK now. I'll try it again from my other machine after the weekend just to be sure, but I think that did it!
Thanks again for your work on the Pulse driver. On Saturday, December 12, 2015 at 8:58:05 PM UTC+9, Rob wrote: > > Hi, > > Could you run a test with extra debugging information from pyglet? You can > enable it by adding the following at the very start of your code. It should > be the very first thing you do with pyglet as it is processed when the > pulse audio driver module is loaded by python. > > import pyglet > > pyglet.options['debug_media'] = True > > > This will give me some insight into what pyglet is trying to do. > > Rob > > On 8 December 2015 at 03:15, Benjamin Moran <[email protected] > <javascript:>> wrote: > >> I did some more testing, and it seems like Python 3 is only partially >> working on my machine. Could you share which pulseaudio version you have? >> I'm running Arch, with Pulse 7.1 here. If your on a differnt version, I'd >> like to test that on my end. Perhaps it's a change/bug in Pulseaudio >> itself. >> >> Running pulseaudio from the CLI in verbose mode (pulseaudio -vv) shows >> that in both cases, a client connection is properly created. It just >> doesn't seem to receive any audio in Python 3, but does in Python 2.7. >> Python 3 shows the following output only, whereas Python 2.7 is followed by >> the details of the received audio data: >> >> I: [pulseaudio] client.c: Created 9 "Native client (UNIX socket client)" >> D: [pulseaudio] protocol-native.c: Protocol version: remote 30, local 30 >> I: [pulseaudio] protocol-native.c: Got credentials: uid=1000 gid=100 >> success=1 >> D: [pulseaudio] protocol-native.c: SHM possible: yes >> D: [pulseaudio] protocol-native.c: Negotiated SHM: yes >> D: [pulseaudio] srbchannel.c: SHM block is 65472 bytes, ringbuffer >> capacity is 2 * 32712 bytes >> D: [pulseaudio] protocol-native.c: Enabling srbchannel... >> D: [pulseaudio] module-augment-properties.c: Looking for .desktop file >> for python3.5 >> D: [pulseaudio] protocol-native.c: Client enabled srbchannel. >> >> >> >> >> >> On Tuesday, December 8, 2015 at 3:28:21 AM UTC+9, Rob wrote: >>> >>> In the Plasma audio mixer I do see the python icon pop up for both py2 >>> and py3. However the name is not very nice, it is the decimal address of >>> the driver context. That is something I want to solve properly for all >>> drivers later. >>> >>> Rob >>> >>> Op maandag 7 december 2015 03:00:59 UTC+1 schreef Benjamin Moran: >>>> >>>> Thanks for your work on this Rob! >>>> >>>> Unfortunately It doesn't look it's working quite right under Python 3. >>>> For example, in the Gnome sound control panel, you can see a >>>> "Python2.7" application >>>> appear when loaded_sound.play() is called. Under Python 3, the sounds >>>> load correctly, >>>> and appear to play correctly, but no active application appears. >>>> >>>> Let me know if there is any troubleshooting I can help with. >>>> >>>> -Ben >>>> >>>> On Monday, December 7, 2015 at 2:17:40 AM UTC+9, Brandon Keith Biggs >>>> wrote: >>>>> >>>>> Hello Rob, >>>>> This is awesome!!! Thank you so much for doing this! >>>>> Can't wait to see what happens with the OpenAl refactoring! >>>>> thank you, >>>>> >>>>> Brandon Keith Biggs <http://www.brandonkeithbiggs.com/> >>>>> On 12/6/2015 3:54 PM, Rob wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I just completed a complete rework of the PulseAudio driver. It >>>>> started out as refactoring, but in the end I mostly rewrote the driver. I >>>>> hope this will solve some segmentation faults and threading issues. >>>>> Please >>>>> try it out and let me know if there are any issues. >>>>> >>>>> I will now move on to the OpenAL driver and do the same. The >>>>> DirectSound driver will follow after that. And then I can do some >>>>> additional refactoring and fixes in the generic media support. >>>>> >>>>> Rob >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "pyglet-users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at http://groups.google.com/group/pyglet-users. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>>>> -- >> You received this message because you are subscribed to the Google Groups >> "pyglet-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/pyglet-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
