How about multi GPU setups? like an A10-7850K w/ an R9 series GPU? Would it be able to make use of both or would just one be used and if so which?
AMD Open-Sources VCE Video Encode Engine Code
Collapse
X
-
Originally posted by GreatEmerald View PostIt would be nice if this was available in FFmpeg. (Does FFmpeg support VA-API encoding, by the way?)
Comment
-
-
Originally posted by Kivada View PostHow about multi GPU setups? like an A10-7850K w/ an R9 series GPU? Would it be able to make use of both or would just one be used and if so which?
Comment
-
-
Originally posted by agd5f View PostIs there some specific app you have in mind? There doesn't seem to much that supports hw encoding in general on Linux (either API). Most people use gstreamer for encoding which supports both omx and vaapi. Additionally omx has some nice features for implementing more efficient transcoding.
(seriously, people use gstreamer for encoding? It is unusable for playback due to being 3-10x slower than mplayer derivatives...)
Comment
-
-
Originally posted by curaga View PostMplayer supports vaapi for playback, so adding it for encode ought to be easier than adding a whole new api.
So to support VA-API the software stack would look something like this:
1. VCE encodes the frame to an elementary stream
2. driver decodes the elementary stream back to slice level data
3. VA-API passes slice level data to application
4. Application encodes slice level data back to an elementary stream
That makes no sense on both CPU and implementation overhead and is the main reason why we dropped VA-API support.
Comment
-
-
Originally posted by Nille View Postffmpeg has no h264 encoder. They use libx264
Originally posted by Nille View Postand that project don't want hardware encoders. the result is not so nice like what the cpu generates.
Comment
-
-
Originally posted by GreatEmerald View PostOh... Well, that's too bad. Hardware acceleration may be limited, but it's fast, and it would be nice to have that option.
Comment
-
-
Originally posted by Deathsimple View PostSorry forgotten to explain that. The encoding part of VA-API works with slice level data, but the output of VCE is an elementary stream.
- the mentioned flexibility doesn't include slice output?
- if it was known from the start AMD's solution would have this output, why didn't they take part in vaapi design to have it in there?
Comment
-
-
Originally posted by curaga View PostOh, that makes sense, though it does raise some questions:
- the mentioned flexibility doesn't include slice output?
- if it was known from the start AMD's solution would have this output, why didn't they take part in vaapi design to have it in there?
Comment
-
Comment