Posts: 4,146
Joined: Jan 2008
Reputation:
40
Support is planned and worked on.
Always read the
online manual (wiki),
FAQ (wiki) and search the forum before posting.
Do not PM or e-mail Team-Kodi members directly asking for support. Read/follow the
forum rules (wiki).
Please read the pages on
troubleshooting (wiki) and
bug reporting (wiki) before reporting issues.
Posts: 639
Joined: Feb 2004
Reputation:
0
Clumsy
Team-XBMC Forum Moderator
Posts: 639
"Bad development decision" lol! Davilla is an osx developer, who loves his ATV boxes - that's one of the main reasons for the broadcom stuff. It's not like Team-XBMC has some drunk guy with a whip at the top, making decisions about who has to code what in his free time. This is still a free project made by people for fun in their spare time and open for everybody to contribute to. There are even people who DO work on dxva and whatnot, if you get frustrated by the time it takes to develop when there are 1-2 people working on a specific topic, then get your hands dirty and learn c++ (as Tiben for example did, when he wanted to make his directshow branch work), pay somebody to do it - or just be grateful for what you are getting.
/rant off
/annoyed
/back to topic: we are talking about scaling pixel shaders for windows here, take everything else elsewhere please.
Posts: 3,872
Joined: Mar 2006
Reputation:
157
Just wanted to add that, as little as I understand this, from what I do understand scaling on a GPU is far from being an inefficient solution. GPUs can do with shaders what a CPU has to waste many more cycles to achieve.
This is what I understand. Am I wrong devs?
Posts: 3,872
Joined: Mar 2006
Reputation:
157
I'm thick. So... was I right?
Posts: 2,752
Joined: Dec 2008
Reputation:
23
bobo1on1
cheapass Team-XBMC Developer
Posts: 2,752
You're absolutely correct, most graphics operations are very specific and can be split up into small parts and executed in parallel, gpu designers take great advantage of that by creating a chip that can perform those specific operations extremely fast and efficient.
A cpu core on the other hand has to scale one pixel at a time so it will never be as efficient, you need an expensive quadcore cpu and 4 scaling threads to match the speed of a $50 videocard.
Posts: 45
Joined: May 2008
Reputation:
0
One major thing that's holding XBMC back ATM is it's poor picture quality/lack of post-processing.
Compared to eg. the Cyberlink MPEG-2/1 codec in K-Lite media pack - the picture is simply very bad in terms of how clarity. This works even with old cards like early Radeon 9xxx.
I understand that if you have a VDPAU capable card, you will get activate some PureVideo filters that gives the same effect. However, this doesn't work with older cards - you need Nvidia 8xxx and above.
Is there any chance that we might get support for GPU-assisted postprocessing in older cards in the future? Or is it not prioritized at all or impossible to do with today's linux drivers for those cards? And in that case - is it likely that the open drivers will improve soon so that we can take advantage of these slightly older cards built-in postprocessing support?
Posts: 2,752
Joined: Dec 2008
Reputation:
23
bobo1on1
cheapass Team-XBMC Developer
Posts: 2,752
So what type of post processing do you think is needed?
Posts: 489
Joined: Apr 2004
Reputation:
13
Freddo
Skilled Skinner
Posts: 489
It's actually not an external player, its another internal player engine alongside the existing dvdplayer one, but it supports directshow filters.
It's still fairly early days but it'll let you load a custom filterchain I guess maybe even using purevideo, though I don't think I've seen anyone try it. Tibens concentrating on subtitles right now though, so you may be on your own experimenting.
sorry if its still academic since your on linux, but I thought it was worth clarifying for anyone else reading.