Initial native support for DXVA2 in SVN - Time to say goodbye to your firstborns - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: XBMC General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: Windows support (/forumdisplay.php?fid=59)
+---- Thread: Initial native support for DXVA2 in SVN - Time to say goodbye to your firstborns (/showthread.php?tid=69306)
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121
- Hitcher - 2010-02-02 18:51
I can't win -
DSPlayer = Great video / no sound
DXVA = Green screen / sound
- pettson3816 - 2010-02-02 18:54
oDium Wrote:Hey guys! I've been waiting for Dxva for a longgggg time. . .
So what you're saying is that this green artifact problem will never be solved then?
- elupus - 2010-02-02 18:58
Just a note.. The video scalers are doing nothing for dxva at the moment. I render directly to backbuffer so it's all how dxva processor scales at the moment.
And as i noted, it's still a WIP, untill i get some sort of detection working as to what will work and what will not it can't really be used auto.
Any reason you say it's better to render to a texture then to backbuffer? we don't do any 3d stuff, and that would just be another step of renderering + to use any of the more advanced dxva processors, you'd have to render to a texture of backbuffer size.
It would allow the use of shaders to continue processing the video i suppose. But i'm not sure how big benefit that would be.
The late loading I would really like to avoid, but i can be convinced otherwise if it will fail totally on XP (which i suppose is likely now that i think of it). It's not that many functions that needs to be getproced.
- elupus - 2010-02-02 19:01
Also, debug logs with a short description of how it's failing would be appreciated. Don't post for many files thou as that is likely pointless untill i can sort our why it fails on my hw for so many files.
- kuroyume - 2010-02-02 19:05
tiben20 Wrote:i would love too see some benchmark test to compare both players
i'll be glad to run some for you if you send me instructions on how to run them
- oDium - 2010-02-02 19:09
pettson3816 Wrote:So what you're saying is that this green artifact problem will never be solved then?
Ati's technicians have been asked many times in ati's forums , by users,
about the well known limitations their drivers have. No activity seems
to be taking place , but who knows. Maybe in their next catalyst release
they will deactivate the limitation and all files will play correctly. On the
other hand maybe not. The point is that nvidia guys even use that , in
order to attack the ''other'' side.
There was a trailer from apple's site , quantum of solace in particular ,
which was used in a nvidia dxva demonstration , where the same trailer
was playing correctly using their cards , while when it was playing under
ati cards , the green artifact fenomenon was present , making the video
totally unwatcable . MPC - HC as far as i remember , has the ability to detect whether the card is able to cope with the video in dxva. That means that
if you try to play such a file using an ati card , the player simply won't use
dxva and it will revert back to software rendering .
Maybe something like that can be a part of dvdplayer also .
And don't forget. It has nothing to do with the horse-power of the cards .
All capable - dxva ati cards can decode everything , it is simply an inner
driver limitation which ati has to remove .
- IndustrialPope - 2010-02-02 19:20
well, well: just as I was chatting to a friend about my woes with 1080p content and no proper solution.
This is manna from heaven for my little htpc. It works beautifully even though it's only a first step.
- ArtVandelae - 2010-02-02 19:22
oDium Wrote:For all of you that ypu experience green artifacts in some of your files
Yes, ATI "only" supporting H.264 up to L4.1 is obviously why 480p (L3.1) quicktime trailers, 1080p (L4.0/L4.1) quicktime trailers and unaltered Blu-Ray material (L4.1) doesn't work on either Nvidia or ATI at the moment .
- oDium - 2010-02-02 19:51
ArtVandelae Wrote:Yes, ATI "only" supporting H.264 up to L4.1 is obviously why 480p (L3.1) quicktime trailers, 1080p (L4.0/L4.1) quicktime trailers and unaltered Blu-Ray material (L4.1) doesn't work on either Nvidia or ATI at the moment .
To be a little more specific. From internet searching and reading a LOT of
forums and user's experiences , ati has a limitation as far as it concerns
the reference frames in a video file. Both ati and nvidia can decode in dxva
everything as far as the file remains in BLURAY original specs. If the file gets
out-of-bluray specs , then only nvidia cards will be able to decode it properly.
As far as it seems , it doesn't matter if a file has L4.1 or bigger profile , it has
to do with the reference frames. I think that ati can't cope with 5 reference
frames and above.
Some people have managed to go over the limitation using a very specific version of powerdvd
with ati catalyst 9,4 and only that !
But we all have to be aware of something else also . Not only the card's drivers have to be limited - free ,
but the player also . MPC - HC
from what i know wasn't always limited - free. It the first versions , it
also had the above bluray limitation . When the developers removed
the limitation , then again only nvidia managed to decode files with out-of-bluray specs .
Lastly i copied - paste something useful from ati forums :
'' Intel’s DXVA limitations is the same as ATI, but if these two wants to, they can follow nVidia’s lead and remove the limitation.
MPC-HC recent releases can already decode out-of-spec H.264 videos with DXVA, but that is for nVidia cards only ''
- ashlar - 2010-02-02 19:53
First of all... well, THANK YOU to all the developers involved. XBMC devs, VLC devs, FFMPEG devs. This is a big step ahead for open source. Thank you.
1) Is this implementation different from CrystalHD? I have an ATI 4890 and a BCM970012 in my system (it costed little money, was curious to try it and I'm hopeful it could be the way to go to playback VC-1 interlaced stuff). Meaning, on my system, I'm gonna have a Software, CrystalHD and DXVA renderer?
2) Does this implementation open up the possibility of shaders postprocessing? MPC-HC has some really nice ones (nudge, nudge, wink, wink).
3) In case the answer to #1 is yes (three different renderers), what's the target for the autoselection thing? Once everything will be working, what is the desired behaviour? Will this offer a "fallback mode" as MPC-HC does (where you can select a different codec for DXVA compliant material and non-DXVA compliant material)?
Once more: thank you!