By the way, the NLCS game last night had FOX-NAT and FOX-INT streams. I was able to access the international stream by checking for 'fox_auth_required', just like tbs and mlbn.

At a guess, libcurl wasn't updated to use the new certificate store. At any rate, this is definitely a bug in libcurl/nss/ca_certificates, and not in mlbViewer or mlbhls.

Yeah. I'll probably go submit an Arch bug report. Thanks for your help.

I haven't used mlb-viewer the last few seasons, although it was always a great project. I remember when mlb.tv was pretty broken on ANY platform and mlb-viewer worked amazingly well. It was always a pleasure to see it running on any of my systems.

I also remember testing it and getting my account banned, and daftcat's connection within mlb.tv got it reinstated for me. I owe him one for that.

With that said, I wanna say this:

GO ROYALS!!

I know Daftcat is a Royals fan, and he always stuck with them over the years, through ups and (mostly) downs. It's gotta feel good for him to see that squad perform at this level.

As a cubs fan, I can only envy what that team is doing. *sigh*

Sirius XM keeps replaying Gm 7 and I keep hoping Aoki's ball gets past Crawford, Panik doesn't make the catch that leads to the double play, Hosmer doesn't slide into first, and/or Jurschele sends Gordon home. Still, it was a great run and far more than I had expected.

Cubs are getting Maddon so that should help next year.

Hi everyone, just raising this post from its offseason slumber to see if anyone is aware of what sort of changes are coming to the MLB streaming landscape for 2015. MLB just sent out my MLB.tv renewal notice, and they talk about a new web-based player:

Anyone have any idea what to expect in terms of compatibility with mlbhls, the MLBViewer scripts, etc.? I would hate to have to go back to using a web-based player when these tools have worked so well in previous years.

Not sure why I didn't see this post earlier...

Spring training isn't just for the players. MLB.TV will be using last year's player for the bulk of March while they finish development and test of their 2015 player. We probably won't get a look at the 2015 offering until the last week or so of March and it probably won't be stable on their end in the first two or three weeks of the season.

It's a long season. Don't sweat any slow or rocky starts this early. ;)

I finally got a smart TV and some inexpensive toys to connect to it: a Roku, a ChromeCast, and a Raspberry Pi. And I have to say, mlbviewer on the Pi is very awkward, even for me, compared to any of those other devices. Now of course, this is still just pre-season and there's only a fraction of the load on their servers this early. But I am hopeful that one of the toys will provide a smooth experience. That screen is too pretty to waste on buffering and dropouts.

I have only just started to look into Pi and mlbviewer but so far, I'm not impressed. I got everything installed just to learn that the mplayer2 packaged with Raspbian or in the Wheezy sources is not hardware accelerated. I did find omxplayer, but it has no option to stream from standard input. I hacked together a video_player= line to dump the stream to a file and then played from the file in omxplayer from a different terminal. After all that, the picture quality was far below Samsung TV app, the Roku, and the ChromeCast. Also, omxplayer bailed before the stream was finished being dumped. Which brought home just how many cool features will be cut off at the knees because omxplayer cannot stream from stdin. Anyway, that's all I want to look at this tonight. I believe at least one of you had asked about the Pi last year. If you got anywhere with it with mlbviewer, please share with me what you did. Thanks!

Hey people, happy spring!

So, now that there are actually some video feeds available, I wanted to check: is mlbhls (or nexdef) working for anyone? When I attempt to use mlbhls for any stream, I just get this ad infinitum:

I get this for live streams, recent archived streams, and archived streams from last year. I'm pretty sure it's not a login permissions issue because it persists after waiting several hours, and the rtmp streams (always) work fine for video and audio.

Also, this seems very new: a couple weeks ago I tested my existing mlbviewer setup by loading the Cubs game from July 26, 2014, and everything including mlbhls worked as expected. Now, using mlbhls to loading the same game with the same setup on the same computer gives me an error like the one above (and again, the rtmp streams work perfectly).

Frankly, I've been kind of expecting this, since MLBAM has been trumpeting how they're switching away from the nexdef plugin, so it would make perfect sense for them to shut down those streams now (indeed, it's great that they're not waiting until the real season!). But of course who knows if they'll have some sort of legacy support hidden in there somewhere...

Anyway, I figure this might be the start of the hunt for a way to handle the new format, so I wanted to check if the old one is broken for everybody or just for me.

Let the games begin!

Also, daftcat, sorry to hear the Pi has been a PITA -- I looked into buying one a little while ago but lost interest once I learned how tightly locked down the video chip was (the proprietary GPU *controls the CPU*!).

But I wonder if there's a version of the vanilla mplayer that can get good video on the Pi? If so, that should work for the rtmp streams, and, if the mlbhls streams start working again, you could use the patch I posted at http://www.linuxquestions.org/questi...chmentid=14848 to play them?

Mind you, that's all a bit academic if the mlbhls streams are gone for good since you'll need to make sure that a new player will play an as-yet-unknown format...

mlbhls working for me.

What distro are you using? I suspect the distro messed with the certificates/certificate authority crap (not my strong point here.) Can you try a game from 2014 (e.g. mlbviewer.py startdate=10/01/2014)? If that's also broken, then it's likely an environment/distro issue and nothing to do with mlbviewer/mlbhls itself.

Just want to remind you that there is a live CD / virtual machine version of mlbviewer that I have verified working for 2015 preseason:

http://sourceforge.net/projects/mlbv...files/mlblive/

It could use an "svn up" though to bring in media detail screen and any late season bug fixes.

It's a useful way to determine whether you have an environment issue or a genuine bug since the environment is already locked down.

Because of the proprietary GPU, mplayer does not support hardware acceleration on the pi. I am looking at a fork of omxplayer to get stdin playback working.

I am also considering the CuBox-Pro. I'm intrigued by the IR transmitter it has.

But currently, I'm watching the Royals on my Roku and loving it. So far. I understand pre-season is easier than regular season on their networks so we'll see how well the Roku streaming and buffer management is in a few weeks.

It has been working OK for me, so far. It looks as if something using libcurl does not like the certificate chain offered by mlb.tv, and in particular that one of the intermediate certificates is out of date. Presumably, one of the python modules called up by mlbviewer uses libcurl - I do not think mlbviewer does so directly.

You probably just need to update your certificate bundle.

Hmm interesting, thanks for the info. I get that same error on two computers running Ubuntu 14.04 LTS, and like I say it persists with games from 2014. And the systems are pretty up-to-date (I just did an apt-get dist-upgrade on one of them yesterday). Does seem a little strange that one of them worked great two weeks ago but not now...

Anyway now that I know it's working for other people at least I know to keep trying. (And thanks for the live CD reminder, I might give that a try.) Fingers crossed it'll just magically work next time I log in.

(It does make me wonder if/when the nexdef streams will go away though... Surely they won't keep serving them forever?)