I can't recall anyone referring to "IT" prior to about 1990. This term seems to be a fad that sprouted up sometime in the '90s - but now people are acting as if it's an established term that's been around forever.
"Note the open server page mentions nothing about streaming Windows media, QuickTime, MPEG2 or 4, simply Real. All it seems to support is RTSP/RTP/RTCP/SDP
You seem to be confusing codecs and protocols. It turns out that the (open IETF standard) RTSP/RTP/RTCP/SDP protocols are those that QuickTime uses for streaming. These protocols are also widely used for streaming MPEG-2 (and MPEG-1), and are the protocols that everyone will be using to stream MPEG-4.
OTOH, some codecs that QuickTime and RealNetworks stream (using RTSP/RTP/RTCP/SDP) remain closed, and (presumably) won't be included in the Open Source release.
FYI, the "LIVE.COM Streaming Media" software (which includes test programs) will let you stream pre-encoded MPEG-1 or 2 video and/or audio from Windows or Linux (or other Unixes). The streaming is done using open standard RTP/RTCP/RTSP protocols, so you can view the streams using any compliant player (including QuickTime Player). You can also stream live video with this software, if you have a seperate (hardware or software) encoder.
At present the software streams MPEG-1 or 2; MPEG-4 will be supported shortly.
FYI, "LIVE.COM Streaming Media" is a set of Open Source (LGPL)libraries and test programs that can be used to stream video and/or audio using the open standard RTP/RTCP protocol.
These libraries can currently stream (pre-encoded) MPEG-1,2 or H.263+ video. (Support for MPEG-4 is coming.) (To stream live video, you will need a separate (hardware or software) MPEG or H.263+ encoder.)
Am I the only person who's a bit disturbed by the number of product announcements that have been posted as stories recently? While I concede that many of these product announcements might indeed be considered newsworthy, I also note that Slashdot's parent company (VA Linux) is hard up for money right now.
Could Slashdot's editors state - for the record - that they (or VA Linux) are not receiving any special consideration in exchange for posting product announcements as stories?
One good application for playing with multicast over a LAN is liveCaster. This lets you stream MP3 files via multicast. (Receiving software is also available.)
Also, source code libraries for multicast streaming (using RTP) are available here ("LIVE.COM Streaming Media")
It's an IETF standard. (ISO/OSI did, indeed, have a set of internetworking protocol 'standards' that were competing against TCP/IP, but they lost that battle hands-down in the '80s, as it became clear that TCP/IP was the de facto standard.)
IANAL, but I fail to see how Thomson (or anyone else) could have any legal basis for charging royalties for streaming MP3 (or MPEG audio of any form).
Certainly the encoding and decoding of MPEG audio is covered by patents, and is thus licenseable.
(And obviously the content of some MPEG audio files is protected by copyright.) But once you already have encoded MPEG audio data, to stream this data requires only unencumbered, open standard protocols (TCP, or RTP (RFC2250 or RFC3119)).
It's hard to see how any restriction on the streaming of pre-encoded, non-copyrighted audio could have any legal weight. In fact, such a restriction might even be seen as a violation of free speech rights...
Yes, Cliff Skolnick of "BAWUG" - the San Francisco Bay Area wireless interest group mentioned in the article - has such a database (for the Bay Area) online here. (See the "map" links for latitude/longitude coordinates that you can enter into a GPS receiver.)
Re:Isn't .mars a bit of an Ameriocentric name?
on
The Dot in .mars
·
· Score: 1
(such as an Ethernet, or a wireless LAN)
You can stream MP3 via multicast using liveCaster. (This is built from the Open Source "LIVE.COM Streaming Media libraries.)
ps. Why don't all/. articles go on the front page? Most readers probably don't even know that non-front-page articles (like this one) even exist.
Not quite true. MPlayer now has support for RTSP/RTP streaming.
> I've installed mplayer on two SuSE 8.0 linux machines, and it's amazing.
> You can see DVD's, AVI's and even look at at microsoft media streams.
Even better, mplayer can now play open standard RTSP/RTP streams.
I can't recall anyone referring to "IT" prior to about 1990. This term seems to be a fad that sprouted up sometime in the '90s - but now people are acting as if it's an established term that's been around forever.
You seem to be confusing codecs and protocols. It turns out that the (open IETF standard) RTSP/RTP/RTCP/SDP protocols are those that QuickTime uses for streaming. These protocols are also widely used for streaming MPEG-2 (and MPEG-1), and are the protocols that everyone will be using to stream MPEG-4.
OTOH, some codecs that QuickTime and RealNetworks stream (using RTSP/RTP/RTCP/SDP) remain closed, and (presumably) won't be included in the Open Source release.
Apparently "blackpaper" means "white text on a black background".
Please - this is one fad from the '90s that deserves to die, quickly.
At present the software streams MPEG-1 or 2; MPEG-4 will be supported shortly.
These libraries can currently stream (pre-encoded) MPEG-1,2 or H.263+ video. (Support for MPEG-4 is coming.) (To stream live video, you will need a separate (hardware or software) MPEG or H.263+ encoder.)
See this link.
Microsoft may be evil, but none of their web pages commit the sin of having white text on a black background :-)
It's bad enough when the Slashdot editors tell us whether or not an article is "interesting"; it's even worse when the author of the article tells us.
Enough of the hucksterism! Let us evaluate these articles ourselves.
Or even better, Boring!
Could Slashdot's editors state - for the record - that they (or VA Linux) are not receiving any special consideration in exchange for posting product announcements as stories?
Also, source code libraries for multicast streaming (using RTP) are available here ("LIVE.COM Streaming Media")
"Should individuals and businesses be allowed to use encryption to prevent penetration of their computers and communications by terrorists?"
The results of the poll would have been very different.
Geez, slashdot, I'm glad you finally decided to post a story about this. I guess my two earlier submissions weren't enough of a hint.
It's an IETF standard. (ISO/OSI did, indeed, have a set of internetworking protocol 'standards' that were competing against TCP/IP, but they lost that battle hands-down in the '80s, as it became clear that TCP/IP was the de facto standard.)
Certainly the encoding and decoding of MPEG audio is covered by patents, and is thus licenseable. (And obviously the content of some MPEG audio files is protected by copyright.) But once you already have encoded MPEG audio data, to stream this data requires only unencumbered, open standard protocols (TCP, or RTP (RFC2250 or RFC3119)).
It's hard to see how any restriction on the streaming of pre-encoded, non-copyrighted audio could have any legal weight. In fact, such a restriction might even be seen as a violation of free speech rights...
I hope I'm not the only person to see the irony here...
When Armstrong stepped onto the moon, it was July 20th in the U.S., but further East (much of Europe, Asia, Australia, New Zealand) it was July 21st.
No, not every article. The article about the keystroke capturing dongle was actually not an April Fools prank. There really are devices like this.
That's the problem with having so many April Fools stories. Legitimate stories don't get taken seriously.
Yes, Cliff Skolnick of "BAWUG" - the San Francisco Bay Area wireless interest group mentioned in the article - has such a database (for the Bay Area) online here. (See the "map" links for latitude/longitude coordinates that you can enter into a GPS receiver.)
".MA" is already taken - it's for Morocco.
ps. Why don't all /. articles go on the front page? Most readers probably don't even know that non-front-page articles (like this one) even exist.