Error: Could not find player config

Question

Error: Could not find player config

deepak-jha-kgp opened this issue 4 years ago · comments

Getting the following error on a large number of devices. The issue is not device/network/video-specific, happens on any device randomly.
Error: Could not find player config
Please let me know if you need any help from me in solving this. The number of the affected devices is increasing each minute, almost 40% (around 30k) of my users seem to be affected by this.

deepak-jha-kgp commented 4 years ago

Yes

Abel Tesfaye · Answer 1 · Sat Oct 24 2020 22:21:21 GMT+0800 (China Standard Time)

I haven't encountered this error but I did not test on a lot of videos. Could you check to see if this issue is still there on the latest version?

deepak-jha-kgp · Answer 2 · Sun Oct 25 2020 20:22:06 GMT+0800 (China Standard Time)

I've tested on a few devices and rolled it out to production. Will keep you updated. Thanks.
Also, I've noticed that 404 on some videos problem is back again since version 3.4.1

Kapil Bhosale · Answer 3 · Mon Oct 26 2020 13:56:14 GMT+0800 (China Standard Time)

I am facing the same issue
Error: Could not find player config

This error never occurred in past, it started to pop up for the last 4-5 days.
Is it related to youtube-dl DMCA takedown?
If yes, what is the workaround for it?

dungle27 · Answer 4 · Tue Oct 27 2020 10:12:49 GMT+0800 (China Standard Time)

@AbelTesfaye : This issue still occur with latest version: 3.4.2

const urls = await ytdl(youtubeURL, { quality: 'highestaudio' });
=> always throw error: Could not find player config

please help us fix this issue. thank you!!!

Abel Tesfaye · Answer 5 · Tue Oct 27 2020 14:35:08 GMT+0800 (China Standard Time)

I doubt it has anything to do with DMCA. Are you encountering this on coprighted videos?

…

On Monday, 26 October 2020, Kapil Bhosale ***@***.***> wrote: I am facing the same issue Error: Could not find player config This error never occurred in past, it started to pop up for the last 4-5 days. Is it related to youtube-dl DMCA takedown? If yes, what is the workaround for it? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#42 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBF4MMWR7VY64YRZ3QI5NLSMUFQXANCNFSM4S5MCJ5Q> .

Abel Tesfaye · Answer 6 · Tue Oct 27 2020 14:36:48 GMT+0800 (China Standard Time)

Which video ids are causing this error? Could you send a couple of them?

…

On Tuesday, 27 October 2020, Abel Tesfaye ***@***.***> wrote: I doubt it has anything to do with DMCA. Are you encountering this on coprighted videos? On Monday, 26 October 2020, Kapil Bhosale ***@***.***> wrote: > I am facing the same issue > Error: Could not find player config > > This error never occurred in past, it started to pop up for the last 4-5 > days. > Is it related to youtube-dl DMCA takedown? > If yes, what is the workaround for it? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#42 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AHBF4MMWR7VY64YRZ3QI5NLSMUFQXANCNFSM4S5MCJ5Q> > . >

deepak-jha-kgp · Answer 7 · Tue Oct 27 2020 16:59:49 GMT+0800 (China Standard Time)

The issue is not video-specific. Some videos work well on some devices while throws this issue on some.
Uninstalling and reinstalling the app solves the issue for some people, for some it doesn't. Couldn't identify any pattern yet on the basis of device/video/android version/region.
Could this be because of any asynchronous calls anywhere(just thinking out loud)?

Abel Tesfaye · Answer 8 · Tue Oct 27 2020 21:03:25 GMT+0800 (China Standard Time)

I saw some issues mentioning this error on the previous version of node-ytdl-core. I'm not sure but rebasing to their latest version might fix it.

There were a bunch of new changes/moved files, so it might take a while. I'll probably review and import the new changes over the weekend.

Kapil Bhosale · Answer 9 · Wed Oct 28 2020 14:44:38 GMT+0800 (China Standard Time)

@AbelTesfaye If you have the task plan ready and some help on what to achieve.

We can try to fix it.

Abel Tesfaye · Answer 10 · Wed Oct 28 2020 16:21:45 GMT+0800 (China Standard Time)

I've previously written some sort of a "mini-guide" before, you can find it here.

During development, if you encounter any issues or have any doubts/questions feel free to send them in this thread.

deepak-jha-kgp · Answer 11 · Fri Oct 30 2020 15:16:01 GMT+0800 (China Standard Time)

@kapilbhosale any luck?

Abel Tesfaye · Answer 12 · Sat Oct 31 2020 21:21:45 GMT+0800 (China Standard Time)

Updated :)

deepak-jha-kgp · Answer 13 · Sun Nov 01 2020 17:13:17 GMT+0800 (China Standard Time)

Thanks for this @AbelTesfaye

In the latest update, I notice some of the itags are returning non-dowloadable urls(even for non-DASH and non-HLS streams).
These formats are returning a new param type": "FORMAT_STREAM_TYPE_OTF", on getInfo . I'm not sure how can we access resources in those URLs. To reproduce please try the following link
https://youtu.be/4kF6sTSgkDk itags : 160, 133
Any ideas on what is happening here?

Abel Tesfaye · Answer 14 · Mon Nov 02 2020 00:30:32 GMT+0800 (China Standard Time)

Ah yes, videos with FORMAT_STREAM_TYPE_OTF don't usually work. Most YouTube stream extractor libraries just ignore formats that have this parameter. You should filter them out as well. Maybe you should open an issue at node-ytdl-core to let them know this edge case isn't handled.

deepak-jha-kgp · Answer 15 · Mon Nov 02 2020 00:33:28 GMT+0800 (China Standard Time)

Ohh okay. In that case, the latest update reduced the number of available streams. We get OTF for 144p, 240p and 480p now.

Abel Tesfaye · Answer 16 · Mon Nov 02 2020 00:43:41 GMT+0800 (China Standard Time)

YouTube recently made some changes in their website, I guess you might need to wait a while till the node library can extract the smaller video formats, after that I can port it to react-native

deepak-jha-kgp · Answer 17 · Mon Nov 02 2020 00:47:19 GMT+0800 (China Standard Time)

I don't think it is because of changes on the youtube website. The previous version of the library is still returning usable URLs.

Abel Tesfaye · Answer 18 · Mon Nov 02 2020 00:54:08 GMT+0800 (China Standard Time)

Oh, I guess the shorter formats array is probably caused by the HLS and DASH streams. They are now grouped by url and not by itag as before (before v4.0.0)

deepak-jha-kgp · Answer 19 · Mon Nov 02 2020 00:56:59 GMT+0800 (China Standard Time)

No, the problem is with non DASH and non-HLS streams

Abel Tesfaye · Answer 20 · Mon Nov 02 2020 01:08:55 GMT+0800 (China Standard Time)

Some formats might not be getting detected properly. I'll take check it out, hopefully it can be fixed soon

Abel Tesfaye · Answer 21 · Mon Nov 02 2020 01:10:52 GMT+0800 (China Standard Time)

The last version which had all the formats was 3.4.2 right?

deepak-jha-kgp · Answer 22 · Tue Nov 03 2020 15:40:18 GMT+0800 (China Standard Time)

Hey @AbelTesfaye. Were you able to reproduce the issue? Any ideas what is happening here?

Abel Tesfaye · Answer 23 · Fri Nov 13 2020 01:44:53 GMT+0800 (China Standard Time)

@deepak-jha-kgp I found a bug that prevented DASH streams from being available. But you seem to be missing non-DASH streams so I don't think this bug affects you.

I tested several videos with both v3.4.2 and v4.0.4 and both return the same formats (v3.4.2 didn't have the FORMAT_STREAM_TYPE_OTF parameter). Could you send videos where the two versions return different formats?

deepak-jha-kgp · Answer 24 · Sat Nov 28 2020 02:20:29 GMT+0800 (China Standard Time)

This is fixed in the latest update. Thanks