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
I've built this on msys2 mingw64 targeting x86_64 (and then mingw32 and i686), and ran it on Windows 10.
The main window appeared, said it couldn't find an audio device; at the same time, there appeared a console window on the background saying this:
[DEBUG] Weirdness on line 12
[DEBUG] Weirdness on line 18
[DEBUG] Weirdness on line 26
[DEBUG] Opening audio device
[DEBUG] Failed to open audio: No such device.
[DEBUG] Audio init failed
[DEBUG] Opening audio device (null)
[DEBUG] sampleRate = 192000 buffer = 15360
[DEBUG] Running audio thread (deviceId = 2) 15360
In a few seconds, both builds crashed.
Interestingly, your w32 build also complains about my audio device on the first run, but instead of crashing it finds and enumerates its options properly.
The text was updated successfully, but these errors were encountered:
Kaens
changed the title
"Weirdness" when running my w64 build
"Weirdness" when running my builds
Jun 30, 2022
The "weirdness" refers to the GUI definition file that it has a syntax error (IIRC it has comments or empty lines or so) - completely harmless. Not sure if the 192 kHz sampling rate might be a factor in the crash?
Well, your build definitely works with the same mixer settings! Might not be that.
A glitch somewhere in MinGW libs? I recently built HivelyTracker on it though, works like a charm...
Oh yeah, this is what my sound stuff is like...
I've built this on msys2 mingw64 targeting x86_64 (and then mingw32 and i686), and ran it on Windows 10.
The main window appeared, said it couldn't find an audio device; at the same time, there appeared a console window on the background saying this:
In a few seconds, both builds crashed.
Interestingly, your w32 build also complains about my audio device on the first run, but instead of crashing it finds and enumerates its options properly.
The text was updated successfully, but these errors were encountered: