destreamer

This project is abandoned. It will probably not work anymore against your MS Stream tenant.

A heartfelt thank you to all the contributors over the years. You are the real MVPs.

Check out kylon's Sharedown for a SharePoint-backend implementation - https://github.com/kylon/Sharedown

---

(Alternative artwork proposals are welcome! Submit one through an Issue.)

Saves Microsoft Stream videos for offline enjoyment

v2 Release, codename Hammer of DawnTM

This release would not have been possible without the code and time contributed by two distinguished developers: @lukaarma and @kylon. Thank you!

Specialized versions

• Politecnico di Milano: fork over at https://github.com/SamanFekri/destreamer
• Università di Pisa: fork over at https://github.com/Guray00/destreamer-unipi
• Università della Calabria: fork over at https://github.com/peppelongo96/UnicalDown
• Università degli Studi di Parma: fork over at https://github.com/vRuslan/destreamer-unipr

What's new

v2.2

• Added title template

v2.1

• Major code refactoring (all credits to @lukaarma)
• Destreamer is now able to refresh the session's access token. Use this with -k (keep cookies) and tick "Remember Me" on login.
• We added support for closed captions (see --closedCaptions below)

Disclaimer

Hopefully this doesn't break the end user agreement for Microsoft Stream. Since we're simply saving the HLS stream to disk as if we were a browser, this does not abuse the streaming endpoints. However i take no responsibility if either Microsoft or your Office 365 admins request a chat with you in a small white room.

Prereqs

• Node.js: You'll need Node.js version 8.0 or higher. A GitHub Action runs tests on all major Node versions on every commit. One caveat for Node 8, if you get a Parse Error with code: HPE_HEADER_OVERFLOW you're out of luck and you'll need to upgrade to Node 10+. PLEASE NOTE WE NO LONGER TEST BUILDS AGAINST NODE 8.x. YOU ARE ON YOUR OWN.
• npm: usually comes with Node.js, type npm in your terminal to check for its presence
• ffmpeg: a recent version (year 2019 or above), in $PATH or in the same directory as this README file (project root).
• git: one or more npm dependencies require git.

Destreamer takes a honeybadger approach towards the OS it's running on. We've successfully tested it on Windows, macOS and Linux.

Limits and limitations

Make sure you use the right script (.sh, .ps1 or .cmd) and escape char (if using line breaks) for your shell. PowerShell uses a backtick [ ` ] and cmd.exe uses a caret [ ^ ].

Note that destreamer won't run in an elevated (Administrator/root) shell. Running inside Cygwin/MinGW/MSYS may also fail, please use cmd.exe or PowerShell if you're on Windows.

WSL (Windows Subsystem for Linux) is not supported as it can't easily pop up a browser window. It may work by installing an X Window server (like Xming) and exporting the default display to it (export DISPLAY=:0) before running destreamer. See this issue for more on WSL v1 and v2.

Can i plug in my own browser?

Yes, yes you can. This may be useful if your main browser has some authentication plugins that are required for you to logon to your Microsoft Stream tenant. To use your own browser for the authentication part, locate the following snippet in src/destreamer.ts and src/TokenCache.ts:

const browser: puppeteer.Browser = await puppeteer.launch({
  executablePath: getPuppeteerChromiumPath(),
  // …
});

Navigate to chrome://version in the browser you want to plug in and copy executable path from there. Use double backslash for Windows.

Now, change executablePath to reflect the path to your browser and profile (i.e. to use Microsoft Edge on Windows):

        executablePath: 'C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe',

You can add userDataDir right after executablePath with the path to your browser profile (also shown in chrome://version) if you want that loaded as well.

Remember to rebuild (npm run build) every time you change this configuration.

How to build

To build destreamer clone this repository, install dependencies and run the build script -

$ git clone https://github.com/snobu/destreamer
$ cd destreamer
$ npm install
$ npm run build

Usage

…

• both --videoUrls and --inputFile also accept Microsoft Teams Groups url so if your Organization placed the videos you are interested in a group you can copy the link and Destreamer will download all the videos it can inside it! A group url looks like this https://web.microsoftstream.com/group/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

• Passing --username is optional. It's there to make logging in faster (the username field will be populated automatically on the login form).

• You can use an absolute path for -o (output directory), for example /mnt/videos.

• We default to .mkv for the output container. If you prefer something else (like mp4), pass --format mp4.

Download a video -

$ ./destreamer.sh -i "https://web.microsoftstream.com/video/VIDEO-1"

Download a video and re-encode with HEVC (libx265) -

$ ./destreamer.sh -i "https://web.microsoftstream.com/video/VIDEO-1" --vcodec libx265

Download a video and speed up the interactive login by automagically filling in the username -

$ ./destreamer.sh -u [email protected] -i "https://web.microsoftstream.com/video/VIDEO-1"

Download a video to a custom path -

$ ./destreamer.sh -i "https://web.microsoftstream.com/video/VIDEO-1" -o /Users/hacker/Downloads

Download two or more videos -

$ ./destreamer.sh -i "https://web.microsoftstream.com/video/VIDEO-1" \
                     "https://web.microsoftstream.com/video/VIDEO-2"

Download many videos but read URLs from a file -

$ ./destreamer.sh -f list.txt

Input file

You can create a .txt file containing your video URLs, one video per line. The text file can have any name, followed by the .txt extension. Additionally you can have destreamer download each video in the input list to a separate directory. These optional lines must start with white space(s).

Usage -

https://web.microsoftstream.com/video/xxxxxxxx-aaaa-xxxx-xxxx-xxxxxxxxxxxx
 -dir="videos/lessons/week1"
https://web.microsoftstream.com/video/xxxxxxxx-aaaa-xxxx-xxxx-xxxxxxxxxxxx
 -dir="videos/lessons/week2"

Title template

The -t option allows user to specify a custom filename for the videos.

You can use one or more of the following magic sequence which will get substituted at runtime. The magic sequence must be surrounded by curly brackets like this: {title} {publishDate}

• title: Video title
• duration: Video duration in HH:MM:SS format
• publishDate: The date when the video was published in YYYY-MM-DD format
• publishTime: The time the video was published in HH:MM:SS format
• author: Name of video publisher
• authorEmail: E-mail of video publisher
• uniqueId: An unique-enough ID generated from the video metadata

Examples -

Input:
    -t 'This is an example'

Expected filename:
    This is an example.mkv

Input:
    -t 'This is an example by {author}'

Expected filename:
    This is an example by lukaarma.mkv

Input:
    -t '{title} - {duration} - {publishDate} - {publishTime} - {author} - {authorEmail} - {uniqueId}'

Expected filename:
    This is an example - 0:16:18 - 2020-07-30 - 10:30:13 - lukaarma - [email protected] - #3c6ca929.mkv

Expected output

Windows Terminal -

iTerm2 on a Mac -

By default, downloads are saved under project root Destreamer/videos/ ( Not the system media Videos folder ), unless specified by -o (output directory).

KNOWN BUGS

If you get a

[FATAL ERROR] Unknown error: exit code 4

when running destreamer, then make sure you're running a recent (post year 2019), stable version of ffmpeg.

Contributing

Contributions are welcome. Open an issue first before sending in a pull request. All pull requests require at least one code review before they are merged to master.

Found a bug?

Please open an issue and we'll look into it.