fix(player): support current signature and nsig extraction paths#1148
fix(player): support current signature and nsig extraction paths#1148chadacious wants to merge 2 commits intoLuanRT:mainfrom
Conversation
|
When parsing this video (0P4A1K4lXDo) in the browser, the following message appears: exportedVars.rawValues is not a function |
Simulating a mobile phone in the browser allows for normal parsing. |
* LuanRT/YouTube.js/pull/1148 hasn't been merged in yet but old player ids have stopped working
* chore: use PR LuanRT/YouTube.js#1148 * fix PO token validation search filters * chore: use fixed player id 01bde470
|
seems like music videos/topic channel content dont work with playback someetimes the rest work fine! |
|
when will this be merged? |
i think luan is working on a better fix himself. n-sig stuff is fine but the sig stuff isn't with this PR. |
* chore: use PR LuanRT/YouTube.js#1148 * fix PO token validation search filters * chore: use fixed player id 01bde470
* LuanRT/YouTube.js/pull/1148 hasn't been merged in yet but old player ids have stopped working
That YouTube.js commit is from LuanRT/YouTube.js#1148
|
Superseded by #1152 |
Fixes #1146
Summary
This updates player extraction to support the current signature and
nsigpatterns used by newer YouTube player variants.What changed
nsigextraction from the same URL-helper class used by the matched signature helperNotes
This was validated against multiple player ids, including:
6c5cb4f456211dc299f55c01ecc3e9a705540cb09f4cc5e4and confirmed with real playback for both standard and purchased content in downstream integration testing.
Motivation
Recent player variants no longer match the older extraction assumptions:
nsigevaluationThis patch updates the extractor and matchers to handle those cases while keeping the external decipher API unchanged.