Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Having followed your superb instructions as carefully as I could, I have had mlbviewer working flawlessly here on my Mandriva 2008.1 system for a few days now. When it gave me a "WTF error" at the outset of today's BoSox game, I came right to this thread and there was the freshly-minted fix; three minutes or so, from WTF to WTG! lol
A couple of things I did do a bit differently, though.
1) Rather than copy *.xsd from ~/mlbviewer-svn to ~/.mlb on first installation, I used softlinks, like so:
Code:
cd ~/.mlb
ln -s ~/mlbviewer-svn/*xsd ./
This tactic paid off nicely with today's update of an .xsd file.
2) When I compiled mplayer, I set prefix=/usr/local to avoid clobbering my distro's mplayer package. For my video_player setting, I'm using:
Works like a charm, and the "stock" mplayer gets run for everything else, due to the $PATH priority of /usr/bin over /usr/local/bin.
3) Made a little script called "mlb", put it into ~/bin (which is in my $PATH), and made it executable:
Code:
#!/bin/sh
cd ~/mlbviewer-svn && python ./mlbviewer.py && cd - >/dev/null
killall -9 mplayer &>/dev/null
The killall bit cleans up any lingering mplayer processes that might persist after those rare occasions when mplayer has lost its mind and its video window, but not its life ...
4) I've been using screen to run autobahn.jar, then I detach from it and I only reattach if I think that it needs to be Ctrl-C'd and relaunched; this does appear to be needed/helpful from time to time, AFAICT, so that's now my first troubleshooting step whenever any part of this lashup begins to behave in an unexpected manner. I'm using Sun's 1.6.0_06 JRE here, BTW.
As I sit here watching B[r]ad Penny struggle through his outing in Anaheim this afternoon in glorious HD, I am filled with gratitude for all of the efforts of both daftcat and those that have helped him with their testing and their feedback. This is one of that class of apps that I really love, the kind that I can show to my Windows-using friends and make them green with envy, as they wish that their system could do that. ;-)
--
Bill Mullen
RLU #270075
Thanks for the success story and the tips. The only one that caught me by surprise is linking the xsd instead of copying it. Brilliantly played.
And your Windows-using friends can use mlbviewer with cygwin. Of course, if your goal is to convert them to Linux users, you may not want to tell them that.
Since I started rebuilding mplayer from svn, I've found that the stock mplayer is hopelessly old so I have no issues with clobbering it.
Your tips are well taken but many of my users are novices. I tried to shape the documentation and recommended procedures for what would be easiest. But of course, the power users will always figure out different ways to do things based on their personal preferences.
And I love screen. I'll often start a build of mplayer from work and start using it at home. I update almost daily hoping that one of these days, they will inadvertently, if not intentionally, fix some of the issues with MLB streams and mplayer. Or I occasionally need to bounce between Windows and Linux on my couch laptop so I'll use screen with the nearly headless media server laptop to keep the game going between reboots.
hehe. well played sir! i can make an "adjustment" as well...
that is interesting that mlbam sent you an email. were they thanking your for your contribution, or putting you on notice that they have their eyes on you (think meet the parents)?
are you a premier customer? if you have a contact over there it would be great to get an official answer. i think most of the frustration in that thread is due to the fact that the forum support is either misinformed or is simply lying. if they needed more time to work on it, they should have come out and said that for a few weeks the hd stream would not be available. certainly that would have been better than the mess we are in now. we just want the service that we paid for (was the 3000k stream even 720p?), and at the beginning of the season those 3000k streams looked pretty damn good! and now with mlbviewer, all the stuttering issues are gone as well, so when (hopefully) the 3000k feed returns, the experience will be fantastic!
I had made a few posts on the mlb.com supports boards in one day. Since someone had already brought up mlbviewer in a thread, I replied with a "what is mlb.com's official stance on projects like mlbviewer?". In another thread someone had mentioned how Linux users could use NexDef by unraveling the Mac installer and running the jar file. I replied that even though Linux wasn't officially supported, it would be of great help to Linux users if they could make an official download location for the nexdef jar since it was such a pain to unravel the dmg and the pax contained within it. I sometimes search the mlb.com support boards for linux or mlbviewer just to see what others are saying about it.
Anyway, I get an email from what I thought was just a supportive developer who had made a download link with the nexdef jar and asked that we used that link and not re-post the jar so legal team wouldn't have to get involved. I could tell he found me off sourceforge because the mail was directed to my sourceforge address. He concluded the email with something to the effect of, "I don't have time for everyone so keep my contact info off the public forums. Keep it for yourself though because I wouldn't mind answering questions for developers like yourself." It was later when I looked at the signature that I realized it was a director.
I've tried contacting him a couple of times with technical questions but got no response. I ended up figuring them out myself. The lack of response to any subsequent emails I have sent is why I say they tolerate mlbviewer. If I actually got some responses back, I'd love to upgrade my assessment to "they support us." Still, I certainly don't want to spoil any goodwill by confronting him with something he is probably well aware of. I imagine they are having meetings as we speak about how they are going to deal with this. I'd rather let it play out just the way it is now. Let the angriest users make the loudest noise and force their hand to do something. They have nothing to lose but their $100 whereas I have a project and a considerable amount of time invested in it. It's not worth risking mlbviewer to become confrontational.
As someone who is a software test engineer professionally, I have great admiration for what they have achieved and sympathy for the troubles they still have. I also know that once bugs are reported, they will usually get fixed even without raising a big stink. Throwdowns only weaken the customer/provider, tester/developer relationships.
So, with the updated Mediaservice and whatnot files, when I open the game, it seems to progress further, but still won't play (an archived game).
mplayer(SVN-r29285) pops up in an xterm, but says "reading from stdin... Cache Fill: 0.00% (0 bytes)" and doesn't change
Oh, I missed this part the first time I replied to this. Yes, this won't work. Remove the "xterm -e" part of the video_player line in your ~/.mlb/config.
So... When attempting to play live games, it is not even giving me the freeze-frameness. I get
Code:
Buffering streamRTMPDump v1.5a
(c) 2009 Andrej Stepanchuk, license: GPL
DEBUG: Parsing...
WARNING: RTMP URL: No :// in url!
WARNING: Couldn't parse the specified url ()!
ERROR: You must specify a hostname (--host) or url (-r "rtmp://host[:port]/playpath") containing a hostname
MPlayer SVN-r29285-4.3.3 (C) 2000-2009 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing -.
Reading from stdin...
Cache fill: 0.00% (0 bytes)
Exiting... (End of file)
So... When attempting to play live games, it is not even giving me the freeze-frameness. I get
Code:
Buffering streamRTMPDump v1.5a
(c) 2009 Andrej Stepanchuk, license: GPL
DEBUG: Parsing...
WARNING: RTMP URL: No :// in url!
WARNING: Couldn't parse the specified url ()!
ERROR: You must specify a hostname (--host) or url (-r "rtmp://host[:port]/playpath") containing a hostname
MPlayer SVN-r29285-4.3.3 (C) 2000-2009 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing -.
Reading from stdin...
Cache fill: 0.00% (0 bytes)
Exiting... (End of file)
I assume you can deduce what the problem is.
Are you in the blackout region of either the Giants or the Mets? (the only live game left tonight.)
i see a new "time" display while the feed is playing. is this the exact time for what we are seeing on the screen? i guess this makes it possible to see how far behind the game is. that is a very cool addition. how does it work?
also, what is "MS"?
finally, regarding the mlbam -- i agree that the service is making progress in some ways. however, i do not think it is acceptable to mislead the customers. trust me, i would me far less concerned if they came out and said that they had to remove the feeds while they worked something out. my issue is simply that they denied over and over again that the feeds were gone, despite a great deal of evidence to the contrary. we both know that the feeds didn't go away on their own, so draw your own conclusions. that being said, i certainly understand your position on the issue. hopefully you see my point as well.
i see a new "time" display while the feed is playing. is this the exact time for what we are seeing on the screen? i guess this makes it possible to see how far behind the game is. that is a very cool addition. how does it work?
also, what is "MS"?
NexDef operates in milliseconds, or more specifically, the milliseconds since midnight ET (Eastern Time), where 00:00.001 ET would be an MS value of 1. Since the MS value is of little use to anyone but NexDef and myself (but handy nonetheless for seeing the progress from one control request to the next), I convert the MS value to ET. So that time you see is the counter time. You are correct. That counter time is the stream time so you can compare counter time to computer time/clock time/mlb time (which is partly why I don't bother converting to local time) to see how far behind the stream is. Ideally, NexDef is operating something like BitTorrent in that it is building a stream from several different slices (possibly from different servers??) and the plugin itself is recombining everything to attempt to give a smoother playback experience than if you had received it from a single source in a single stream. You can read up on how this works at getautobahn.com. In fact, I should do that reading myself.
Quote:
finally, regarding the mlbam -- i agree that the service is making progress in some ways. however, i do not think it is acceptable to mislead the customers. trust me, i would me far less concerned if they came out and said that they had to remove the feeds while they worked something out. my issue is simply that they denied over and over again that the feeds were gone, despite a great deal of evidence to the contrary. we both know that the feeds didn't go away on their own, so draw your own conclusions. that being said, i certainly understand your position on the issue. hopefully you see my point as well.
Of course I understand your position. It sucks to be lied to no matter how complex the underlying reasons for that lie might be. I don't fault any of you for making noise. I'm grateful for it. It means I don't have to. As I said, I have a considerably larger investment (lots of time and sleep lost to writing and maintaining mlbviewer) to lose than most.
They handled this poorly but it will come to a head. Deception can't last very long in the Information Age and they should have realized that.
I still want to give them the benefit of the doubt though.
mlbsupport in the forums is probably a just a touch higher on the food chain than an IRC chat bot. If they aren't programmed with the answer for why the streams disappeared (if they weren't even told the streams disappeared), they probably have strict instructions not to ad-lib. But mlbsupport should have come forward with the "I'll look into your concerns" a lot sooner than they did.
Received this today when I attempted to watch Mets@Giants archived game from last evening.
Code:
/usr/local/lib/python2.6/dist-packages/suds-0.3.5-py2.6.egg/suds/wsse.py:26: DeprecationWarning: the md5 module is deprecated; use hashlib instead
Traceback (most recent call last):
File "mlbviewer.py", line 1494, 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 "mlbviewer.py", line 1190, in mainloop
u = g.soapurl()
File "/home/rob/mlbviewer-svn/MLBviewer/mlbtv.py", line 1176, 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'
Received this today when I attempted to watch Mets@Giants archived game from last evening.
Code:
/usr/local/lib/python2.6/dist-packages/suds-0.3.5-py2.6.egg/suds/wsse.py:26: DeprecationWarning: the md5 module is deprecated; use hashlib instead
Traceback (most recent call last):
File "mlbviewer.py", line 1494, 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 "mlbviewer.py", line 1190, in mainloop
u = g.soapurl()
File "/home/rob/mlbviewer-svn/MLBviewer/mlbtv.py", line 1176, 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'
You also need to copy the MediaService.xsd file from revision 204 to ~/.mlb. I don't care if you have done this when you first installed mlbviewer. You MUST replace that file with the changes made in rev 204 or you're going to get the error you are seeing now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.