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.
Feature request: Screenwave support #7039
Comments
|
Thanks for your thorough research. However, youtube-dl already supports screenwavemedia links which means that only the first two steps need to be added. My PR (linked above) adds support for SF Debris. Can you test it please? |
|
Looks good to me on Python 3.4/Ubuntu. I don't intend to test Python 2 because as far as I'm concerned it's there purely for backwards compatibility. |
|
Screenwave is already supported by youtube-dl and http://sfdebris.com/videos/animation/transformerss1e01.php is processed by generic extractor just fine. |
|
Is there a chance that one of these two extractors could be updated to work with a page (coincidentally also at sfdebris.com (via channelawesome.com): http://channelawesome.com/the-terminator-sf-debris/ ? While it works for the first video on the page, the second video is, seemingly, completely ignored. I ended up grabbing the download link for the first video via "youtube-dl -g", getting the video id from the page, changing the retrieved download link with the new video id, and then having wget grab the second video with the new url. |
SF Debris has switched from Blip to Screenwave, so I cannot use youtube-dl on it anymore. Fortunately the Javascript is reasonably easy to read; the mechanism for retrieving video URLs is as follows.
http://sfdebris.com/videos/animation/transformerss1e01.phpas a test case).http://player[0-9]+.screenwavemedia.com/player.php?id=[^']+.vididin theattributesmap.http://player[0-9]+.screenwavemedia.com/player.js.sourceslist insidejwoptions.playlistcontains the video URLs at decreasing levels of fidelity.thisObj.options.videoserveris a reference to an object declared earlier in the file;playerVidIdis the value ofvididwhich was recorded in step 4.Some of this errs on the side of trying not to take advantage of what may be coincidences and trying to minimise the possible necessity of future maintenance. For instance,
vididrecorded in step 4 is the same as theidparameter of the script whose URL is matched in step 2.playerserver,player2.screenwavemedia.com, at the moment.