Empty title when used in crontab, fine when launching directly ( Youtube )

[arthurwolf]

• I'm reporting a broken site support issue [ not sure if this is site-related or not ]
• I've verified that I'm running youtube-dl version 2019.10.29 [ just done and retested, problem initially happened on a recent but different version if that helps ]
• I've checked that all provided URLs are alive and playable in a browser
• I've checked that all URLs and arguments with special characters are properly quoted or escaped
• I've searched the bugtracker for similar bug reports including closed ones [ this is similar to https://github.com//issues/21934 but I think the crontab element makes it different, tell me if wrong ]
• I've read bugs section in FAQ

arthur@aquarelle /media/arthur/Storage/Series/AniSound : youtube-dl --version
2019.10.29

Verbose log

To show the bug I have to run the script in two different context: in my shell ( works fine ) and from cron ( titles are now missing ... ).

The script I run: https://pastebin.com/U3rJ9zy3 ( located at /media/arthur/Storage/Series/AniSound/playlist.sh ), where you can see how the command is invoqued

Stdout from running that in shell: https://pastebin.com/Qy6NUnm9
Stderr from running that in shell: https://pastebin.com/d9tcB7iZ ( able to extract title no problem, no warning about it )

Stdout from running from cron: https://pastebin.com/2MJ0m5wP
Stderr from running from cron: https://pastebin.com/jDpHHqBG ( you can see it's unable to extract title in this one, but not in the one started from a shell directly ... what ? )

Crontab:
19 21 * * * /media/arthur/Storage/Series/AniSound/playlist.sh

Description

It is perfectly capable of extracting the title when running it directly in a shell ( zsh ), but it is unable to extract the title ( warnings about it, title empty in filenames ) if running from cron. Any idea what could be causing this ? Thank you very much.

Thanks a lot for the awesome work by the way.

[arthurwolf]

Just as I was doing this, I realized my cron is executing version 2019.01.17 not the most recent. I will find why and fix it, but this isn't you guys' fault, so nevermind my idiot head.