obsproject / obs-amd-encoder Goto Github PK

My OBS keeps crashing when I'm trying to start a new stream with the simple interface. I haven't tried the advanced one. Reinstalling plugin does not help. Here's the log:

http://pastebin.com/QKe8ueBP

Greetings,
JLNNN

Plugin settings
http://prntscr.com/c9gi3u

Output
http://prnt.sc/c9ghk8
Uploading 2016-08-23 19-36-17.txt…

The quality is very bad altough I have my bitrate set to 1900kbit/s. It's wierd, somehow one frame looks very bad and the next one is okay. I don't know how to explain this, so i uploaded a video of it.

You need to download the files to really see the effect, because of googles video transcoding.
https://drive.google.com/open?id=0B1y2xDp8JscndHByMjZKTUZVaGM (VBR)
https://drive.google.com/open?id=0B1y2xDp8JscnLWVHU1JZQjF6VTA (CBR)

Here are my settings. I set the recording encoder to use the stream encoder.
http://imgur.com/a/1I2uU

I am currently using the 16.7.3 driver on a 64bit Windows 10 Pro. This happened with all versions of the plugin I tested till now. I have a R9 390, a FX 8350 and 12GB of DDR3 1600 RAM.

Specs:
OBS 0.15.2 and OBS 0.15.4
Windows 10
AMD Radeon HD 7730 with driver 15.7.1

This only happened when I launch 64-bit version, 32-bit still working normal.

I attached the crash file below.
Crash 2016-08-14 19-01-42.txt

It seems that starting with version 1.2.0pre2 Bitrates stopped working correctly. Have to figure out if this is due to my own doing or due to AMD preparing for the next SDK version. If you're experiencing this too, please follow this guide and add your report.

would have been great to have this ability

• export as json
• copy as markdown (for forums/github/etc)

As i reported on the forum:

https://www.twitch.tv/bgshiny/v/87384175

This is what i get with pre7, downgrading to pre5 fixes things.

Here's the logs from when it happened :

2016-09-03 21-57-47.txt
2016-09-03 23-27-59.txt
2016-09-03 23-29-35.txt
2016-09-03 19-24-51.txt

My specs :

DESKTOP-UOARCO8.txt

The Pre8 Installer cant find the default obs folder to install it?

or its only on my pc?

MSI Gaming X 480/ Catalyst 16.8.3
FX-8350, 32GB 1600mhz, 850 PRO SSD
OBS 0.15.4 x64 on Windows 10 x64
AMF Plugin 1.3 Pre7
Simple mode: Recording preset (default settings)

2016-09-04 02-24-17.txt
2016-09-04 02-23-34.txt

sometimes it works, sometimes it doesn't, its random, i only notice it when the obs video hangs at either la st picture og black screen, when i try to stop it and it will still say "stopping recording" for a hundred years

PS: setting scan type to progressive seems to do the opposite aka making it interlaced

Can you open the wiki page so I can edit and add something to it?

Can't reopen an issue since I don't own this project, so I looked up how and it said I have to reference the issue, so the issue is #22. Reopen old one and get rid of this one if you feel the need to.

Edit: After updating to the newest release of OBS, the old encoder and this plugin both seem to be able to handle 1080p60 recordings with no issue? Don't know what happened there.

whatever i do it seems broken with build pre3 worked fine with older builds
https://beam.pro/

https://www.twitch.tv/derawesumdude/v/88108600

At first my stream starts as usual but later on it's getting async with sound/video and then it stops completely. Guess it's the same kind of issue that @CKannas stated here.

Switched back to 1.3.0pre7 and it's working fine for a stream longer than 3 hours.

Installed the lastest build, with of course removing the previous one. OBS crashes straight away. Please help. https://app.box.com/s/ozo3ga4fz1yu15ufsuyxvplkvk2siy7g

Have a box that changes the recommended values for specific graphics cards so that the user does not have to fiddle with all the settings. For example if I entered rx 480 it would change the settings for an optimized experience on the 480. If I changed back to a r9 290 you would then get the recommended settings for that card.

when i use default settings and set constrained bitrate to 2000, it goes to like 3800 and 22k :/

its like its using CRF or something
stupid question is QP the same as CRF?

• HD 7970 3GB
• OBS 0.15.2 64-bit
• OBS AMD Media Framework 1.1.2 64-bit
• Crimson 16.7.3
• Media SDK installed (runtime or something from link on plugin page)
• Windows 10 Redstone 1

this is not where i parked my car bitrate

Clean install of OBS Studio & the latest plugin Pre3,

Settings: all default / simple encoder / recording preset

Start recording , play for 1 minute (to test) exit the game and when i press stop recording it gets stuck at
''Stopping Recording'' & encoding overloaded in down left of the obs window.

Thanks for your work btw. Cheers!

Latest obs version 0.15.4 clean install
Latest plugin version 1.3.0pre3

CPU:i5 750 | Cooler:Corsair A50 | Fans:3x SilentWings2 | M/b:Asus P7P55-M | Ram:HyperX 8GB | GPU:Gigabyte R9 380 4G |
SSD:Kingston v300 | HDD:WD BLUE 1TB | Soundcard:SB-Z | Case:Corsair Air 540 | PSU:XFX TS 550w |

2016-08-23 18-44-29.txt
2016-08-23 19-14-07.txt

OBS-AMD-Media-Framework 1.2.rc1 Stress test 1080p@60fps no scaling - 3000-3200kbit
https://youtu.be/Z2_pOOozY9Y

OBS-AMD-Media-Framework 1.2.rc1 Stress test 1080p@60fps scaled to 1280@720@60fps - 3000-3200kbit
https://youtu.be/m60WFCT2O7s

OBS-AMD-Media-Framework 1.2.rc1 Stress test 1280,960@60fps scaled to 1280,720@60fps stretched - 3000-3200kbit
https://youtu.be/d5Q4Dj4uki4

Hardware:
CPU: Intel 4790K
Graphics: AMD R9 290 4GB GDDR5 modded to 290x - Then remodded to 390x
Motherboard: Asus MAXIMUS VI FORMULA
Ram: 16GB DDR3 2400mhz
Disk: 1TB Samsung EVO 840

Settings:

Type: Advanced Video Coding
Usage Type: Transcoding
Quality Preset: Balanced
Profile: Main
Profile Level: 5.0
Maximum LTR: 0

Scan Type: Progressive
Rate Control Method: CBR: Constant Bitrate
Frame skipping: Disabled
Filler Data: Disabled
Enforce HRD Compatability: No
Group Of Picture Size: 60
VBV Buffer Size (In Bits): 3200000
Initial VBV Buffer Fullness: 1
Maximum AU Size (In Bits): 0
B-Picture Delta QP: 4
Reference B-Picture Delta QP: 2
Minimum QP: 1
Maximum QP: 35
I-Frame QP: 22
P-Frame QP: 22
B-Frame QP: 22
Target Bitrate (In Bits): 3000000
Peak Bitrate (In Bits): 3200000
Header Insertion Spacing (In bits): 0
Number of B-Pictures: 0
De-Blocking Filter: Enabled
B-Picture Reference: Disabled
IDR (Keyframe Period) (In frames): 120
Intra-Refresh Memory Per Slot In Macroblocks (In MB): 0
Slices Per Frame: 1
Motion Estimation: Both
Temporal Enchancement Layers: -1

Remember this is a stress test where the game is speeded up a lot to see how the recording/streaming looks under extreme and unrealistic fast paced circumstances

Problem: After upgrading to 16.7.3 and downgrading to 16.7.2, submission time is tripled (or more) so that fluid recording becomes impossible.

Solution:

1. Wipe AMD drivers with DDU and install a clean 16.8.2 version. This should return it to normal.
2. Install 1.2.0pre4 or a newer version of the plugin

would be useful to go back to defaults?

The new Shared Encoder seems to not send off the required settings to the encoder before init. This causes the FPS to be stuck at "1000" in the file, with only exactly one keyframe being generated.

Hardware:
CPU: Intel 4790K
Graphics: AMD R9 290 4GB GDDR5 modded to 290x - Then remodded to 390x
Motherboard: Asus MAXIMUS VI FORMULA
Ram: 16GB DDR3 2400mhz
Disk: 1TB Samsung EVO 840

Logs
logs.zip

OBS apparently creates two encoder instances instead of just one. This leads to all kinds of oddities, like stream being blank or a corrupt mkv file (what).

A bug introduced in the new shared Encoder causes the Timestamps to be wrong - video length will be okay but the playback location and skip location will be completely wrong.

AMF is rather undescriptive about what does what and why.

da-DK.zip

Add a secondary encoder for users not so well-versed in encoding terms. Should probably hide more advanced settings behind a checkbox.

For some reason I am able to record at 1920x810 but no higher. This was an issue with the default AMD 264 encoder on Studio even though it should be supported by the encoder?

Hi,

first i want to thank you for your good work and hope you continue ;)

i noticed your 1.3.0pre5 - The AMF SDK Path (and 1.3.0pre3) dont have "GOP size" or fixed i-Frames (I Pic Period) // please could you also add "MV Search Range" & "IME Search Range" & "Force 16x16 skip" & "Force IME search window center to [0,0]"

maybe would be also nice to choose between DX9, DX11, DX12
oh and with newer dirvers "Disable D3D/OpenCL interoperability" is forced

ty again

ps: if you need a tester with some time i can assist you ;)

As is stated in the title, nothing happens when I click Record. It doesn't start recording. I only have this problem this encoder. x264, QSV, etc., all work fine.
2016-08-21 14-35-29.txt

When selecting preset it does not show up which preset you have selected, just blank.

http://prntscr.com/c9hra7

Also Profile level only shows max 5.1. is 5.2 missing?

http://prntscr.com/c9hl1l

Hence translation files goes up to 5.2

Hi,

I tested your plugin today and like it very much. But I have one issue that makes it for me impossible to use.
All videos don't have the frame rate that I set up in OBS. It does not matter if I record 30 or 60fps. So I can't import them in the editing software.
I tried lots of settings and found out that the quality setting has influence.
I recorded just the desktop at 1080p at 60fps. The result was a video with 59fps and Speed setting.
If I set it to Quality i got 50fps. The same with 30fps records.

I use an AMD R9-290´card with the 16.8.2 drivers under Win 10 x64.
Add-on version is 1.2.0 (RC1) and OBS 0.15.4 (64bit)

@Xaymar I added the logfiles and spec informations.

PC.txt
2016-08-26 13-53-19.txt
2016-08-26 13-46-56.txt
2016-08-26 13-40-12.txt

Its free for open source projects
https://crowdin.com/page/tour
https://crowdin.com/page/open-source-project-setup-request

Crash 2016-07-31 11-45-57.txt

Settings: http://prntscr.com/c8kx2e
Video info: http://prntscr.com/c8kwox

I think those two pictures speak for themselves. Also there still is some kind of flickering throughout the whole video, not as much as there was with the broken B-Frames, but still a little. I'll see if I can create an example where it is easily visible.

I tried to experiment with my settings a bit but the issue persists.

Also, is the advanced encoder gone for now?

Instead of calling VCE functions directly wrap them through this interface - ideally nothing should have to be done by the user interface that works with this.

This worked fine with the queue version, in the non-queued one it is broken. I may have broken something necessary for it to work while rewriting - a function somewhere.

Seen it go to the lows of 400 then spike up to 1200 when I start moving a lot.

I'd rather it stick within the 2000 range + Because it makes my stream look bad.

Any suggestions?

Hi,

I just encountered a memory leak using Version 1.1.2.
Memory detail out of Windows event-log:
Windows hat diagnostiziert, dass der virtuelle Speicher unzureichend ist. Die folgenden Programme belegten den meisten virtuellen Speicher: obs64.exe (3280) belegt 13665398784 Bytes, Overwatch.exe (1292) belegt 3823415296 Bytes und RadeonSettings.exe (2516) belegt 195080192 Bytes.

OBS Version 0.15.4 (64bit)
2016-08-31 20-41-07.txt
Crash 2016-08-31 19-34-44.txt
PC.txt

This Issue is meant to track progress on the upgrade to AMF SDK. Commits that are related to it will show up here.

AMF SDK: https://github.com/GPUOpen-LibrariesAndSDKs/AMF

• Library Binding Class for AMF SDK.
• New Shared Encoder based on Library Binding Class and AMF SDK updates.
• Update Capability Reporter to use new SDK.
• Update Simple Encoder Interface to new Shared Encoder.
• Update Advanced Encoder Interface to new Shared Encoder.
• Proper Color Profile and Range

Notice text in Danish left top corner (Svare ikke = Not responding)

http://prnt.sc/c9gbjr

Did a test record, stopped it after around 30 seconds, went to options to change setting since I'm getting flickers again with new update, started with b-pictures setting it to 0 and obs stalled/not responding

2016-08-23 19-15-49.txt

My previous issue is gone from here?
I had the overload problem and the ''stop recording got stuck"
now i got passed this problem - stop recording was execute correct without stuck, opened the recording file
main menu recorded ok...but when it got into the game it got freeze into a scene,

2016-08-27 10-08-59.txt
2016-08-27 10-16-36.txt
2016-08-27 10-27-11.txt

would been useful to have a mode where we can test settings and see if it can keep up, msi afterburner has something similar benchmark mode, we just need a simple one that has text with Good(Green)/Acceptable(Yellow)/Bad(Red) and results from a simple game/demo

So while recording Overwatch, I can play in 60fps and the shitty original AMD encoder can do 720p60 with no issues, this plugin can't do 1080p60 (highest I could get was 48fps). I've tried lowering the settings and setting the preset to Speed but it doesn't work. It also shows up choppy and low fps in the preview window. Should I attach a log to this when I get home later? I have to go out soon.

Edit: Forgot to add I tried with frameskipping turned on and off, no difference.

This Issue is dedicated to gather new tested settings. Only Settings with the latest Driver, 64-Bit OBS and latest Plugin Version are accepted. You can find the exact plugin version in the log output of obs:

15:05:59.207: [AMF Encoder] Version 1.3.0pre8-1.3.0.5

Please format your reply like this:

### System Specs
* CPU: ...
* GPU: ...
* RAM: ...GB DDR... ....Mhz
* Disk: HDD/SSD/...
* WIDTHxHEIGHT, FPSfps
* Driver Version: xx.x.x
* OBS Studio Version: x.xx.x 32/64-Bit
* Plugin Version: x.x.x-x.x.x.x

### Interface: Simple/Advanced
* Individual Settings listed here

### Examples:
* Preview: [YouTube/Twitch/Beam/...](LINKHERE)
* Raw File: [Download](mega.co.nz, google drive, ...)
* [MediaInfo](link to txt output here)

Edit: Comments that aren't on the newest version have been nuked from orbit.

I attached two crash logs, and two logs from OBS Studio (I'm not sure which one goes with which crash, that's why I'm adding two).
I tried recording with Game Capture and Display Capture. Every crash was at 19sec, 20sec, 21 sec. The result is a low quality video, I can upload an example if it could help.

2016-07-31 14-28-41.txt
Crash 2016-07-31 14-29-53.txt
2016-07-31 14-30-13.txt
Crash 2016-07-31 14-27-48.txt

With some rate control types, the plugin lets OBS climb to 8 or more gigabytes of memory.
Would be nice if I had some help tracking this down.

If you aren't a coder, you can help by reporting games and settings that this happened on.

Crash 2016-08-12 12-45-56.txt
Crash 2016-08-12 12-46-30.txt

32bit does not crash

Rewrite the advanced encoder to use the shared Encoder class (AMFEncoder::VCE). Depends on Issue #7 to be done.

AMF will randomly return AMF_ACCESS_DENIED for various properties after a while. Usually restarting OBS helps, but a better solution is necessary.

05:36:41.176: [AMF Encoder 1.2.0] AMFEncoder::VCE_H264_Encoder::VCE_H264_Encoder Initializing...
05:36:41.176: [AMF Encoder 1.2.0] AMFEncoder::VCE::H264 Attempting to create AVC Encoder...
05:36:41.206: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetUsage Set to Transcoding.
05:36:41.206: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetMemoryType Set to Host.
05:36:41.206: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetSurfaceFormat Set to NV12.
05:36:41.207: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetUsage Set to Transcoding.
05:36:41.207: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetQualityPreset Set to Balanced.
05:36:41.207: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetFrameSize Set to 1280x720.
05:36:41.207: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetFrameRate Set to 60/1.
05:36:41.207: [AMF Encoder 1.2.0] AMFEncoder::VCE::SetRateControlMethod Failed to set to Constant Bitrate, error AMF_ACCESS_DENIED (code 3).