if you can figure out how to get rtmpdump to compile on a mac with daftcat's patch, it will work. please let me know if you manage to do that. the nextdef functions work perfectly on a mac (leopard) running mlbviewer

That is your problem, I don't use a mac.

No, the reason why rtmpdump isn't compiling on Mac is because it's a different byte order than Windows/Linux. I mean you could always try but I don't think it's going to work at all. Even on the same hardware platform there is a bit of kernel magic necessary to make bsd run linux executables. Mac is essentially more BSD than it is Linux.

Hey, the issue was mplayer. I fixed it and it is working with everything

I had a wierd config option (that I didn't change) that wouldn't let it start. On top of that, I had compiled it without xv/x11 support, so it wasn't opening anything
I have no idea how I didn't notice that.

I recompiled it and it is working great. Except it won't scale the game to fullscreen with -fs. It plays it in a small window with the whole screen black.

Home stream as well.

Others that will be available in 3000K according to NexDef:

Angels-Mariners, home and away.
Mets-Dodgers, home and away.

The only two games I wasn't able to check (with the script that doesn't exist ) were the two I'm blacked out from: Giants and A's.

I think they are trying to quietly reintroduce the 3000K streams as beta tests. Perhaps with a controlled re-introduction, they can have fewer problems than they did at the start of the season.

That sounds like it's not using xv.

I have no idea what x11 would look like but it's not recommended. I also have no idea how xv is going to look over VNC. Once you can confirm that xv is properly compiled in and it is being selected (for this, you'll have to turn off -really-quiet and watch the output (or use the test file you create with soapevent.py), you can add "-vo xv" to your video player to force it to select xv. Finally, you might have to tune the MTRR or otherwise do some system/driver tuning according to the instructions in the Video Output section of the MPlayer documentation.

I recommend using mlbviewer from now on since it's a lot more customizable than the test tools. Also, if you have confirmed that you can launch an xterm on his display from your ssh session, then you can use mlbviewer from ssh to launch a game on his screen.

Chances are good that mplayer launched remotely in this fashion will look better than mplayer launched from a vnc session. You'll need to call up granddad to confirm the results. In other words, mplayer uses video resources that vnc may not be able to forward so you might not be able to trust vnc once you get Xv video output working correctly.

I think I figured out why I don't like the 3000K stream. I had this forehead-slapping moment and realized my laptop doesn't support 1280x720. It only goes up to 1024x768 so the video has to be down-squished (*very technical term!) to fit the screen.

i see some people have made some progress mlbviewer to work with vlc. i cannot not seem to get this working on my os x with the newest nightly build of vlc. what are you using in config to set this up?

also, do i need some additional codecs? i downloaded some when i installed mlbviewer, but i think they were specifically for mplayer.

as far as the streams go, i actually missed a call this afternoon from mlb level 3 support. they said they will call again tomorrow, so perhaps we will finally know what went on with the 3000k feed. but, i am happy to see that it made a limited appearance this evening, even if it wasn't for my team's game.

I'm really hating vlc. They checked in a patch over the weekend that reverted a patch which loosened up the xv-xcb requirement. Now configure won't run because it wants xv-xcb >= 1.1.90.1. Searching google, I can't even figure out where xv-xcb comes from. Grr! I also still don't know where it picks up its ffmpeg so even if I re-compile yet again (which takes entirely too long), I don't know that it will find the correct codecs.

So the one or two of you that have figured out how to get vlc working with mlbviewer, please speak up and report back what you did.

The rest of you, I recommend trying out a nightly build if you want to see if vlc will work.

Tried it... I still get the weird errors like before but it loads and appears to work after that -- jump to innings is completely functional. Thanks so much!

Which weird errors are you still getting?

We fixed the backlight right?

The bandwidth is going to have to be 800K or your housemates will complain (and you won't be able to do anything else with the network.) By the way, if you go back to the mlbviewer window after about 10 seconds, you'll see a stream selection menu where you can manually select 800K if NexDef ignored the max_bps setting. I suspect that many people have -fs in their video_player line to fullscreen it and thus they never see this stream selection window since it appears after mplayer playback.

The games always start with a few seconds of molasses and then it cruises right along at the correct pace. Pausing the playback for a second and then resuming (space bar in mplayer, not the mlbviewer window) often helps with the molasses but it will also works itself out anyway.

Are there other weird errors you're still encountering?

I love jump to innings. I never have to wait for a game to complete to start watching it from the beginning. That's what I think of when someone says DVR, not the pause/rewind bit. It's baseball when it's convenient for me. I may not be home at 5 when the KC game starts, but I know whenever I do get home, that's first pitch time for me.

I checked on several different games, NYY, BOS, KC, and it looks like the 3000K stream is universally restored (at least the first four or five games I looked into.)

Hey, thanks so much, I have gotten it running over ssh and over vnc.

The problem /is/ That his computer doesn't have xv output, because we are using a vesa driver because the mga one screws with his display (crazy artifacts make the screen unreadable)

However, recently, I have been getting

$ mlbviewer.py
Traceback (most recent call last):
File "/usr/bin/mlbviewer.py", line 1501, in <module>
curses.wrapper(mainloop, mycfg.data)
File "/usr/lib/python2.5/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/bin/mlbviewer.py", line 388, in mainloop
+ len(coveragetoggle.get(cfg['coverage'])) + 2
TypeError: object of type 'NoneType' has no len()


I tried setting coverage=home, coverage=away, and just coverage= in the config, but all of them give the same error. (It says error parsing listings). This is for mlblistings.py and for mlbviewer.

I thought we went through this before. Maybe it was someone else. The coverage part of that error is a red herring. I suspect you have the speed set to something other than 800 or 400. Set the speed to 800 (speed=800) and remove any coverage= line. Video follow overrides this setting anyway (and 's' can change it, so it's really not necessary to set it the config file anymore.)

The reason for the speed parameter is mostly historic but it is still used to some extent with the non-NexDef code.

If this doesn't clear up the issue, please post your configuration file again (without the user/pass.)

You could try the pan/scan (zooming) feature of mplayer to fill the screen but I'm not sure that the vesa driver supports it. I think it's 'e' to zoom in and 'w' to zoom out. That might result in some distortion though due to the aspect ratio. This is really someone else's department so forgive me if I misquote here. But I believe screens are usually 4:3 whereas movies and most of the games are broadcast in 16:9 (which is why it has that letterboxed look of widescreen movies.) Anyway, that's the best I can come up with. So you looked at the mplayer documentation and there's no way to get Xv working for his graphics card?

Let me know how it goes. Maybe you can get him a new graphics card for Father's Day.

Ah, That was it, I did change the speed (in case you are wondering, at least I haven't gone over this before), because his connection was just a little bit too slow to get the 800 kbps stream. How should I change it so it actually gets a different speed?