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.
Hi, I'm getting a new error (new since this afternoon). I try to run mlbviewer.py, and it says it's logging in, then dies with the following message:
This is with revision 356. I tried reverting to 350 (which is what I had this afternoon, but I got the same result. Maybe it's because there are no games going on at the moment? mlblistings.py works fine, and mlbplay.py worked fine for the archived audio from today I tried (although it said it couldn't find the stream for the condensed was-nym game).
What setting do you have for speed in your ~/.mlb/config?
I'm guessing it's 800 as that was formerly the default. 800 is no longer supported for basic rate. Your choices for basic rate are 300, 500, 1200, 1800, or 2400. If you just comment speed out of your config file, it should default to 1200. Let me know if that fixes it. I'll add some defensive code around that line number to see if that's really the issue.
Revision 357: Defensive code for invalid speed= setting in config
If speed= setting in config file is invalid, an error message will appear saying, "Invalid speed in .config. Using speed=1200." and it will set the speed to 1200. If you use 'R' key to reload configuration and that speed value is still incorrect, it will print the same error message and set the speed to 1200.
Previous seasons, there was an 800K stream and that was the default even into the first few revisions this spring. Since you ran mlbviewer for the first time (when the initial config file is created) before I changed the default to 1200, it's very likely the config is set to speed=800.
The only other place where that particular line your error refers to can go wrong is if you entered something other than 'home' or 'away' in coverage= setting. But most people don't touch this setting since home or away can be toggled in mlbviewer with the 's' key.
If you still have problems after this revision, change 'debug=0' to debug=1 in ~/.mlb/config and post the error here.
Not sure why I removed the saving of sessionkey but I'm restoring the writing and reading of the sessionkey file.
Those of you who were having sign-on restriction errors, please try starting mlbviewer, selecting a stream, quit, restart, and repeat. See if you get sign-on errors across mlbviewer restarts. The revision earlier should fix the problem of multiple streams during a single mlbviewer session. This revision, I hope, should fix the problem of sign-on restriction across multiple mlbviewer sessions. At least that's the plan.
I'm calling this a Sourceforge candidate build. If this fix works as I hope it will, then I'm uploading this revision to Sourceforge as the main download link. Of course, I will continue to check patches into SVN but the main download tarball is there for people who don't really care about day-to-day fixes or don't want to keep up with SVN or this thread. The sourceforge build is intended to last until the next time MLBAM changes something (which hopefully won't be for awhile.)
I hadn't cleared any of these before trying; I'll do so next time, and also post session.xml after each attempt.
Hopefully I'll also get a chance to debug that mlbhls -F thing a little further, but I may not get to that today...
To clarify, you get the restriction within the same session (no mlbviewer restart) or across sessions? If you are getting it within the same session, we still have a problem. Across sessions might not be fixable even with the sessionkey file.
Well, you know how to hit it where it hurts, now don't do that. I'm working on adding more debug to see that I'm doing it right.
To clarify, you get the restriction within the same session (no mlbviewer restart) or across sessions? If you are getting it within the same session, we still have a problem. Across sessions might not be fixable even with the sessionkey file.
Yeah, this is with restarting mlbviewer in between each attempt. I tried again and backed up the cookie and session info before and after each try (although I missed the cookie before the first try).
Yeah, this is with restarting mlbviewer in between each attempt. I tried again and backed up the cookie and session info before and after each try (although I missed the cookie before the first try).
That third try is what I have after the restriction.
Still no ftmu info written anywhere that I can see...
How about cookielog?
ftmu you are not going to get until I figure out another page to get ftmu from. Getting the session-key from the first media reply seems to work alright. I think what's odd is that fprt (fingerprint) is changing (that's not that odd) so when you give the server the old session key with a new fingerprint, it objects, gives you a new session-key (which we handle just fine), and rings up your first strike. Three strikes, you're out.
Until I find another mlb.com web page you can get ftmu from, I think you're just going to have to limit your restarts. Keep an mlbviewer always open...as it should be.
Cookielog should be the second link there. Unless you just meant that I didn't need to post all the other stuff!
No worries anyway, I can avoid restarting. It's still weird if you can do it and I can't, but really, meh.
Was searching google for ftmu last night and was reading the xbmc thread. It seems to be a difference between premium and basic/gameday subscribers. I guess premium gets to watch more.
Yeah, look for more debug added later this weekend. But I'm guessing I'm not really going to get anywhere with that. One thing I can and should do is toss out the session-key if the fingerprint has changed. I don't think that will really do anything for you though.
hey guys, i was directed here from the ubuntuforums about this issue for future updates...
i just loaded up a preseason game today and see they rolled out a new version of their player, a few weeks ago it was still last years version, its larger by default, the non-nexdef quality bar has alot more levels than previous years of just 3, but when i loaded up last years method for running the jar file for mac (Nexdef version Autobahn 4.2.21.MLB_10_122) first off, i just had to F5 the popup window in chrome and it loads up very fast compared to the stupid "white line going to each base" process last year
how ever there was still only the 5 quality levels in Nexdef, like last year but all 5 levels looked drastically better, hardly no compression artifacts at all, even during fast action camera pans
so my question is,when the newer jar file comes out this year, will it just be as simple as putting it where i have the current version and when i load up the terminal code it will replace it, or will there need to be more to it?
and how exactly can you find the raw URL to download the jar file cause the download url on the mlb site is a popup process and after clicking it, a # sign is added at the end but nothing ever pops up and i cant save the jar file.
but apart from that, worst case scenario, would i be able to just keep using my current version of nexdef to watch this seasons games with perhaps just minor limitations(all of last years Nexdef options but no new ones(whatever those might be)) if the newer one cant be implemented?
hey guys, i was directed here from the ubuntuforums about this issue for future updates...
i just loaded up a preseason game today and see they rolled out a new version of their player, a few weeks ago it was still last years version, its larger by default, the non-nexdef quality bar has alot more levels than previous years of just 3, but when i loaded up last years method for running the jar file for mac (Nexdef version Autobahn 4.2.21.MLB_10_122) first off, i just had to F5 the popup window in chrome and it loads up very fast compared to the stupid "white line going to each base" process last year
how ever there was still only the 5 quality levels in Nexdef, like last year but all 5 levels looked drastically better, hardly no compression artifacts at all, even during fast action camera pans
so my question is,when the newer jar file comes out this year, will it just be as simple as putting it where i have the current version and when i load up the terminal code it will replace it, or will there need to be more to it?
and how exactly can you find the raw URL to download the jar file cause the download url on the mlb site is a popup process and after clicking it, a # sign is added at the end but nothing ever pops up and i cant save the jar file.
but apart from that, worst case scenario, would i be able to just keep using my current version of nexdef to watch this seasons games with perhaps just minor limitations(all of last years Nexdef options but no new ones(whatever those might be)) if the newer one cant be implemented?
This forum has really morphed into a project called "mlbviewer" which is an open source terminal based method of selecting games and launching them in an external player like mplayer2. For nexdef, this project doesn't use autobahn.jar anymore. I'm not sure what current version of autobahn.jar does anymore (been awhile since I decompiled it), but the nexdef streams are basically Apple's HTTP Live Streaming (HLS) protocol which is supported, at least by this project, with an external utility called mlbhls.
If trying something other than the Flash player and getting your hands slightly dirty with terminal stuff doesn't sound too scary to you, give it a day or two and I'll have the current development version packaged (and documented) for download on sourceforge.
Mlbviewer used to have this feature that would allow you to start live nexdef games from the beginning of the broadcast even before the game was finished and archived. The configuration file option is 'live_from_start'. If set to 1 or True, live nexdef games will open from the start of the broadcast. If false, you'll jump in wherever the action happens to be....otherwise known as a live broadcast.
Even if you have no interest in this feature, please update to this revision and tell me I didn't break anything.
If this last minute "fix" didn't break anything, revision 361 with updated documentation will go live as the main Sourceforge download later this weekend. This might be a new record to have a fully-functional Sourceforge release before Opening Day...well, North America Opening Day anyway.
I know it's April Fool's Day, but this is no joke.
The 2012 official release has gone live on Sourceforge!
Thanks guys for helping me test this release and get it ready for public download.
You all know how much time I put into this. If you would like to give back, I would happily accept a donation of any size. Please see the bottom of the README for my Paypal address.
Thanks to everyone who helped out this spring and everyone who has helped out over the years.
Is anyone else seeing the mlb hls option fail with a message "mlbhls failed - invalid option -F"? My player command is mlbhls -B aHR0cDovL21sYmxpdmUtbDNjLm1sYi5jb20vbHMwNC9tbGJhbS8yMDEyLzA0LzAzL01MQl
9HQU1FX1ZJREVPX1NFQUNPTF9IT01FXzIwMTIwNDAzL21hc3Rlcl93aXJlZC5tM3U4fEFJNFlWTllydX
lrYk5LNWdYTHlITXhWOXk1Yz18cGxheWJhY2s9SFRUUF9DTE9VRF9XSVJFRCZjb250ZW50SWQ9MjAzMT
M0MzMmYXBwQWNjb3VudE5hbWU9bWxiJmV2ZW50SWQ9MTQtMzMyNTY1LTIwMTItMDQtMDMmaXBpZD03Nz
c1MTUzJnNlc3Npb25LZXk9TVVOVmslMkZWeWlIdSUyQkhLTXpGd0h5UU90QkdNUSUzRA== -L -s 450
0000 -F 16:00:13 -o - | mplayer -cache 2048 -
for today's Mariners @ Rockies game.. they're in the 6th inning as I tried this. I get the same error and seg fault with archived games as well, with or without live from start.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.