MLB.TV in Linux

berni42 · 02-28-2011, 02:12 AM

Quote:

Originally Posted by mkomko

You have to check out the nexdef2010 branch, not the "default" mlbviewer directory.

Sorry but same roblem with the nexde2010 "There was a parser problem with the listings page". I noticed there is a log file in the ~/.mlb directory. This is showing:

WARNING:root:Could not connect to LIRC, retrying: [Errno 2] No such file or directory
LIRC not initialized

Any clues? I am using Debian Squeeze.

Theophile · 02-28-2011, 11:21 AM

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.

Theophile · 02-28-2011, 12:05 PM

I poked around in the code for a while, long enough to confirm that I really don't know what I'm doing. But I did turn on debugging in order to get this error:

Code:

Traceback (most recent call last):
  File "mlbviewer.py", line 1545, in <module>
    curses.wrapper(mainloop, mycfg.data)
  File "/usr/lib/python2.6/curses/wrapper.py", line 43, in wrapper
    return func(stdscr, *args, **kwds)
  File "mlbviewer.py", line 207, in mainloop
    raise Exception, detail
KeyError: '2011'

daftcat · 03-01-2011, 02:40 AM

Quote:

Originally Posted by Theophile

I poked around in the code for a while, long enough to confirm that I really don't know what I'm doing. But I did turn on debugging in order to get this error:

Code:

Traceback (most recent call last):
  File "mlbviewer.py", line 1545, in <module>
    curses.wrapper(mainloop, mycfg.data)
  File "/usr/lib/python2.6/curses/wrapper.py", line 43, in wrapper
    return func(stdscr, *args, **kwds)
  File "mlbviewer.py", line 207, in mainloop
    raise Exception, detail
KeyError: '2011'

That's fixed in the latest revision released a few days ago. I think it's 272 on the nexdef2010 branch.

daftcat · 03-01-2011, 02:44 AM

Quote:

Originally Posted by Theophile

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.

daftcat · 03-01-2011, 02:49 AM

Quote:

Originally Posted by berni42

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.

berni42 · 03-01-2011, 07:44 AM

Quote:

Originally Posted by daftcat

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:

svn co https://mlbviewer.svn.sourceforge.net/svnroot/mlbviewer/branches/nexdef2010

Note: the mlbviewer.py file needs execute permission.

Theophile · 03-01-2011, 06:19 PM

daftcat,

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?

daftcat · 03-01-2011, 11:23 PM

Quote:

Originally Posted by Theophile

daftcat,

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.

rashley · 03-02-2011, 01:28 PM

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;

Traceback (most recent call last):
File "nexdef2010/mlbviewer.py", line 1545, in <module>
curses.wrapper(mainloop, mycfg.data)
File "/usr/lib/python2.6/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "nexdef2010/mlbviewer.py", line 1239, in mainloop
u = g.url()
File "/home/rashley/nexdef2010/MLBviewer/mlbtv.py", line 1281, in url
self.workflow()
File "/home/rashley/nexdef2010/MLBviewer/mlbtv.py", line 1057, in workflow
self.login()
File "/home/rashley/nexdef2010/MLBviewer/mlbtv.py", line 1037, in login
raise MLBAuthError, self.error_str
MLBviewer.mlbtv.MLBAuthError: Login was unsuccessful.

Theophile · 03-02-2011, 03:46 PM

Yes, getting that too.

kweisen · 03-02-2011, 06:29 PM

My first try this spring, got the parser error, upgraded svn, now seeing this: (on nexdef branch)

Traceback (most recent call last):
File "mlbviewer.py", line 1545, in <module>
curses.wrapper(mainloop, mycfg.data)
File "/usr/lib/python2.6/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "mlbviewer.py", line 1239, in mainloop
u = g.url()
File "/home/kim/nexdef2010/MLBviewer/mlbtv.py", line 1289, in url
'sessionKey': urllib.unquote(self.cookies['ftmu']),
KeyError: 'ftmu'
kim@kim-desktop:~/nexdef2010$

daftcat · 03-03-2011, 03:35 PM

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.

daftcat · 03-04-2011, 12:26 AM

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.

mkomko · 03-04-2011, 12:46 AM

Quote:

Originally Posted by daftcat

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.