Is --opencll 'concurrency' safe?

[asarian]

Is using --opencll with x264 'concurrency' safe? Like, if you use it, can you even use your video card for other things? (Like gaming) I'd hate to go play a game, only to found out, later on, that my rendering job suddenly had weird artifcacts in it or something, because it was using OpenCL with x264.

Thanks.

[mastrboy]

Looking at the changelog: http://git.videolan.org/?p=x264.git;a=shortlog I would say it's not ready for "production" usage.
There hasn't been a a commit related to opencl in 2 years.

The option probably isn't popular enough, or the effect from using it is not enough for people to bother.

The only purpose to use it is to decrease the encoding time if I remember correctly? If so, how much to you gain? Hours? Minutes?

[asarian]

Looking at the changelog: http://git.videolan.org/?p=x264.git;a=shortlog I would say it's not ready for "production" usage.
There hasn't been a a commit related to opencl in 2 years.

The option probably isn't popular enough, or the effect from using it is not enough for people to bother.

Thanks for your reply.

Prior to using it, I did sample testing (of course); and gained about a 2-3% increase in encoding with --opencl added. Not spectacular per se, no; but still. But yeah, ony later I realized I'd be keeping my GPU tied up for the duration of the entire encode.

For KNLMeansCL, the speedup was far more significant, btw (close to 40%. really).