kenichi512
commented
6 years ago I think this has to do with the change to HTML5. The "CSRF token" error no longer appears after updating my coockies a few days ago. In the command lines I never add --write-sub or --embed-subs (because by default the program did not make hardsub and there was no need to add an instruction for that), but now I have the same problem with the hardsub, that did not happen before the erorr of the "CSRF token" appeared at the end of July. I do not know, but I think that now we need an instruction to force the non-authorization to have the video with harsub.
TxBase
Please follow the guide below
xinto all the boxes [ ] relevant to your issue (like this:[x])Make sure you are using the latest version: run
youtube-dl --versionand ensure your version is 2018.09.10. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.Before submitting an issue make sure you have:
What is the purpose of your issue?
The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue
If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the
-vflag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):Description of your issue and other information
For easy reproduction I choose a short video as representation and keep the args as simple as possible. In general there are 2 things, which maybe belong together. 1.) unwanted output. After some tests I recognise, that the output belongs to ffmpeg. In the last stable version (ffmpeg-4.0.2-win64-static) it occur ever. In the last nightly version, I used for this log, it occur only in case of problem 2. 2.) the video contains hardsubs, which are unwanted, especially in combination with softsubs. I think this issue is related to the new HTML5-player on which CR is developing. See http://www.crunchyroll.com/forumtopic-1024184/updates-on-the-new-crunchyroll-video-player since only 50% get the new player, the reproduction isn't deterministic.
Possible solution
For now I recreate a new cookie related to the old player, but I don't realy know, where the information of the player is stored. Since now it work. My old cookie, which was created before the change, still use the old player (confirm in browser), but it have nondeterministic behavior in youtube-dl. I don't know, what is the cause.
PS: On closer consideration the only values in my cookie, which was changed, was: