Status
Not open for further replies.

DetonicsK

New Member
From what I can see it's due to too low bitrate. You can try experimenting with Constant QP (start with I-/P-/B-Frame QP at 41 and figure out how to get a bitrate that works. Until we get HEVC or Two Pass encoding, there is not much that can be done.
ok~ thanks
 
From what I can see it's due to too low bitrate. You can try experimenting with Constant QP (start with I-/P-/B-Frame QP at 41 and figure out how to get a bitrate that works. Until we get HEVC or Two Pass encoding, there is not much that can be done.


Try lowering Max QP, default is 51, I find 45 works best, Gets rid of some of the blockiness when moving. Try slightly lower if you can. If your bitrate goes skyhigh then your Max QP is too low move it back up a bit. Good Luck
 

vapeahoy

Member
I've just barely tested the latest version but I have to say, it works absolutely fantastic so far. I can only hope it continues to do so. Thank you so much!
 

ball2hi

Member
From what I can see it's due to too low bitrate. You can try experimenting with Constant QP (start with I-/P-/B-Frame QP at 41 and figure out how to get a bitrate that works. Until we get HEVC or Two Pass encoding, there is not much that can be done.
Is HEVC / Two Pass something that needs to be introduced by AMD, or by the OBS developers?
 

Xaymar

Active Member
Is HEVC / Two Pass something that needs to be introduced by AMD, or by the OBS developers?

or by the stream services (regarding the HEVC part).

It needs support by OBS (codec needs to be known), ffmpeg (which most likely already supports it) and streaming sites. I expect YouTube or HitBox to be the first ones to support this - in theory YouTube already can support HEVC streams.
 

Xaymar

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

1.3.0pre6 - The AMF SDK Path

  • Added: B-Picture settings for Simple Interface (only shown if supported).
  • Added: De-Blocking Filter setting for Simple Interface.
  • Added: Enforce HRD Compatibility setting for Simple Interface.
  • Changed: Language files have been massively simplified.
  • Changed: Timer Resolution is now half the expected frametime (1000 / framerate / 2) to reduce CPU usage and Power draw.
  • Updated: Languages en-US, vi-VN, ru-RU and es-ES.
  • Updated: Presets in Simpler Interface will now also set up advanced properties (if supported).
  • Fixed: Log messages from encoder will not come from an impossible source/class.
  • Fixed: 32-Bit now shows the correct Version number.

Read the rest of this update entry...
 
Last edited:

Xaymar

Active Member
I recommend using the Simple Interface now, as the advanced interface will slowly be replaced by it. In fact, the advanced interface may end up being completely rewritten in the future, because right now it's just ugly as hell - I'd be murdered by UX/UI Designers for this.
 

Xaymar

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

1.3.0pre7 - The AMF SDK Path

  • Fixed: Incorrect Packet order in Streams and Recordings.
  • Fixed: Crushed Colors in Streams and Recordings by forcing a specific set of color settings.
  • Fixed: High CPU usage due to increasing timer resolution too early.
  • Fixed: Slowness due to repeated Library loading, caused by lost references.
  • Fixed: Advanced Interface now applies properties in the same order as the Simple Interface.
  • Fixed: Crash in Simple Interface on Cards that don't support B-Pictures.
  • Updated: Languages en-US (American English), de-DE (German), Vi-VN (Vietnamese).

Read the rest of this update entry...
 
Last edited:

locodicegr

Member
I just reinstall OBS and Pre7,

tried recording bf1 beta real fast to see if it works..and finally is working!

all default / simple encoder...but the quality was a bit poor thats all.

thanks for the hard work.
 

ball2hi

Member
@Xaymar @Jim
I am currently having an issue using OBS Multi-platform, and this encoder after remuxing.

I save my local recordings at FLV, and then use OBS Multi-platform to remux them into mp4 for easier video editting. However for some reason now, my videos after remuxing have no thumbnail unlike before.
Missing-Thumbnail-OBS-Remux.jpg
 

Xaymar

Active Member
Thanks for releasing another update so quickly. 1.3.0pre6 wasn't working for me. 1.3.0pre5 and 1.3.0pre7 work great.

I'm using an AMD R9 290 with the Crimson 16.8.3 Hotfix drivers on Windows 10 Pro. I'm using OBS Studio for streaming on Twitch.

Neat! I wanted to see more people streaming with AMD hardware so spread the word - it would make my day if a large streamer starts using this plugin.

I just reinstall OBS and Pre7,

tried recording bf1 beta real fast to see if it works..and finally is working!

all default / simple encoder...but the quality was a bit poor thats all.

thanks for the hard work.

HEVC will fix it! (TM)

@Xaymar @Jim
I am currently having an issue using OBS Multi-platform, and this encoder after remuxing.

I save my local recordings at FLV, and then use OBS Multi-platform to remux them into mp4 for easier video editting. However for some reason now, my videos after remuxing have no thumbnail unlike before.
View attachment 18890

No idea why this happens. Try recording using mkv instead of flv, and use ffmpeg to remux. I can tell you that the issue is not the encoder but how OBS saves the streams.
 
Last edited:

ball2hi

Member
Make sure you are remuxing the h264 stream as annexb. ffmpeg has no issues with this, so consider using ffmpeg instead of avidemux. Also mkv > mp4 > flv.
I'm using the built in remux feature from OBS Multiplatform. Also, I am not going to go through the hell of ffmpeg when Avidemux has a simple user interface that is easy to use/understand. I only really use it to split clips by the way.

Also, I save my files as FLV because MP4 become corrupt if the video ends abruptly like from a crash or bluescreen.
 

leporel

New Member
I record three videos with similar settings via OBS+VCE, OBS Studio+MF and OBS Studio+AMF
And compare media info, i notice second video(AMD AMF) does not contain string "Format settings, GOP: M=1, N=30"
Maybe this is the reason of glitches on Twitch
 

Attachments

  • OBS.mp4.MediaInfo.txt
    5.7 KB · Views: 35
  • ObsStudio.mp4.MediaInfo.txt
    4.1 KB · Views: 30
  • ObsStudio MediaFoundation.mp4.MediaInfo.txt
    4.2 KB · Views: 32
Last edited:

locodicegr

Member
Neat! I wanted to see more people streaming with AMD hardware so spread the word - it would make my day if a large streamer starts using this plugin.



HEVC will fix it! (TM)



Make sure you are remuxing the h264 stream as annexb. ffmpeg has no issues with this, so consider using ffmpeg instead of avidemux. Also mkv > mp4 > flv.

Edit: Also OBS uses ffmpeg-mux for combining into the target streams instead of libav, which is used by the AMF SDK examples. I think libav would be a better choice, but I don't know anything about that.

any word from amd about the HEVC support?
 
Neat! I wanted to see more people streaming with AMD hardware so spread the word - it would make my day if a large streamer starts using this plugin.

Well, thanks to you, AMD VCE is absolutely a viable alternative to x264 for streaming. However, as the bitrate requirements are higher with AMD VCE to produce the same video quality as x264, 720p 60 FPS streaming isn't really viable with AMD VCE for non-partnered Twitch streamers. You can do it, but it looks pretty bad at 3000 bitrate. It looks acceptable, in my opinion, at 3500 bitrate, but buffering will definitely be an issue (at least, as of September 2016).

Recommendation for non-partnered Twitch streamers looking to use AMD VCE: If 60 FPS is a must, as it is for me, and you like the performance improvements that come with using GPU encoding, as I do, I would recommend downscaling from 1920x1080 to 960x540 and using a maximum of 3000 bitrate. Alternatively, stick with 720p 30 FPS.

720p 60 FPS 3000 bitrate using the AMD VCE encoder looks roughly equivalent, to my eyes, to 720p 60 FPS x264 superfast with somewhere around 2500-3000 bitrate (ie. not good). GPU encoding is great for people who like to stream competitive first person shooters and want the best performance possible (at the expense of stream video quality, unless you're partnered and able to increase the bitrate beyond 3500).

If I'm missing something, please correct me. Just trying to help!
 
Last edited:
Status
Not open for further replies.
Top