Status
Not open for further replies.

Xaymar

Active Member
@Excel-081 If you haven't gone through the Troubleshooting Guide (linked in the original post), go through it now. The encoder initialition is failing, likely due to other settings (Color format, range, resolution, framerate, ...).
 

Excel-081

New Member
@Xaymar but my setting is fine before i updated my AMD driver to Adrenalin. My previous version that i use for recording are Crimson Relive 17.7.2, OBS 19.0.3 , AMF 2.1.6. It works fine with that setting
 

Xaymar

Active Member
@BetaAlphaDelta If you have a CPU that was made in the last 15 years, none. The option simply splits an already very simple workload into multiple threads, resulting in higher latency and higher CPU usage, but across multiple cores if that option is enabled. There are no CPUs that can't handle the single-core load that the plugin has (which is barely 1% of an i5-4690).
 
@Xaymar its been a long time since i posted here but i'm now using your latest version of the amf encoder and i get this in a log, obs no longer crashes but i cant see an option for the amf encoder even when set to use my dedicated gpu and not my integrated graphics. Im guessing i cant use the amf encoder because of a amf error
 

Attachments

  • 2018-05-05 16-23-03.txt
    14.5 KB · Views: 102

Xaymar

Active Member
@Nicholas Josey-T.D.B [YT] Unfortunately a crash at that stage means that there's really been a critical error which would otherwise cause OBS to crash. Usually these are driver crashes, so you should report these directly to AMD after verifying that the following is true:
  • You are running the latest Windows 10 Version (run Windows Update, let it update, and reboot - repeat until no more updates are available).
  • You are running a clean install of the latest Stable or Optional Game Ready Driver, which is currently 18.2.1 for your GPU, alternative if you like experimenting you could also try the 18.4.1 optional driver. Remember that you need to run Display Driver Uninstaller first, otherwise you will likely end up with an unclean install - especially if your previous driver install was already unclean.
  • Test with an older version of the plugin. While this likely won't fix the crash, it will produce a crash log that shows what went wrong at the time.
 

Sacarto

New Member
hi @Xaymar

I was reading the publications about the loss and the bitrate peaks (the last thing I found was from 2017) because have a similar problem.
I am trying to streming a game (dayz) but the problem is the foliage since it looks very pixelated when it is moving (with the qpmax = 51 it is awful).
My settings with rx 480 + radeon 18.6.1 + obs 21.1.2:


Quality preset = balanced
Profile = main
Profile lvl = 4.2
rate control method = CBR
Target bitrate = 6000
QPmin = 18
QPmax = 38
Filler data = enable
Frame skipping = disable
Vbv buffer(manual) =6000
keyframe interval = 2,00
Video api = direct3d 11
Opencl transfer =disable
Opencl conversion =disable
view mode advanced


With this configuration I have peaks of 7k and sometimes 8k but it is acceptable for me, I can stream, the problem is in the quality.
I was trying all kinds of configurations but when I get off qpmax = 36-37 the bitrate goes crazy with peaks of up to 20k
Did you manage to find some stable and good quality configuration like qpmin = 18 and (qpmax = 36 or less)?
 

Attachments

  • 2018-06-27 23-50-36.txt
    11 KB · Views: 76

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

2.4.1 - Stability Improvements

A new version, but it's merely a few stability improvements. A crash on missing D3D11 or D3D9 has been fixed, capability testing always writes supported GPUs to the log file and the H264 and H265 encoder now follow the specification of the codec and set Profile, Level and Tier before Resolution and Frame Rate - which might actually improve support for higher resolution and frame rate capture.

Hotfix 1: Additional stability improvements by fixing a crash with a very old driver...

Read the rest of this update entry...
 

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

2.4.2 - Stability Improvements (Hotfix 2)

A new version, but it's merely a few stability improvements. A crash on missing D3D11 or D3D9 has been fixed, capability testing always writes supported GPUs to the log file and the H264 and H265 encoder now follow the specification of the codec and set Profile, Level and Tier before Resolution and Frame Rate - which might actually improve support for higher resolution and frame rate capture.

Hotfix 1: Additional stability improvements by fixing a crash with a very old driver.
Hotfix 2: Fix...

Read the rest of this update entry...
 

TofuCrushKing

New Member
Hello everybody,
I'm totally new to this whole streaming thing and while testing out different things I stumbled upon this plugin.
Now I'm aware that OBS has already an option to use AMD VCE as an encoding option,
so is there any advantage of installing this plugin?
Or is it for users using older versions or OBS classic etc. ?
 

Suslik V

Active Member
@TofuCrushKing This is the the plugin that shipped with the OBS Studio. Plugin can be updated more frequently than OBS Studio itself (until now you need to update it manually if you what to have most recent version).
 

peachpit

New Member
How do I uninstall this plugin?

I was told I need to choose the right dll files to remove, so if that's really the only way to do it a list of dll files would help too.

thanks
 

peachpit

New Member
I'm guessing part of it is the enc-amf.dll & enc-amf.pdb files in my obs-plugins\32bit folder, but what about the 64bit folder?

Does it install anywhere else on my system?

Thanks
 

Xaymar

Active Member
If you installed the plugin through the installer, then just using the uninstaller will work fine. For a full list of files created by the plugin and the relative path, take a look at the .zip file.
 

SO7iD

New Member
OBS is now crashing immediately after I hit the stream button. This started happening after I installed LG monitor drivers and the LG "OnScreen Control" software. I have since uninstalled the LG drivers and software, reinstalled OBS, installed the newest version of OBS while deleting old settings, reinstalled drivers with DDL, installed newest drivers with DDL. Still nothing. Please help!
 

Attachments

  • Crash 2018-08-18 21-35-50.txt
    99.3 KB · Views: 43
  • 2018-08-18 21-35-45.txt
    5.4 KB · Views: 42
Status
Not open for further replies.
Top