Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210731-f94c0da-uxp-620374316-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210731-f94c0da-uxp-620374316-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210731-f94c0da-uxp-620374316-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.4a1.win32-git-20210731-61f3c7277-uxp-620374316-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.4a1.win32-git-20210731-61f3c7277-uxp-620374316-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.4a1.win64-git-20210731-61f3c7277-uxp-620374316-xpmod.7z Official UXP changes since my last build: - [no issue] Replace PurpleBlock with SegmentedVector to reduce indirect memory accesses when calling suspect (738448aa0) - Issue #1781 - Follow-up: fix debug assert in MergeMultiplicativeR() (620374316) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Issue #1875 - Rebrand Help menu item URI from FF to PM. (61f3c7277) My changes since my last build: - cubeb_winmm.c overflow fix by mixit@MSFN, Thanks! This should fix the famous 23m18s freeze bug for audio/video playback. (85149582f)

Fingers crossed. Honestly, unless they're hell-bent on flushing all memory of XP, I can't think of a good reason for why they wouldn't accept this fix. Let's hope Tobin won't have a heart attack if his so-called "MSFN hackers" manage to get official recognition. (Less name-calling, cussing, and paranoid lashing out at people who have been helping their project, and maybe they wouldn't need appeals like UXP development: it doesn't magically happen...) EDIT: If Tobin or someone else from PM reads this: sarcasm aside, I'm actually not saying this to fan the flames of conflict, the point is that it's painful to watch the upstream I believe most of us would ideally like to support and root for make that as hard as possible, and not just for MSFN members, but also a number of those in their own community.

... This is Windows XP SPx you're still talking about , official Mozilla Firefox builds NEVER supported natively the h264 proprietary decoder in HTML5 video; the decoder is patented and its native inclusion in a browser requires the browser authors pay a "handsome" fee to the patent owners (the MPEG4 consortium). Google are rich enough to afford that fee, so Google Chrome comes bundled with that decoder (AVC=h264) and hence it's capable of native h264 playback under Windows XP... When Adobe Flash Player was around, it itself came with bundled h264/aac decoders (again, because Adobe are rich), so MP4 video streams could be played, via that plugin, even in browsers (like Firefox) without that decoder built-in (and XP users, like yourself, were "happy"...). When many video sites abandoned Flash and instead started using HTML5 embedded web players, the lack of h264 decoder in Firefox rose to the surface, again for Windows XP users ONLY... Your favourite OS is deficient in this sector because the vendor, Microsoft, did not equip it originally with that patented decoder, nor a provision was made to add it in a later stage via an update... You see, Mozilla, instead of paying the h264 patent fee, decided to shift the "issue" to the OS itself, so that Firefox could make use of the h264 decoder already present in the OS (as Microsoft had already paid that fee themselves); unfortunately for you, h264 dec is only present in Vista SP2+Platform-Update-Supplement and higher - the way for Firefox to use it is through Microsoft's WMF (Windows Media Foundation) framework, so you can't bring h264 support to Firefox under XP via installing Codec Packs (these are used for DirectX media players, like WMP). The Adobe Primetime CDM (content decryption module) came with a bundled h264 decoder (patent fee paid by Adobe) and as a side-effect (its primary purpose was DRM) it can be used as an HTML5 h264 decoder in versions of Firefox that supported the CDM (off the top of my head, I think it was v47.0-51.0 officially, but v52.0 also works) - again, this is solely for XP... Regarding Roytam1 browsers: New Moon 27 doesn't support h264 natively (on any OS), but you can "install" such support by downloading an additional "package" (lav), extracting it and placing some DLLs adjacent to "palemoon.exe". The UXP-based browsers, like New Moon 28 and Serpent 52, come with a special "kludge", i.e. h264 decoding support is included in the ffvpx third party library (for XP's sake only, the UXP-based browsers can still use WMF's native decoder, if on Vista SP2 and up...). Lastly, HTML5 video decoding in a browser under XP is S/W only, so the video watching performance you get depends, among other things, on the video codec selected to begin with and your CPU; some codecs are taxing your CPU more heavily than others; the higher the resolution/bitrate/framerate, the more your CPU suffers; performance of the youtube webpage alone (which is a literal beast of JS and CSS code currently) depends on the browser engine, CPU, GPU, available bandwidth, CDN you are served from, content blockers, etc. so, while I find these "stats-for-nerds" logs to be of some substance, they have little statistical weight when compared between different setups... The Adobe Primetime CDM requires SP3 for Windows XP... His "log" mentions the av01 video codec, aka av1/AOM, do note AOM != AVC, official Firefox ESR 52 never supported that codec; the codec is, however, supported in UXP browsers via a pref: media.av1.enabled;true but decoding taxes heavily your CPU... PS: @UCyborg 's post appeared in the middle of writing this , he's right, of course, but my post expands on what he kindly posted...

PR submitted! https://github.com/mozilla/cubeb/pull/656

Thanks, man! Ran a quick test on both with MP4, seems to "work for me". Hopefully the same will be the case for everyone!

the change is caused by https://github.com/roytam1/UXP/commit/9e19d368129f7405c09fdddc75c06e1ba46ed10c to add dark-theme support. if you don't like this change and want previous look, you may manually editing <root folder>\omni.ja\chrome\toolkit\content\global\logopage.xhtml and change back the values using left side of commit above for the time being. maybe I can do something more for this. EDIT: a fix has been committed to custom tree. will become available in next build: https://github.com/roytam1/UXP/commit/d6a5a51430ca21c72debe8d7818c6da72969f56f

Sorry, it was another Firefox version... This is with Firefox ESR 52.9.0 on XP SP3:

Hi dencorso, Thank you for your donation of $25.00. We look forward to improving the forums and stay online with your donation. MSFN Team

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210731-45b8007f3-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210731-45b8007f3-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210731-45b8007f3-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210731-45b8007f3-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1190636 - Replace AutoStringVector with Rooted usage; r=njn (5d287ee81) - Bug 1190911 - Replace AutoIdValueVector with normal Rooted usage; r=jonco (b6c8ce668) (9ff3d301a) - ported cubeb_winmm.c overflow fix by mixit@MSFN, Thanks! This should fix the famous 23m18s freeze bug for audio/video playback. (2d96070f5) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1191529 - Remove JSIdArray and AutoIdArray and replace with Rooted<IdVector>; r=mccr8, r=jonco (9c0d645aa) - Bug 1083752 - Calling Map/Set/WeakMap (without new) should throw. r=Waldo (bd0b31a3d) - Bug 1142279 - DataView should require 'new'. - r=efaust (97ef8ba02) - Bug 1155838 - Fix a build warning on windows; r=till (f9af00bff) - Bug 1129313 - Part 2: self-host MapIteratorObject#next(). r=jandem (b30734a0b) (11b532c45) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1150717 - Test request with no params in the Network Monitor. r=brings (a60e9e8d9) - Bug 1168077 - Remove remaining spidermonkey js specific syntax from browser/devtools; r=miker (c98f20c30) - Bug 1168125 - Fix existing tests, r=jsantell (b1dfa101e) - Bug 1169439 - Pull out marker definitions into its own file, and move formatter and collapse functions into marker-utils. r=vp (17eb24ab3) - Bug 1173654 - Part 1: Add logging methods for SurfaceType and ImageFormat. r=Bas (22f2fa019) - Bug 1169125 - Part 1: Allow sending any DataSourceSurface-backed image over WebRTC and fix failure cases. r=bwc (1fb0def92) - Bug 1169125 - Part 2: Use UniquePtr for scoped delete of yuv data in MediaPipeline. r=bwc (cdb79e201) - Bug 1173654 - Part 2: Use namespaces in MediaPipeline.cpp. r=bwc (311696260) - Bug 1173654 - Part 3: Attempt to GetDataSurface() and convert if sending pure I420 fails. r=bwc, r=jesup (58520b820) - Bug 1173654 - Part 4: Add detailed logging and asserts to MediaPipeline::ProcessVideoChunk. r=bwc (ba08ae5bc) - Bug 1155089 - Part 1: Reset |TrackID| for MediaPipelineTransmit::PipelineListener on replaceTrack(). r=bwc (304fb8703) - adapted Bug 1142688 - Wait for actual audio data on remote side before checking audio sanity. r=jesup,padenot (479f6356c) - Bug 858927 - Move the mozilla::TimeStamp into mozglue. r=glandium (751938e09) - Bug 1166559 - Add documentation for ProfileTimelineMarkers from a dev tools perspective. r=fitzgen (ed1563dfb) - Bug 1141614 - Part 4: Expose cycle collection markers in the devtools frontend; r=jsantell (2eb830de7) (45b8007f3)

Operating system makes a HUGE difference on that test. @IXOYE is on XP SP2. Warnings on XP can be 3 to 6 times higher on 7, haven't tested anything in 10. I know it is labeled as a "browser audit", but it says more about your operating system then it does about your browser.

AFAIK, Firefox itself only ever used Windows Media Foundation (Vista+) for AVC, which is not available on XP, hence you need a plugin on that OS, but otherwise, Firefox 52.9 can do AVC without a plugin.

Most of the complaints I've seen have been on their support site though, not at Bugzilla where the devs would see them first hand. And there never seemed to be that many people joining in and confirming the bug. The point @grey_rat kindly reminded us about would also definitely play a role in this. In any case, far be it from me to absolve Mozilla from its responsibility, I've mostly just been meaning to point out that there have been interfering factors along the way that don't (in this case) necessarily involve full-on Google agents within Mozilla's ranks. Thanks! After I found that it didn't matter if I used an online stream or a local file, I just downloaded a a random longish file VP8 WEBM video from search results, which happened to be this one. As you said, you won't be able to stream it because FF 15.0 can't handle the current HTTPS ciphers, but you can play it locally. (I've got to say, by the time I was finally done with the fix, I was totally haunted by the faces of those debate participants! ) Sure thing, go for it , but maybe wait until people have had a chance to play with your builds? I'd thought of this too, but I didn't want to bring it up before it's been confirmed that the fix works well for everyone. But there'd definitely be some nice irony in getting this XP-specific fix into the current Firefox code via their stand-alone cubeb lib, after they took great care to remove all traces of XP from their main tree! That's an excellent point! It's been a long time since I switched from Flash to the Primetime codec for H.264, so Mozilla's messing around with H.264 and especially its support on XP has faded from memory a bit. Yeah, those watching MP4/H.264 stuff using the Flash player wouldn't see this 2x:xx issue (I think - never tested for it specifically) and wouldn't have anything to report until maybe the last few XP-compatible Firefox versions, by which time Mozilla barely cared about XP any more. And VP8/9, which Firefox supported natively, were mostly available on Youtube, hence the strong association with the site for a long time.

Nobody can ever be 100% safe from anything.

I will likely use Windows 8 until the late spring 2024. During that time (between October 2023 until I pull the plug), I hope that Edge is at least supported, so that some sort of current browser is used. Beyond that, my tentative plan is to migrate to an iPad Pro and Bluetooth keyboard combination. Major strides are taking hold in order to make tablets (well iPads) more productive as a PC replacement. I hope that in three to four years from now, those strides will appreciate and make the iPad a suitable make shift workstation. As time goes by, there is less that I need a dedicated workstation for. If I wanted to, I have an older Windows XP x64 workstation that I could use (disconnected from the Internet of course) as an audio editing workstation. That was my old HP xw8200 PC. Time will tell.