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.
Has anyone else tried the new PostSeason.TV support in mlbviewer? Or is this like the bookmark feature (a cool feature that nobody uses)?
I'm an international subscriber, so I can't comment on that. I just wanted to say thanks, because I'm using it to watch the postseason archives after they have aired. It has been working fine since the LDS finished.
What python version are you running? Are you running the latest SVN off the nexdef2010 branch?
What happened to your ~/.mlb directory?
EDIT: Python 3? Yeah, not looking into that until next season. Install python 2.6. That's the last that I've qualified. You might have to write a wrapper script to explicitly call python2.6 like:
What a pain in the a$$!!! I just started reading python3.0 documentation and they changed print to be a function. Ain't no way I'm going to support python3.0 anytime soon (meaning probably not this offseason either unless I find something really compelling in python3.0 that mlbviewer can't live without.) I haven't read the entire rationale for the changes, but I slightly resent the "intentionally backwards incompatible" nature of python3.0. I can't get super-upset about that because I intend to make mlbviewer intentionally backwards incompatible since MLB.TV changes every year and the if/else madness of keeping previous seasons working isn't worth it.
If anyone wants to view previous seasons, let me know. I'll create separate mlbviewer branches for each season. Kind of a pain, but I'm going to remove the setup.py script so you can have an mlbviewer parent directory and 2008/, 2009/, 2010/, etc subdirectories.
But it seems from the lack of bug reports when I break previous season support (just like bookmarks), that (at least among the ones who post here), none of you really care about watching games from previous seasons once the season has finished.
What a pain in the a$$!!! I just started reading python3.0 documentation and they changed print to be a
[big snip]
here), none of you really care about watching games from previous seasons once the season has finished.
Do you figure you'll be using python 3 by next season? I suppose you'll be forced to eventually but if not, I've got a Debian type distrution on another old computer that is using python 2.6 + and Mlbviewer works fine. I'll just use it if you aren't planning on going to 3.
Another question while I've got your attention is that I can no longer build Mplayer using the sh configure --enable-dynamic-plugins --prefix=/usr
I get this and then the process halts. "Error: yasm not found, use --yasm='' if you really want to compile without". Doing what it says doesn't work because when it finishes and tells me to use "make", it then dies too.
Oh great! That means my next few months are going to suck!
Let me set the proper expectations based on several years of experience.
First few weeks of Spring Training, they'll be using the same platform as last year with maybe a few minor changes to the XML files just to keep things exciting for me.
Starting in the last week or two of Spring Training, they'll roll out the beta of the 2011 MLB.TV. This is where it gets "interesting."
If the last two or three years are any indication, it may take a few weeks to get all the bugs worked out and they probably won't be all on my side.
Expect non-nexdef service to start working smoothly by May. Or as I was fond of saying last year, when David Ortiz is batting above .250. ;-)
For nexdef? Who knows? I never really got it working well at all last year. It seemed like last year should have been a slam dunk. They turned the plugin into a proxy but there was something that just didn't quite work between rtmpdump and the plugin.
Side note: There was a guy from the librtmp/ffmpeg team who chimed in last year about ffmpeg supporting RTMP directly using the URL to form the headers. Unfortunately, his example of that was the diff file he used to patch libRTMP/ffmpeg. Since I'm not a C/C++ programmer, that meant very little to me. If you're still reading this thread, can you please give me a real example? I can give you a real argument list we pass to rtmpdump if you could show me how to convert that into an mplayer URL. Thanks!
Speaking of which, anyone know where rtmpdump/flvstreamer live these days?
And to whoever asked last season, I'm not planning to support python 3.0. Didn't look at it at all this off-season. What I remember from briefly looking at it last year, I would have to fork and re-write mlbviewer to support it because they intentionally made it backwards-incompatible. (Those jerks!
Finally, while I loved receiving the donations last year, there's always a chance MLBAM will do something to the service that makes it impossible for mlbviewer to support it. So unless you're unconditionally generous or the gambling type, I wouldn't want to take your money unless I knew I could deliver a working product. Might want to hold off on your donations until the real 2011 service rolls out in late March and I see what I'm up against.
Ah, Spring is in the air. The smell of fresh-cut grass tells me it's time to put this thread back in its familiar tab, right between Gmail and the Boston Globe.
I looked around and it appears that there hasn't been any active development on flvstreamer in nearly a year. The changelog for rtmpdump shows no updates since June 2010. I've posted to the ffmpeg list about this so hopefully we'll soon have some trees up which to bark.
Optimistically looking forward to another season of quietly upstaging MLBAM!
Not getting any bites on ffmpeg-users concerning the ability to access RTMP content with publisher authentication. But it looks like ffmpeg can be built against librtmp, which appears to be the magic behind rtmpdump. That said, I can't tell whether librtmp has been updated any more recently than rtmpdump has. And beyond that, the ffmpeg man page section concerning RTMP streams looks just like the man page for librtmp, except that the subsection on "Security Parameters" does not appear in the ffmpeg documentation. I guess the only way to test is to use the documented syntax for librtmp and pass it to ffmpeg and see what happens.
Since mplayer uses librtmp through ffmpeg, assuming ffmpeg works, it may now be possible to use mplayer without needing rtmpdump as an intermediary.
First bug fix for 2011. Missing the daylight saving time dates for 2011.
You should now see the games listed for Saturday.
No promises that they'll actually be playable, though.
As with all previous seasons, please be patient and don't expect things to work smoothly until mid-April or early May. It's a good thing baseball is a six month season.
EDIT: Fixed on nexdef2010 branch. Haven't got around yet to branching for 2011.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.