Most unfortunately, I can reproduce ; and it isn't only the Adobe Primetime CDM affected, as reported by @dencorso, but also the Widevine CDM too, which is installed and visible under Vista+; Widevine CDM v1.4.9.1088 is currently broken since August 13th 2019, due to Google changes - effort is underway by MCP to restore Widevine support in official Basilisk ( see here ), which is currently hitting a deadend, but any success won't benefit Vista users of Serpent, as updated Widevine DLLs don't run on Vista and require Win7+; still, having a working implementation of WV on Serpent would certainly benefit St users on Win7+
I normally don't have Adobe Primetime CDM (APCDM) installed in my Serpent 52 profile, but to humour @dencorso I did correctly install it (v17) and made sure I disabled the other h264/aac decoders:
media.wmf.enabled;false (Vista's native WMF decoder)
media.ffvpx.enabled;false (Serpent's bundled FFmpeg decoder)
while I made sure media.gmp.decoder.enabled;true (APCDM's decoder)
Widevine CDM (WVCDM) v1.4.9.1088 is also correctly installed.
Extended testing reveals that:
A. 2019-11-15 Serpent win32 build is the last good build where:
1. WVCDM appears installed in both "about:addons => Plugins" and about:plugins :
2. APCDM's decoder properly works for MP4 HTML5 video; e.g., first test clip on
https://tekeye.uk/html/html5-video-test-page
(1: HTML5 MPEG Video Test)
B. By simply updating to the next Serpent 52 build, 2019-11-22, one discovers that it's the first bad one, since:
1. WVCDM magically vanishes from both "about:addons => Plugins" and about:plugins :
2. APCDM, while still present in both "about:addons => Plugins" and about:plugins, simply quits functioning as a h264/aac decoder (as reported by dencorso):
@Mathwiz : Could you be so kind as to confirm my tests, preferably on Win7 where Widevine CDM is visible (thanks in advance ) ?
======================================
Now, examining more closely related code, MCP did remove APCDM support in official Basilisk in UXP #1259 ; the bulk of the patches would have landed in the 2019-11-15 build, as per
but you did revert those (more accurately, did not apply at all in your custom branch), as per
... furthermore, the reversion has been successful, as the 2019-11-15 build is, according to my analysis above, the LAST GOOD one
The MCP devs did not revisit issue #1259, except for
https://github.com/MoonchildProductions/UXP/pull/1293
(Adjust Widewine strings after removing Adobe Primetime support) and thus
https://github.com/MoonchildProductions/UXP/commit/36c81a9
This would have normally landed in the 2019-11-22 build of Serpent 52:
while you did not technically revert that, you added your own version with a slightly modified code:
https://github.com/roytam1/UXP/commit/e50e93c
Since I'm not a code wizard by any stretch of the imagination, I can't be certain that the culprit for the issues reported here lies within that commit of yours... What is absolutely certain is the offending changeset(s) lives inside the changelog (in your custom UXP branch) between Serpent build 2019-11-15 and build 2019-11-22 ; please, at your discretion, investigate further ... Because, while you took the extra effort to keep APCDM support inside Serpent 52 alive (against MCP's agenda), not only did we end up with a crippled APCDM installation, but also Widevine took an unexpected hit and did a disappearing act...
Thanks for your time reading this long report, hopefully you'll get it sorted out!
Many thanks, as ever, for providing your forks to the community!
Best regards