Originally posted by jrch2k8
View Post
Announcement
Collapse
No announcement yet.
AMD's UVD2-based XvBA Finally Does Something On Linux
Collapse
X
-
-
New updates avaible:
libva 0.31.0-1+sds9
xvba-video 0.5.2
mplayer-vaapi 20091127
Comment
-
Updated the script to use 0.5.2 as there are no latest links for the debs (download the script again). The "svn up" variant "-1" works again too. For nvidia the updates are really nice - now it is basically on par with vdpau mode - you can deinterlace with D. Maybe even DIVX works with new nvidia cards, could not test this. Best check vainfo with such a card.
Comment
-
Originally posted by Qaridariumbelieve it or not you are wrong!
wrong because the UVD2 unit itself use the GPU-shader
Dirac!,Theora,OGG,FLAC and more future codexs
Comment
-
Originally posted by Qaridarium"There is no reason to believe you. "
longer time ago there was the same Tropic in this forum!..
you can ask Bridgman about the UVD unit!
Bridgman will say something like that: "yes the UVD unit use the shader for some functions. "
Nowadays, the shaders are only used for colorspace conversion and some other *post* processing. The core video decoding is done by the specific ASIC (UVD). Again, show me code proving what you say (or what you are dreaming of).
Comment
-
OK, here's my understanding :
- UVD handles the top half of the playback stack (decoding), when present. This includes bitstream / IQ / IDCT / deblocking / MC for H.264/VC-1 and IDCT / MC for MPEG2.
- The bottom half of the playback stack (scaling, color space conversion, post-filtering, not sure about adaptive deinterlacing) is done on shaders.
- UVD's HW programming interface is tied pretty closely to the DRM blocks so I'm telling people to assume that we will *not* be able to provide programming docs for open source drivers. Once we get through the current work and have a chance to spend some quality time with UVD we should be able to give a definitive answer.
For decode acceleration without UVD, I expect that MC, deblocking etc will be a good fit for shaders, while bitstream decode, IQ and IT will probably stay on CPU. That partitioning should work pretty well -- not too hard on the GPU, but offloading enough CPU that a single core should be able to keep up. There were some efforts to move IT onto shaders but with the simplified IDCT algorithm in H.264 (and VC-1 ?) the CPU load is lower than before so it seems best to leave on the CPU.Last edited by bridgman; 28 November 2009, 03:06 PM.Test signature
Comment
-
All my mplayer-vaapi scripts are updated and use 0.5.3 xvba-video. I would prefer that the debs would be also available as "latest" instead of the version then i don't have to update it everytime. But it is really nice update for xvba users:
Version 0.5.3 - 28.Nov.2009
* Handle up to 16 subpictures in OpenGL rendering mode too
That means OSD finally works with opengl output! It does not fix color rendering problems or stability issues but at least you can use OSD/subtitles. Now i want m2ts subtitles for mplayer and xvba support for mpeg1/2 too - then you don't need to switch from vaapi to gl everytime. A fallback for other codecs should be possible too just like using a clever vdpau config. Btw. as mplayer (or better ffmpeg) has broken mpc support there is currently a -2 script with a hotfix too.
Comment
Comment