You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Don't worry about the LIRC error. I think the parser errorm especially in Spring Training, is caused by MLB using new team codes for split-squad teams that mlbviewer doesn't have in its database. I can't remember the location of the xml that is being parsed, but I'll dig around and see what I can find.

Don't worry about the LIRC error. I think the parser errorm especially in Spring Training, is caused by MLB using new team codes for split-squad teams that mlbviewer doesn't have in its database. I can't remember the location of the xml that is being parsed, but I'll dig around and see what I can find.

Unknown team codes show up as "Unknown Teamcode" such as "Texas Rangers at Unknown Teamcode". Fixed that last season so it wouldn't result in crashes or parser errors. There are a handful of Unknown Teamcodes this Spring Training. I'll fix them as we get to them.

I checked out mlbviewer which reports revision 272 mlbviewer for 26/2, 27/2, and 28/2 report:

There was a parser problem with the listings page

And then:

No listings available for this day.

Is this because I am in the Uk?

If you ever ran the setup.py in the default branch, make sure you are calling mlbviewer.py directly in the nexdef2010 directory, e.g.

Code:

$ cd nexdef2010
$ ./mlbviewer.py

If you just run:

Code:

$ mlbviewer.py

without the "./", you might be running the default even though you are in the nexdef2010 directory.

setup.py was a good idea at the time, but now that I'm planning on maintaining branches for each season, globally installed mlbviewer is going to be a nuisance. That's why setup.py was removed from the nexdef2010 branch.

If it's not that, I'm not sure what to do except remove all mlbviewer / nexdef2010 directories, repeat the checkout, and try again.

If you ever ran the setup.py in the default branch, make sure you are calling mlbviewer.py directly in the nexdef2010 directory, e.g.

Code:

$ cd nexdef2010
$ ./mlbviewer.py

If you just run:

Code:

$ mlbviewer.py

without the "./", you might be running the default even though you are in the nexdef2010 directory.

setup.py was a good idea at the time, but now that I'm planning on maintaining branches for each season, globally installed mlbviewer is going to be a nuisance. That's why setup.py was removed from the nexdef2010 branch.

If it's not that, I'm not sure what to do except remove all mlbviewer / nexdef2010 directories, repeat the checkout, and try again.

Sorry it seems I have been checking out the wrong version by not understanding the info on page 1. The clue was the presence of the setup.py file. This version worked for me:

Do you have any strong interest in eliminating rtmpdump/flvstreamer? Both ffmpeg and mplayer support librtmp, though not be default. I've been thinking about compiling a version of mplayer with librtmp support to try to get it to work directly with mlbviewer. But if that's not of much interest to you, I probably won't bother. The nice thing about the current setup is that mlbviewer will work with most distros without the need to compile anything extra, like we used to have to do. Thoughts?

Do you have any strong interest in eliminating rtmpdump/flvstreamer? Both ffmpeg and mplayer support librtmp, though not be default. I've been thinking about compiling a version of mplayer with librtmp support to try to get it to work directly with mlbviewer. But if that's not of much interest to you, I probably won't bother. The nice thing about the current setup is that mlbviewer will work with most distros without the need to compile anything extra, like we used to have to do. Thoughts?

Never could find satisfactory documentation on how to construct a rtmp url to pass the parameters necessary for stream connection.

In any case, I certainly don't want to put forth much effort until the new service goes live. It would be a shame to figure it out just to have it not work because they changed something.

But yeah, most people are already used to the way it is now and it's already documented. If I had to change it, I'd either have to support both methods (code yuck!) or change the code, the documentation, and answer the questions about it for months in here. As long as it works, I don't want to touch it.

That's weird. Monday Nexdef branch worked for me. Today, I get an error logging in. I double checked and even changed my password on the mlb site and in my .mlb/config file. They're definitely the same but I can't access live streams. Is anyone else having trouble? The debug error I get is;

Our authentication method that we have been using for years might have finally gone away. I need to spend some time with the debuggers like HttpAnalyzer and Firebug to discover how the official player does it. I hope I have time to do that tonight because it was awful nice to watch some baseball the other night.

Looks like it was just an outage as I'm watching the Royals vs Angels game now. Good because I wasn't looking forward to writing any code tonight. I don't want to redesign anything until the new service is rolled out.

Looks like it was just an outage as I'm watching the Royals vs Angels game now. Good because I wasn't looking forward to writing any code tonight. I don't want to redesign anything until the new service is rolled out.

Phew *wipe sweat off forehead*. I'm sure figuring out and emulating a new authentication method wouldn't be easy. Let's hope it stays the same.