Closed roman380 closed 5 years ago
For the reference: I checked that use of Virtual Audio Cable and VB-Audio VoiceMeeter applications are in general compatible with Rainway, provided that configuration is correct in first place. That is, Rainway can capture audio from virtual audio endpoints just like from physically existing ones.
The original problem in first place comes from user with VB-Audio setup where, though, the problem is not yet identified or resolved. This is still supposed to be a configuration problem rather than Rainway incompatibility with certain virtual audio application.
The problem was eventually resolved by reporting user via re-install of both VB-Audio and Rainway.
I could once reproduce a close (but not exactly this) issue when Rainway was set to use wrong audio device, which was at the same time exclusively used by third party software.
All in all, it sounds like a misconfiguration issue.
Streaming shows black screen on remote device but can be fixed by disabling audio
The problem existed in many versions (not something recent). In some cases the screen is not black but shows one or a few frames of video which then freeze.
Steps
The problem might com up as a result of misconfiguration of sorts, including Rainway and other software. Presumably a typical cause is that audio device is already in use by [another] application in exclusive form, and system does not allow Rainway to capture audio output for streaming purposes.
This is an example of how the problem can be reproduced.
A virtual audio cabling application VB-Audio VoiceMeeter can be set up to process output of certain audio device X. In turn it creates a virtual audio output device "VoiceMeeter Input" that takes audio from apps (then VoiceMeeter forwards streams to device X internally).
If Rainway configuration is to use audio device X for remoting purposes, streaming would fail as described because VoiceMeeter acquired exclusive access over this device.
Same time, going to settings.json and setting DisableAudio to true fixes streaming for video because audio leg no longer issues a fatal failure.
What happens
Remote client device shows black (or frozen at initial frames) feed.
What is expected
Proper streaming when possible.
In case of audio failure it is expected that application reports the cause to help troubleshooting.
Other
Audio device issues a failure with misleading
AUDCLNT_E_UNSUPPORTED_FORMAT
error code internally.Rainway fails to deliver meaningful description for the problem, even reference to problem doing audio part of the streaming.