Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Guide: Supporting Users

Michael Fabian Dirks edited this page Mar 6, 2017 · 1 revision

The first step to supporting other people is knowing what is actually wrong. Once you know that, the next step is figuring out the details necessary to fix the problem. So let's get you started on how to support people using this encoder. This guide is separated into individual steps and tasks to complete that step.

The Log File

Your top most priority is to always have a log file in which the encoder was used. In extreme cases (driver crashes, encoder crashes, etc) you should request one where the 'Debug' checkbox is checked and OBS was started with the parameters '--verbose --log_unfiltered'.

Understanding the log file

The log output of the plugin is pretty simple to read, but if for some reason you are having trouble, this guide is for you.

The Basics

How to tell apart Plugin output from OBS output?

It's actually pretty simple, here let me show you an example:

02:59:19.147: 	fps:               60/1
02:59:19.147: 	format:            NV12
02:59:19.149: ---------------------------------
02:59:19.152: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded
02:59:19.154: Required module function 'obs_module_load' in module '../../obs-plugins/64bit/d3dcompiler_46.dll' not found, loading of module failed
02:59:19.156: [AMF Encoder] Version 1.3.0-1.3.0.5
02:59:19.156: [AMF Encoder] <Plugin::AMD::AMF::AMF> Initializing...
02:59:19.158: [AMF Encoder] <Plugin::AMD::AMF::AMF> Loaded 'amfrt64.dll'.

As you can see the Plugins output is tagged with [AMF Encoder].