Tested on Windows 10 x64, 32 bit ffmpeg 3.3 and 3.4. Realtek HD Audio.
Using the noisy example to test wav and ogg.
The sound does not work without ffmpeg, and wav. Same with ffmpeg loaded. I
tested an ogg file instead of wav and neither work.
With either, the first sound will be the distorted sound popping, and then
nothing plays after the initial pop.
Not sure what other information you need from me or tests to perform.
Also unrelated, trying to start the example gives an error:
Traceback (most recent call last):
File "D:\pyglet-1.4.0a1\examples\noisy\noisy.py", line 46, in <module>
from pyglet.gl import *
File "C:\Python27\lib\site-packages\pyglet\gl\__init__.py", line 219, in
<module>
from .win32 import Win32Config as Config
File "C:\Python27\lib\site-packages\pyglet\gl\win32.py", line 6, in
<module>
from pyglet.canvas.win32 import Win32Canvas
File "C:\Python27\lib\site-packages\pyglet\canvas\__init__.py", line 99,
in <module>
from pyglet.canvas.win32 import Win32Display as Display
File "C:\Python27\lib\site-packages\pyglet\canvas\win32.py", line 7, in
<module>
from pyglet.libs.win32 import _kernel32, _user32, types, constants
File "C:\Python27\lib\site-packages\pyglet\libs\win32\__init__.py", line
237, in <module>
_user32.GetRawInputData.argtypes = [HRAWINPUT, UINT, LPVOID, PUINT, UINT
]
NameError: name 'PUINT' is not defined
Removing the PUNIT works.
On Tuesday, November 21, 2017 at 3:50:09 AM UTC-6, Daniel Gillet wrote:
>
> Hello,
>
> Claudio Canepa and myself have worked on a new wrapping of FFmpeg with
> ctypes to replace AVbin. Benjamin Moran helped also a lot with his opinions
> on various topics and to coordinate our work with pyglet main branch. Many
> bugs were also fixed in the Audio Drivers and in the Media Player itself.
> There should not be any breaking API changes but there are a couple of
> additional features. All is described in the documentation.
>
> Today our work is available from pyglet repository in the default branch.
> A new tag 1.4.0a1 will be added soon. So anyone who wants to give this a
> try can create a virtual environment as described in the documentation
> <http://pyglet.readthedocs.io/en/latest/internal/virtualenv.html>, and
> install pyglet from within the virtual environment with pip install -e hg+
> https://bitbucket.org/pyglet/pyglet/#egg=pyglet
>
> Here is a quick extract from the new documentation regarding the
> installation of FFmeg.
>
> FFmpeg installation
>
> You can install FFmpeg for your platform by following the instructions
> found in the FFmpeg download <https://www.ffmpeg.org/download.html> page.
>
> For Mac OS and Linux, the library is usually installed system-wide. For
> Windows users, it’s not recommended to install the library in one of the
> windows sub-folders.
>
> Instead we recommend to use the pyglet.options search_local_libs:
>
> import pygletpyglet.options['search_local_libs'] = True
>
> This will allow pyglet to find the FFmpeg binaries in the lib folder
> located in your running script folder.
>
>
>
>
> At the time of development, we've been using FFmpeg 3.3.
> We are really thrilled by the new code and we're looking forward to
> hearing if you encountered any difficulties in order to improve the
> documentation or the code.
>
> Dan
>
--
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.
