jackun
Member
Get the latest. Others are for just in case new version breaks something for someone etc. Which reminds me to upload v0.64.
OBS branch with AMD VCE support.
- Thread starter jackun
- Start date
any will. Just dont set b frames to 1. Even if you do ill just throw an error and continue streaming. Get the latest if i were you. Its the most up to date since jackun ports over the builds from the main obs then adds in his changes.
who are you referring to. Im a bit confused...
supamesican
New Member
Hmm alright thanks, I got the 2015-02-01 build. What does AMF instead of OVE do?
jackun
Member
It uses newer (beta) AMF library from AMD Media SDK instead of the deprecated OpenEncode API.
E: Oooh, newer v1.1 was released on 29th.
supamesican
New Member
Oh that sounds cool, gonna go try it.
nice! Only 2 months late. Oh and what's that app SDK 3.0 beta thing?
jackun
Member
App SDK has the OpenCL, C++AMP/Bolt stuff. But the "ExtraData" property that returns initial SPS/PPS NALs returns nothing with v1.1, ugh.
Some new settings but of course they are missing from headers/undocumented.
Updated a little: DX11 buffers where not unlocked.
Last edited:
ill have to dig in a bit. Hopefully they will publish documentation updates on it.
Also, i thought the max for profile 4.1 was 1088@30? 4.2 can do 1088@68 max. Could you include a profile selector with the next version?
D
Deleted member 30350
Just curious - and it doesn't even have anything to do with OBS - I thought the VCE encoding was done by specific part of the GPU which is separate from all the rendering stuff, but when I try to record some game footage with Afterburner, using VCE as the encoding method, my fps dropped by like 25. How does it really work then?
It still uses up GPU memory bandwidth if DX11 is selected. host/DX9 uses system memory instead which is already shared and not as reliant on game rendering
jackun
Member
Random googling. TLDR: best perf when CPU/GPU work async, asking for front buffer data to capture it makes CPU wait for GPU to finish rendering so CPU can't schedule new commands for GPU and so GPU waits for CPU again probably, etc.
Behind the scenes stuff roughly:
Behind the scenes stuff roughly:
- game renders to front buffer
- copy FB to separate texture that CPU has access to
- copy pixels from texture to RAM
- convert BGRA to NV12 with CPU (OBS does it with 2 threads and from YUV444 (32bits))
- copy NV12 buffer back to GPU
- VCE is told to get next frame from NV12 buffer
Well that somewhat makes. I am no programmer but I dont know when the last time an older brother waited on a younger one :)
Lucil
Member
so on games that are high vram intensive its better to go host/dx9 when you are only you sing some of your system ram or have large amounts of system ram?
ie. 290x with 4x4gb 1600hz (16gb ram) on a windows 8.1x64 machine
Jackun's description is better. basically with DX10/11 the CPU pass stuff back and forth and wait on eachother. when its in host, that doesn't happen?
Hey. First of, love this thing. I read on the first few pages that some people had issues with a green line at the bottom. Also read that there was a fix for it. Said file is no longer available. My problem is that I have the green line on the vertical axis. As seen here (the solid green line to the right):
The thing is, this line only happens when I'm streaming. If I use OBS with the exact same settings to record to a local file, this doesn't happen. As can be seen here (this is all recorded):
So I'm not entirely sure where the issue is here. It's not a super big deal, but if there was a fix for it, that would be super dandy.
I may add that I play on a 21:9 monitor (2560x1080) that gets downscaled to 1706x720 when streaming.
The thing is, this line only happens when I'm streaming. If I use OBS with the exact same settings to record to a local file, this doesn't happen. As can be seen here (this is all recorded):
So I'm not entirely sure where the issue is here. It's not a super big deal, but if there was a fix for it, that would be super dandy.
I may add that I play on a 21:9 monitor (2560x1080) that gets downscaled to 1706x720 when streaming.