Status
Not open for further replies.

Suslik V

Active Member
Hope this fix will not broke the encoding. VBV itself is so hard to understanding (for me).

For the translation, I will use this part:
...Strictness here means how strictly it should follow the constraints given (Target Bitrate or Peak Bitrate, depending on situation).

Thank you for the help.
 

Xaymar

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

1.4.0.0 - Modern User Interface Update

The days of spending a lot of time setting up the encoder are gone, here are the days of simplicity! With this update both advanced interface are now one allowing for faster setup, easier control and better overall support. Some of the properties have also been simplified to be less overwhelming. The best of it all? You don't lose any control over any feature, you can still use all of them if you need to.

There are also a few property changes that come with this update:
You can now control how strict the VBV Buffer is when automatically calculated, Keyframe Interval supports sub-second precision now, CABAC is no longer considered experimental and GOP Size was removed (controlled by Keyframe Interval). Most of the properties also now have a tooltip that directly explains what it does, with certain ones even including recommended settings and supported values.

The internal encoder part has also been updated for better hardware support, better crash resistance, runtime version tracking and is now also following proper AMF code guidelines as requested by MikhailAMD. Logging has also been changed severely for the better and should allow for massively easier supporting down the line.

And with all that said, here is 1.4.0.0 in all it's new shiny glory.

Notes:

Due to the nature of changes in this update, your previous settings may end up lost or incorrect. Make sure to revalidate them before attempting to record or stream.

Changelog:

  • Changed: Unified both advanced interfaces into a single easy to use one without removing any features from it.
  • Changed: The simple advanced interface has been marked [DEPRECATED], it will be removed in a future version.
  • Changed: CABAC is no longer experimental, however there are some Driver issues with it right now.
  • Changed: Cards without B-Picture support default to using LTR Frames instead.
  • Changed: B-Picture properties are only shown to Cards supporting this feature.
  • Changed: B-Picture properties will be correctly hidden and set when LTR Frames are in use.
  • Added: All properties now have a hover-tooltip explaining their purpose and effect.
  • Added: Automatic VBV Buffer calculation using a strictness constraint with 100% is as strict as possible and 0% as loose as possible.
  • Added: Plugin will now print the actual runtime version to the log files.
  • Added: Ability to specify which DirectX 11 device to use.
  • Removed: GOP Size is no longer supported as Driver Version 16.10.1 and up ignore it completely.
  • Fixed: Crash with OpenCL when Device is no longer available.

Read the rest of this update entry...
 

Xaymar

Active Member
For users on Windows versions older than Windows 8, I'd like to hear if the plugin still works. I use some DXGI functionality for querying devices in multi-gpu systems, so I hope it still works on older versions.
 
Nice update, @Xaymar! Thanks again for your hard work.

Just to let you know, I'm going to be replacing my R9 290 in the near future. I'm currently looking at getting the Sapphire Nitro R9 Fury as a temporary solution until the non-reference RX 490 (or whatever it's going to be called, Vega 10) cards come out next year. I'll have a VCE 3.0 card to test with very soon.
 
Last edited:

R A F I D

New Member
amd new driver released today 16.11.1 and in Fixed issues this was mentioned
  • OBS screen capture may stutter after extended periods of use while capturing video and watching or streaming content in a web browser.
i just want to know if this fix has any impact on the performance like if it improved obs performance or not
 

Ascaron

New Member
OBS Studio version 0.16.3
Plugin version 1.3.3.1 worked well
Plugin version 1.4.0.0 crashed
 

Attachments

  • Crash 2016-11-04 07-40-00.txt
    44.9 KB · Views: 27

Xaymar

Active Member
Nice update, @Xaymar! Thanks again for your hard work.

Just to let you know, I'm going to be replacing my R9 290 in the near future. I'm currently looking at getting the Sapphire Nitro R9 Fury as a temporary solution until the non-reference RX 490 (or whatever it's going to be called, Vega 10) cards come out next year. I'll have a VCE 3.0 card to test with very soon.

Neat, Furys are one of the cards I really like because they have near-zero latency when it comes to VRAM-VCE interactions. :)

amd new driver released today 16.11.1 and in Fixed issues this was mentioned
  • OBS screen capture may stutter after extended periods of use while capturing video and watching or streaming content in a web browser.
i just want to know if this fix has any impact on the performance like if it improved obs performance or not

No idea, it could have and it could not. The driver apparently contains the fix for B-Pictures on VCE 2 and CBR on RX 4xx.

I feel sorry for you @Xaymar , you're about to have a lot of issue posts over at your Github!

And I've closed like 25% of them already! I work fast.


Seen it, though that error makes little sense to me. It should be missing dxgi or d3d11 instead of some internal driver stuff.

OBS Studio version 0.16.3
Plugin version 1.3.3.1 worked well
Plugin version 1.4.0.0 crashed

Already fixed in the next version.
 

Xaymar

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

1.4.1.0 - The Oversight Fix

Sometimes your changes seem fine and then users happen. Have you ever had users happen? They break things in ways that you didn't think was possible before! It's insane!

This update aims to fix some of the reported issues in addition to making the user interface even simpler to use.

Notes
Due to the nature of changes in this update, your previous settings may end up lost or incorrect. Make sure to revalidate them before attempting to record or stream.

Changelog
  • Fixed: Crash with default settings being used.
  • Fixed: Properties should now show the correct tooltip when hovered over.
  • Fixed: Frame Rate should now be applied properly again.
  • Fixed: Compatibility issues with Windows 7 and older.
  • Changed: Default value for LTR Frames is now 0 for better compatibility.
  • Changed: Profile is now a Basic property.
  • Changed: Profile Level is now an Expert property to avoid user errors.
  • Changed: Min/Max QP is now considered an Advanced property to avoid user errors.

Read the rest of this update entry...
 

Pinky

New Member
Sorry, doesnt crash, it stops recording immediately and throws an error complaining about missing files.
 

Xaymar

Active Member
Sorry, doesnt crash, it stops recording immediately and throws an error complaining about missing files.

Well, it's not the encoder that is having issues then. I can't provide support for anything but the encoder here, make a thread in Windows Support for OBS Studio instead.
 

Pinky

New Member
No worries. Cant understand why previous versions worked fine but obs is now saying I dont have avutil-55.dll, avformat-57.dll or avcodec-57.dll
 

Pinky

New Member
Well, it's not the encoder that is having issues then. I can't provide support for anything but the encoder here, make a thread in Windows Support for OBS Studio instead.

Xaymar after much fiddling it appears that obs is fine and this only occurs when 'use opencl' is set to 'enabled'.
 

Attachments

  • Capture.JPG
    Capture.JPG
    106.8 KB · Views: 38
Status
Not open for further replies.
Top