In the previous thread on this topic it was mentioned that the developers who had originally started a VDPAU implementation were considering moving their work to VA-API.
Quote:
Originally Posted by tball
Printable View
In the previous thread on this topic it was mentioned that the developers who had originally started a VDPAU implementation were considering moving their work to VA-API.
Quote:
Originally Posted by tball
Seems like a duplication of effort to me. Wouldn't it be better if AMD just contributed to the r600g driver hosted at freedesktop.org, instead of writing their own Gallium3D driver? Or could it be that phoronix is spreading misinformation again?Quote:
Originally Posted by phoronix
If you spend a little more time on making sure your articles are correct without ambiguity and a little less time on fluffing up your articles with irrelevant stuff just so you can squeeze in more links to yourself, maybe people would start taking phoronix seriously. Just maybe.
The two main projects that I can think of were:Quote:
Originally Posted by 89c51
1) Younes Manton, GSoC project. g3dvl, already mentioned in this thread
2) Robert Rudd @ MIT. Another GSoC project that attempted H.264 decode via GLSL shaders using the ffmpeg/libav framework as a starting base. He got some stuff working, but didn't finish the project. Someone forked his code and at least got it to compile: https://github.com/kasbah/gsoc.
Give it a few weeks, and I'll be sending my initial VP8 OpenCL implementation to the WebM mailing list to live in a sandbox while I continue work on it post-graduation. It's functional, but much slower than CPU-only decoding at the moment. It does at least produce correct output... in its own good time.
Once its in the sandbox and my thesis is finished up, I wouldn't object to anyone helping me out with getting the performance up to speed.
I think he means r600g. AMD's not writing 'their own' Gallium3D driver. Sigh.Quote:
Originally Posted by monraaf
AFAIK, MPEG2 works. Christian König has a working XvMC implementation, for r600g. I haven't tested it, but others have, and it's working (not perfectly optimised yet). He also has iDCT working and some other stuff.Quote:
Originally Posted by plonoma
Most of the steps which any modern high-quality codec does are similar: iDCT, motion compensation, etc. If it's done for H.264, it can be easily ported to other codecs. The main difficulty is getting the infrastructure and a reference implementation down.Quote:
And why is everybody trying to make H.264 get a foothold on Linux?
Please support FLOSS formats/libraries instead of the latest flashy thing like H.264.
Now, THAT sounds fantastic! Great work!Quote:
Originally Posted by Veerappan
Now we need Clover :D
Good news, thank you!Quote:
Originally Posted by Veerappan
Let's hope that we'll have an opencl state tracker to actually use it. :)
Quote:
Originally Posted by monraaf
I think Michael meant "the Gallium3D driver for their hardware", which a lot of people shorten to "their Gallium3D driver" even if that is not strictly equivalent.Quote:
Originally Posted by mattst88
did you put your current alpha/beta prototype code on a github or do you intend to soon? and when do you assume your thesis will be doneQuote:
Originally Posted by Veerappan
there's all those other bit's and peace's of openCL/Cuda code mentioned on the x264dev logs etc too, it's not clear if they do/cover other stuff besides your "I've managed to convert Subpixel Prediction (sixtap + bilinear), IDCT, Dequantization, and the VP8 Loop filter" routines yet , as no ones bothered to collect them up and list the github etc location's on a web page somewhere
How the hell is MPEG-2 "free and open"? It is patented and licensed by MPEG-LA.Quote:
Originally Posted by plonoma
MPEG-1 is basically MPEG-2 with lower resolution. It doesn't need hardware acceleration anyway.