Thanks for the quick work. "Standard" live games appear to work fine so far. Nexdef games are working for a short time but then failing...the autoban.jar process is emitting errors when I try to watch a live nexdef game. I was playing the start of the Pirates/Cardinals archive from yesterday with nexdef, and it seemed fine (although it was just the rain delay screen since the game was delayed 2.5 or so hours), but playing other archived streams that start with game video also have the same errors.

The error coming from autobahn (this is version 109 coming from our "official" link) is of the form
It happens each time you start a live game, and the stream plays for maybe five seconds. Also sometimes rtmpdump says "ERROR: rtmp_connect1 handshake failed" before anything starts. The archived game streams lasts a little bit longer, maybe twenty seconds. I think what is happening is that some of the stream gets downloaded, then something happens that autobahn.jar doesn't like, and it stops downloading, but the player gets the rest of whatever has been downloaded. The archived games presumably can download faster since the whole game is available, so the stream lasts a little longer than live. I don't know, that's just what I think might be happening.

Don't know if any of this helps, but there it is.

I've updated the documentation and removed the suds requirement and the MediaService.* files and renamed the latest nexdef2010 revision to 0.2alpha01. This is the sourceforge release for 2010. I haven't yet merged the nexdef2010 branch back onto the trunk though. This will be a project for another morning.

If you haven't yet switched to the nexdef2010 branch, please do so.

Once you've checked out the nexdef2010 branch, you can choose to remove your old mlbviewer directory and rename the nexdef2010 directory to mlbviewer if you wish.

From here, any further revisions I make, you can download using the "svn up" command.

I've done a lot of work to strip out a lot of legacy code from prior seasons and remove unnecessary dependencies. This is the easiest to install version of mlbviewer since the project first started. The only python dependencies now are pyxml. The documentation has been updated with the current location for rtmpdump.

Nexdef is flakey. Oh well. I've done my best.

With this latest revision and updating the sourceforge release, I am taking a code break from mlbviewer. I will continue to monitor this forum for bugs and provide fixes as necessary but I'm no longer writing any new features for awhile. It's time to sit back and enjoy the final stretch of the season.

Nexdef games look horrible and also quits, how do I watch in standard mode?

Okay, this is better. I can see now that you are using the new code. I think this error is from one of today's "National Blackout" games. Try an archived game from yesterday or wait until the 7:05 ET games.

The soapevent approach works for me.

No joy as yet with the nexdef2010 mlbviewer.py. Game listings are produced. Selecting a game from yesterday’s archive then pressing enter gives this error:

"An error occurred in locating the game stream:
Could not connect to NexDef. Is autobahn.jar running?"

My script:-

PATH=$PATH:~/bin/nexdef2010
java -jar autobahn.jar &
DEST=~/mlb
[ -d $DEST ] || mkdir $DEST
cd $DEST
mlbviewer.py

Here is some debugging:
Traceback (most recent call last):
File "/home/elbournb/bin/nexdef2010/mlbviewer.py", line 1499, 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 "/home/elbournb/bin/nexdef2010/mlbviewer.py", line 1193, in mainloop
u = g.url()
File "/home/elbournb/config/hp6715/bin/nexdef2010/MLBviewer/mlbtv.py", line 1330, in url
return self.nexdef_flash_url(self.nexdef_url(game_url))
File "/home/elbournb/config/hp6715/bin/nexdef2010/MLBviewer/mlbtv.py", line 1352, in nexdef_url
raise Exception,self.error_str
Exception: Could not connect to NexDef. Is autobahn.jar running?

Yes it is:-

elbournb 18460 18459 6 20:56 pts/0 00:00:00 java -jar autobahn.jar

I bet that autobahn.jar isn't loaded into memory by the time you're running mlbviewer, since it takes a few. I always run autobahn.jar in a separate terminal window without &, then just CTRL+c when I'm done with it.

Also, someone else wanted to know how to use standard def with nexdef mlbviewer, and although it's not in the help, here's the trick: press n in the listings screen to toggle from nexdef to standard, then p to switch data rates. s switches between home and away feeds as well.

1 members found this post helpful.

autobahn.jar just exits after 30 seconds which is about the time I need to find a from last weeks listings ... I tried toggling off the nexdef using the n key in the listings and playing works!!! I only have standard subscription so I'll happily go with nexdef=0 in my ./mlb/config

Yippee!

If you're not a premium user, then nexdef wouldn't do anything for you anyway. In fact, you'd probably get a entitlement error which I'm just misinterpreting in the code as a nexdef error.

Besides, this year's nexdef really isn't working too well with rtmpdump. If that mplayer/ffmpeg developer who responded to this thread about a dozen pages back is reading this, I'd like to know how to specify rtmpdump command-line options on the mplayer command line to see if I can use mplayer's libRTMP directly for any better results. Otherwise, I'll just go searching through this thread.

It was working just fine until this last change a week ago by MLBAM. When did nexdef start using RTMP...wasn't it just an HTTP stream before?

daftcat:

Not sure if this is what your looking for, but there are some command line options here:

http://all-streaming-media.com/recor...pplication.htm

It was actually always an RTMP stream before, it's just the autobahn.jar used to handle all the RTMP streaming bits and buffering and then proxy an HTTP stream for the client. Now it's cut out the RTMP to HTTP conversion but there's something, either rtmpdump or mplayer, that's seg faulting. It was version 108 of autobahn.jar that did away with the http interface.

Nah, I know how to do the rtmpdump options. That's what we're doing now. Actually, we're streaming rtmpdump to stdout and piping that to mplayer's stdin. One of them is crashing and I can't figure out which.

Mplayer has integrated the rtmpdump code into mplayer source calling it libRTMP. But I can't figure out what flags to give mplayer to pass those same options to libRTMP. I think if I could reduce the command-line to just mplayer, we could probably have a better chance of having the mplayer or libRTMP folks look into who is crashing and why.

It's rtmpdump. I've been playing around with rtmpdump's verbose output and at some point it keeps getting some information from autobahn that it isn't liking, and after that it can't right itself. Autobahn keeps downloading data (and presumably serving it), but rtmpdump stops consuming it.

I'm seeing messages like this from rtmpdump when it stops consuming:

and also some stuff like

on some runs. I wish I knew more about RTMP or could figure out a way to see more specifically what stuff autobahn is sending that rtmpdump doesn't like.

I don't know what option needs to be set in the Linux kernel or in rtmpdump or libgcc, but it would really help if we could get a core dump when rtmpdump seg faults. That way the developers could see what was in memory right before the crash and possibly fix it.

Problem with RTMP is that even with the specification that Adobe released, there is so much crap they can do in ActionScript that the spec wasn't as useful as I thought it would be. As protocols go, it's not a great one.