Very poor quality at 1900kbit/s. "Flickering" about obs-amd-encoder HOT 14 CLOSED

set number of b-pictures to 0 not -1

also try idr frames 120 and gop size to the number of your recording fps.

from obs-amd-encoder.

Setting Number of B-Pictures to 0 helped, thanks!
GOP Size is set to my recording FPS and IDR Frames are set to 60 since Twitch wants you to have a 2 second keyframe interval. Or am I wrong here?

from obs-amd-encoder.

This is mine for twitch. - still testing and helping out xaymar

http://prntscr.com/c3osru

from obs-amd-encoder.

Hi all,

I'm using Xaymar's OBS AMD Media Framework for a couple of days now.
First let me thank Xaymar for his work!

My setup has an AMD Athlon 860K and an MSI R7 370 2GB Gaming OC.
The settings I use for OBS (0.15.4) is a mixture of Xaymar's tested
configuration and the suggested configuration from the OBS VCE fork, mostly
for the values of QP (https://community.amd.com/thread/198392 and
https://obsproject.com/forum/threads/obs-branch-with-amd-vce-support.13996/
).

For streaming my games at Twitch I downscale from 1080p 60FPS (VSync
enabled) to 480p 30FPS using CBR and the configuration is:

http://prntscr.com/c3x5yn
http://prntscr.com/c3x6ff

Note: I have a 2Mbits upload line.

Last night's streaming result (skip to 00:27:00 to have sound :/ I had it
muted by mistake): https://www.twitch.tv/nobodyhells/v/82679089

I have a configuration for 720p 30FPS mostly for streaming programming
related content which I haven't tested much...
The difference is only in target bitrate from 1600 Kbps to 1700 Kbps, which
I know is not enough for 720p streaming, but I just want clearer image.

When I had the default -1 value for QP variables the output was really bad
during movement: https://www.twitch.tv/nobodyhells/v/82424814

​Best Regards,​

Christos

Christos Kannas

On 9 August 2016 at 23:43, wazerstar [email protected] wrote:

This is mine for twitch. - still testing and helping out xaymar

http://prntscr.com/c3osru

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#25 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADj_St4lC0a6S0wnYCfk5853e0M20xUpks5qeOZ2gaJpZM4JgNUZ
.

from obs-amd-encoder.

@razorlikes What you're experiencing is known as the broken IDR problem - IDR-Frames just overwrite the I-Frame and you don't get any I-Frames for some reason. Also the Keyframe distance is further down and called IDR-Period, which is set in Frames. GOP Size is meant to further restrict or widen the bitrate range over a specific amount of frames.

@CKannas You have the same issue as many others, set Number of B-Pictures to 0 and Reference to B-Frame to Disabled.

from obs-amd-encoder.

I also had to set my B-Pictures to 0 to get the blocking/flickering to go away.

@Xaymar Does this IDR period refer to how many I-Frames there have been since the last IDR or just how many frames in general?
It shouldn't be an issue to have every I-Frame to be an IDR frame.

from obs-amd-encoder.

IDR frames are keyframes. If you find it useful to store an entire keyframes for each i frame to ahead, but don't blame the plugin for quality :p

from obs-amd-encoder.

IDR frames shouldn't be any bigger than a regular I-frame, they just prevent P and B frames from referencing before the IDR frame which would make a larger file size.

My first question remains about IDR period. Say I'm recording at 45FPS with 60GOP and a 30 IDR period. Which is correct?

1. IDR frames are every 1800 frames because I-Frames come at the beginning of GOP and every 30 I-Frames is a IDR (60/45*30 sec or every 45 seconds)
2. IDR frames every 30 frames (or every .66 sec)

from obs-amd-encoder.

@inkahootz
If you're recording at 45 fps with 60 GOP and a 30 IDR Period, you get a IDR frame every 30 frames. So 2 would be correct here.
If you have any further questions about how AMF works, please direct them at AMD and their developer forum.

from obs-amd-encoder.

RX 4xx sets the B-Frames to 0 by default and refuses to change this setting, so we're most likely looking at something that AMD is now aware of. Let us hope that Media SDK 1.2 (or whatever it is going to be called) will fix these issues.

Edit: 1.2.0pre4 does a lot for the quality at lower bitrates, see these example files:

R9 285: http://cdn.xaymar.com/private/2016/08/2016-08-12%2016-24-31.mkv
RX 480: http://cdn.xaymar.com/private/2016/08/2016-08-13%2015-52-05.mkv

Please remember that you can't expect the same quality from a hardware encoder that you get from a software encoder at a certain bitrate.

from obs-amd-encoder.

1.2.0rc1 should mostly fix this. Please report back if you have any issues.

from obs-amd-encoder.

Everything works awesome on Quality: Speed.
http://imgur.com/uYPUffr.png

When I set to None, Balanced, or Quality then I get what looks like some light random static all over the image. I'm happy with it though.

from obs-amd-encoder.

Try disabling the Deblocking Filter, that seemed to cause some issues for some tests on my end.

from obs-amd-encoder.

This issue, similar to many others, will most likely be fixed by the new SDK. I'm closing this as there is no further work being done on the Media SDK version.

from obs-amd-encoder.