How the heck to I add returns to the code box lol? So, it doesn't scroll forever in my runoff sentences.
|
Quote:
Trust me. You don't want to use rtmpdump. I mean, it's okay for archive but it totally sucks for live video. It's great for audio both live and archived. You also can only get 800K max from rtmpdump. The quality bars map out to 164, 400, 600, 800 for non-nexdef. Anything higher than 800 requires nexdef. In other news, I finally got a troublesome bit of code figured out for stream selection. Now I'm going out dancing and I'll finish up that piece of code when I get back. |
Hey Dafcat, Since this morning, mlbviewer suddenly stopped working.
Here is the error message: Code:
Traceback (most recent call last): |
BTW, for all Ubuntu users, who want an easy way to install pyxml and suds:
Code:
sudo apt-get install python-setuptools |
Today by chanche I stumbled upon rtmpy, which seems an rtmp enabling extension to the twisted engine.
What may be interesting is a) it's in python. b) they have a client example in their sources. For what I understood by some inaccurate reading twisted should be a network abstraction layer so you could uniform rtmp and swarmcast interaction and maybe simplify your work. from the other side I don't know if this is worth the mess of learning a new middleware. Just a hint for you developers out there. |
Quote:
|
RE: System requirements
Quote:
Code:
1.7 Ghz , 512 Mb RAM Code:
rtmpdump... I live in my team's blackout region, so archives only for me Code:
Only watch off peak, no experience. Code:
Never have a stream drop. Occasional audio/video sync issues, autosync usually clears those p. Code:
NA Code:
800K... best I can get. At least MLB has been letting me chose home or away streams... No Hawk |
Quote:
|
Quote:
It seemed like more effort than it was worth to try and reinvent rtmpdump from poorly documented RTMPy. Thanks anyway, though. |
Quote:
Unfortunately, I do a lot of manipulation on the time so when the time is listed as "Gm2" instead of a real time, it's going to fail in multiple places. Fortunately, I've been working on new code to use a different xml to get the listings. At least in this xml they fudged the time as 3:33 AM. Which is weird because you'll get Game 2 appearing before Game 1 in the listings. But at least it will be there. This code is almost ready. Stay tuned. In the meantime, if you want to watch yesterday's games, start mlbviewer with a startdate of yesterday: Code:
$ mlbviewer startdate=04/27/09 |
Thank you very much !!!
1. What specs do you have: CPU / RAM Code:
Dual Core 1.7 Ghz, 3 GB Ram Code:
awesome next-def all the way Code:
with mplayer really good. Flash player barely usable. Code:
nearly perfect with mplayer, except for occasional audio off-sync. Code:
Way better. Code:
max_bps = 300000 |
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
|
I stumbled upon mlbviewer almost by accident. I can't heap enough praise on you guy~!! This is AWESOME!
1. What specs do you have: CPU / RAM Code:
2.10 GHz Intel Core 2 Duo, 3GB RAM (6 mo. old HP laptop) Code:
Nexdef Code:
Excellent. Very occasional hiccups in stream. Code:
Amazing. Code:
Overall better with mlbviewer. Code:
Premium subscriber so whatever is highest. Looks simply amazing. |
SVN revision 171: A lot of testing code still unfinished
The doubleheader today has forced my hand to check in a lot of unfinished code.
I had started to work on parsing the media listings from grid.xml instead of epg.xml. Fortunately, this paid off because epg.xml has the start time= element of the second game of the doubleheader as "Gm2" which is failing the time parsing code. While grid.xml just made up a time for the game 2 (3:33 AM.) So at least that gets through all the time parsing code. Also, I parse these games in listing order rather than time order so Game 2 does appear after Game 1 in the listings unlike my earlier post stated. The majority of the unfinished code isn't used so I'm not going to bother explaining it just yet. One thing you will notice in this new code is that I poll nexdef with control messages about every ten seconds and update the screen with the currently selected stream. This way you guys can know what stream you are actually using* and when the stream up or down shifts on you. It's still the same max_bps code meaning all you are doing is specifying what you can handle. It's still up to nexdef to decide what it's going to give you. The stream adjustment code will be in a future revision. Because of the poll code, it may take up to 10 seconds to return to the listings after the player quits and it may take longer if mplayer decides to take its time exiting after a "read failed" error. This is part of the unfinished bit of the code. *I suspect many of you think you are getting the 3000K stream but are actually getting the 2200K stream (still a damn fine stream, by the way.) There's really nothing I can do right now to fix this just yet but at least now you'll know for sure. Gameday audio and non-nexdef users, you can update to this revision to get the doubleheader fix ("Need more than one value to unpack") but please continue to use mlbdvr. Your integration code isn't ready yet. |
As a non-nexdef user, do live games work? (with rtmpdump I assume) and if they do, are there any problems with them. You seemed to say that they were not working well, but that would imply that they are at least working. If they are working, how do you get them up, just the normal way with mlbviewer.py?
|
All times are GMT -5. The time now is 08:43 PM. |