You're a non-NexDef user, right?

You can set it to 800 or 400 in the config file (it gets translated to 600K for 2009 games) or try the 'p' key to switch speeds between 800 and 600. I haven't tested this code since spring training though.

Okay, I do have a bug in this code. It's found and ready to fix. Before I fix it, here's your chance to offer input on how to get this just right for your grandfather. I think that's very cool what you're trying to do for him so I want to get this working great.

If he were using the flash interface, how many bars would he be using?

The four bars of regular (non-NexDef) map to 164, 400, 600, and 800. 800 is already supported. Since you're the first who has asked for something other than 800, if you could have just one other quality bar for your grandfather, which would it be?

I will tell you the 400 has better support across all games. The 600 stream is sometimes cranky or just non-existent, but it is a better quality stream when you have it.

Basically, the non-NexDef code is set up for a high-low setting only. It would take a lot of code (and a lot of compatibility code to work with last year) to support more than two settings.

I have a fix ready but I want to do more testing. Right now I'm in sign-on restriction so I can't test. Anyway, I was going out tonight so it doesn't matter. I'm leaving for the weekend tomorrow though so if I don't hear from you, I'll check in 600 into mlbviewer and I'll patch stdout.py to let you specify 400, 600, or 800. This way if 600 gives you trouble for a specific game, you can use the test tool to overcome the high-low limitation and get a 400 stream to him.

Sound good?

There was a bug for non-NexDef speed switching that prevented the lower quality stream, 600K from being selected.

Note 1: even though the low quality stream for 2009 is 600K, the config file setting should be "speed=400" to auto-select the low quality stream. This is largely a compatibility issue with 2008 and 2007 seasons. At some point, this will be fixed to either specify the real speed or change the speed to a "high" / "low" setting. For now, remember that "speed=400" means 600K for 2009.

Note 2: The "speed=" parameter is a non-NexDef setting. NexDef users should use "max_bps=". At some point, I will merge these settings so all users use either speed or max_bps. But for now, remember, NexDef users, specify your preferred upper limit for stream selection using max_bps, not speed.

Also in revision 207 is a minor fix to stdout.py for the same issue with one big difference. stdout.py does not care what speed is set to in the config file and defaults to 800K. This can be overridden by adding an optional second parameter, the stream name.

Stream names are:

Flash Player setting , speed, stream name
1 bar , 164K, MLB_FLASH_164K_STREAM
2 bars, 400K, MLB_FLASH_400K_STREAM
3 bars, 600K, MLB_FLASH_600K_STREAM
4 bars, 800K, MLB_FLASH_800K_STREAM

So, if the 600K stream doesn't work in mlbviewer, you can select an alternate speed using stdout.py as follows:

which would select the 400K stream.

As always, the event-id's can be looked up using mlblistings.py.

[EDIT] NexDef users do not need to take this revision. There's nothing changed for NexDef use.

mlbviewer is running well again for me since today, so thanks again for all the hard work numerous people are putting into this great project!

two questions remain for me right now though:
i have recompiled mplayer. when i play a game in mplayer and go into fullscreen mode, it leaves fullscreen mode and goes back to a smaller size about once every 3o seconds (sometimes it stays longer). is there a way to stop the player from exiting fullscreen mode and just adjust the speed/quality? it gets old after a certain time...

second issue: watching games right in the middle. i am nexdef user. when the tigers game was over today, i wanted to watch the rest of the royals game vs cleveland, but when i entered the game, it started from the beginning. knowing what the score was, i wanted to jump right into the action. how does that work?

sorry, i am still a newbie, so i appreciate any advice and help!
thanks so much,
markus

Concerning your 2nd problem, use the jump to an inning feature. Just highlight the game you want to jump right into and press "i", there is a small help section to guide you from there.

As far as your first question, I don't know. You might try taking the 'fs' out of your player command in your config file and then the game will start in less than fullscreen. Then you can adjust from there. I've had some erratic behavior with what I think you are describing and it just went away after awhile.

Just the opposite. Add the -fs flag to the mplayer command and it will not drop out of fullscreen mode.

Has something happened to rtmpdump at Sourceforge? When I search for it, I get one result, which is fine, but when I click on it, the results are invalid. When I try to download it, there's a message about how permission is denied. I created an account at SF, but that didn't seem to matter. Could someone please let me know if I'm missing something obvious? Or make rtmpdump v1.6 available for download?

Thanks

UPDATE
http://linuxcentre.net/adobe-has-iss...-for-rtmpdump/

What does this mean for mlbviewer & my non-premium Gameday Audio subscription?

Thanks again.

Here, if you can't download it here, I uploaded my 1.6 copy. It is not patched. http://www.mediafire.com/?sharekey=9...4e75f6e8ebb871


Daftcat:

I use the little script you gave me to open the game on his computer. It uses stdout.py, so the update works perfectly. He is currently watching the 600k stream, and it seems to be small enough for him to watch (800k is just at the limit and pauses sometimes.) For the first time it is playing well fullscreen (with -zoom in mplayer), almost synced sound (with -autosync 30 and -framedrop), and a slow enough stream that there is no pausing. Thank you so much, and I am sorry if I was annoying to you.

Also, does ./stdout respect the config at all? What parts of it does it listen to?

Well that's interesting. Looks like someone's going to have to put it on a European server.

Who said that? I didn't.

I believe it's just taking user/pass from the config file.

The scripts in test are the rough drafts of testing the network code and also easy ways for me to debug the network related stuff without having to deal with the MLBviewer library or the mlbviewer gui. I could probably fix them to read the video_player setting though.

It "jerks" out of fullscreen when the stream speed changes. The stream speed changes also change the dimensions of the stream which is really why it "jerks" out of fullscreen. So there are two things going on here and two possible solutions. First, you should add -fs to your video_player line. This tells mplayer you want it fullscreen even if the stream switches dimensions/speeds on you. This should fix it from "jerking" out of full-screen. The other thing you want to look at is if the stream speed you are requesting is really the most appropriate for your computer and connection. You can also make a best attempt to lock in a particular screen by using the stream selection menu. This theoretically has the effect of picking a quality bar and turning off auto-adjust but I've also seen nexdef still downshift in times of stress (computer or network.) If you don't mind or don't notice the speed changes, you can just rest on the -fs flag to solve the fullscreen issue.

In the earliest svn revisions that had nexdef support, I didn't quite have it worked out as to request live vs. archived, so I essentially treated everything as an archived game (I specified a start time that matched the start of the game.) A revision or two later, I introduced an option called, "live_from_start" which was set to true by default for a revision or two. Lately, it should be "false". Also, it's really not necessary anymore since I implemented the jump to innings interface ("i" screen.) Check your config file and make sure "live_from_start" is not set to true. Set it to "false" or remove it from your config file.

I really appreciate it when the veteran mlbviewer users can help out the new users.

This weekend even more so. I'm gone for the weekend and the hotel I'm staying at has very flaky wifi. So even if I do find a moment, like now, there's no guarantees the wifi will be here for me (like it hasn't for the last hour or so.)

Please be patient. I'll be back Monday evening. Help each other out.

Sad news about rtmpdump. I can't endorse pirated copies of rtmpdump. I also won't discourage them either. That software should be free (as in speech and as in beer.)

Looks like rtmpdump will be replaced by something called flvstreamer. This is essentially a fork of the rtmpdump code with support for RTMPE (the encrypted version of RTMP) removed. I think it may have been the support for RTMPE that Adobe took particular exception to. Anyway, MLB.tv uses RTMP rather than RTMPE, so that is not a problem. I'm not sure where it might be hosted, but you should be able to track it down from the get_iplayer site for now (linuxcentre.net - note that centre is spelt correctly).

I'm getting this error when trying to listen to a game. I've cleared out my suds cache and copied MediaService.xsd to ~/.mlb/.

/usr/bin/mlbviewer.py
/usr/lib/python2.6/site-packages/suds-0.3.6-py2.6.egg/suds/wsse.py:26: DeprecationWarning: the md5 module is deprecated; use hashlib instead
Traceback (most recent call last):
File "/usr/bin/mlbviewer.py", line 1250, in <module>
curses.wrapper(mainloop, mycfg.data)
File "/usr/lib/python2.6/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/bin/mlbviewer.py", line 1018, in mainloop u = g.soapurl()
File "/usr/lib/python2.6/site-packages/MLBviewer/mlbtv.py", line 1155, in soapurl reply = client.service.find(**soapd)
File "build/bdist.linux-x86_64/egg/suds/client.py", line 240, in __call__
File "build/bdist.linux-x86_64/egg/suds/client.py", line 379, in call
File "build/bdist.linux-x86_64/egg/suds/client.py", line 240, in __call__
File "build/bdist.linux-x86_64/egg/suds/client.py", line 422, in call
File "build/bdist.linux-x86_64/egg/suds/client.py", line 480, in invoke
File "build/bdist.linux-x86_64/egg/suds/client.py", line 505, in send
File "build/bdist.linux-x86_64/egg/suds/client.py", line 537, in succeeded
File "build/bdist.linux-x86_64/egg/suds/bindings/binding.py", line 140, in get_reply
File "build/bdist.linux-x86_64/egg/suds/bindings/binding.py", line 197, in replycomposite
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 302, in process
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 87, in process
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 103, in append
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 180, in append_children
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 103, in append
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 180, in append_children
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 101, in append
File "build/bdist.linux-x86_64/egg/suds/bindings/unmarshaller.py", line 323, in start
suds.TypeNotFound: Type not found: 'view-keys'