Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Inability to download JSON metadata #18442
Comments
|
Note: I can view the video in question with no difficulty on this system |
|
I think there are multiple problems in the Kaltura extractor: the second is that no dataUrl gets produced by the extractor, so the extraction fails at https://github.com/rg3/youtube-dl/blob/9b27a78a881bceb9d62f3364399d7572e8e2be24/youtube_dl/extractor/kaltura.py#L283 . I managed to fix the first one (https://github.com/Steffo99/youtube-dl/commit/7a879c247855c8cc4c7637254cf24721b1b8904b), but I'm not able to figure out how to solve the second. |
|
Thank you for the response. I am interested in downloading the video since my granddaughter is in the choir.
Sincerely,
Hank Mike
--------------------------------------------
On Wed, 12/26/18, Stefano Pigozzi <notifications@github.com> wrote:
Subject: Re: [rg3/youtube-dl] Inability to download JSON metadata (#18442)
To: "rg3/youtube-dl" <youtube-dl@noreply.github.com>
Cc: "HankMike" <eanruig0@yahoo.com>, "Author" <author@noreply.github.com>
Date: Wednesday, December 26, 2018, 1:45 PM
I think there are multiple
problems in the Kaltura extractor:
the first is a buggy regex at https://github.com/rg3/youtube-dl/blob/9b27a78a881bceb9d62f3364399d7572e8e2be24/youtube_dl/extractor/kaltura.py#L151
the second is that no dataUrl gets produced by the
extractor, so the extraction fails at https://github.com/rg3/youtube-dl/blob/9b27a78a881bceb9d62f3364399d7572e8e2be24/youtube_dl/extractor/kaltura.py#L283
.
I managed to fix the first one (Steffo99@9cf8cb7#diff-3acbc82f402c63ae10e50e082b4f57fb),
but I'm not able to figure out how to solve the second.
I'm pinging @dstftw, since he wrote
most of the extractor; he may be able to figure it out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view
it on GitHub, or mute
the thread.
|
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.12.03. 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 ```):If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):
Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
Description of your issue, suggested solution and other information
I have inquired with Liberty University, and have been told that there is no copyright issue for the video above.
The issue is the failure to download JSON metadata as shown in the verbose log shown above.
There was an apparently identical bug report #18374, however, the youtube-dl version there was outdated.
I am running on 32 bit Lubuntu version 14.04 and Python 2.7.6
I have not tried to download from this site before, and have no idea why the download attempt failed
I had tried with an earlier version of youtube-dl, and thought the newer version would resolve the issue. However, the new version also failed, as shown in the log.
If you need further information, please let me know. Thank you