"Device open failed" error message [Windows 10 Pro 64bit]

Report issues and bugs here.
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

"Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Sun Sep 06, 2020 5:35 pm

Hello,

Following the recommendations kindly provided there, I get a "Device open failed" error message on Windows 10 Pro 64bit - sometimes. After dismissing the message, the game starts, but sometimes it does not. The log tells me:

Code: Select all

Audio: Initializing OpenAL device
Error: Device open failed
And indeed, there was sound only on the first start of the game (clicking sound when going through the menus), but no sound later on.

I unzipped game_files.zip under C:\Programs\RVGL\
On top, I extracted everything from rvgl_20.0905a_win64.7z also under C:\Programs\RVGL\, overwriting everything when asked.

Was that maybe a misunderstanding from my side? Any hints what I can do?
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Sun Sep 06, 2020 6:20 pm

Code: Select all

> .\openal-info64.exe
Available playback devices:
    Generic Software on VE228 (Intel(R) Display-Audio)
Available capture devices:
    !!! none !!!
Default playback device: Generic Software on VE228 (Intel(R) Display-Audio)
Default capture device:
ALC version: 4207180.0

** Info for device "Generic Software on VE228 (Intel(R) Display-Audio)" **
ALC version: 1.1
ALC extensions:
    ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE, ALC_EXT_EFX
HRTF extension not available
OpenAL vendor string: Creative Labs Inc.
OpenAL renderer string: Software
OpenAL version string: 1.1
OpenAL extensions:
    EAX, EAX2.0, EAX3.0, EAX4.0, EAX5.0, EAX3.0EMULATED, EAX4.0EMULATED,
    AL_EXT_OFFSET, AL_EXT_LINEAR_DISTANCE, AL_EXT_EXPONENT_DISTANCE
Resampler info not available
EFX version: 1.0
Max auxiliary sends: 1
Supported filters:
    !!! none !!!
Supported effects:
    !!! none !!!
Anything bad about this?
User avatar
Huki
Developer
Posts: 345
Joined: Wed Dec 06, 2017 5:54 am
Discord: Huki#1668

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by Huki » Sun Sep 06, 2020 7:19 pm

There is something wrong with audio driver initialization, but I can't pinpoint what.

Where did you get the openal-info64.exe?

Code: Select all

OpenAL vendor string: Creative Labs Inc.
OpenAL renderer string: Software
OpenAL version string: 1.1
This looks wrong - RVGL is not supposed to use the Creative Labs OpenAL. We use the modern community implementation called OpenAL Soft. This is bundled with the game (the OpenAL32.dll), so anything else you see is wrong. Here is a sample openal-info output from my Linux system:

Code: Select all

]$ openal-info
Available playback devices:
    Built-in Audio Analog Stereo
Available capture devices:
    Monitor of Built-in Audio Analog Stereo
Default playback device: Built-in Audio Analog Stereo
Default capture device: Monitor of Built-in Audio Analog Stereo
ALC version: 1.1

** Info for device "Built-in Audio Analog Stereo" **
ALC version: 1.1
ALC extensions:
    ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
    ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
    ALC_EXT_thread_local_context, ALC_SOFT_device_clock, ALC_SOFT_HRTF,
    ALC_SOFT_loopback, ALC_SOFT_output_limiter, ALC_SOFT_pause_device
Available HRTFs:
    Default HRTF
    Built-In HRTF
OpenAL vendor string: OpenAL Community
OpenAL renderer string: OpenAL Soft
OpenAL version string: 1.1 ALSOFT 1.20.1
OpenAL extensions:
    AL_EXT_ALAW, AL_EXT_BFORMAT, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE,
    AL_EXT_FLOAT32, AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS,
    AL_EXT_MULAW, AL_EXT_MULAW_BFORMAT, AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET,
    AL_EXT_source_distance_model, AL_EXT_SOURCE_RADIUS, AL_EXT_STEREO_ANGLES,
    AL_LOKI_quadriphonic, AL_SOFT_bformat_ex, AL_SOFT_block_alignment,
    AL_SOFT_deferred_updates, AL_SOFT_direct_channels,
    AL_SOFT_direct_channels_remix, AL_SOFTX_effect_chain, AL_SOFTX_events,
    AL_SOFTX_filter_gain_ex, AL_SOFT_gain_clamp_ex, AL_SOFT_loop_points,
    AL_SOFTX_map_buffer, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
    AL_SOFT_source_length, AL_SOFT_source_resampler, AL_SOFT_source_spatialize
Available resamplers:
    Nearest
    Linear *
    Cubic
    11th order Sinc (fast)
    11th order Sinc
    23rd order Sinc (fast)
    23rd order Sinc
EFX version: 1.0
Max auxiliary sends: 2
Supported filters:
    Low-pass, High-pass, Band-pass
Supported effects:
    EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Frequency Shifter,
    Vocal Morpher, Pitch Shifter, Ring Modulator, Autowah, Compressor,
    Equalizer, Dedicated Dialog, Dedicated LFE
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Sun Sep 06, 2020 7:25 pm

Blimey, I had installed OpenAL from there before:
https://openal.org/downloads/oalinst.zip
Meanwhile I deinstalled it and rebooted, but maybe there is a leftover? I will have to check.

I got the openal-info64.exe from there:
https://openal-soft.org =>
https://openal-soft.org/openal-binaries ... .1-bin.zip

So do I not have to install OpenAL Windows-wide, as it ships with RVGL, so I should not further mess with it?

Well, after the first start, there is sound and no error. But on 2nd start, the error pops up, no sound (despite deinstallation of https://openal.org/downloads/oalinst.zip and reboot). Hmm...
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Sun Sep 06, 2020 7:36 pm

The dll is 32bit (OpenAL32.dll), whereas I use the 64bit version of RVGL. Is that maybe a problem?
EDIT: Oh, I see that it is in fact 64bit, sorry.
Last edited by 7wells on Sun Sep 06, 2020 7:46 pm, edited 2 times in total.
User avatar
Huki
Developer
Posts: 345
Joined: Wed Dec 06, 2017 5:54 am
Discord: Huki#1668

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by Huki » Sun Sep 06, 2020 7:44 pm

7wells wrote:
Sun Sep 06, 2020 7:25 pm
So do I not have to install OpenAL Windows-wide, as it ships with RVGL, so I should not further mess with it?
That's right, everything necessary ships with RVGL.
The dll is 32bit (OpenAL32.dll), whereas I use the 64bit version of RVGL. Is that maybe a problem?
The filename is always OpenAL32.dll, even when it's 64-bit. Some library names are like this for historical reasons (just look at "System32" ;)).

Try this: run the alsoft_log.bat script in the game folder and it should generate profiles\alsoft.log. Can you post that file?
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Sun Sep 06, 2020 7:47 pm

Yeah, I figured it out - see EDIT above. ;)
I copied openal-info64.exe to RVGL and executed it there (via Windows Powershell):

Code: Select all

PS C:\Program Files\RVGL> .\openal-info64.exe
Available playback devices:
    OpenAL Soft on VE228 (Intel(R) Display-Audio)
Available capture devices:
    !!! none !!!
Default playback device: OpenAL Soft on VE228 (Intel(R) Display-Audio)
Default capture device:
ALC version: 1.1

** Info for device "OpenAL Soft on VE228 (Intel(R) Display-Audio)" **
ALC version: 1.1
ALC extensions:
    ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
    ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
    ALC_EXT_thread_local_context, ALC_SOFT_device_clock, ALC_SOFT_HRTF,
    ALC_SOFT_loopback, ALC_SOFT_output_limiter, ALC_SOFT_pause_device
Available HRTFs:
    Built-In HRTF
OpenAL vendor string: OpenAL Community
OpenAL renderer string: OpenAL Soft
OpenAL version string: 1.1 ALSOFT 1.20.1
OpenAL extensions:
    AL_EXT_ALAW, AL_EXT_BFORMAT, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE,
    AL_EXT_FLOAT32, AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS,
    AL_EXT_MULAW, AL_EXT_MULAW_BFORMAT, AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET,
    AL_EXT_source_distance_model, AL_EXT_SOURCE_RADIUS, AL_EXT_STEREO_ANGLES,
    AL_LOKI_quadriphonic, AL_SOFT_bformat_ex, AL_SOFT_block_alignment,
    AL_SOFT_deferred_updates, AL_SOFT_direct_channels,
    AL_SOFT_direct_channels_remix, AL_SOFTX_effect_chain, AL_SOFTX_events,
    AL_SOFTX_filter_gain_ex, AL_SOFT_gain_clamp_ex, AL_SOFT_loop_points,
    AL_SOFTX_map_buffer, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
    AL_SOFT_source_length, AL_SOFT_source_resampler, AL_SOFT_source_spatialize
Available resamplers:
    Nearest
    Linear *
    Cubic
    11th order Sinc (fast)
    11th order Sinc
    23rd order Sinc (fast)
    23rd order Sinc
EFX version: 1.0
Max auxiliary sends: 2
Supported filters:
    Low-pass, High-pass, Band-pass
Supported effects:
    EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Frequency Shifter,
    Vocal Morpher, Pitch Shifter, Ring Modulator, Autowah, Compressor,
    Equalizer, Dedicated Dialog, Dedicated LFE
That is almost identical to yours.
It still would not explain, why I get the error on 2nd (and further) start(s) without sound, though.
Log follows...
User avatar
Huki
Developer
Posts: 345
Joined: Wed Dec 06, 2017 5:54 am
Discord: Huki#1668

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by Huki » Sun Sep 06, 2020 7:49 pm

Since you mentioned it works fine the first time and fails the second time onwards: I wonder whether the RVGL process isn't exiting properly? Did you check for stray rvgl.exe processes in Task Manager?
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Sun Sep 06, 2020 8:26 pm

Good idea! I have checked that, though, and the task manager does not show any rvgl.exe still running. Here is the alsoft.log:

Code: Select all

AL lib: (II) Initializing library v1.20.1-f5e0eef3 master
AL lib: (II) Supported backends: wasapi, dsound, winmm, null, wave
AL lib: (II) Loading config C:\Users\master\AppData\Roaming\alsoft.ini...
AL lib: (II) Got binary: C:\Program Files\RVGL, rvgl.exe
AL lib: (II) Loading config C:\Program Files\RVGL\alsoft.ini...
AL lib: (II) Key disable-cpu-exts not found
AL lib: (II) Detected max CPUID function: 0x18 (ext. 0x80000008)
AL lib: (II) Vendor ID: ""
AL lib: (II) Name: "Intel(R) Pentium(R) Silver J5005 CPU @ 1.50GHz"
AL lib: (II) Extensions: +SSE +SSE2 +SSE3 +SSE4.1
AL lib: (II) Key rt-prio not found
AL lib: (II) Key resampler not found
AL lib: (II) Key trap-al-error not found
AL lib: (II) Key trap-alc-error not found
AL lib: (II) Key reverb/boost not found
AL lib: (II) Key drivers not found
AL lib: (II) Starting message thread
AL lib: (II) Message thread initialization complete
AL lib: (II) Starting message loop
AL lib: (II) Initialized backend "wasapi"
AL lib: (II) Added "wasapi" for playback
AL lib: (II) Added "wasapi" for capture
AL lib: (II) Key excludefx not found
AL lib: (II) Key default-reverb not found
AL lib: (II) Got message "Open Device" (0x0000, this=000000000748b5c8)
AL lib: (II) Got message "Close Device" (0x0004, this=000000000748b5c8)
AL lib: (WW) Failed to open playback device: Device init failed: 0x80070490
AL lib: (WW) Error generated on device 0000000000000000, code 0xa004
AL lib: (II) Freeing device 00000000073cdfb0
Hmm, several "not found" messages and a "Failed to open playback device: ..." message. I do not know what to make of this and will look further tomorrow.

Thank you so much for bearing with me and your kind help. I truly appreciate it! :thumbsup:
7wells
Posts: 78
Joined: Tue Aug 25, 2020 5:18 pm

Re: "Device open failed" error message [Windows 10 Pro 64bit]

Unread post by 7wells » Mon Sep 07, 2020 12:01 pm

Hi Huki,

I have a suspicion:

The PC where I have the difficulties with the audio device is a Gigabyte "mini PC", i.e. it has no own loudspeakers. The only way to hear something is either via line out or via HDMI. I have a monitor (with speakers) connected via HDMI cable and also went through the "problem solving" steps of Win 10; however, without success.

Now on a laptop (which has speakers), there is no problem with the audio device; hence I believe that it has to do with the "special" hardware of the "mini PC". Do you have some hints for me if/how I can further drill down to either verify or falsify my suspicion? Thank you so much!
Post Reply