unfortunately thats not true, as I said, most clips play fine so there is a very specific problem with a H264, it does not affect all H264 decoded material, this might be why AMD are having problems here, the might simply be playing clips that work thinking they've fixed it or have no problem:
clip that fails:
clip that works:
Both are H264 encoded.
yes as Imentioned before progressive scan videos work most of the time.....
I have loads of videos taken by iphones (1080p) and all play fine with LAV DXVA turned on.
AMD try this video which works with LAV h.264 ....1080p
AMD arent listening or contributing to this thread, who are you talking to? I thought you'd open up a dialog with AMD, why are you asking AMD to play something from here, I posted those links so you pass them onto whoever is dealing with it at AMD.
Let not confuse the issue further by throwing loads of different formats into the mix.
By default WMC loads microsoft codecs. With the k-lite codec pack there is "Codec Tweak Tool" included which from there I can disable Microsoft Codec so WMC is forced to load LAV. Of course after that I can change LAV settings from LAV tray icon because it appears when media center is playing.
No, i dont think its Crimson, on my A10-7800 i am running latest Crimson, and its fine.
Also using older non Crimson Driver on my Fury X doesnt change a thing.
Thanks for that. I'll pass these clips onto Engineering as well.
What is happening with the driver updates? They just released the same version 16.12.2 as new driver but they have changed some things in the fixed issues (the first thing I saw was the Mouse cursor corruption, which from fixed issue, again has gone to known issues)
I think AMD is totally unable to provide a perfect user experience. Corruption everywhere. Games, mouse cursor, videos, etc.... What the hell is going on with RXxxx?
Have not installed as yet. Does not seem worth the while.
latest driver is more stable for me, in fact a big improvement on anything beyond 16.8.3, there have been around 15 updates since then, all of then crashed mpc-hc with madvr regardless of whether h.64 lav filter was tick or not. Lav has also been updated to 69, madvr has also been updated.
12.2.1 completely shafted my pc, well almost. I got it stuck in a boot loop when I installed the driver. Managed to get in and remove the drive but then when i installed it again it shafted all my kodi installs, I was livid.
When I came home the next day 2.2 was out so I decided to give it a go before having to spend hours sorting kodi and other issues out, basically anything that played a video either froze, crashed, blue screened the PC, chomped up all my memory or sent my CPU to 100%, 2.1 was a total disaster for me, so were some of the other updates, what a total mess AMD have made of this card.
Thanks god 2.2 came along and fixed whatever 2.1 broke, just not h264.
i've learnt not to update my card anymore in case i need to fix something, i'll let other people test the drivers these days
with the greatest of respect Ray, weve been told this before, is anything really happening this time, or have we all paid 240 quid for a lemon?
Also, if engineering are really aware of this and can reproduce it, why was it removed from the list of known issues, or at least not added today with the update.
That is interesting information. With these issues there are so many aspects to consider. Let's wait for some feedback from AMD via Ray hopefully soon.
people need to sign my petition, only 4 have signed, with this level of apathy, no wonder AMD are in no rush to fix it.
ray_m we need some help here, please can you give us an update on the situation in the form of questions to be answered - if you've got time to ask me to edit my post, surely you've got time to answer a few questions....
1. Has this been reproduced from the clips we've given you?
2. Why has the problem been removed from the list of known issues?
3. are you aware this appears to be affecting other generations of cards?
4. Do you not feel that AMD owe its HTPC / media center customers an appologly and an official acknowledgement of a problem this card has had since day one.
5. Given that we've waited months for any sort of action from AMD on this one, what sort of priority is this being given, is it fair for AMD to beat its chest and try get everyone excited about VEGA when your current flagship card hasn't had one single day since release where the card has been 100 % fully functional?
I've owned and used AMD card for over 10 years, I am, was a loyal customer, lets see if you can turn this around but lighting a fire under this problem and getting some sort of fix or at least an official acknowledgement in the next driver release.