obsproject / obs-studio

OBS Studio - Free and open source software for live streaming and screen recording
https://obsproject.com
GNU General Public License v2.0
59.38k stars 7.88k forks source link

OBS Recording or Streaming not possible, failed to start the output #10040

Closed DerScherenmann closed 9 months ago

DerScherenmann commented 9 months ago

Operating System Info

Other

Other OS

Arch Linux

OS: Arch Linux x86_64 Host: MS-7C37 3.0 Kernel: 6.6.7-arch1-1 DE: Plasma 5.27.10 WM: KWin CPU: AMD Ryzen 7 3800X (16) @ 3.900GHz GPU: NVIDIA GeForce RTX 2070 SUPER Memory: 48124MiB

OBS Studio Version

30.0.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/7eSZODfiEAaNNKFt

OBS Studio Crash Log URL

No response

Expected Behavior

Recording gets started and will be saved to a file. Additionally the NVIDIA encoder can be selected in the settings menu.

Current Behavior

In the settings menu under settings -> output -> video encoder, only the Software encoder can be selected. When clicking "Start Recording" in the main window a popup opens which is informing the user that the output cannot be opened. In the first time configuration wizard a message is displayed, that the encoder couldn't be used.

Error Message:

24122023_164329

Encoder Options:

24122023_164413

Steps to Reproduce

  1. Install OBS from the Arch Linux repositories (sudo pacman -S obs-studio)
  2. Start obs
  3. Click "Start Recording"

Anything else we should know?

The following log lines are probably what is causing this issue, note the two forward slashes in the path!

error: os_dlopen(/usr//lib/obs-plugins/obs-ffmpeg.so->/usr//lib/obs-plugins/obs-ffmpeg.so): libSPIRV.so.13: cannot open shared object file: No such file or directory

error: os_dlopen(/usr//lib/obs-plugins/obs-ffmpeg.so->/usr//lib/obs-plugins/obs-ffmpeg.so): libSPIRV.so.13: cannot open shared object file: No such file or directory

warning: Module '/usr//lib/obs-plugins/obs-ffmpeg.so' not loaded
derrod commented 9 months ago

This is a support issue, not a bug. Seems like the package in question is incomplete or broken, but that's not ours.