Thanks for the information! I'm looking forward to the upcoming season .

Will the World Baseball Classic be supported?

No idea. That depends on whether WBC will be part of the subscription. It was two years ago but qualifier games were not broadcasted last fall.

Just a quick note to set the expectations properly for those who haven't been through a spring training with mlbviewer yet...

Expect that it may NOT work on Sat when the first games are aired. They have been pretty good about not doing any major overhauls the last few years but they always (every year) do something a little bit differently than the year before. Maybe it's slight and it will only take an hour to catch up to their changes or maybe it's a little more involved and could take a week to reverse engineer those changes back into mlbviewer code.

Then again, Spring Training is often just last year's architecture as the MLB.TV developers test their new season changes and it could break closer to Opening Day. In any case, be patient and expect a bumpy road possibly stretching into the first few weeks of the regular season.

That said, I am really looking forward to watching baseball on two new beautiful displays I didn't have last season.

I'm excited for the new season .

Maybe I'm too tired this morning to figure it out, but the times seem to be off by an hour for me. Adding in time_offset=-0800 (-8 hours for Pacific Standard Time) in ~/.mlb/config is fixing the times.

The times are correct in the grid.xml (listings on the server) so there must be something in the DAYLIGHT calculation code in mlbtv.py. Maybe I can look at that later after I've had a bit more sleep.

If times aren't correct for you, you can add in your offset from UTC as, for example, time_offset=-0500 for ET, time_offset=-0800 for PT, etc.

Other than that, audio and video seems to be working just as it did last year. That's good news until they roll out the official 2013 offering towards the end of Spring Training.

Wish I had more sleep to enjoy these, but glad baseball is back.

Hi, hi...! :-)
As spring training games started I'm "back", too, and tried to use mlbviewer like last season, but this is what terminal tells me:

lars@X64V:~/mlbviewer2012$ python mlbviewer.py
Traceback (most recent call last):
File "mlbviewer.py", line 1630, in <module>
curses.wrapper(mainloop, mycfg.data)
File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper
return func(stdscr, *args, **kwds)
File "mlbviewer.py", line 500, in mainloop
+ len(coveragetoggle.get(cfg['coverage'])) + 2
UnboundLocalError: local variable 'is_adaptive' referenced before assignment
lars@X64V:~/mlbviewer2012$

Nothing happens...

Btw: In the meantime a had to make a system upgrade from Ubuntu 11.04 to 12.04.
Does that create problems...?

This is my 6th season and by far the easiest to get up and running on the Gameday Audio. Ran the svn upgrade for MLB2013, edited my config file - and I'm listening. The times are off by an hour, but I'll wait, at least until we change to DST, and see if somehow doesn't rectify itself.

Hi kweisen...

I would like to do the same: do the upgrade and edit the config file. But: How...?

Thanks in advance for some help... :-)

See the post - back one page, dated 1-22-2013 - by daftcat.

run the svn command, I just did a copy / paste. For editing config, from root - cd .mlb, the config file is there.

good luck

It is not the cause but I notice that the date format for 2013 is wrong. You have given the end of DST as being in 2012. The line in mlbtv.py:

'2013': (datetime.datetime(2013,3,10),datetime.datetime(2012,11,3))

should read:

'2013': (datetime.datetime(2013,3,10),datetime.datetime(2013,11,3))

I am on revision 375, which is the latest.

Great to see it working for 2013 without any apparent changes to the MLB format. It may be too much to hope that this continues.

Ah, cancel that, I was on your old repository. This is fixed in revision 376.

I did so, but what do I do with the "information" I get:
lars@X64V:~$ svn checkout svn://svn.code.sf.net/p/mlbviewer/code/trunk mlbviewer2013
A mlbviewer2013/test
A mlbviewer2013/test/nexdef.py
A mlbviewer2013/test/nexdefdl.py
A mlbviewer2013/test/gdaudio.py
A mlbviewer2013/test/mediaxml.py
A mlbviewer2013/test/mlbgame.py
A mlbviewer2013/test/mlbgamedl.py
A mlbviewer2013/LICENSE.txt
A mlbviewer2013/TOOLS
A mlbviewer2013/REQUIREMENTS-2012.txt
A mlbviewer2013/mlbviewer.py
A mlbviewer2013/INSTALL
A mlbviewer2013/NEW-MLBPLAY
A mlbviewer2013/mlbplay.py
A mlbviewer2013/MLBviewer
A mlbviewer2013/MLBviewer/LIRC.py
A mlbviewer2013/MLBviewer/mlbprocess.py
A mlbviewer2013/MLBviewer/__init__.py
A mlbviewer2013/MLBviewer/mlblogin.py
A mlbviewer2013/MLBviewer/mlbtv.py
A mlbviewer2013/MLBviewer/config.py
A mlbviewer2013/README
A mlbviewer2013/mlblistings.py
Ausgecheckt, Revision 376.
lars@X64V:~$

If it downloaded correctly, you should have a mlb2013 directory. In this directory are a couple of READE and Requirements.txt files that contain a lot of information.

You will have to edit the config file in .mlb with you username / password.

To start mlbviewer, once you're in the mlbviewer2013 directory - it is a python command 'python mlbviewer.py - that should bring up a list of available games. Then type 'h' to bring up the help menu with list of shortcuts. For exmample, pressing 'a' brings up gameday audio.

I found the mlbviewer2013 folder after doing the svn command, started mlbviewer.py from that directory, and it works... :-)
without having to edit the config file... :-)

Cool! Glad you worked it out.

For some reason, the digest got flagged as spam so I wasn't seeing the updates. I figured it was too quiet so I decided to check in. Glad to see it all worked out by the time I got here.

So yeah, about a season or two ago, I decided I would just branch off at the end of the season and start the new season on the trunk. This year, Sourceforge had other plans and decided to "upgrade" (haven't taken the time to figure out what the new features are) to a completely different repository and hence the new URL:

I kinda expected Spring Training (at least initially) will be just a rehash of last year's service. Towards the end of Spring Training, they usually roll out beta testing of the new year's service and things may/likely will break. Generally, by the end of April, things are stable again. This is usually a combination of me having to reverse engineer their changes and their changes themselves being a little unstable to begin with.

So just like baseball itself, it usually takes about a month for MLB.TV and mlbviewer to find its swing.