Has anyone else been having troubles either snagging a stream or the stream cutting off after about 10 minutes?

This is has been happening to me the past couple of days.

I actually am having so much trouble even snagging the stream right now that I'm grabbing the streamid from the log and using test/mlbgameid.py.

I wonder if I broke something implementing condensed games...

I've had now problem getting the streams. But I haven't updated for quite some time. I still have .1alpha6svn.

the very best would be without spoilers. usually most top plays are from winning team or top plays like "Morneau walkoff homer" are quite explicit!!!

i've another question.. lot of windows users are asking me if it's possibile to have mlbviewer working on a ms box. is it possible?

ps. no prob with streams..

I'm not having any troubles with getting the streams. Everything is working fine, even with the condensed games added.

I have to agree with lephio about the spoilers - but just to get mlb.tv available on linux is a godsend.

Finally, lephio: there is a simple way for your friends to get mlbviewer on their ms boxes - install linux on them!

It is with cygwin. I use it all the time. I find it easier than the web page.

You have to manually install the python dependencies as only python itself is available through the cygwin installer. Make sure you also install subversion (under Development packages) and pull the latest version from svn. This has the INSTALL file that has the web addresses of all the dependencies.

I'll look into implementing condensed games like audio support. I'll have to add some kind of visual indicator that a condensed game is available so you guys aren't hitting 'c' all the time checking to see when it will become available. I'll see what I can do in the next week or two. Work is starting to get busy again.

I didn't feel like doing much debugging so I just rebooted my entire network (Linux, Windows, Linksys, and cable modem.) It seems one of them needed it because that cleared up the problems I was having. At that hour, I didn't really care which. I just wanted to watch my game.

So I have this idea for implementing CG without spoilers.

But I'd like to take a poll of users to see what they think.

My first thought is to add a visual indicator to the listings and just tack it to the end like:

My other thought was to prepend a field indicator that could be reserved for future enhancements like in-game highlights. It might look like:

Where the codes could mean:

The problem I see with this is that even with a codes cheat screen, that could be too much information. Also, I'd only want to support one code at a time (which kind of makes sense because if CG is available, then the game is archived and Top Plays are also available and H, A, and B would not apply. Likewise B, H, and A would be exclusive codes.)

The third option is to put CG in the status bar like:

In all cases, 'c' would select a CG (if available) just like 'a' selects gameday audio.

The third might be easiest to implement because I could just add a new status code while parsing the listings. The second might gives us the most growth opportunities for future enhancements but also might be the most cluttering of all the options.

I'm open to other ideas.

Now that I see it and consider it, I'm leaning towards the third option which would keep the listings uncluttered but also allow us to add status lines like "Final (Top Plays Available)".

Still open to your votes or ideas.

I made some mods to the 0.1alpha6 build to let me easily run it on windows sans cygwin. What I wanted was to just run it without curses, so I could use it as a command line launcher. My real goal is to get it running on my smartphone for audio;-)

Anyway, I created mlbviewer-cmdline.py, which lets you list in-progress games, and listen or watch a team's game. I ignored TopPlays and such, but it works really well.

I made 2 changes to the existing code; I made TEAMCODES visible from mlbtv.py, and dropped a curses import somewhere in the MLBViewer package that was extraneous.

Not having curses lets it run against stock windows python, no cygwin needed (which is good, because I prefer MSys).

Tonight I'll try it on my phone for listening to the radio stream.

Is anyone interested in the code? mlbviewer-cmdline.py is around 200 lines total, so it is pretty small.

ok i know i have too much time on my hands but...

already looked at all yesterdays games..todays havent started yet

so i try out the jump-to-date feature

watching the a's-giants from a year ago, dan haren vs zito

neat-o!

how far back are there games available for?

!!thank you!!

Mlbviewer only supports games from 2007 and 2008. There isn't a high and low quality stream for 2006. It's all a 350K low quality stream. Before 2006, I can't find the jsp's that we rely on for the schedule.

Cool!

I'll look for that curses import and if it's not needed for mlbviewer, I'll remove it. If that's the only change that's required to use the mlbtv.py library, that's awesome. I'd have to check with Jesse but I'm sure we'd be willing to add a contrib directory in the project page and the svn repository for any frontends other users develop. We had this idea (actually, it was more his idea but a great one it was) to separate out the library from the "gui" so that others could develop whatever gui they wanted using the library we maintain and support (and the curses client as a model of how to use the library.)

Email the code or a link to the code and I'd be happy to look it over and test it.

And now I have a favor to ask...

Could you change the name to mlbcmd.py? I think it would help people identify it as a separate (but related) script. I think it would also make both our lives easier as you wouldn't have to field my bug reports and I wouldn't have to field yours. And we wouldn't have to ask every time, "is this the curses or the cmd-line tool?" Plus, I'm lazy and wouldn't want to have to type a command that long.

Thanks!
Matthew

@daftcat
I think you "third" option could be the one that fits best in the gui we've had so far. Second is indeed too much.

IMHO, obviously

@daftcat

I think it depends on how many extra enhancements you have lined up for development. I think the third option is best in the short term but if more features are to be added after condensed games it would start getting impossible to cram all the indicators in.

I like the look of the second option, but with this change - all the codes for which features are not yet available are replaced with dots, e.g.:

Might be a little fiddly to introduce at first (especially the right-aligning) but once in, it would allow you to add more features without having to worry about the clutter, and you could display more than one code at once.

But unless there are a lot of new features planned, then I think the third option is best. One of the things I love about mlbviewer is just how simple it is, so I'm a little wary of lots and lots of "enhancements".

i think that first of all we need the fastest way to implement the "anti-spoiler". so if "third option" is the fastest.. go with it!

the very best implemention is for sure the "second" option "redseventysever version". because i can immediatly see the availability of choices for my favourite team.

by the way.. i suggest this feature. it would be nice if in config file i can set my favourite team (i.e. MIN). so mlbviewer can UNDERLINE my favourite matchup and i immediatly track it.

at last, command line version is a nice idea. so we can think about customized scripting and things like that.

you're doing great job guys!