You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since switching to sdl2-compat, the python pygame.mixer does not seem to find audio devices anymore when supplied the devicename parameter.
It appears that when pygame.mixer.init is first run, sdl2-compat's GetAudioDeviceLocked has an empty list for AudioSDL3PlaybackDevices.
For my use case, always rebuilding the list when calling GetAudioDeviceLocked restores previous behaviour. This is the patch that I currently use: 6c7bd3e. I have also tried only rebuilding the list when it is empty, but this results in a invalid ID being used to open the audio device.
This may be an issue with pygame itself, but since it has previously worked and stopped since sdl2-compat, I'm suspecting that some compatibility layer is incompatible with pygame. Unfortunately, I haven't had the capabilities to test sdl2-compatdirectly yet.
I'm still hoping that this helps in some way.
The text was updated successfully, but these errors were encountered:
Hey there!
Since switching to
sdl2-compat
, the pythonpygame.mixer
does not seem to find audio devices anymore when supplied thedevicename
parameter.It appears that when
pygame.mixer.init
is first run, sdl2-compat'sGetAudioDeviceLocked
has an empty list forAudioSDL3PlaybackDevices
.For my use case, always rebuilding the list when calling
GetAudioDeviceLocked
restores previous behaviour. This is the patch that I currently use: 6c7bd3e. I have also tried only rebuilding the list when it is empty, but this results in a invalid ID being used to open the audio device.This may be an issue with pygame itself, but since it has previously worked and stopped since
sdl2-compat
, I'm suspecting that some compatibility layer is incompatible with pygame. Unfortunately, I haven't had the capabilities to testsdl2-compat
directly yet.I'm still hoping that this helps in some way.
The text was updated successfully, but these errors were encountered: