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.
Please add "debug=True" to your config file and run mlbviewer.py again.
Post the stack trace that it generates here for me to see where the parser is failing.
Pay no attention to the LIRC errors. These are harmless. Basically, if you have an IR remote, you can use LIRC to control mlbviewer. I don't have one so I've never been able to test this code. I'm not sure if anyone else is using this because I've never received a bug report on it.
But yeah, if mlblistings.py is working, pyxml is also working. So the only thing I can think of is that there is some config file option that isn't right. I just tested with the default config (e.g. renamed my config and let it autogenerate a new one) and didn't have any parser problems.
Can you do the following:
1. Post your config here (don't post your user and pass.)
2. Add or change debug=0 to debug=True and post whatever stack trace is generated when you get the parser failure.
I may not be able to replicate my success, but I managed to get mlbviewer up and running on cygwin (windows 7). seems to work really well... now I may try to get it running on my netbook and see if it's better than snow leopard.
Pay no attention to the LIRC errors. These are harmless. Basically, if you have an IR remote, you can use LIRC to control mlbviewer. I don't have one so I've never been able to test this code. I'm not sure if anyone else is using this because I've never received a bug report on it.
I've got a remote, and IIRC it worked fine "out of the box" with mlbviewer. However, I have since re-written the LIRC code in my local copy (version control software is neat) so I'm not sure about the original code anymore. Now that I think about it, perhaps the LIRC code wasn't working and that's why I rewrote it...I don't really remember. If you'd like, I can tidy up my code and send you patch at some point.
Pay no attention to the LIRC errors. These are harmless. Basically, if you have an IR remote, you can use LIRC to control mlbviewer. I don't have one so I've never been able to test this code. I'm not sure if anyone else is using this because I've never received a bug report on it.
But yeah, if mlblistings.py is working, pyxml is also working. So the only thing I can think of is that there is some config file option that isn't right. I just tested with the default config (e.g. renamed my config and let it autogenerate a new one) and didn't have any parser problems.
Can you do the following:
1. Post your config here (don't post your user and pass.)
2. Add or change debug=0 to debug=True and post whatever stack trace is generated when you get the parser failure.
Thanks!
Sorry it took so long to reply - I was at work but now I am home and ready to watch some baseball.
Traceback (most recent call last):
File "/usr/local/bin/mlbviewer.py", line 1508, in <module>
curses.wrapper(mainloop, mycfg.data)
File "/usr/lib/python2.6/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/local/bin/mlbviewer.py", line 206, in mainloop
raise Exception, detail
KeyError: 'blackout'
I hope this helps, and I apologize in advance for what I'm sure is a user error on my side. Thanks a ton!
I don't see any problems with your config.
That trace is kind of helpful but I see you already have blackout defined in your config file. Even when I leave blackout blank, I don't have a parser problem. One thing I did notice is that my line numbers don't match up with yours.
It's not until around revision 210 (the last Sourceforge release) that the line numbers match up.
Did you just download this from sourceforge?
Okay, here's what I want you to do. Install subversion if you don't have it already. Then checkout the latest svn version (development version) of the code and run setup.py again.
Code:
$ sudo apt-get install subversion
$ svn co https://mlbviewer.svn.sourceforge.net/svnroot/mlbviewer/trunk mlbviewer-svn
$ cd mlbviewer-svn
$ python setup.py install
Now when I post about future revisions (the post "Title" is always something like: SVN Revision 237: Some Description of What's Fixed), you'll only need to cd to this directory and run svn up, e.g.
Code:
$ cd mlbviewer-svn
$ svn up
It's an honest mistake. I was going to wait until NexDef is implemented but since Sourceforge release is obviously broken, I'll update it with the latest svn code later tonight.
Hmm...weird. I just downloaded revision 210 and the outer error, the first line number, matches up with yours, line 1508, but the inner error doesn't match up.
In any case, because /usr/local/bin/mlbviewer.py appears in your stack trace, it looks like you have already run setup.py once before. In that case, making sure you have the latest svn revision and running setup.py again should get everything back in sync. If it doesn't, we might have to perform some detective work to remove old components first.
is there anyway someone could make an idiot's step by step on how to get mlbviewer working. just signed up for mlb.tv yesterday, flash is so crappy on linux, and i am very overwhelmed with trying to install mlbviewer, sifting thru this 182 page thread. is there a simple guide anywhere, or could someone copy/paste all the right steps. the requirements 2009 file is a bit over my head.
if anyone is interested in knowing how to set up mlbviewer on windows 7, (should work for any windows though) let me know I may write up a guide for how I did it...
took me roughly 15 minutes start to finish once I knew what I was doing.
I got mlbviewer working for the first time tonight, but I can't get the 1800k stream to work - every game says "no video." I don't know if it's just me, or are there just no games available at that bitrate today?
I got mlbviewer working for the first time tonight, but I can't get the 1800k stream to work - every game says "no video." I don't know if it's just me, or are there just no games available at that bitrate today?
I checked the grid.xml file, the file used to generate the listings and there are no 1800K streams listed today. Perhaps they're experiencing/anticipating problems with those streams? 1200K looks available though. Sorry that 1800K isn't available on your first day of mlbviewer but glad at least that code to tell you so is working.
is there anyway someone could make an idiot's step by step on how to get mlbviewer working. just signed up for mlb.tv yesterday, flash is so crappy on linux, and i am very overwhelmed with trying to install mlbviewer, sifting thru this 182 page thread. is there a simple guide anywhere, or could someone copy/paste all the right steps. the requirements 2009 file is a bit over my head.
Well, the requirements file is nearly definitive but let's see if I can sum it up for you.
Almost there. At this point, after running mlbviewer once, it will generate a config file at ~/.mlb/config (where ~/ is your home directory.) Edit that config file filling in your MLB.TV username and password in the user= and pass= lines.
You're still not quite there yet. You need rtmpdump to actually get the Flash video streams to mplayer.
This part might fail so I'm separating it from the rest.
Code:
$ svn co svn://svn.mplayerhq.hu/rtmpdump/trunk rtmpdump
$ cd rtmpdump
$ make posix
If this fails, first edit the Makefile and change this line:
Code:
LIB_OPENSSL=-lssl -lcrypto
to this:
Code:
LIB_OPENSSL=-ldl -lssl -lcrypto
And then re-run the "make posix".
If that works, do this:
Code:
$ sudo cp rtmpdump /usr/bin/rtmpdump
If that doesn't work, post the output of "make posix" here and we'll figure out what is still needed.
If you've gotten this far without any errors, you can now go back to mlbviewer and hopefully you'll be up and running:
Code:
$ cd ../mlbviewer-svn
$ python mlbviewer.py
If you're stuck, please post as much output as you can from the step that failed here so we can help get you going again.
(Hopefully we can skip the re-compile mplayer step but we'll figure that out when we get there.)
This whole process may take a few days between posting problems and getting solutions here. Please be patient. I've tried to make the installation process as easy as possible (using as few additional libraries as I can) but it's definitely not idiot proof. We'll get you through it though. I promise the users here are much more responsive and helpful than the MLB.TV support forums.
its somewhat related because you use a bash terminal in windows (cygwin) and a lot of various linux components to make it work... and as far as I know this is the only forum where mlbviewer is discussed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.