thanks. that gets the stream working. unfortunately it stops after a few seconds or more... but i assume that is just network issues in my house. 14 people on one dsl line...
thanks daftcat!

Hi long time lurker 1st time poster... 1st let me say thank you daftcat for all the hard work and effort you have put into this! Paypal on the way shortly!

I am on FC11 and am getting the following error:

The game boots up just fine but after a few minutes mplayer auto exits (mlbviewer stays open)

Could this have something to do with why I am getting booted? I have tried running 2200k feed and the same happens.

I have cleared tmp/suds and the same continues.

Thanks in advance!

I'm wondering what people are doing to get non-NexDef video and the radio working. I have compiled flvstreamer-1.7 and renamed the compiled flvstreamer_x86 binary to rtmpdump but it always segfaults on me for both radio and non-NexDef. Thanks!

Hi Daftcat,

Yes, it resolved itself for me as well an hour or so into the game (NYY vs. Nats). For at least some of that hour, the flash player wasn't playing a stream either (though there was a period where flash player worked but I still got parser errors from mlbviewer).

P.S. Thanks again for creating this wonderful tool!

Shot in the dark but both work very well for me and I'm using rtmpdump1.6.
You can get it at http://tinyurl.com/mwmzh3

Since it isn't working, you have nothing to lose by trying it.rr

I've already tried rtmpdump1.6 before and haven't had any success with that either. There's no working "make install" for this so I'm wondering what people are doing to get this working.

Oh...just copy the executable that is created in your build directory to /usr/bin/ or someplace in your path.

You did run the patches first, right?

patches? we don't need no steenkin patches!

lol of course i didn't. it's hard to find info in this thread sometimes.

Neither rtmpdump nor flvstreamer will work without a patch. The segfault you are seeing with flvstreamer is that the unpatched flvstreamer (same with unpatched rtmpdump) doesn't allocate enough memory for one of the RTMP connect messages (I think it's createStream, but I don't remember offhand.) Consequently, when we fill in that message with far more bytes than it was expecting, buffer overflow and crash. I haven't created a patch for flvstreamer yet but as others have posted and as documented in the README, INSTALL, and REQUIREMENTS pages, you must use rtmpdump and it must be patched with the Patch.sh I supply in rtmpdump-patches directory.

I'll get an flvstreamer patch ready soon.

I know you're not running the patch because the patch adds a make install to the Makefile.

Which is why there are README, INSTALL and REQUIREMENTS files distributed with mlbviewer. The thread should be used in addition to, not in place of, those files. You're very lucky my RTFM gun is sitting on a shelf too far for me to reach.

ha! yeah, I'm scatterbrained. I found the patch now and patched 1.6. flvstreamer doesn't patch cleanly though. I have yankees vs orioles up now with rtmpdump. thanks!

Nope. If the game is started, suds has done its job. This is a warning and it's harmless.

What stream are you trying to use? 3000K? That's kind of dicey at the moment even in a perfect world and using the flash player. As I can't even test with 3000K myself (my laptop doesn't support 1080p), 3000K comes with no warranty (not that any of mlbviewer has a warranty. )

So, let's see if we can't get you 2200K working instead. Once that works, I'll leave you on your own (or with the help of others here) to figure out 3000K.

First, do you have the CPU, memory, and bandwidth to handle 2200K? Post those numbers for us.

Second, how long has it been since you've restarted autobahn.jar? This code isn't perfect and it's probably best to restart it first before we go any further with mlbviewer and mplayer.

Third, is your mplayer relatively current? Has it been built from SVN sources newer than April 24, 2009? Don't rely on any pre-packaged mplayer binary distribution to be this current.

Finally (for now), what video_player line are you using in ~/.mlb/config?

flvstreamer is rtmpdump in an Adobe-friendly disguise. At some point, I'd like to hack up one or the other and remove the dump-to-disk option (leaving only the stdout option) as well as the RTMPE code so that it behaves more like a streamer vs. a downloader to further Adobe-proof it and release that as its own spin-off just for mlbviewer users.

You're right. Flvstreamer doesn't patch cleanly and I believe that it would also require mlbviewer changes to support flvstreamer since it messed with the command-line as well. So for now, stick with rtmpdump v1.6. At least I know that code base works for mlbviewer and it won't be changing anymore.

Eventually I'll either move to flvstreamer or create my own mlbstreamer off one of those code bases.

Adjust the max_bps in the config file until you get a setting that works for your household. 14 on a DSL? Ouch! Are you sure it wouldn't just be easier to use 800K non-nexdef? Also, the very first thing you should do when you encounter streaming issues with nexdef is restart the autobahn.jar. It's not perfect code. But it is the closest piece of the puzzle to the actual media stream.

To expand a little on that, mlbviewer is like a matchmaker. It sets up a date with your media player and the mlb network. Once both parties show up for their date, it is out of mlbviewer's hands whether they'll like each other or not. So if you are encountering problems getting the game to start, that's (probably though not definitely) mlbviewer's fault. If you are having problems not with the game starting but rather it exits early, then either mplayer or the network wasn't happy and left the date with a headache. (or it had to wash its hair?) Blame the network first (because it's closer to the media and it's easier to debug) and restart autobahn.jar or lower the max_bps. Then work backwards to mplayer which is a lot trickier since that's very machine dependent with all the output plugins and command-line options.

I like problems that resolve themselves.