Jump to content

Mathwiz

Member
  • Posts

    1,855
  • Joined

  • Last visited

  • Days Won

    50
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Mathwiz

  1. You're not going to believe this - it downloaded and installed 1.4.8.903 again! This was with Serpent 52.9.2019.11.15 (last one before Primetime stopped working) on Win 7, with Firefox & Gecko compatibility enabled. I tried again, but this time, before I went to the Axinom site, I checked about:addons#plugins. It said "Widevine Content Decryption Module provided by Google Inc. will be installed shortly." It remained in that state until I visited the Axinom site, at which point I got a notice at the top of the screen: "Serpent is installing components needed to play the audio or video on this page. Please try again later." Then it installed 1.4.8.903 yet again. I suppose official Basilisk might fare better (although "better" in this context would be v1.4.9.1088, which still wouldn't play squat). It's probably something we'll need to figure out if/when official Basilisk catches up with Google's ever-changing DRM requirements.
  2. Sorry for the delay; it's been a busy week. I can understand MCP removing Primetime support, since the Windows versions they support have WMF and thus don't need it the way XP users do. I can confirm that under Win 7, Primetime works on Serpent 52.9.2019.11.15 (with media.ffvpx.enabled & media.wmf.enabled both set to false) just as it does under Win XP. And Widevine is visible, although I still have v1.4.8.903 for some reason. (See attached thumbnail.) Unsure why it never updated to v1.4.9. Not sure it matters now, since one needs 1.4.10 now and AIUI 1.4.10 isn't yet compatible with Serpent/Basilisk. I'll recheck with 52.9.2019.11.22 tonight, but I expect you're right: Primetime and Widevine will still be visible but Primetime won't work. IIRC @dencorso originally installed Primetime because the built-in support (media.ffvpx.enabled) produced distorted audio on some sites. I asked about this issue not long ago, but Serpent users were getting around it by just setting the Firefox compatibility settings in about:config (apparently some web sites use an audio codec Serpent/Firefox can't handle if they don't see Gecko/Firefox in the UA). BTW, thanks for the "FT-DeepDark" theme link! Only problem I see is that the "Tab Tally" drop-down menu has very low contrast with it. Know of a way to fix that annoyance?
  3. Placeholder (reserved for use further on).
  4. Guys, how hard can you make this? Facebook will nag you if it sees you're running FF 45. I recommend going into about:config, creating a new string preference called general.useragent.override.facebook.com, and setting it to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:57.0) Gecko/20100101 Firefox/57.0. @roytam1's FF 45 builds support SSUAOs of this kind, so this will tell Facebook you're running FF 57 on Win 7, and it won't nag you anymore. No need to install any browser add-ons. Please don't do this! It's not required and will only disable the above setting, ensuring you get nagged by FB to update your browser. As explained earlier, FF 45 doesn't have built-in support for h.264 video. You need to add something.... Since those browsers run on your PC, you have an sse2 processor; therefore, you could install the Adobe Primetime CDM using the instructions at the first post of @mixit's thread. I've confirmed that Primetime works with @roytam1's FF 45 builds. However, most FF 45 users probably don't have sse2 processors. Those users should instead download the @roytam1 LAV filters for their architecture (links are in the first post of his original thread), and unpack them into the same folder as firefox.exe. Either method will let FF 45 play videos. I believe other possible methods (e.g., Flash, Silverlight) are no longer supported by FB, but I may be wrong about that.
  5. I'm sorry too; profiles.ini does exist in my Serpent 55 installation: You do need to create a second profile in order for changing the setting to 0 to work, though.
  6. Slight mistake in that first quote: profiles.ini is 2 levels higher, in folder containing "profiles" folder, not in profiles folder itself.
  7. Unfortunately no; I jumped from XP over Vista to 7. But I know there are several Vista users here, including ...
  8. You may be right - you usually are - but ... ... so I think it's at least worth a try.
  9. ... which is why I added You need to install the Adobe Primetime CDM.
  10. I'm sure Mozilla had (what they thought was) a good reason to redo the rendering engine in FF 49. It's probably tied into a thousand other things. So I'd expect putting the old engine into a new browser to be a bit like transplanting a brain.... I imagine there's some way to fix it; I just don't think that's the right approach. @VistaLover's probably our best expert on these questions, though, so I'll defer....
  11. OK, so the e10s code is still there; it just doesn't work properly in the SSE-only build. Weird, but it is what it is, I guess. Wouldn't the NM28 version of the patch be your best bet, since the only difference between the 52 version and the NM28 version was the latter not enabling e10s? Yes, I would generally expect it to behave the same as the SSE2 build; bugs and all, unfortunately. Fixing it is certainly possible, but probably not a trivial task. There were many changes between FF 48 and FF 49, AIUI. @roytam1 would have to figure out which one(s) broke APZ and tiled compositing; then perhaps they could be reverted, but it depends on whether later changes depend on the ones needing reversion.
  12. Heck - just making Chrome 76 Vista-compatible would help some of us! (But please keep striving for XP compatibility.)
  13. Try findstr; e.g., findstr /rxv "\[.*\]" "<infile>" >"<outfile>" I believe that will filter out any lines that start with a "[" and end with a "]".
  14. Interesting, since the regular (SSE2) build does support E10S. Not a big deal, but curious: did @roytam1 have to remove the e10s code to make his SSE build work?
  15. I didn't miss the point; I just thought folks might like an idea of how much the license would cost if this goes through, and what they'd get for their money. It's reasonable to assume the cost for an XP license would be the same as for the Win 7+ version, or at least close to the same. After all, the answer to "would you be willing to pay?" usually depends on the answer to "how much?" Probably wouldn't get many responses without that tiny bit of info....
  16. Here are the license terms: If you need a Slack client, that seems pretty reasonable.
  17. FYI: I don't know if MCP plans to follow suit.
  18. @roytam1's browsers (at least, the UXP-based ones) do play HTML5 videos OOTB; but I'd still say they're aimed at the MSFN crowd, not the general public. For one thing, they lack installers; for another, they aren't release builds. We just had a discussion about that a few pages back. It seems you need to change your user agent. @msfntor suggested a SSUAO: For a more general solution, you could just set general.useragent.override (without adding a specific site), or in Serpent, just make sure general.useragent.compatMode.firefox and general.useragent.compatMode.gecko are both set to true and general.useragent.compatMode.version is set to the Firefox version you want to pretend to be (e.g., "52.9", "55.0", "60.9", etc.). In NM 28 there's a Firefox compatibility setting in Tools / Preferences that does the same thing. Evidently many sites need to know you're using a Firefox fork in order to send you video with the right audio codec.
  19. I realize you were asking another question, but if interested, instructions to get HTM5 video playback in SM 2.49.5 are here:
  20. Well, SM 2.49.5 (last for XP) doesn't, anyway. You either have to install Adobe Primetime or copy some DLL's from one of @roytam1 browsers. We had a bit of an adventure trying to figure this out in the original (now closed) thread, but we eventually did figure it out, and we now have two ways to play HTML5 videos in SM 2.49.5. Note: That only applies to Windows XP. On newer Windows versions SM 2.49.5 can use WMF to play HTML5 videos, but XP lacks WMF.
  21. Interesting; according to https://www.seamonkey-project.org/releases/legacy SM 2.48 seems to be on par with FF 51, whose JS engine can output SSE2 instructions, so some sites may crash it on your machine. Nevertheless, if you find out that tiled compositing works, let us know!
  22. Which SeaMonkey version do you recommend? If it's 2.49, that would imply Mozilla did eventually fix tiled compositing in at least one UXP browser, so perhaps the fix(es) could be ported to Serpent 52/NM 28. Also, if it works in 2.49, does it work in BNavigator?
  23. Well, there may be a bit of a problem: Gorhill upped the minimum required version to 55 in 1.18: It still runs OK on older versions, but to get it from AMO, you must spoof your FF version number to 55 in the URL (at extensions.update.url and extensions.update.background.url) and user agent (at general.useragent.override.addons.mozilla.org), or AMO won't offer anything past 1.17.4. Then you have to click "See all versions" and scroll down to 1.18.16 (newer versions won't run). It's probably simpler to get uBO from GitHub instead. Next, you need to edit the minimum version requirement down from 55 to the FF/Serpent version you're running. This will invalidate the signature, so you should remove that too, making it an unsigned extension. In FF 52 ESR, you then have to set xpinstall.signatures.required to false to install it. That's the default in @roytam1's builds, so you don't have to worry about that with his builds. (BTW, it's possible to install an unsigned extension in non-ESR FF builds too, but it's trickier: you have to set up some JavaScript to run at browser startup.) Edit: BNavigator is UXP-based too, so the uBO 1.18.16 should work there also, after the usual "surgery" required to install anything on that browser (including removing the signature). One more thing: Serpent 55 is different! Because it identifies as FF 55, you don't need to edit the minimum version, and AMO will offer 1.18.nn, but it will also offer newer versions that won't run! You can get around that by downloading and installing 1.18.16, then spoofing Serpent's version number as 53 so AMO won't keep offering incompatible "upgrades." Finally, after all that, you'll find that a few uBO options are greyed out. Are you really that determined to run 1.18.16? To avoid all this rigamarole, use the latest "legacy" version, 1.16.4.11, and install uBO Updater, which forces the browser to look for uBO updates at GitHub, and to only look for the latest 1.16.4.nn version. No options are greyed out in the legacy version.
  24. You may be right; unlike @roytam1's browsers, stock FF 52 ESR requires something extra, like Adobe Primetime, to decode h.264 videos on XP. But the OP said the problem was only in Instagram. If Facebook/YouTube are working it sounds like he's over the h.264 hurdle already. So, IDK; we'll see what he says, I guess....
  25. A site-specific user agent override should fix that specific issue, letting you at least download add-ons from ATN (though you'll still need to patch them after downloading as @TechnoRelic explained). Go into about:config and create a new string preference general.useragent.override.addons.thunderbird.net and set it to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5.
×
×
  • Create New...