Open GoogleCodeExporter opened 8 years ago
Windows is 7-x64 while the Python is 32-bit.
avbin.dll is located at C:\Windows\SysWOW64\avbin.dll which is the system
directory used by 32bit applications. It is redirected at the Windows API level
when loading libraries. Irrelevant by the fact the library can be loaded before
opengl and work.
Original comment by sugoib...@gmail.com
on 12 May 2011 at 11:38
As a workaround an attempt to load AVBin DLL in the __init__.py of pyglet works
for me. It's bit ugly solution though, but I have patch prepared if someone
happens to need it. I think the bug should be reported to upstream Python to
get a proper fix (if this is an issue with ctypes, that is).
Original comment by zok...@gmail.com
on 8 Oct 2011 at 7:39
Attachments:
Same here. The fix works for me too.
Original comment by michal....@gmail.com
on 2 Dec 2011 at 11:59
Issue 546 has been merged into this issue.
Original comment by Adam.JT...@gmail.com
on 11 Dec 2012 at 11:40
Original comment by useboxnet
on 17 Jul 2013 at 4:27
I ran into this issue this week. The suggested patch fixed the issue, but it
seems like there should be a cleaner solution. I'll take a look if I have time.
Juan, do you have any ideas for this one?
Original comment by larson.e...@gmail.com
on 24 Apr 2014 at 3:49
If I understand the report it looks like a problem with python itself and not a
pyglet issue (windows 64-bit running python 32-bit), although the workaround
may help.
Original comment by useboxnet
on 24 Apr 2014 at 5:36
Ahh, you're right. I wonder what's going on there -- seems like this issue
would crop up in many other places if this were a problem with `cdll`. Maybe
it's documented that `cdll` changes behavior based on what's been loaded...? It
would be nice if there were some nice way to deal with it. I'll see if I can
find something.
Original comment by larson.e...@gmail.com
on 24 Apr 2014 at 5:41
I still have to apply this patch any time I update Pyglet on my windows system.
Is there a drawback to adding the patch upstream? It's not an elegant solution,
but it works -- is it expected to break something?
Original comment by schoolbo...@gmail.com
on 2 Jul 2014 at 3:51
Actually the patch no longer works (maybe some upstream change affected it?),
so on my system I just changed it so it doesn't try to import avbin anymore.
Original comment by schoolbo...@gmail.com
on 2 Jul 2014 at 5:37
What do you mean by "no longer works"? What's your OS/Python configuration?
Original comment by michal....@gmail.com
on 3 Jul 2014 at 5:32
Windows 7 64-bit, running Python 2.7.6 32-bit. (I was commenting from my lab
mate's account yesterday.) The fix worked (somehow) on previous versions of
Pyglet -- I probably last updated it six months ago -- but now when I apply the
suggested patch to the latest `tip.zip` it doesn't. I need the latest Pyglet in
order for my audio player objects to have `.delete()` support, so reverting to
an older Pyglet version where the patch works isn't an option in my case.
Original comment by larson.e...@gmail.com
on 3 Jul 2014 at 1:49
What happens if avbin.dll is in the same directory of your script.
Original comment by useboxnet
on 3 Jul 2014 at 1:55
Still fails. Just doing `from pyglet.media import Player` causes it to bomb.
Removing Calling `from pyglet import Media` does not. And removing `avbin.dll`
from the directory (and everywhere else on my system) allows it to pass. For
now I've just removed `avbin.dll` from my system, which should prevent the
problem. I think the modified date for my `avbin.dll` was sometime in 2013, is
it possible an old version could be causing problems?
Original comment by larson.e...@gmail.com
on 3 Jul 2014 at 2:59
Possibly, just try version 11 alpha 4 from:
https://github.com/AVbin/AVbin/downloads
It has some known issues with video but it fixes a lot of problems with audio.
Original comment by useboxnet
on 3 Jul 2014 at 3:01
Although that was released in 2012; well... worth a try.
I'd love to investigate this, I'll try to allocate time to play with Windows
(ufff).
Original comment by useboxnet
on 3 Jul 2014 at 3:03
Once I realized that we can just remove `avbin` altogether as a workaround, the
bug became much less problematic for us. So probably not so high a priority, at
least at our end.
Original comment by larson.e...@gmail.com
on 3 Jul 2014 at 3:17
Hi! We still have this issue under 64bit win7, 32bit python 2.7.5, pyglet
1.1.4. Removing the avbin dll is not an option for us, since we use pyglet for
video/audio playback for data analysis.
The current workaround is to set the import order properly (i.e. "from
pyglet.media import avbin" at early import stage), but every once in a while
the issue arises again and we have to pollute more and more the codebase. Our
user base is growing, so I'd appreciate your support :) Thanks
Original comment by gregorio...@gmail.com
on 4 Jul 2014 at 7:23
Gregorio: it's unlikely we will fix this on 1.1.4, our target is to get 1.2 out
of the door ASAP.
I'm going to add this issue to the 1.2 release blockers list.
Original comment by useboxnet
on 4 Jul 2014 at 7:38
Sounds promising, thank you.
Original comment by gregorio...@gmail.com
on 4 Jul 2014 at 8:17
Original issue reported on code.google.com by
sugoib...@gmail.com
on 12 May 2011 at 11:33