MLB.TV in Linux

daftcat · 04-02-2013, 07:15 PM

So I had more waiting around time at work to look into it and it wasn't that hard at all to add five seconds to the published start of game. Combined with thegryghost's edits in rev62 and 63, it seems all archived nexdef games including my beloved Royals are starting from the correct time now. Now you will be able to actually watch the game before seeing the "Thank You For Watching" screen.

Please update your mlbhls and your mlbviewer to the latest revisions.

I have tested my hack with the latest mlbhls for several (but not all) games. If you still see any problems with games starting at the incorrect time (my hack should be isolated to just the nexdef start of game), tell me which day and which game.

Thanks thegryghost for your continued support.

thegryghost · 04-02-2013, 07:43 PM

Quote:

Originally Posted by daftcat

Thanks for the awesome support!

Bos@NYY and Mia@Was yesterday work from start with 63.

Now to a game I actually care about.

KC@Cws still seems to be affected.

X-PROGRAM-DATE-TIME is 2013-04-01T20:00:06+00:00 and innings start_time is 20:00:06. So the date-time minus the -F is 0. Since that's less than 5 seconds, that gets set to 1. Correct? The first timestamp in the file is 20/00/07. This seems like it should be a perfect match to your algorithm. But instead it starts playing from the end (a 23/../...ts something timestamp.) I realize my "fix" for getStartOfGame would not be so easy as I will need to convert the string to a time structure before adding the five seconds to make sure a published start time of hh:mm:56 does not become a nonsense value of hh:mm:61. Still something I might do, but just not right now.

I just commited another fix (rev 64). The code assumed that the user specified start time would always be greater than the playlist start time. In the KC@CWS, the times are equal so mlbhls never even tried to find the proper position.

Again, let me know if it's still broken and I'll try to fix it

edsmith123 · 04-02-2013, 08:33 PM

Quote:

Originally Posted by daftcat

Weird. Default config file writes a coverage= setting. I suppose you could have removed it. Not sure how to defend against that in the code. Maybe in the loads() routine, I can do a check of mandatory parameters? I'll have to think that one over to see how to fix it.

But I'm glad you got it working again.

I may have just accidently overwritten that line in the config and not noticed.

daftcat · 04-02-2013, 08:38 PM

Quote:

Originally Posted by thegryghost

I just commited another fix (rev 64). The code assumed that the user specified start time would always be greater than the playlist start time. In the KC@CWS, the times are equal so mlbhls never even tried to find the proper position.

Again, let me know if it's still broken and I'll try to fix it

Perfect. I have commented out the hack and I think I am just about ready to check in the sourceforge release at the nice round number of revision 400.

daftcat · 04-02-2013, 09:08 PM

In what may be a record, first sourceforge release is posted just three days into the season.

First sourceforge release denotes all major functionality is tested and working.

For those who like version number trivia, the sourceforge release is called "2013rev400sf-1" (first sourceforge release for 2013.) And shortly after the link went live, I revved the version number to "2013rev401+". This means any of you who continue to stay up-to-date on the SVN releases will be using a revision that is at least 401 or newer. I will eventually look into getting svn to auto-increment my version string for me. Until then, it probably won't change much unless I do another sourceforge release or I want to mark a major change like post-rewrite (the last time I changed the version string.)

randcoop · 04-03-2013, 03:16 AM

I'm using mlbhs version 64 and mlbviewer version 401. Trying to go back a couple of days and watch the nexdef archive doesn't work...it drops me to the end of the game. It does the same thing when I try to go to an inning. It says it's trying to get to 17:31, but I'm put at the end of the game anyway.

But trying yesterday's games, it works...although admittedly, it takes me to the Game Will Start Shortly message for a long time (several minutes). Jumping to the top of the first inning sort of solves that problem, since that worked.

I can't explain why the archive from two days ago doesn't work, but the one from yesterday works.

daftcat · 04-03-2013, 03:27 AM

Quote:

Originally Posted by randcoop

I'm using mlbhs version 64 and mlbviewer version 401. Trying to go back a couple of days and watch the nexdef archive doesn't work...it drops me to the end of the game. It does the same thing when I try to go to an inning. It says it's trying to get to 17:31, but I'm put at the end of the game anyway.

But trying yesterday's games, it works...although admittedly, it takes me to the Game Will Start Shortly message for a long time (several minutes). Jumping to the top of the first inning sort of solves that problem, since that worked.

I can't explain why the archive from two days ago doesn't work, but the one from yesterday works.

Two days ago doesn't help me. Which game?

splittter · 04-03-2013, 08:23 AM

Just started using mlbviewer this season, looks awesome, thanks a lot.

Got a question about the 'jump to innings' feature, should it be able to differentiate between the Home and Away feeds? At the moment I think it's only playing Home. I'm set to follow the Giants, and if I start the nexdf stream of last night's game at the Dodgers normally I get the Giants coverage, but using jump to innings (was trying T1) I always got the Dodgers stream. I then looked at the Cardinals/Diamondbacks game, and could toggle between Home & Away streams fine when starting normally, but jump to innings was always the same one.

Am using rev401, if that's the way things are, fair enough, but thought I'd ask.

daftcat · 04-03-2013, 12:23 PM

Quote:

Originally Posted by splittter

Just started using mlbviewer this season, looks awesome, thanks a lot.

Got a question about the 'jump to innings' feature, should it be able to differentiate between the Home and Away feeds? At the moment I think it's only playing Home. I'm set to follow the Giants, and if I start the nexdf stream of last night's game at the Dodgers normally I get the Giants coverage, but using jump to innings (was trying T1) I always got the Dodgers stream. I then looked at the Cardinals/Diamondbacks game, and could toggle between Home & Away streams fine when starting normally, but jump to innings was always the same one.

Am using rev401, if that's the way things are, fair enough, but thought I'd ask.

Short answer: lazy coding bug. Should be fixed now in rev402.

Longer answer: the entire GUI and a lot of the backend got rewritten this Spring Training to re-organize and clean up the code. The very first thing I wanted to rewrite was the innings window (which was a mess just mashed into the "Big Daddy Action": audio, video, condensed games, and highlights are handled in one major clause) even before I had the logic for follow and coverage rewritten. To get the new code working, I just chose the first video entry which happens to be home. I forgot to update that piece of code once I had rewritten the preferred media selection (choose follow first if present and matching, then prefer coverage setting, and finally default to home if neither is available.)

randcoop · 04-03-2013, 12:32 PM

Quote:

Originally Posted by daftcat

Two days ago doesn't help me. Which game?

I tried both the Yankees Red Sox and the Washingon games of April 1 (hence, two days ago).

splittter · 04-03-2013, 01:17 PM

Quote:

Originally Posted by daftcat

Short answer: lazy coding bug. Should be fixed now in rev402.

Longer answer: the entire GUI and a lot of the backend got rewritten this Spring Training to re-organize and clean up the code. The very first thing I wanted to rewrite was the innings window (which was a mess just mashed into the "Big Daddy Action": audio, video, condensed games, and highlights are handled in one major clause) even before I had the logic for follow and coverage rewritten. To get the new code working, I just chose the first video entry which happens to be home. I forgot to update that piece of code once I had rewritten the preferred media selection (choose follow first if present and matching, then prefer coverage setting, and finally default to home if neither is available.)

Thanks a lot, updated and it works fine.

daftcat · 04-03-2013, 01:42 PM

Quote:

Originally Posted by randcoop

I tried both the Yankees Red Sox and the Washingon games of April 1 (hence, two days ago).

Yes, but when I saw your message, that was only one day ago for me. I have mlbviewer users in Europe, Asia, and Australia while I'm in California. I wasn't going to make an assumption on where you were or what "two days ago" meant in your timezone.

That's surprising because Yankees-Red Sox game was the first one we focused on to get it working.

There is no "make install" for mlbhls. Is it possible that you didn't actually replace your mlbhls binary? I always do it this way to make sure it overwrites the one that mlbviewer is likely to pick up:

Code:

$ make clean && make && sudo cp mlbhls $(which mlbhls)

If you are certain that you are actually using the rev64 binary, then can you see if my 5 second hack works? Uncomment lines 655-658 in MLBviewer/mlbSchedule.py. Search for "hack" and uncomment these four lines that follow that comment:

Code:

                            #d=datetime.datetime.strptime(start_time, "%H:%M:%S")
                            #t=datetime.timedelta(seconds=5)
                            #n=d+t
                            #start_time=n.strftime("%H:%M:%S")

If that works for you, I could make enabling that code a configuration file option.

If I get a chance today, I can add some additional debugging to the log file to help you get the information we (mlbhls dev and myself) would need to see what exactly is going on at your end.

randcoop · 04-03-2013, 05:36 PM

Quote:

Originally Posted by daftcat

Yes, but when I saw your message, that was only one day ago for me. I have mlbviewer users in Europe, Asia, and Australia while I'm in California. I wasn't going to make an assumption on where you were or what "two days ago" meant in your timezone.

That's surprising because Yankees-Red Sox game was the first one we focused on to get it working.

There is no "make install" for mlbhls. Is it possible that you didn't actually replace your mlbhls binary? I always do it this way to make sure it overwrites the one that mlbviewer is likely to pick up:

Code:

$ make clean && make && sudo cp mlbhls $(which mlbhls)

If you are certain that you are actually using the rev64 binary, then can you see if my 5 second hack works? Uncomment lines 655-658 in MLBviewer/mlbSchedule.py. Search for "hack" and uncomment these four lines that follow that comment:

Code:

                            #d=datetime.datetime.strptime(start_time, "%H:%M:%S")
                            #t=datetime.timedelta(seconds=5)
                            #n=d+t
                            #start_time=n.strftime("%H:%M:%S")

If that works for you, I could make enabling that code a configuration file option.

If I get a chance today, I can add some additional debugging to the log file to help you get the information we (mlbhls dev and myself) would need to see what exactly is going on at your end.

First, I understand about the days and meant nothing by my parenthetical comment about two days. I'm in Europe and 9 hours ahead of the US west coast time.

Second, you're correct. It turns out that I was apparently not truly updating the version of mlbhls (I was simply using svn to update). I promise not to make that mistake again. The games play correctly now, including the older archived games.

mchapter · 04-03-2013, 08:09 PM

Looking good daftcat.

Went to watch the phils @ barves, a couple hours in. It looks like the live_from_start setting is not recognized, which lead me to another oddity: after 2 hours of game time, on the innings screen mlbviewer shows "Last available half inning is: Bot 14"

i'm using mlbhls version 64 and mlbviewer 402.

daftcat · 04-03-2013, 09:09 PM

Quote:

Originally Posted by mchapter

Looking good daftcat.

Went to watch the phils @ barves, a couple hours in. It looks like the live_from_start setting is not recognized, which lead me to another oddity: after 2 hours of game time, on the innings screen mlbviewer shows "Last available half inning is: Bot 14"

i'm using mlbhls version 64 and mlbviewer 402.

live_from_start: wouldn't doubt it. More than a few things didn't make it into the rewrite. I can add that later tonight.

innings oddities I can also look into. Sounds like I forgot to do a minus 10 somewhere. I believe I have the top innings in innings[x] where x is 1-9 and the bottom innings in innings[y] where y is 11-19. I bet if you wait until the top of 6th inning, it will say, last available Bot 15. I guess I should look at that one now while there are still live games available.