Compiled 32.1.2 on Windows does not show Connect Account for streaming services.

[wesmason4]

I am attempting to build OBS from source to use. My build environment is on Windows 10 Pro (22H2, 19045.6466) with 16gb ram, 120gb disk, 4 cores. It is a VM on my desktop PC with a Ryzen 9 5900X 12 core running Windows 11.

I followed instructions here as they seemed the most up to date. I targeted Release for x64.

Build Instructions For Windows

OBS Studio - Free and open source software for live streaming and screen recording - obsproject/obs-studio

github.com

I then also attempted to use Build-Windows.ps1:

pwsh .\Build-Windows.ps1 -Target x64 -Configuration Release

In both cases everything seemed to compile correctly and I got a working build. In both cases under stream I did not see Connect to Account buttons under any services like restream, youtube, or twitch. This lead me to links telling me I needed to enable compiling with obs-browser. Checking my results, I do have the plugin obs-browser, and I also have libcef.dll. So it does look like Chrome Embedded Framework did download with cmake and compile.

I also discovered the cmake option -DENABLE_BROWSER:BOOL=ON but that didn't seem to make any difference.

Am I missing something?

 

[wesmason4]

Ok, noticed the following in the cmake output:

                      _                   _             _ _
                 ___ | |__  ___       ___| |_ _   _  __| (_) ___
                / _ \| '_ \/ __|_____/ __| __| | | |/ _` | |/ _ \
               | (_) | |_) \__ \_____\__ \ |_| |_| | (_| | | (_) |
                \___/|_.__/|___/     |___/\__|\__,_|\__,_|_|\___/

OBS:  Application Version: 32.1.2-2-g085a51ab0 - Build Number: 1
==================================================================================


------------------------       Enabled Features           ------------------------
 - Browser panels
 - Direct3D 11 renderer
 - NVIDIA Audio FX support
 - NVIDIA Video FX support
 - OpenGL renderer
 - Plugin Support
 - RNNoise noise suppression
 - Scripting Support (Frontend)
 - Scripting support
 - SpeexDSP noise suppression
 - User Interface
 - What's New panel
------------------------       Disabled Features          ------------------------
 - Idian Playground
 - Restream API connection
 - Twitch API connection
 - YouTube API connection
------------------------        Enabled Modules           ------------------------
 - aja
 - aja-output-ui
 - coreaudio-encoder
 - decklink
 - decklink-captions
 - decklink-output-ui
 - frontend-tools
 - graphics-hook
 - image-source
 - libobs-d3d11
 - libobs-winrt
 - nv-filters
 - obs-browser
 - obs-ffmpeg
 - obs-filters
 - obs-nvenc
 - obs-outputs
 - obs-qsv11
 - obs-text
 - obs-transitions
 - obs-virtualcam-module
 - obs-vst
 - obs-webrtc
 - obs-websocket
 - obs-x264
 - obslua
 - obspython
 - rtmp-services
 - text-freetype2
 - vlc-video
 - win-capture
 - win-dshow
 - win-wasapi
------------------------        Disabled Modules          ------------------------
 - obs-libfdk
 - test-input
----------------------------------------------------------------------------------
-- Configuring done (60.3s)
-- Generating done (6.8s)
-- Build files have been written to: C:/Users/wmason/OBS/obs-studio/build_x64

Specifically:

------------------------       Disabled Features          ------------------------
 - Idian Playground
 - Restream API connection
 - Twitch API connection
 - YouTube API connection

Not seeing options to enable them yet...

 

[wesmason4]

Ok, looks like I need to make my own API keys for each service I want to enable and then add them via option during the initial cmake run something like:

cmake --preset windows-x64 \
  -DENABLE_BROWSER:BOOL=ON \
  -DRESTREAM_CLIENTID="XXX" \
  -DRESTREAM_HASH="XXX" \
  -DTWITCH_CLIENTID="XXX" \
  -DTWITCH_HASH="XXX" \
  -DYOUTUBE_CLIENTID_HASH="XXX" \
  -DYOUTUBE_SECRET_HASH="XXX"

I'm currently testing with RESTREAM. Initial issue I found was that restream handed me codes with '-'s in it and this does not want that. Twitch handed me codes that were not in HEX and it didn't like that either, but since that is out of my scope right now it will be tomorrow's problem.