Article View: alt.comp.hardware
Article #1649Re: TV and PC
From: kony
Date: Fri, 28 Nov 2003 19:41
Date: Fri, 28 Nov 2003 19:41
81 lines
5665 bytes
5665 bytes
On 28 Nov 2003 08:44:34 -0800, ecmcdougall@iname.com (ECM) wrote: ><Nittaku> wrote in message news:<3fc1395c$0$28292$ba620e4c@reader1.news.skynet.be>... >> "ECM" <ecmcdougall@iname.com> wrote in message >> news:232689b7.0311221855.62889dfc@posting.google.com... >> > <Nittaku> wrote in message >> news:<3fbe483e$0$21196$ba620e4c@reader3.news.skynet.be>... >> > > >> > > I found this in a Hauppage FAQ: >> > > >> > > http://www.hauppauge.com/html/stream.htm >> > > >> > > Comments on this? Will it work? Possible problems? >> > >> > I think this might (as long as it's stable software) work fine to help >> > encode your captures to Windows Media format, but you'd still need to >> > publish them to your intranet. This software from Hauppage doesn't >> > encode then stream at the same time - I'm getting the feeling that >> > this is really what you want.... it IS tempting - watching TV on your >> > WiFi Tablet or laptop PC anywhere in the house you want to. The >> > technology isn't up to the challenge yet, though. We'll need >> > gigabit(or at least 100 Mbit async) WiFi, and some serious software >> > and hardware development before this'll happen. >> >> This I don't understand. >> >> Encoding a TV signal in real time is possible, the hauppage card does it. >> Sending data across a 100Mb network should be enough too. I don't see why >> technology isn't up to the challenge yet. > >Well, I think you could stream VCR quality (352X240, 30fps) across a >wired 100 mbit network - that's about SVCD quality. My comment was >that a wireless network, even 802.11g (or .11a), would not be adequate >for that kind of bitrate. > >I think we'll have to see what the next 5 years holds for wireless LAN >- I'm not sure we'll see much of an increase in data transfer rates. >Remember that a lot of the bitrate increases we saw in the 90's (for >instance with modems) was due to better hardware compression BEFORE >transmission, not to more raw data being transmitted through the same >pipe. Video is already pretty optimally compressed - try "zip"ing an >MPEG file sometime - and it won't respond to this strategy. We need a >quantum shift in technology to be able to effectively stream high >quality video wirelessly, not tweaking of the current stuff. > >And as for software, it usually is developed in response to available >hardware. The hardware is not really up to the task yet, so very >little software is available to do what you want. Even the "bleeding >edge" types wouldn't spend a lot of money on technology that would >allow them a small blocky picture with lots of pauses on $2000+ worth >of equipment, when they can turn on a sub-$100 TV and get a far >superior image..... > >Anyways, an interesting thread! >Good Luck! >ECM We don't really need any of that. All that's needed with current technology to achieve better than VCR quality is a server-side app that can use a conexant chipset card as input, compress to divx and stream it, and a client-side app "expecting" the format details communicated to it by the server app, so it can pick up the stream at a keyframe. Current CPUs sold are fast enough, 10Mb lan as well as 802.11g is fast enough, even 802.11b is "almost" fast enough for 640x480 at reasonable bitrate, a few dropped frames if the signal is degraded. The applications just aren't there yet. There really isn't any good reason to use SVCD unless you need to play it in a modern DVD player. The other codecs can have increased bitrate if that level of quality is desired, but bitrate chosen as necessary to fit the available network. Old systems benefitted from hardware-compression cards but today higher quality can be had (and more control over it) with software compression. It's just not something that could be done with a system that's slow, therefore being semi-retired but expected to do this demanding task. Dave
Technical Details
Message-ID:
<3k8fsv8vbaehvhko0jnnk2vmj0n0s9o85t@4ax.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!attbi_s51.POSTED!not-for-mailReferences:
<bpjokh$250o$1@nl-news.euro.net> <dscrrv0fsoqveous5lmictehham9u09gi9@4ax.com> <3fbddf8b$0$26300$ba620e4c@reader1.news.skynet.be> <rvqrrvo12mspse9cm2fbhtq98go8jcki4n@4ax.com> <3fbdf70c$0$21182$ba620e4c@reader3.news.skynet.be> <232689b7.0311210814.2129c42f@posting.google.com> <3fbe483e$0$21196$ba620e4c@reader3.news.skynet.be> <232689b7.0311221855.62889dfc@posting.google.com> <3fc1395c$0$28292$ba620e4c@reader1.news.skynet.be> <232689b7.0311280844.1028ea35@posting.google.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f8da1,bad1893caf8b3ea1 X-Google-Attributes: gidf8da1,public X-Google-Thread: 112149,bad1893caf8b3ea1 X-Google-Attributes: gid112149,public X-Google-Thread: f5f89,bad1893caf8b3ea1 X-Google-Attributes: gidf5f89,public X-Google-Thread: 1151bb,bad1893caf8b3ea1 X-Google-Attributes: gid1151bb,public X-Google-ArrivalTime: 2003-11-28 11:41:32 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!attbi_s51.POSTED!not-for-mail From: kony <spam@spam.com> Newsgroups: alt.comp.hardware,comp.hardware,nl.comp.hardware,be.comp.hardware Subject: Re: TV and PC Reply-To: spam@spam.com Message-ID: <3k8fsv8vbaehvhko0jnnk2vmj0n0s9o85t@4ax.com> References: <bpjokh$250o$1@nl-news.euro.net> <dscrrv0fsoqveous5lmictehham9u09gi9@4ax.com> <3fbddf8b$0$26300$ba620e4c@reader1.news.skynet.be> <rvqrrvo12mspse9cm2fbhtq98go8jcki4n@4ax.com> <3fbdf70c$0$21182$ba620e4c@reader3.news.skynet.be> <232689b7.0311210814.2129c42f@posting.google.com> <3fbe483e$0$21196$ba620e4c@reader3.news.skynet.be> <232689b7.0311221855.62889dfc@posting.google.com> <3fc1395c$0$28292$ba620e4c@reader1.news.skynet.be> <232689b7.0311280844.1028ea35@posting.google.com> X-Newsreader: Forte Free Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 81 NNTP-Posting-Host: 12.220.107.118 X-Complaints-To: abuse@insightbb.com X-Trace: attbi_s51 1070048492 12.220.107.118 (Fri, 28 Nov 2003 19:41:32 GMT) NNTP-Posting-Date: Fri, 28 Nov 2003 19:41:32 GMT Organization: Insight Broadband Date: Fri, 28 Nov 2003 19:41:32 GMT