Of course the best would be if someone would add an about:config setting to completely disable video decoding fallback in native Firefox version... I found it to be too much hassle for me and my old netbook

Of course the best would be if someone would add an about:config setting to completely disable video decoding fallback in native Firefox version... I found it to be too much hassle for me and my old netbook

But unfortunately, because of some reasons ( maybe my GPU is so fast? ), though I tried many ways, I can't trigger the function all the time, so you need test it yourself using below method and report the result to me.1) keep the default value, dxva enabled or disabled?2) set the three about:config to 0 or 1, dxva enabled or disabled?3) set the three about:config to a larger value, dxva enabled or disabled?

Last edited by xunxun1982 on January 31st, 2016, 11:42 pm, edited 1 time in total.

https://bugzilla.mozilla.org/attachment ... ction=diffHere is the change which is already implemented in stable Firefox. It makes the video decoding fallback a little bit less sensitive... but still very easy to trigger (at least for me).In my case 4k@60fps always trigger the fallback (currently only for one problematic video instead of whole Firefox session), so I shouldn't have much problems testing your changes

Dun wrote:https://bugzilla.mozilla.org/attachment.cgi?id=8656218&action=diffHere is the change which is already implemented in stable Firefox. It makes the video decoding fallback a little bit less sensitive... but still very easy to trigger (at least for me).In my case 4k@60fps always trigger the fallback (currently only for one problematic video instead of whole Firefox session), so I shouldn't have much problems testing your changes

Thank you very much for the test build Dunno how detailed feedback you want so let it be '-verbose'. I use Windows 7 x64 with disabled DWM. The E-450 APU has dual core CPU @1,6 GHz, graphics is HD6320 with 512MB (384MB by default, I use my custom unlocked bios) video memory taken from RAM. First I closed all apps possible except ESET, then I have changed values one by one and restarted after every single change. Values which didn't work - extreme shuttering

to be absolutely sure nothing will trigger the fallback. Those worked, I have not noticed the fallback. 300 instead of max int worked as well. Even at 4k@60fps there was less than 100% dropped frames (of course 4k@60fps is way too much to handle by my E-450).So this is a good thing... and here comes the bad thing, not directly related to the test build.

In Firefox builds >37.0.2 the statistics functions which counts decoded/displayed/corrupted/dropped frames as well as those checking functions if x >= y if to trigger the fallback works all the time and may increase CPU usage. Could this be the reason why video playback is not as smooth as using Firefox 37.0.2 x86?

Firefox 37.0.2 x86 does not have the video decoding fallback and related statistics functions implemented (except dropped frames counter for stats for nerds). At the beginning of the video when I switch to full screen mode I have like 20-30 dropped frames total for first few seconds. Then the playback is butter smooth (0-5 dropped frames for next 10 seconds). When I move playback forwards/backwards I have some (~10-15) dropped frames one second later, then the playback is butter smooth again.

Using your pcxFirefox44 x86 test build I had more dropped frames during normal (not moving around) playback, 1-5 frames every 2-5 seconds. That was bit weird. I have noticed the same thing using Firefox Nightly builds (but those differ way too much).

As long as video decoding fallback function does not trigger, which is very easy for me, the native Firefox 44 x64 seems to perform sightly (a little bit lower CPU usage/less CPU usage spikes) than x86 version. However I will probably never get rid of 100% dropped frames thanks to bad AMD drivers...

//edit@:

xunxun1982 wrote:1) keep the default value, dxva enabled or disabled?2) set the three about:config to 0 or 1, dxva enabled or disabled?3) set the three about:config to a larger value, dxva enabled or disabled?

I'll test a bit more with those values.

********************************************Using Firefox Nightly builds there is a (hidden?)

Dun wrote:Using your pcxFirefox44 x86 test build I had more dropped frames during normal (not moving around) playback, 1-5 frames every 2-5 seconds. That was bit weird. I have noticed the same thing using Firefox Nightly builds (but those differ way too much)

I guess XunXun got sick of releasing a new version of his Firefox every week. There is now 45.0 but I'd expect a 45.0.1 or 45.0.2 to arrive very soon. There is already a 46.0 beta available on the Mozilla FTP server. These continuous updates can be very annoying.

I'm wondering wether you're going to keep around the ability to disable signature checking. I'd very much like that because I have addons that are not signed.

They recently removed it in beta and a bunch of my addons got disabled. (Which couldn't even be re-enabled on other channels, so I had to reinstall them)(They also kept the about:config setting lying around which now does nothing on beta.)

pcx im testin firefox 48 alpha and result is direct2d and page movment with using GPU is mutch more faster then preview version in future build your you using new render firefox 48 alpha, in your builds firefox 47 for example, result is totaly more faster and perfect for this feature.