Question / Help Log Files Show Many Windows DLLs and Plugins Not Loading Or Found

[SumDim]

Too many bugs guys. I pulled up my current log file today after a OBS Studio 19.0.2 install and noticed these:

Required module function 'obs_module_load' in module '../../obs-plugins/64bit/chrome_elf.dll' not found, loading of module failed
Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libcef.dll' not found, loading of module failed
Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libEGL.dll' not found, loading of module failed
Required module function 'obs_module_load' in module '../../obs-plugins/64bit/libGLESv2.dll' not found, loading of module failed

But all of these exist in my 64 bit plugins directory. These seem to be run time errors. Either in finding the module with the wrong path or the function call itself is failing with error.

I also get this error message but I know that VLC is installed.
Couldn't find VLC installation, VLC video source disabled

All these modules are reported being loaded:
17:12:21.959: Loaded Modules:
17:12:21.959: win-wasapi.dll
17:12:21.959: win-mf.dll
17:12:21.959: win-dshow.dll
17:12:21.959: win-decklink.dll
17:12:21.959: win-capture.dll
17:12:21.959: vlc-video.dll
17:12:21.959: text-freetype2.dll
17:12:21.959: rtmp-services.dll
17:12:21.959: obs-x264.dll
17:12:21.959: obs-vst.dll
17:12:21.959: obs-transitions.dll
17:12:21.959: obs-text.dll
17:12:21.959: obs-qsv11.dll
17:12:21.959: obs-outputs.dll
17:12:21.959: obs-filters.dll
17:12:21.959: obs-ffmpeg.dll
17:12:21.959: obs-browser.dll
17:12:21.959: image-source.dll
17:12:21.959: frontend-tools.dll
17:12:21.959: enc-amf.dll
17:12:21.959: coreaudio-encoder.dll

I also got these errors showing up in the log file but the coreaudio-encoder.dll file exists in my 64 bit plugins directory.
17:34:37.542: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded

This DLL doesn't even exist in my installation:
17:34:37.543: [AMF] Encountered Exception during AMF initialization: Unable to load 'amfrt64.dll', error code 126.

17:34:37.543: Failed to initialize module 'enc-amf.dll'
This dll exists in my plugin directory.


17:34:37.550: Failed to load 'en-US' text for module: 'obs-browser.dll'
No idea what could be causing this. Perhaps a dll calling another dll problem.


This is on a new installation of OBS Studio 19.0.2. I installed it in C:\ObsStudio, not the default location. I also uninstalled and chose the default location and still come up with the same loading errors. I did that to test out the cases where it may have been hard coded DLL paths the program was looking for but this is not the case. There are some serious problems here that need to get fixed. All this functionality is not being used.

I happen to be a former lead s/w and q/a engineer so if you need additional assistance let me know. But as far as I am concerned, these are bugs wearing both of my technical hats.

 

[Fenrir]

None of these are bugs, they are expected.

The obs_module_load messages are because those files are not plugins, but components of the browser source.

VLC source needs to make the same bitness. You probably have 32bit VLC installed, not 64bit.

CoreAudio AAC encoder is preferred over pretty much any other encoder, but it's not included by default because it's a proprietary Apple codec. See the resources section for a guide on how to install it without the entire iTunes suite.

The amfrt64.dll not found and the following message are standard messages when the AMD AMF encoder is not found. You don't have an AMD GPU, this is also expected.

The browser source one is actually a bug, but it has no real impact on anything.

 

[Osiris]

The browser source one isn't a bug either, there is just no localization.

 

[SumDim]

So what you are saying is that "Modules failing to load" are heuristic messages at OBS load time and not error messages even though they read like it. That there is a context around it as part of a discovery process in finding if a DLL that provides certain functionality exists or not before it is loaded.

What threw me, is that these messages say "Required" and "Failed" - pretty strong output messages. They leave the impression that they are needed for program execution and one should not continue running the program until they are fixed.

I think it would be a good idea to add more to this thread of these kinds of "problems" which aren't "problems" This for users who may look into the log files and try to solve the perceived problems themselves. It will save people a whole lot of time and frustration.

I've changed the title to be a catch all.

 

[Fenrir]

99% of users will never look at a log file. They're mostly there for us to help users with any support requests, both on the forums and in the support chat. It's informational only, and is unlikely to be changed.

OBS is open source, and if you go look at the code you'd understand what those messages actually mean.