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.
SVN Revision 106 fixes a logic error in the media indications (in case you're aiming for 105 and wondering why you got 106.)
You can also use 'svn log' to see what's in the most recent svn revision.
Code:
matthew@tango:~/mlbtv/svn/mlbviewer$ svn log | head
------------------------------------------------------------------------
r106 | daftcat75 | 2009-02-26 20:29:44 -0800 (Thu, 26 Feb 2009) | 2 lines
Fixed a logic error in media availability indicators.
------------------------------------------------------------------------
r105 | daftcat75 | 2009-02-26 19:55:09 -0800 (Thu, 26 Feb 2009) | 3 lines
Added media availability indication to status line for ease of use during
Spring Training.
svn: Write error: Broken pipe
matthew@tango:~/mlbtv/svn/mlbviewer$
I'm new here -- if I do an svn up do I need to run the setup.py again?
(Thanks for all of your work on this -- it's totally excellent.)
If you ran setup.py even once, then I would guess you'll need to run it every time you do a svn up. Just a guess though. Personally, I never used setup.py since I want to make sure the code I'm running is the code I just changed. Give it a try without running setup.py and jump to Mar 6 or start at Mar 6 with:
Code:
./mlbviewer.py startdate=03/06/09
If it crashes out, it's using the previously installed library and you'll need to run setup.py every time you svn up.
If you ran setup.py even once, then I would guess you'll need to run it every time you do a svn up. Just a guess though. Personally, I never used setup.py since I want to make sure the code I'm running is the code I just changed. Give it a try without running setup.py and jump to Mar 6 or start at Mar 6 with:
Code:
./mlbviewer.py startdate=03/06/09
If it crashes out, it's using the previously installed library and you'll need to run setup.py every time you svn up.
Let me know what the result is.
I tried using my previous version first for today's games. It told me there were no games today (didn't catch the exact error).
Then I svn upped in the source directory and did 'sudo python setup.py install', which ran fine and then mlbviewer could find today's games. Awesome.
Has anyone watched a Spring Training game video yet? Have you found that the audio portion hisses and pops?
I've tested this with:
- 2009 game, Linux mplayer, win32 codecs (hisses and pops)
- 2008 game, Linux mplayer, win32 codecs (sounds fine)
- 2009 game, Windows mplayer, win32 codecs (hisses and pops)
- 2009 game, Windows Media Player, (sounds fine)
If it weren't for the last result, I'd just write it off as Spring Training. Then again, there's no use worrying about it now since it will likely change next month. Still, it's been annoying enough that I haven't watched any Spring Training games. I'd like to catch at least some of the WBC.
Please let me know if you have video that doesn't hiss and pop with 2009 Spring Training and what player/codec version you are using.
Has anyone watched a Spring Training game video yet? Have you found that the audio portion hisses and pops?
I've tested this with:
- 2009 game, Linux mplayer, win32 codecs (hisses and pops)
- 2008 game, Linux mplayer, win32 codecs (sounds fine)
- 2009 game, Windows mplayer, win32 codecs (hisses and pops)
- 2009 game, Windows Media Player, (sounds fine)
If it weren't for the last result, I'd just write it off as Spring Training. Then again, there's no use worrying about it now since it will likely change next month. Still, it's been annoying enough that I haven't watched any Spring Training games. I'd like to catch at least some of the WBC.
Please let me know if you have video that doesn't hiss and pop with 2009 Spring Training and what player/codec version you are using.
Thanks!
daftcat
No problem except the White Sox -Dodger game today went into a big squeal. I figured maybe the sound card had drank draino but it turned out to be just that particular feed and after disconnecting and reconnecting all was fine. Other games I've watched have been okay too.
Sound is okay here with either mplayer or vlc. Codecs are whatever Arch supplies. Doesn't VLC come with codecs now too? Anyhow, VlC now works when it wouldn't last year, both video and audio. Sorry I can't be more specific.
Opening day, that will be the test. Wonder how they'll screw it up this year. To protect myself against that inevitability I've put a tiny install of XP into a tiny partition on an old laptop. That'll give me a fallback until you can fix the inevitable. You are indispensable man, be around on opening day for the hopefully quick fix.. pretty please, sugar on top.
i am not too smart when it comes to using the terminal in ubuntu, so i hope someone can help me with my questions concerning watching some of the spring training games. when i start mlbviewer on today's date (march 2nd) it tells me "there was a parser problem with the listings page" and shows me no games for today.
then, as readme told me, i checked out the svn repository on sourceforge. this is what my terminal did show me.
Quote:
mrks@kom:~/Programme/mlbviewer-0.1alpha8$ svn co https://mlbviewer.svn.sourceforge.ne...lbviewer/trunk mlbviewer
A mlbviewer/test
A mlbviewer/test/mlbgameid.py
A mlbviewer/LICENSE.txt
A mlbviewer/mlbviewer.py
A mlbviewer/INSTALL
A mlbviewer/setup.py
A mlbviewer/MLBviewer
A mlbviewer/MLBviewer/LIRC.py
A mlbviewer/MLBviewer/__init__.py
A mlbviewer/MLBviewer/mlbtv.py
A mlbviewer/MLBviewer/config.py
A mlbviewer/README
Ausgecheckt, Revision 107.
what can i do next? i have no idea... mlbviewer practically hasn't changed a bit...
thanks so much for all the work on mlbviewer, it is an amazing tool!
markus
i am not too smart when it comes to using the terminal in ubuntu, so i hope someone can help me with my questions concerning watching some of the spring training games. when i start mlbviewer on today's date (march 2nd) it tells me "there was a parser problem with the listings page" and shows me no games for today.
then, as readme told me, i checked out the svn repository on sourceforge. this is what my terminal did show me.
what can i do next? i have no idea... mlbviewer practically hasn't changed a bit...
thanks so much for all the work on mlbviewer, it is an amazing tool!
markus
Just run
Code:
python mlbviewer.py
in the directory where the new svn files are and you ought to be back in business.
No problem except the White Sox -Dodger game today went into a big squeal. I figured maybe the sound card had drank draino but it turned out to be just that particular feed and after disconnecting and reconnecting all was fine. Other games I've watched have been okay too.
Sound is okay here with either mplayer or vlc. Codecs are whatever Arch supplies. Doesn't VLC come with codecs now too? Anyhow, VlC now works when it wouldn't last year, both video and audio. Sorry I can't be more specific.
Opening day, that will be the test. Wonder how they'll screw it up this year. To protect myself against that inevitability I've put a tiny install of XP into a tiny partition on an old laptop. That'll give me a fallback until you can fix the inevitable. You are indispensable man, be around on opening day for the hopefully quick fix.. pretty please, sugar on top.
What version of mplayer are you using?
I tried recording the stream to see if it was a network issue and that's a no-go. Still hisses and crackles. I was hoping it was just a 400K vs 800 K issue because the hiss and crackle is what eventually turned me off of the MiLB.TV offering (that and only a couple of games a day and usually the same four teams.)
I'm tempted to play hookey on Opening Day but it's quite possible that more than half the problems we run into in Opening Month are on MLB.com's end rather than mlbviewer.
So....I just encourage you all to have some patience and check back here frequently in April. I'll try to fix any problems on mlbviewer's end within a day or two but I'm quite sure I'll be answering, "there's nothing mlbviewer can do to fix mlb.com" quite a bit in the first month.
i am not too smart when it comes to using the terminal in ubuntu, so i hope someone can help me with my questions concerning watching some of the spring training games. when i start mlbviewer on today's date (march 2nd) it tells me "there was a parser problem with the listings page" and shows me no games for today.
then, as readme told me, i checked out the svn repository on sourceforge. this is what my terminal did show me.
what can i do next? i have no idea... mlbviewer practically hasn't changed a bit...
thanks so much for all the work on mlbviewer, it is an amazing tool!
markus
The changes in recent revisions are very subtle (as are the problems they fixed.)
At least until Opening Day, the mlb.com service hasn't changed much and so mlbviewer hasn't had to change much. A little defensive code here and there to handle exhibition games with unknown or "to be determined" team codes was added. New teamcodes are added as they put up new listing pages. I don't expect to (and really don't want to) change anything big until Opening Day because your guess is as good as anyone else's (including mine) about whether mlbviewer will even work with the 2009 regular season service. This is also a big reason why I haven't cut a new official release with these recent changes yet.
I tried recording the stream to see if it was a network issue and that's a no-go. Still hisses and crackles. I was hoping it was just a 400K vs 800 K issue because the hiss and crackle is what eventually turned me off of the MiLB.TV offering (that and only a couple of games a day and usually the same four teams.)
I'm tempted to play hookey on Opening Day but it's quite possible that more than half the problems we run into in Opening Month are on MLB.com's end rather than mlbviewer.
So....I just encourage you all to have some patience and check back here frequently in April. I'll try to fix any problems on mlbviewer's end within a day or two but I'm quite sure I'll be answering, "there's nothing mlbviewer can do to fix mlb.com" quite a bit in the first month.
I really have no idea. Since Arch is allegedly "cutting edge" I assume it is the latest or close to it since I stay updated well. Below is what the package manager says.
[mike@arch ~]# pacman -Si mplayer
Repository : extra
Name : mplayer
Version : 28347-2
URL : http://www.mplayerhq.hu/
I can't find a command for the version with a $ mplayer --help
and $ mplayer --version comes up with this.
MPlayer dev-SVN-rUNKNOWN-4.3.2 (C) 2000-2009 MPlayer Team
There is also a Gmplayer which has a little GUI control box and in the "about" section where you can often find the version number...nothing but a picture of a girl and a list of credits to the developers.
Not having problems with video or audio is for the *400* stream though. I didn't give them the extra bucks for the faster one being the DSL connection up here has been so erratic getting the slow one I consider to be a blessing. And not having problems means that I just lost the video feed totally somewhere around halfway through the Sox-Mariner game today.<snicker>
I was using mplayer-1.0rc2 that I built myself. I reinstalled the mplayer packaged by debian which is an SVN version (not sure if it's older or newer than rc2) and that seems to have fixed it. On the windows side, I downloaded an svn version with the gui. The gui is nice and the sound hisses quite a bit less, but still has a hiss/crackle to it. Not enough to be annoying though. Thanks Wolfvorkian!
I've found using mlbviewer within "screen" to be very useful. Although screen does mangle some of the curses gui like the horizontal rule, the colors still show up, and what screen allows makes it invaluable for me.
Quick demo of what a typical session would be for me:
Start screen.
Start mlbviewer.
Select a game and begin playback.
Detach the session using Ctrl-A, then Ctrl-D key sequence.
Now the terminal is re-usable for other tasks.
When game is over, you can screen -r to reattach to the session.
For me, this is an awesome option because I watch games remotely, e.g. there's a laptop connected to a wall mounted monitor that I ssh into and start a game from another, remote laptop on the couch. If I lose the ssh session (been known to happen), I lose the game I was watching. If I've detached the session, I can shutdown the remote laptop and the game still continues to play.
If I lose the ssh session (been known to happen), I lose the game I was watching. If I've detached the session, I can shutdown the remote laptop and the game still continues to play.
Just so you know, you don't even have to detach the session. As long as you're 'screen'ed, the process will not die if you lose your terminal session.
I'm looking forward to seeing how they implement things come opening day. I am really, really hoping they move to .flv and they add a 720p stream. I would probably cry with joy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.