Downloading MMS streams in Linux (CentOS, Ubuntu, Debian, Fedora...) with mmsclient

By -
Hello!

So I was looking into solutions for saving a MMS stream on my server. My connection at home isn't fast enough so I cant watch most of the streams, I'd rather have those downloaded by my dedicated server and then I download the file off my server.

I first looked into mimms: http://savannah.nongnu.org/download/mimms/
Unfortunately it was written in Python and I was missing Python 2.5. After struggling with my system I couldn't get it to work (missing dependencies one after the other).

So I kept looking and I found mmsclient.
The official website: http://ole.tange.dk/projekter/kontroversielt/www.geocities.com/majormms/ (actually a copy of the site, which was hosted on Geocities previously).
Scroll down to the bottom of the page where it says "mmsclient". You will find a link to download it. I've mirrored the link here just in case: http://gbatemp.net/up/mms_client-0.0.3.tar.gz

To install mmsclient, follow these simple steps:
1) Download the package:
wget http://gbatemp.net/up/mms_client-0.0.3.tar.gz
2) Extract it:
tar xzvf mms_client-0.0.3.tar.gz
3) Configure, make, make install:
cd mms_client-0.0.3
./configure
make && make install

That's it! Now you can download mms streams. Just use the "mmsclient" command, followed by the URL of the stream you want to download:
mmsclient mms://example.com/stream.wmv
Additionally, you will notice that it outputs a lot of data to the command line window. To make it quiet, add >/dev/null at the end:

mmsclient mms://example.com/stream.wmv >/dev/null

Enjoy your downloaded streams!

Comments

Unknown said…
hi thanks for this tutorial, however on centos6 I get:
host : >blah-de-blah/file.wmv<
file : >/4D885E5457A8C701.wmv<
creating output file '4D885E5457A8C701.wmv'
port: 0000db06
socket open
request: Connection refused

any ideas?
Sat Nov 22, 06:52:00 PM
packers movers ahmedabad said…
Nice information. Thanks for sharing this. packers and movers Allahabad
Wed Apr 22, 05:41:00 PM
Post a Comment

Popular posts from this blog

Dealing with Nginx 400 Bad Request HTTP errors

By -
Today I'll write about something I experienced personally, on my websites. Some visitors reported that they were getting a "400 Bad Request" Nginx error randomly when visiting pages. And when they start getting that error, they can't access the site anymore: it'll output the same error no matter the page, until you "clear your cache and cookies". The error is easily understandable and is likely to be caused by... too much cookie data. Every time a visitor loads *any* page/content/file of your website, it sends the cookie data to the server. Cookie data is sent under the form of 1 header line starting with "Cookie: ". Basically, Nginx by default is configured to accept header lines of a maximum size of 4 kilobytes. When a line in the headers exceeds 4 kilobytes, Nginx returns the '400 Bad Request' error. Cookie data sometimes gets big, so it causes the error. It particularly happens on forums like vBulletin, Invision and others...
Read more

How to set up a simple mail server on Debian in 5 easy steps

By -
Image
This tutorial will take you through the steps of setting up and configuring a simple mail server (SMTP, POP3, IMAP) on Debian/Linux. The instructions will be given for Debian, but they can be adapted quite simply to other distributions such as Ubuntu and other Debian-based OSes; you could even pretty much follow the same steps if you're running Red-Hat based systems such as CentOS or Fedora. I can promise you that this is as easy as it gets, provided you have correctly verified and validated the pre-requisites step. What we will achieve in this tutorial We will be setting up a simple email server with the following basic functionality: The server will be able to both send (via SMTP) and receive emails (via IMAP and POP3) optionally with SSL functionality User accounts and  passwords will be encrypted and stored in a simple text file , which can be managed easily with a text editor. It will support a potentially infinite amount of mailboxes over one or more domains As...
Read more

Nginx error 413: Request entity too large Quick Fix

By -
A quick article today about a common error people encounter with Nginx: the infamous 413 Request Entity Too Large HTTP error. I had the problem myself just yesterday on one of my newly configured servers, so I thought I'd make a blog post about it to make sure I don't forget this next time. Error 413: what does it mean? This error shows up when a visitor sends too much data in the HTTP request. This is normally caused by: • an overy large file being uploaded by the visitor • more generally too much POST data being sent by the client The fix is as simple as setting a directive in your Nginx configuration, read on below. How to fix it? client_max_body_size To fix this, you need to increase the value of the client_max_body_size directive. This directive defines the maximum amount of data Nginx will accept in an HTTP request. By default this value is set to 1 megabyte, meaning if you attempt to upload a file larger than 1 megabyte you'll be getting an  Error ...
Read more