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.
Does GMT even have a DST setting or do you have to manually adjust to GMT+1 later this month?
I just realized that the fix becomes more complicated, at least the way I have the code now, because the first conversion (ET to UTC) has to check ET for DST. The second conversion (UTC to localtime) has to check the local timezone for DST. I think it's just easier, for now anyway, to bring the time_offset= functionality back.
Does GMT even have a DST setting or do you have to manually adjust to GMT+1 later this month?
Nah, I never touch the thing. I just wake up on the morning it changes and the time's correct. I'm not sure whether the timezone then changes to BST (British Summer Time) or just applies it, but it works correctly.
Quote:
I just realized that the fix becomes more complicated, at least the way I have the code now, because the first conversion (ET to UTC) has to check ET for DST. The second conversion (UTC to localtime) has to check the local timezone for DST. I think it's just easier, for now anyway, to bring the time_offset= functionality back.
That woud be fine, I'm sure. As was mentioned upthread, this is a pretty easy issue to work around, especially because most of the live games are very late at night in Europe; so I (and I assume most other users) tend to watch archived games the next day, and the time doesn't matter in that case.
Does GMT even have a DST setting or do you have to manually adjust to GMT+1 later this month?
That's not a particularly meaningful question. Do you have to manually adjust for EDT (assuming you are on the east coast)? Most devices will surely automatically handle it for you? I do not know of any computer operating system which does not do so.
If your question is "does Western Europe have a daylight savings time", then the answer is yes. Not every country does. Much of Asia does not for example.
That's not a particularly meaningful question. Do you have to manually adjust for EDT (assuming you are on the east coast)? Most devices will surely automatically handle it for you? I do not know of any computer operating system which does not do so.
If your question is "does Western Europe have a daylight savings time", then the answer is yes. Not every country does. Much of Asia does not for example.
No, I was specifically asking about GMT itself. Seeing as that's the reference point for all other timezone offsets, it would seem confusing to me to shift GMT as well. For example, Pacific, where I am, is GMT-8 during standard time and GMT-7 during DST. If GMT also changed, then I would expect it to only be GMT-7 for the few weeks where US shifts before UK. So if there's no manual intervention, then it's likely that GMT, in his case, is just an alias for another timezone that does observe DST. I'll definitely be asking for date output from fang2415 again in a couple of weeks.
In the meantime, there are routines and libraries to localize times based on timezones, etc. Time to learn some new classes. I've basically got two problems to work out here. The listings are in Eastern time so they need to be converted to UTC according to EDT offset. The second conversion to local time must be done according to the local timezone's DST rules and offset. Currently, as in just revision 590, it's a single call to time.localtime().tm_isdst. That should work correctly for the second conversion, but the first one needs to be mindful of ET DST rules rather than local DST rules. All of this is me just thinking aloud but now I know the task ahead.
GMT here is analogous to EST in NY, and BST is analogous to EDT. As far as I can recall, the British machines will automatically apply the GMT/BST changes the same way a New Yorkian machine would apply an EST/EDT change. But I'll try to post back later in the month with the details.
No, I was specifically asking about GMT itself. Seeing as that's the reference point for all other timezone offsets, it would seem confusing to me to shift GMT as well.
OK I see. GMT/UTC stays the same throughout the year (as does Eastern Standard Time, Central European Time, etc). Clocks advance from that to British Summer Time, as they do to Eastern Daylight Time and Central European Summer Time, and so forth. All time zone designations are deliberately non-ambiguous.
Stupid question perhaps, but I am nothing if not daring. I gave mlbviewer a brief spin last year and really liked it. However, life intervened (job lost, job found, Linux distro changed), and now I sort of find myself starting from scratch. I now want to install mlbviewer on my laptop running openSUSE 13.1. Am I correct in thinking I need to start by downloading and installing the various components from the Sourceforge page and then installing svn so I can get the incremental updates that may appear throughout the season?
Also, while the Sourceforge page lists the files required, there are no installation instructions. Do I correctly guess that those would be found in a file within mlbviewer once it is downloaded and unpacked? Since I successfully installed mlbviewer last year on anothe distro, I am assuming (perhaps incorrectly) I can do so again successfully this year - also assuming I can find and/or remember my login and password for MLB.com.
Stupid question perhaps, but I am nothing if not daring. I gave mlbviewer a brief spin last year and really liked it. However, life intervened (job lost, job found, Linux distro changed), and now I sort of find myself starting from scratch. I now want to install mlbviewer on my laptop running openSUSE 13.1. Am I correct in thinking I need to start by downloading and installing the various components from the Sourceforge page and then installing svn so I can get the incremental updates that may appear throughout the season?
Also, while the Sourceforge page lists the files required, there are no installation instructions. Do I correctly guess that those would be found in a file within mlbviewer once it is downloaded and unpacked? Since I successfully installed mlbviewer last year on anothe distro, I am assuming (perhaps incorrectly) I can do so again successfully this year - also assuming I can find and/or remember my login and password for MLB.com.
Thanks for all you do.
There's no common installer and prerequisites are not automatically included or installed by mlbviewer because there are just too damn many distributions and they all manage packages and package versions differently.
Look in YaST for the dependencies I mention and install anything else those dependencies require (YaST should do that for you but I have no experience with that one.) If you want to use mlbhls ("Nexdef" streams), you'll need to install subversion, make, and gcc. You'll need subversion (svn) to pull the latest mlbhls source because their official download is too old.
Give it a go with this and let us know if you get stuck.
There's no common installer and prerequisites are not automatically included or installed by mlbviewer because there are just too damn many distributions and they all manage packages and package versions differently.
Look in YaST for the dependencies I mention and install anything else those dependencies require (YaST should do that for you but I have no experience with that one.) If you want to use mlbhls ("Nexdef" streams), you'll need to install subversion, make, and gcc. You'll need subversion (svn) to pull the latest mlbhls source because their official download is too old.
Give it a go with this and let us know if you get stuck.
Because I did not reformat my /home directory when I changed distributions, I had some bits of mlbviewer still on my computer. After installing python, rtmpdump, mplayer2, and svn, I was able to get mlbviewer working. I do still have a couple of questions, though.
At the time I originally installed, mlbviewer had one structure and directory (mlbviewer-2013). Then it went through some changes and the directory became mlb2013. Can I safely delete the mlmbviewer-2013 directory, or are there bits from there still used? Second, how important or useful is mlbhls if I do not have a premium subscription from MLB.tv? Thanks again.
Because I did not reformat my /home directory when I changed distributions, I had some bits of mlbviewer still on my computer. After installing python, rtmpdump, mplayer2, and svn, I was able to get mlbviewer working. I do still have a couple of questions, though.
At the time I originally installed, mlbviewer had one structure and directory (mlbviewer-2013). Then it went through some changes and the directory became mlb2013. Can I safely delete the mlmbviewer-2013 directory, or are there bits from there still used? Second, how important or useful is mlbhls if I do not have a premium subscription from MLB.tv? Thanks again.
If you cd into either one of those directories and type "svn info" and it comes back with something like "URL: http://svn.code.sf.net/p/mlbviewer/code/trunk" or "URL: svn://svn.code.sf.net/p/mlbviewer/code/trunk" in the output, you should only need to do an "svn up" to get to the latest. You can rename the directory to mlbviewer or mlb2014 if you want.
If you get "svn: '.' is not a working copy" instead, you're using a sourceforge download which is almost guaranteed to be too old. Honestly, very little has changed in 2014 so far, but that's about to change soon. MLBAM uses the previous year's offering for Spring Training and then rolls out the current year offering usually in the last week of Spring Training.
As for mlbhls, it used to be that only premium subscribers could access the "nexdef" or HLS streams. Or at least that's what I thought. However, it seems that basic subscribers can also use the HLS streams, but they just don't get access to the very top level streams (3000 kbps.)
So it just comes down to personal preference. Some find that the rtmpdump streams are more stable. Some like the HLS streams better. One thing the HLS streams can do that the rtmpdump streams cannot is adapt the bitrate to network conditions. If your network is slowing down, it adjusts to a slower bitrate until your network speeds up again.
However, this may all change soon. In the product brief for MLB.TV this year, they said something about doing away with the Nexdef plugin (which is what mlbhls emulates), so who knows whether the HLS streams will even be available this season.
I ran into some of the error stuff about my version being too old, but once I found the right directory, I was able to "svn up," and I now have version 590, which is the latest - correct? It sounds like I can safely delete the older directory. My installation of openSUSE actually saved my menu links for mlbviewer and mlbvideos, so I just need to double-check which directory is actually the old one. As for mlbhls, I may wait and see what happens with Nexdef. Thanks.
Last edited by WaltH; 03-20-2014 at 02:14 PM.
Reason: added missing word
Second, how important or useful is mlbhls if I do not have a premium subscription from MLB.tv?
There are three main things mlbhls offers you if, like me, you only have the basic subscription. First, mlbhls will give you the home team's radio commentary when watching the TV feed as an alternative to the home team's standard TV commentary - some people prefer that (with mplayer, press # to cycle through the audio feeds). Secondly, if you are watching an archived game, mlbhls will provide you with a 800kb/s stream whereas the standard feed (via rtmpdump) will not - the standard feed will only give you a 800kb/s stream when viewing live. All the other speeds (500k, 1200k, 1800k and 2400k) are available archived and live on both. Thirdly, mlbhls allows you to watch from the beginning of the game if the game is already underway when you start viewing.
If you cd into either one of those directories and type "svn info" and it comes back with something like "URL: http://svn.code.sf.net/p/mlbviewer/code/trunk" or "URL: svn://svn.code.sf.net/p/mlbviewer/code/trunk" in the output, you should only need to do an "svn up" to get to the latest. You can rename the directory to mlbviewer or mlb2014 if you want.
If you get "svn: '.' is not a working copy" instead, you're using a sourceforge download which is almost guaranteed to be too old. Honestly, very little has changed in 2014 so far, but that's about to change soon. MLBAM uses the previous year's offering for Spring Training and then rolls out the current year offering usually in the last week of Spring Training.
I get this error: "svn: E155007: '/home/walt/mlb2013' is not a working copy" even though I downloaded and installed mlbviewer-sf-8, and that is the version number shown when I launch the application, yet I get the error I posted earlier when I try to upgrade or check for upgrades. Have there been that many changes since version eight was posted on Sourceforge? If so, is there any way for me to upgrade, or do I just need to wait for version nine? Thanks.
I get this error: "svn: E155007: '/home/walt/mlb2013' is not a working copy" even though I downloaded and installed mlbviewer-sf-8, and that is the version number shown when I launch the application, yet I get the error I posted earlier when I try to upgrade or check for upgrades. Have there been that many changes since version eight was posted on Sourceforge? If so, is there any way for me to upgrade, or do I just need to wait for version nine? Thanks.
SVN updates cannot be performed from Sourceforge releases. One is the stable release and the other is (potentially) not as stable. If you want to get onto the SVN releases, delete all your mlbviewer directories (except /home/walt/.mlb) and do the following:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.