Now it works again.
Oh, mlb.tv you are some strange lady, and I won't ever get the knack out of you.

And today, the same mistake as yesterday, it stopped working again.

I know there's a bug in there but that it keeps resolving itself makes it both tricky to debug/fix and low on my motivation list to go hunting for it.

I've been very pleased with the way mlbviewer has been holding up on my end and the rest of my life has gotten so much the busier that it's hard to find a free moment to work on mlbviewer and harder to convince myself that that free moment should be spent on mlbviewer. Maybe this weekend I'll put in some code cleanup time.

No biggie. I didn't miss a live game because of it. I just like to watch some archived innings after work (I live in Europe), and I had to wait for mlbviewer to work maybe an hour monday and tuesday, so no problem at all.

And I'd like to add, I am more than just happy, how mlbviewer works. I am german, so i might lack the words to describe the absolute stunning awesomeness of mlbviewer, but I pity every windows user, who has to cope with mlb.tv's flash player version.

So thank you, dafcat, thank you very much. I appreciate your work more than you could imagine.

Hi Daftcat,

Thanks again for all the time and hard work in getting mlbviewer to its current state. It's fantastic for me to be able to watch my Yankees in HD whereever I am, even on my little netbook running Ubuntu jaunty. mlbviewer/mplayer shows about 1/5 the CPU load of flash player on Linux, so it's the difference between nigh-unwatchable and fantasticly smooth .

Anyhow, as has happened more than once, I'm having problems today getting the Yankees/Minn game. I'm only using Nexdef, and it returns the error "Could not parse NexDef stream list. Try alternate coverage".

Often when I get errors like this, the Flash player is equally fubar, but this time the Flash player works fine. Also, other games besides NYY/MINN are working fine.

I do notice however that when selecting NYY/MINN in the Flash player, it now gives me a new choice of choosing "in-market" or "out-of-market" coverage. Since the Yankees are the first team to get the in-market coverage, I wonder if this is mucking with the URL parsing routines in mlbviewer.

Since in/out-of-market coverage is coming to other teams soon, you may want to take a look at the Yankees games now for a preview and see if there's anything new/different.

Of course, it could just be the usual random errors that sometimes occur, but I figure I'd let you know .

Thanks again and good luck!
---DanQ

As of the last few days, I've been unable to use audio. My config has
which is the same as I've always used. Now if I want to listen to a game I have to use dump the stream to disc first and then listen to it via mplayer. That works fine but adds an extra step that I'd prefer to not use.

What does gamedayaudio.py in the test directory say? You can post the output to pastebin.com and I can look at it tomorrow or Saturday.

When you get another "Could not parse" error, please try again with nexdef.py in the test directory and post the complete output to pastebin.com.

I'll look into the "in-market" vs. "out-of-market" perhaps this weekend.

Excuse the ignorance but do I run gamedayaudio.py with the event id or just run gamedayaudio?

I was playing around a few hours ago trying to figure this out and all I accomplished was them locking me out for "too many logins". I'm not very fond of them for starters and I don't want this to happen when there is a game I want to watch occurring.

Just thought I'd pop in and say that I've been using mlbviewer in conjunction with XBMC via a quirky but reliable workflow. For the past couple weeks, I've been getting rock-stable connections over NexDef in constant 2200 kbps res. The result has been that I can start a game, kick back and enjoy it, and not even have to think about all the magic going on behind the scenes.

So often with these projects, there's a certain amount of babysitting the technology. At least for me, I haven't had to do that for a while now and it's pretty nice. And using XBMC as the player, I don't even have to resync the A/V.

Thanks to daftcat for doing the hard work, and to the rest of the community for finding the bugs. This is a top-notch program and I hope it continues to be.

You can get the event-id from either the 'z' screen or mlblistings.py.

Tee the output to a file and post that file's contents to pastebin.com so I can review all the output.

Then copy all the contents of /tmp/gamedayoutput.log to pastebin.com and post the url here.

Thanks, I was just going to do that and when I tried to bring up MLBViewer the listings would not appear with parser error message. My guess is this happens only when they are in the process of changing their listings and this being All-Star game time, it sort of follows. I suspect by Friday or even earlier, it will fix itself again.

I checked out the SourceForge page and I see where your program has had at least 2600 downloads. Hopefully there's enough appreciation from that group to have sent you a few bucks. Although this year due to the change to flash, MlbViewer isn't a necessity but it certainly was last year after Silverlight screwed up some of the other ways of using Linux to view the games. But how about next year? Who knows what they'll do and with the increasing complexity, most of us will just be screwed if someone like you doesn't keep an alternative going.

straycat: results are @ http://pastebin.com/m62ae13a1

./gamedayaudio.py 5492073 | tee /tmp/gamedayoutput.log

I used the game ID for the White Sox broadcast (Score) last Sunday, 7/12

thanks...

#
session-key = pGHW49r4ROINMAMhsieDMQOBaXU%3D
#
(reply){
#
entitlements[] =
#
"",
#
status-code = "-1000"
#
}

1000 = Requested Media Not Found

I probably need to sit down with the code and see if a) mlb.com is still acting as expected, and b) I'm doing the right things.

All-Star Game

Haven't taken a look at why it went foul, but the listings didn't pick up the correct event-id.

You can watch the All-Star game using NexDef or rtmpdump with the test tools: nexdef.py and stdout.py.

The event-id is: 14-245524-2009-07-14