MLB.TV in Linux

daftcat · 04-11-2008, 04:00 PM

Quote:

Originally Posted by Theophile

Daftcat,

Could I get a working copy of your mlbrecord script? I'd like to try out the "DVR" method tonight with the Sox/Yanks game.

It's not really even alpha but I'll let you test this. You only, though. (Okay, maybe jkr too....)

I don't really have as much time to develop as it looks like I do and it might hit the skids fast soon. So I'd like to release an alpha to an inner circle of users on Monday but I probably won't have a general release until the end of the month. That should give jkr some time to nail down the networking code.

Theophile: check your email.

daftcat · 04-11-2008, 04:09 PM

Quote:

Originally Posted by jkr

Color is great for the interface. Splash screen sounds fine to add, but as with other things, I would say there should be an option to turn it off (splash=0). I would go crazy if I had to deal with the emacs splash screen every time I opened it up to edit something.

As a promise of cool stuff in the future, though, and speaking of interfaces, I just wanted to send you to a link of about 5 minutes worth of work, using wxPython and the already existing classes. Great thing about this gui library is that it's already cross-platform (much more so than python-curses). This is just an example, but I think some people might like this. And if anyone is actually good at programming wxPython, you know, make yourself heard.

http://www.columbia.edu/~jr2075/xmlbviewer.png

Daftcat-- I'll add those bits to the file soon. Things sound great. I might not get the chance to update the official script, so in the next day or two, I'll set up an svn repos on sourceforge, and people can update, branch, etc. to their hearts' content.

I don't know wxPython, but as of a week ago, I didn't know python either. I'll look at wxPython but I was also thinking of a tk gui. Though honestly, my particular setup loves console apps and despises gui's.

Of course, the splash would be disable-able.

I'd rather you focus your effort on getting the library and api settled and separating the engine from the gui. I know there will be folks who will develop gui's once the engine is in place. I, for one, will probably be forever tinkering with the curses gui. Though I wouldn't mind scripting support or a cli like:

mlbcmd video 800 4-11-2008 kc

to play the 800k stream today for whatever game the Royals are playing. This is something I could develop once the engine and API are separate from the gui and "import"-able.

daftcat · 04-11-2008, 04:18 PM

Another thing I was thinking of looking at the tv listing is supporting all the entries including condensed games and top plays. This might be something better suited for a real gui where screen real estate isn't so limited. But this would also require engine support in filling out the tv listings dictionary and supporting different methods for getting the game id. Does python support method overloading? e.g.

gameStream(email,pass,speed,blackout)

and

gameStream(email,pass,feed,speed,blackout)

It would be good to get a project page up somewhere so we can wishlist this and determine what and what shouldn't be supported by default and what will have hooks for future development or outside contribution. Like if the engine supported parsing top play listings, someone else could contribute the code to select them.

daftcat · 04-11-2008, 06:18 PM

Looks like we have a new status code. According to the Scoreboard page, it looks like 'IP' is being translated to 'Delayed Start - Rain'

mr_e_uss · 04-11-2008, 08:45 PM

Thanks to everyone here, I am finally enjoying MLB TV on Ubuntu.

My latest problem is this: when the video is streaming (using the default "xterm -e mplayer" settings in mlbviewer.py), the video display is very small. I can toggle mplayer back and forth between fullscreen and not fullscreen, but even in fullscreen mode, the video itself stays the size of the original small mplayer window. In other words, in fullscreen mode the mplayer window becomes fullscreen, but the video remains the same small size -- the rest of the fullscreen window is black. Any ideas?

Thanks...

jkr · 04-11-2008, 09:42 PM

mr_e_uss:

Sounds like you are using the x11 video out instead of xv, which allows scaling.

Try adding "vo=xv" to ~/.mplayer/config, or just add "-vo xv" to your custom video_player command.

Also, you'll see that the 4:3 games still have black bars on the side. You can either crop (it's discussed earlier in the thread) or make use of mplayer's panscan feature. It should be bound to e and w. Press e a few times to make the image fill the screen.

daftcat:

I made a sourceforge project page. It will take them a day or two to approve it. Then when I upload the separated-out code for the libraries and the player as it now stands, I'll open up access. I think I'll need your email to register you, though. Could you mail me that?

anyone else:

I know other people have hacked around on this as well. If anyone else wants svn access get in touch. Otherwise, you can also just send individual patches in.

Best,
Jesse

mr_e_uss · 04-11-2008, 09:50 PM

Thanks jkr.

Unfortunately, after adding the vo=xv line to ~/.mplayer/config, this is what I see on the mplayer console:

[VO_XV] It seems there is no Xvideo support for you video card available.
[VO_XV] Run 'xvinfo' to verify its Xv support and read
[VO_XV] DOCS/HTML/en/video.htm#xv!
[VO_XV] See 'mplayer -vo help' for other (non-xv) video out drivers.
[VO_XV] Try -vo x11

Argh...

hanophix · 04-11-2008, 09:52 PM

I'm getting this.

Traceback (most recent call last):
File "/home/nick/Desktop/mlbviewer2.py", line 570, in <module>
datadct['user'],
KeyError: 'user'

jkr · 04-11-2008, 10:00 PM

mr_e_uss:

Quote:

Unfortunately, after adding the vo=xv line to ~/.mplayer/config, this is what I see on the mplayer console:

[VO_XV] It seems there is no Xvideo support for you video card available.
[VO_XV] Run 'xvinfo' to verify its Xv support and read
[VO_XV] DOCS/HTML/en/video.htm#xv!
[VO_XV] See 'mplayer -vo help' for other (non-xv) video out drivers.
[VO_XV] Try -vo x11

So what happens when you run xvinfo?

hanophix:

What version are you using? Sounds like you probably didn't switch to the new format of the config file (use EQUAL ("=") instead of COLON (":")).

mr_e_uss · 04-11-2008, 10:04 PM

Here's what xvinfo tells me:

X-Video Extension version 2.2
screen #0
no adaptors present

hanophix · 04-11-2008, 10:06 PM

JKR Got it working...but getting an error when I click a game
mplayer doesn't start and error appears "I'll be more useful in beta"

ARCHIVED GAMES APPEAR TO WORK

jkr · 04-11-2008, 10:10 PM

mr_e_uss

Well that's a problem with your Xorg config or your video card driver. You could play around with other outputs ("mplayer -vo help" to see a list, maybe try -vo sdl), but really you should do some googling on your video card. Which card do you have, and which distribution? (If you don't know the card, run lspci and look for something with "Graphics" in the name.)

daftcat · 04-11-2008, 10:13 PM

jkr

have you thought about using urllib.urlencode() instead of clientform() and/or saving the cookie to the disk using cookielib.LWPCookieJar()?

I'll give something a go this weekend. I'd really like to get to the bottom of the concurrent sessions issue.

I'll also have some better error handling for you.

mr_e_uss

What video card are you using? Maybe you need to find a third-party driver for it that will support xv?

I'm wondering if the -vo sdl might help (if you have sdl installed.)

mr_e_uss · 04-11-2008, 10:13 PM

lspci says (among other things):
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400

Theophile · 04-11-2008, 10:17 PM

daftcat,

Thanks for mlbrecord. It worked like a peach in every instance. I tested it out on some archived games and it caught them all. Then I used it to build myself a 30-minute buffer for the Sox/Yanks game, the 800k feed. I didn't have a single hiccup the entire time.

Except when mplayer and xine attempt to seek beyond the end of the stream, they both die ignominiously. But that's a problem with the media.

jkr,

The gui looks good! Looks like it has real potential for supporting a lot of features. Thanks again for getting the ball rolling on this project. It already far exceeds anything I could have anticipated!