OBS 0.52.08 aquaman build - quicksync & capture improvements

Status
Not open for further replies.
K

kaloc

Member
Re: OBS 0.52.03 toast build - quicksync

coopmine said:
Hey - they seem to have integrated OpenCL natively to x264 in their Github.
https://github.com/DarkShikari/x264-devel

Maybe its worth a look and adding it to OBS - more speed is always good :)
Click to expand...

Yep, its now in the standard builds on the x264.nl site. It was only a matter of time I suppose, before they added it to the main build. It will be interesting to see what people come up with performance wise, when its available of course.
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
Re: OBS 0.52.03 toast build - quicksync

I'm aware of the opencl build, and have used it back in its experimental stages, seems to work pretty nicely. I'll see what I can do about putting it into the next builds
 
B

Bensam123

Member
Re: OBS 0.52.03 toast build - quicksync

OpenCL would be nice, but I was also talking about VCE or NVenc, which are similar to Quicksync. Ideally it'd be nice if all of this could be done in OpenCL so it would compatible with all the GPUs, but I don't think anything like that has been done yet. OpenCL is just used for look ahead (unless that's changed).
 
M

miTTPC

New Member
Re: OBS 0.52.03 toast build - quicksync

Just a quick one. I'm a tad puzzled on enabling IGPU in the bios on a MSI board (Z77A-G45) any help is much appreciated as I'm tearing my hair out here!

EDIT- Sorted that out, only OBS isn't using Quick sync now.....
 
G

Goatfudge

New Member
Re: OBS 0.52.03 toast build - quicksync

DAOWAce said:
Well, Haswell is out.

Currently waiting to see what QuickSync improvements there are, if any.

Other than that, the damn thing is quite a big letdown. Very little improvement in many areas; the only places where it really improves is the iGPU (which no one should be using for gaming anyway) and some video encoding, namely x264.

Regardless of the video encoding improvements, I don't see a reason to pay for the switch unless you're someone who really needs the extra performance. Just a complete waste of money if you're already on IB.

Guess there's always IB-E or Haswell-E, right? *sigh*
Click to expand...

Quick Sync quality seems to have regressed with Haswell for transcoding at least, despite Intel claiming otherwise.

http://anandtech.com/show/7007/intels-h ... spective/8
http://anandtech.com/show/7007/intels-h ... pective/10

No idea if this is a fuck up by Handbrakes implementation, the drivers or hardware.
 
Xphome

Xphome

Member
Re: OBS 0.52.03 toast build - quicksync

miTTPC said:
Just a quick one. I'm a tad puzzled on enabling IGPU in the bios on a MSI board (Z77A-G45) any help is much appreciated as I'm tearing my hair out here!

EDIT- Sorted that out, only OBS isn't using Quick sync now.....
Click to expand...

Do you have a monitor plugged into it or enabled a "fake" monitor? Latest drivers? You can find out how to enable a "fake" monitor earlier in this thread.
 
DAOWAce

DAOWAce

Member
Re: OBS 0.52.03 toast build - quicksync

Goatfudge said:
Quick Sync quality seems to have regressed with Haswell for transcoding at least, despite Intel claiming otherwise.
Click to expand...
That's a damn shame.

We definitely need to see more testing done with this. Hopefully it's due to the software/drivers and not the hardware.. It's unfathomable that Intel could've stepped backwards, though even if they really did, it wouldn't surprise me that much anymore..
 
B

Bensam123

Member
Re: OBS 0.52.03 toast build - quicksync

Jim said:
I'm aware of the opencl build, and have used it back in its experimental stages, seems to work pretty nicely. I'll see what I can do about putting it into the next builds
Click to expand...

Would this interfere with Quicksync? Would it also cause performance issues with games? Would it be possible to offload this to a single GPU? Is this just lookahead or a full blown OpenCL implementation?
 
T

TuFFrabit

New Member
Re: OBS 0.52.03 toast build - quicksync

The x264 implementation of OpenCL/AMD VCE is only partial. OBS could receive even more performance gains with it's own native implementation.

Any chance of getting the source for this QuickSync build? I have the AMD VCE docs and I would like to see how QuickSync was implemented for OBS. Perhaps I can find the time to sit down and bang out a OBS VCE implementation.
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
Re: OBS 0.52.03 toast build - quicksync

The source of it is on github as is everything else. Next test will also have the new x264 build that includes opencl support, so lots of developments on the hardware encoding front as of late
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
Re: OBS 0.52.05 toast build - quicksync

Just uploaded 0.52.05 with the new opencl x264 changes. Many quicksync changes as well. And as a bonus, paibox added in gamma support for capture devices.

Also I think I fixed that annoying bug with arma2, finally.
 
G

Geoning

Member
Re: OBS 0.52.05 toast build - quicksync

OpenCL doesnt work for me.
OBS doesn't encode stream (0kbps in interface)
I was checking with GTX 660M and Intel 4000 (laptop)

Maybe its work only when intel is locked but i cannot lock in laptop. :P
I can only force run OBS on GTX 660M but still 0kbps... Twitch and mp4 have 0 data.
Logs for Jim.

Code: 
15:26:14: Open Broadcaster Software v0.52.05b powdered toast build - 64bit (　^ω^)
15:26:14: -------------------------------
15:26:14: CPU Name: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
15:26:14: CPU Speed: 2494MHz
15:26:14: Physical Memory:  8081MB Total, 5449MB Free
15:26:14: stepping id: 9, model 10, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 4, total cores 2
15:26:14: monitor 1: pos={0, 0}, size={1600, 900}
15:26:14: Windows Version: 6.2 Build 9200 
15:26:14: Aero is Enabled
15:26:14: -------------------------------
15:26:14: OBS Modules:
15:26:14: Base Address     Module
15:26:14: 0000000060CA0000 OBS.exe
15:26:14: 00000000BF360000 OBSApi.dll
15:26:14: 00000000C5700000 DShowPlugin.dll
15:26:14: 00000000C3490000 GraphicsCapture.dll
15:26:14: 00000000C4360000 NoiseGate.dll
15:26:14: 00000000C4310000 scenesw.dll
15:26:14: ------------------------------------------
15:26:14: Adapter 1
15:26:14:   Video Adapter: Intel(R) HD Graphics 4000
15:26:14:   Video Adapter Dedicated Video Memory: 33554432
15:26:14:   Video Adapter Shared System Memory: 1845493760
15:26:14: ------------------------------------------
15:26:14: Adapter 2
15:26:14:   Video Adapter: NVIDIA GeForce GTX 660M 
15:26:14:   Video Adapter Dedicated Video Memory: 2087518208
15:26:14:   Video Adapter Shared System Memory: 2147479552
15:26:14: =====Stream Start: 2013-06-04, 15:26:14===============================================
15:26:14:   Multithreaded optimizations: On
15:26:14:   Base resolution: 1600x900
15:26:14:   Output resolution: 912x514
15:26:14: ------------------------------------------
15:26:14: Loading up D3D10...
15:26:14: Playback device {0.0.0.00000000}.{72222909-7a4d-4d04-84d2-71738b2456bd}
15:26:14: ------------------------------------------
15:26:14: Using desktop audio input: Głośniki (Realtek High Definition Audio)
15:26:14: ------------------------------------------
15:26:14: Audio Encoding: MP3
15:26:14:     bitrate: 48
15:26:14: Using Monitor Capture
15:26:14: Using custom x264 settings: "opencl=true"
15:26:15: ------------------------------------------
15:26:15: Video Encoding: x264
15:26:15:     fps: 60
15:26:15:     width: 912, height: 514
15:26:15:     preset: veryfast
15:26:15:     CBR: yes
15:26:15:     CFR: no
15:26:15:     max bitrate: 346
15:26:15: ------------------------------------------
15:26:15: x264: OpenCL: Invalid value.
15:26:15: x264: OpenCL: fatal error, aborting encode
15:26:15: x264: OpenCL: Invalid value.
15:26:15: x264: OpenCL: fatal error, aborting encode
15:26:15: x264: OpenCL: Invalid value.
15:26:15: x264: OpenCL: fatal error, aborting encode
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
15:26:16: x264: OpenCL: Invalid value.
15:26:16: x264: OpenCL: fatal error, aborting encode
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
Warning -- x264 encode failed
15:26:19: Total frames rendered: 233, number of frames that lagged: 1 (0.43%) (it's okay for some frames to lag)
15:26:19: x264: OpenCL: Invalid value.
15:26:19: x264: OpenCL: fatal error, aborting encode
15:26:19: x264: OpenCL: Invalid value.
15:26:19: x264: OpenCL: fatal error, aborting encode
15:26:19: x264: OpenCL: Invalid value.
15:26:19: x264: OpenCL: fatal error, aborting encode
15:26:19: x264: OpenCL: Invalid value.
15:26:19: x264: OpenCL: fatal error, aborting encode
15:26:19: x264: OpenCL: Invalid value.
15:26:19: x264: OpenCL: fatal error, aborting encode
15:26:19: x264: OpenCL: Invalid value.
15:26:19: x264: OpenCL: fatal error, aborting encode
15:26:19: =====Stream End: 2013-06-04, 15:26:19=================================================
15:26:20: 
15:26:20: Profiler results:
15:26:20: 
15:26:20: ==============================================================
15:26:20: frame - [100%] [avg time: 2.181 ms (cpu time: avg 1.207 ms, total 281.25 ms)] [avg calls per frame: 1] [children: 71.8%] [unaccounted: 28.2%]
15:26:20: | scene->Preprocess - [6.19%] [avg time: 0.135 ms (cpu time: avg 0.134 ms, total 31.25 ms)] [avg calls per frame: 1]
15:26:20: | video encoding and uploading - [65.7%] [avg time: 1.432 ms (cpu time: avg 0.536 ms, total 125 ms)] [avg calls per frame: 1] [children: 59.7%] [unaccounted: 5.96%]
15:26:20: | | CopyResource - [1.51%] [avg time: 0.033 ms (cpu time: avg 0.067 ms, total 15.625 ms)] [avg calls per frame: 0]
15:26:20: | | conversion to 4:2:0 - [0.459%] [avg time: 0.01 ms (cpu time: avg 0 ms, total 0 ms)] [avg calls per frame: 0]
15:26:20: | | call to encoder - [57.7%] [avg time: 1.259 ms (cpu time: avg 0.469 ms, total 109.375 ms)] [avg calls per frame: 0]
15:26:20: | | sending stuff out - [0%] [avg time: 0 ms (cpu time: avg 0 ms, total 0 ms)] [avg calls per frame: 0]
15:26:20: | Convert444Threads - [710%] [avg time: 15.486 ms (cpu time: avg 1.341 ms, total 312.5 ms)] [avg calls per frame: 0]
15:26:20: ==============================================================
15:26:20:

#EDIT: Probably its problem with x264 not with OBS...
 
B

Benji89

New Member
Re: OBS 0.52.05 toast build - quicksync

Tested the OpenCL encoder on a 7970m (Enduro) and works flawlessly, I'm able to stream now without my FPS being effected at all.
 
I

Invi

New Member
Re: OBS 0.52.05 toast build - quicksync

not sure if I'm missing something, but how do I use the OpenCL encoder ?

Edit - nevermind, found it on the main post.... derp :D, for those wondering add "opencl=true" without quotes to custom x264 settings
 
X

xD4rkFire

Member
Re: OBS 0.52.05 toast build - quicksync

Sorry for the noob question but what is OpenCL hardware acceleration and can I enable it on a Radeon HD 6850?
 
G

Geoning

Member
Re: OBS 0.52.05 toast build - quicksync

xD4rkFire said:
Sorry for the noob question but what is OpenCL hardware acceleration and can I enable it on a Radeon HD 6850?
Click to expand...
Check with GPU-Z
 
D

dehixem

Member
Re: OBS 0.52.05 toast build - quicksync

xD4rkFire said:
Sorry for the noob question but what is OpenCL hardware acceleration and can I enable it on a Radeon HD 6850?
Click to expand...

Same question here :) I imagine the CPU is less used or something like that ?
 
L

Lupzi

New Member
Re: OBS 0.52.05 toast build - quicksync

Is there haswell support ? I am using a 4670k and "use quicksync" is grey.
GA-Z87-D3HP is my motherboard.
Am I mising somehting?
 
Status
Not open for further replies.
Top