Closed cyberic99 closed 2 years ago
What Linux distribution are you using?
The main thing that changed between those versions of Raylib Python CFFI was the version of Raylib used. (Although the GitHub Actions build environment also changes regularly and unpredictability) So this seems likely to be either a problem with Raylib itself, or a problem with the way we build Raylib.
Please download Raylib, compile it including examples, and then see if examples such as https://github.com/raysan5/raylib/blob/master/examples/audio/audio_sound_loading.c work
If that works, then build Raylib Python CFFI with your Raylib by
pip3 install --no-binary raylib --upgrade --force-reinstall raylib
Raylib did a pretty major change to their audio system around this time period so that might be related https://github.com/raysan5/raylib/commit/22c17da4d7b33f1c3a345b2e04e7935e16603ae9
What Linux distribution are you using?
Archlinux, which is a rolling release
Please download Raylib, compile it including examples, and then see if examples such as https://github.com/raysan5/raylib/blob/master/examples/audio/audio_sound_loading.c work
they run but I get no sound. and no specific error is printed
(I used raylib 4.2.0-2 from my package manager, did not try the master)
I'm on Arch too. When I run your example the sound plays, and it outputs:
RAYLIB STATIC 4.2.1.1 LOADED
INFO: AUDIO: Device initialized successfully
INFO: > Backend: miniaudio / PulseAudio
INFO: > Format: 32-bit IEEE Floating Point -> 16-bit Signed Integer
INFO: > Channels: 2 -> 2
INFO: > Sample rate: 44100 -> 44100
INFO: > Periods size: 3304
INFO: FILEIO: [sound.wav] File loaded successfully
INFO: WAVE: Data loaded successfully (44100 Hz, 16 bit, 2 channels)
I think it could be something specific to your system. But either way, if the bug is present in Raylib C code (rather than Raylib Python CFFI code) then you'll have to report it to Raylib.
OK, thank you for your answers. I reproduced the issue with only C code, I reported it upstream, I'll let you know about any progress
confirmed as bug in raylib/miniaudio so closing
FYI the bug has been resolved in raylib (or rather in miniaudio), see: https://github.com/raysan5/raylib/issues/2740
Thanks
I am using
raylib
on linux with python 3.10.7Using this script:
same with latest version 4.2.1.1
Thank you