Hi Nathan, On Sat, Sep 28, 2013 at 2:26 AM, Nathan <[email protected]> wrote: > I am going to go ahead and start a new thread in response to this statement: > > On Thu, Sep 26, 2013 at 10:39 AM, John Duprey <[email protected]> wrote: >> >> >> Likewise, there are issues with avbin (that pyglet depends on) that seem >> to be long standing. >> > > Yep, and I'm stumped. I've spent over 100 hours looking into it and > attempting to code a fix. I learned a ton about Libav and about C and ended > up refactoring a lot of the fundamentals of AVbin (in experimental branches) > in an attempt to fix the underlying cause of all the problems (as I > understand it) and ended up with...very similar buggy behavior as I started > with and no more ideas as to why. > > I'd be happy to discuss the problems with anyone who would be willing to > jump in and help with the C code. I believe I need to commit my latest > branches of refactoring attempts, though. > > I picked up maintainership of AVbin 1) to learn, 2) for fun, 3) to ensure it > would keep working with new versions of everything else, and most > importantly 4) because no one else would. > > #1 has been accomplished. #2 is over. It's no longer fun for me and I'm > not willing to invest any more weeks trying to bang my head against it. > I've spent a couple years trying to fix AVbin and Pyglet so that I could > code what I want with them instead of coding what I want with them. I'm > done with that. > > Either someone (or some people) pitch in and help get past this hurdle, or > AVbin is simply going to sit and remain in it's partially functional state > until the OS's pass it by completely. I'm not going to take the couple > hours to writeup all my findings unless someone is willing to actually do > something with them. > > At this point I'd be fine transferring control of the project back to > Richard Jones if that would help anything. > > I'm willing to continue to do standard maintenance, updates, and providing > binary packages if no one else will take it (I'm pretty good at that stuff). > But I can't pretend I currently have sufficient skill in C and Libav to fix > the outstanding issues. >
I can't spend too much time on this, but probably I can help you with some C code. Since avbin is about five hundred lines of code is shouldn't be a problem. BTW, can avbin be a source of but of randomly stopping sounds on OS X? -- Paul -- 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/groups/opt_out.
