Pssst! You still have some forbidden code of mine, right? You can probably hack that into mlbgameid.py.

I didn't tell you that. ;-)

I have no idea what you're talking about. But even if I did, I'm not sure I could learn enough python this afternoon to implement it in time for the game. But that could be a good leaning project for me at some point. If I knew what you were talking about. Which I don't.

ehi daft, do you think is "teorically" possible to add 1.2MB stream implementing mono?

Mono/Silverlight isn't the problem. Receiving the data is the problem. For the 1.2M streams, MLB.com uses packet swarming plugin called NexDef. In order to reliably receive this data, we would have to either port the plugin or write one which accesses the same network. Neither of those are likely to be feasible given the fact that there is likely to be encryption and access restrictions, and there's no way MLB would license a port of the plugin to a platform they evidently don't respect.

Hey everyone,

Just stopping in to say hi. For newcomers, I did some of the early development work on mlbviewer. Then life decided to rear its ugly head and take my free time away. I've been trying to minimize my distractions (getting a few Giants games in all the same) so I've mainly jumped off of development. But it's just fantastic to see all the great work that daftcat and the community have done here. Usually when someone lets a software project slide, they feel a bit of guilt. But lucky for me, there's nothing here to feel guilty about, because the project just continues to get better every week. Pretty awesome. Big shout out to daftcat, big thank you to the community on these forums.

Hope everyone is having a great summer. All the best, and enjoy the games.

Jesse

A link about the nexdef\autobahn linux question.They say that once the osx installer would be ready (and indeed it is) they would start working on a linux installer.

Keep your finger crossed.

Sorry to be the bearer of bad news but the listings pages we use to get the stream information only contain listings for 400 and 800 mb streams. I'm not sure where we would get the listing for 1.2 mb stream. I'd probably have to reverse engineer the Mosaic application and I'm not sure that's possible. Mosaic has some secure authentication scheme besides basic password authentication.

Eh, from what I've read in the Mosaic forums, 1.2mb doesn't work all that well. Then again, there could be much more happy customers who don't write in.

If someone wants to figure it out for me, assuming the plugin is ported, I'll look into what it would take to add it to mlbviewer. Honestly, it's not high on my wishlist because it's very unlikely my laptop would support it. It experiences enough media server indigestion on 800K streams.

in mlb media center 1.2 links appear just during live games. cannot retreive it during ballgames?

The link is not the problem. The problem is that there is no way to get the data in Linux.

ok.. i misunderstood your words..

I don't know where MLB media center gets its information but it's not the same source we use.

I generally don't say never, but I'm ready to eat my hat on this one. I will very likely never write code that parses the media center page directly. It's a rat's nest of tables and javascript retrieved from no fewer than seven other javascript pages.

1.2 support is not on my development roadmap. If someone else wants to figure out how to get the listing (besides parsing the media center page), AND the plugin is ported and working, I may reconsider.

ok!!

keepin this thread up..

the very best feature for mlbviewer would be to permit mplayer to pause the stream without letting "expire" it. i know it's not easy but.. cannot do something like "ping" the stream to keep it alive?

or.. changing everything.. we could record the stream on disk and playing it from disk. when i pause the player, the stream continued to be recorded till end. when i unpause the player continued to play from disk. something like "mysky" decoder ( http://en.wikipedia.org/wiki/My_Sky )

just dreaming?

I have a few minutes between vacation adventures to respond.

Re: pinging, mlbviewer is not a media player, it's like a middle-man connecting media listings with a media player. As such, we really can't affect how the media is played. So, no, there's nothing we can do to ping the media server.

Re: recording, this is where we could possibly get into problems with mlb.com. I'm inclined to believe that this could violate the terms and conditions. Or at the very least, it might attract cease and desist order.

One way to pause and resume is to make sure your buffer is at least as large as the amount of time you intend to pause. For example, if you use the 800K stream, you'll have to have 100 KB of buffer for every second you intend to pause. In other words, to pause for 5 minutes, you would need to use a 32 mb buffer size. Mplayer will continue to fill the buffer while you have paused playback.

The only trouble you'll get into is if you pause for longer than you have buffer for. In that case, I'm pretty sure, mplayer would flush the buffer and then try to reconnect. At that point, your link has likely expired. The other downside of using large buffers is that mplayer will wait until it has 20% of the buffer filled before beginning playback. So for a 32 mb buffer, you'd have to wait about a minute before playback would begin. If you use a 64 mb buffer, you'll be able to pause up to 10 minutes, but you'll have to wait 2 minutes before playback starts. Just figure for an 800K stream, you'll get five minutes of pause for every 32 mb of buffer while waiting 1 additional minute before playback begins.

All that said, there is a way to record mplayer streams but I'll leave that for you to figure out. The only hint I'll give is that mlbviewer will perform string substitution for the url by using %s in the video_player or audio_player commands. I'll offer you no more help on this and I suggest not posting anything here about it...just in case. Better paranoid than to have the project shut down, right?