Is anyone having trouble with mplayer failing to load archived games?

1. What day?

2. What game?

3. What version of mplayer are you using?

If someone can snag the 4/16 stream for the Kansas City game, I'd be happy to know what version of mplayer you are using.

Some games snag and some don't. Very frustrating.

1. I've not had any trouble picking up any archived games (as a Gameday Audio subscriber, I only have access to archived games).

2. See above

3. I was able to view the 4/16 stream of the K.C. game (at about 1:15am PDT), I'm using Ubuntu Gutsy, which uses mplayer 1.0rc1 (Ubuntu version number is 2:1.0~rc1-0ubuntu13.2).

I've tried going back a day or two and haven't had any problem, all told I've loaded somewhere near 10 games... I went all the way through the first half inning of the KC game (which is quite a while with the pregame show)... no problems.

Have you tried using the Firebug method to make sure there's nothing wrong with the script? I don't imagine it's a problem with mlbviewer, but I imagine it's worth checking.

I finally got the stream. The 400k stream is garbage but the 800k stream snags okay.

I wasn't sure my laptop (700mhz/256mb) would handle the 800k stream but it seems to be doing okay with it.

This is exciting.

I should have tried this a long time ago.

That's great news! The 800k stream is leaps and bounds better than the 400k stream.

I'm wondering if it's kosher for me to suggest mlbviewer to others yet? There's someone I know who would probably appreciate using the script rather than the Firebug method, but I know you've wanted to have a limited number of testers so as not to get overwhelmed with support requests. It seems like you're now to the point where the code has pretty well solidified (notwithstanding adding a few features and attempting to make the script look like Firefox when it connects to MLB's servers), are you ready for a few additional testers?

I don't mind a fresh pair of eyes testing it. I'm not sure we're ready for a general release yet, but extending the alpha crowd probably won't hurt us. Do you think he could sign up here and give us feedback?

Huh? No problem with MPlayer 1.0rc2-4.1.2 using the 400 hookup.

I get it though, you just wanted to gloat over the 3-2 win last night. Don't get wound up though; it is the middle of April only and by August or probably sooner they'll be rolling in the gutter with my team the Sox for last place in the Central.

I thought I read somewhere where someone had found a solution for the garbled video with VLC. If so, I can't find it in this thread and I'd appreciate it if someone could point me to it if it does indeed exist or offer a fix if there is one.

Sorry you aren't straycat, but daftcat is good enough.

Don't panic.

Script is not working today here for the early archived games (tv) but is still working for the games from yesterday etc. So I assume it is another MLB glitch. However, I can get the games in XP, so...... more to be revealed. Being by nature paranoid, I can't help but be concerned however.

I'm having a terrible time snagging any games--archived today, yesterday, or several days ago.

I think the content servers in my area are fubar!

Btw, the 400k stream for the Houston game was working on my XP machine.

A quick test shows games (today's three archived and a sampling of yesterday's archived) coming in fine. Don't have a chance to watch and see if things stay good, but it looks okay for the most part. Must be servers in different locations.

BTW, it seems like every day recently there's one or two archived games that just won't work. But it's so arbitrary that I think it means that they're still just a bit loopy from the beating they took on Monday. On the whole, problems on their side notwithstanding, I think we're good for the long haul.

I'm going to make speed a live configurable, a toggle in the statusbar, and add two new config file options: video_player_400 and video_player_800. This way, if you're like me and you're using mplayer's cropping feature to get true fullscreen, then you have two different video_player commands depending on what stream you're downloading. I'll make it so that if video_player_(speed) is not defined in the config file, it will default to video_player for backwards compatibility. This way if you've been trying for the last 20 minutes (or two hours like last night) to snag a 400k stream, you can try the 800k streams without having to exit, edit, and restart.

Has anyone run into the concurrent login issue since upgrading to the new code?

If we've got this licked, then I'd like to move the cookie printing in the log into a debug clause to reduce the amount of messages going into the log.

[Edit: Something got screwed up.]

I know I first mentioned the cropping, but I think I was wrong -- mplayer has a better way: the panscan feature (meant for putting widescreen movies into TV screens).

When it's in fullscreen, just press 'e' and you can change it on the fly. It's set so that you have to press it a few times, but if you only want to press it once, make your own input.conf file and put

e panscan +1.0

in it. I have it set that way and so if it's a 16:9 game, I can watch it wide, and if it's 4:3 I can just press that button once and it does the right thing.

I actually sometimes switch back and forth. 4:3 for the pitches, which don't use widescreen, and then press the button on my remote to zoom out to widescreen for the fielding plays.

I have no problem with this, but I'm curious about its use. Do people frequently watch different speed streams on the same computer?

I guess if you have a laptop that is sometimes on a slow connection and sometimes on a fast connection?

But, yeah, it definitely makes sense to add it in if there's a need. I'm just strongly agreeing with you that we should keep the simplest case -- and the one that I imagine 75% of users will use -- a transparent default.