2014-02-11, 23:19
Ok, look. I didn't come here to complain or "whine". I just wanted a simple answer to a question: Is it possible to make xvba continue working on the latest stable XBMC, with the current LTS, which has to use proprietary AMD drivers to get acceptable frame rates? I don't think that's an unusual or unreasonable question. I'm sure I'm not alone in using this setup. All I've gotten instead is, my hardware is crap, my drivers are crap, xvba is crap, and I should to use bleeding-edge software instead of outdated crap. I'm just looking for a solution to a problem. I don't want to be a bother or to frustrate anyone. I just didn't think it was outside of expectations for something that worked perfectly for my system in XBMC 12.2 to still be usable through the end of the version cycle with 12.3. I guess I was wrong. It appears I've stumbled into a bit of sour grapes here in this thread. I will leave now. Sorry to have bothered you all.
