🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: uk.tech.digital-tv
Article #197

Re: Using an FM-Carrier for the Y [Luminance] Signal -- how to relieve the bandwidth issue?

#197
From: Bob Myers
Date: Thu, 01 Nov 2007 08:15
38 lines
3117 bytes
"Green Xenon [Radium]" <glucegen1@excite.com> wrote in message 
news:47295e0d$0$11519$4c368faf@roadrunner.com...


> Anyways, the QAM should be given the highest practical bit-resolution. 
> 1-symbol-per-second should be the baud.

Fine,  but the question remains - what the hell is so important
about "1 symbol per second"?  Why do you CARE?


> The minimum voltage should be set to 1.6e-19 volt. This is the voltage of 
> one electron.

Wrong.  Electrons have charge, expressed in coulombs, not
voltage.  Go figure out the difference, and come back.


>
> The bit-resolution should be high enough that each "level" is a difference 
> of 1.6e-19 volt from the level above/below. A resolution of 8-bit allows 
> for only 256 different levels -- obviously *way* too low.

Way too low for WHAT?


> The original Y signal is converted to QAM. This QAM signal is then 
> broadcasted on an FM radio carrier wave whose base frequency is 300 Hz. 
> 300 Hz is the lowest ULF frequency and the lowest frequency used by 
> telephones.

Restating nonsense doesn't make it less nonsensical.  What does
"QAM...on an FM radio carrier wave" MEAN on your planet?

The rest is just gibberish as well.

Bob M. 
Technical Details
Message-ID: <fgc1v0$rmh$1@usenet01.boi.hp.com>
Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newsfeed.stanford.edu!newsfeed.news.ucla.edu!ihnp4.UCSD.Edu!sdd.hp.com!usenet01.boi.hp.com!not-for-mail
References: <46fc71d2$0$24285$4c368faf@roadrunner.com> <u9hus4-6vi.ln1@radagast.org> <4722f832$0$25703$4c368faf@roadrunner.com> <ujr6i3dolk1qjon2ij5tta8aip26tff9qa@4ax.com> <slrnfi6tb4.n9a.pm@thinkpad.nowster.org.uk> <4723dde6$0$19659$4c368faf@roadrunner.com> <1193758919.924634.276450@y27g2000pre.googlegroups.com> <5op40sFnr30mU1@mid.individual.net> <1193769738.441836.79230@k35g2000prh.googlegroups.com> <lISdnTog1rjMCrranZ2dnUVZ8vydnZ2d@pipex.net> <4727a189$0$19640$4c368faf@roadrunner.com> <fgb5ae$6da$1@usenet01.boi.hp.com> <47295e0d$0$11519$4c368faf@roadrunner.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: f928c,9d8320c16fbdcf84
X-Google-Thread: ffcae,7e05cb8426dfb96
X-Google-Thread: 107cee,7e05cb8426dfb96
X-Google-Thread: f7d8a,9d8320c16fbdcf84
X-Google-Thread: fdad6,9d8320c16fbdcf84
X-Google-Attributes: gidf928c,gidffcae,gid107cee,gidf7d8a,gidfdad6,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newsfeed.stanford.edu!newsfeed.news.ucla.edu!ihnp4.UCSD.Edu!sdd.hp.com!usenet01.boi.hp.com!not-for-mail
From: "Bob Myers" <nospamplease@address.invalid>
Newsgroups: uk.tech.digital-tv,uk.tech.broadcast,sci.electronics.misc,ba.broadcast,alt.radio.broadcasting
Subject: Re: Using an FM-Carrier for the Y [Luminance] Signal -- how to relieve the bandwidth issue?
Date: Thu, 1 Nov 2007 02:15:24 -0600
Organization: Hewlett-Packard Company
Lines: 40
Message-ID: <fgc1v0$rmh$1@usenet01.boi.hp.com>
References: <46fc71d2$0$24285$4c368faf@roadrunner.com>   <u9hus4-6vi.ln1@radagast.org>   <4722f832$0$25703$4c368faf@roadrunner.com>   <ujr6i3dolk1qjon2ij5tta8aip26tff9qa@4ax.com>   <slrnfi6tb4.n9a.pm@thinkpad.nowster.org.uk>   <4723dde6$0$19659$4c368faf@roadrunner.com>   <1193758919.924634.276450@y27g2000pre.googlegroups.com>   <5op40sFnr30mU1@mid.individual.net> <1193769738.441836.79230@k35g2000prh.googlegroups.com> <lISdnTog1rjMCrranZ2dnUVZ8vydnZ2d@pipex.net> <4727a189$0$19640$4c368faf@roadrunner.com> <fgb5ae$6da$1@usenet01.boi.hp.com> <47295e0d$0$11519$4c368faf@roadrunner.com>
NNTP-Posting-Host: bmyers.americas.hpqcorp.net
X-Trace: usenet01.boi.hp.com 1193904929 28369 16.151.89.242 (1 Nov 2007 08:15:29 GMT)
X-Complaints-To: news@usenet01.boi.hp.com
NNTP-Posting-Date: Thu, 1 Nov 2007 08:15:29 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138