🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: rec.audio.tech
Article #605

Re: DRM -Ain't- IBOC

#605
From: RHF
Date: Fri, 05 Oct 2007 23:57
79 lines
4562 bytes
On Oct 4, 7:31 am, SFTVratings_t...@yahoo.com wrote:
> Hein ten Horn wrote:
> > SFTVratings_t...@yahoo.com wrote
>
> > > DRM has a hybrid digital/analog mode.  See this manual,
> > > page 20.  Notice how the DRM sits "in-band on-channel"
> > > same as the HD Radio works.
> > >www.drm.org/pdfs/Broadcast_Manual.pdf
>
> > No, the manual does not state
> > "DRM has a hybrid digital/analog mode".
> > A simulcast is not necessarily hybrid.
>

- By that reasoning, HD Radio is not a hybrid format, because
- the digital information sits *next to* the AM signal.

SFTV -aka- "Hybrid Digital" Man,

As and "EE", your above Statement is NOT Correct nor Clear
and it does not represent the Technical Specification {Facts}
of both iBiquity's IBOC and DRM.  Please endeavor to be more
Factual and Accurate in your future representaions here.

Now For The Third Time :

iBiquity's IBOC Broadcast System is a Dual Mode Broadcasting
Scheme; with both the Analog AM and Digital Signals 'being'
"Intrinsic" to the Radio Transmission Process.

The Key Word Being : "Intrinsic"
http://www.answers.com/intrinsic&r=67

The DRM Broadcast System was initally designed and implemented
as a Single (1) Mode All Digital Broadcasting Scheme.

Note - Simulcasting and Analog AM Signal along with the Digital is
a 'possibility' but is NOT currently done on the Shortwave Radio
Band.

FWIW - The DRM Digital Signal 'may' be Broadcast along side
of an Analog AM Signal {Co-Channeled} -but- Both Signals are
Broadcast Separately and are 'independent' of each other; they
are NOT "Intrinsic" to each other as part of a Unified Radio
Broadcast System.

Caution - That the DRM Digital Signal has to be 'reduced' when
it is Broadcast along side an Analog AM Signal to prevent any
Interference to the Analog AM Signal.

The-Bottom-Line : Presently in the Shortwave Bands DRM
is Broadcast 'solely' in the 100% Digital Mode; as it was
designed to do.

for the third time or more - keeping it simple and practical ~ RHF
 .

>
> HD Radio is a simulcast format.
>
> > [quote]
> > DRM supports a number of different simulcast options. Currently the
> > supported simulcast modes require the use of additional spectrum outside
> > an assigned 9 or 10 kHz channel (Multi-Channel or Multi-frequency
> > Simulcast, MCS). The DRM signal can be located in the next adjacent
> > upper or lower channel and can occupy a half or whole channel
> > depending on the bandwidth option chosen.
> > [unquote]
>
> > So far nothing about IBOC.
>

- Okay.  By that reasoning, because HD Radio sits "next to" the
- AM signal, then it is not IBOC either.  It is a simulcast format.
-
- Do you agree with that statement?

no ! - and saying it again does not make it so . ~ rhf
 .
Technical Details
Message-ID: <1191628632.480985.29890@57g2000hsv.googlegroups.com>
Path: arc1-ca.pugleaf.net!g2news2.google.com!postnews.google.com!57g2000hsv.googlegroups.com!not-for-mail
References: <1191201354.812168.82840@19g2000hsx.googlegroups.com> <fdrf0l$tb8$1@registered.motzarella.org> <1191324370.137789.13750@w3g2000hsg.googlegroups.com> <1191367070.722183.304380@r29g2000hsg.googlegroups.com> <1191412958.156924.149200@50g2000hsm.googlegroups.com> <470434d7$0$227$e4fe514c@news.xs4all.nl> <1191508280.215104.47160@57g2000hsv.googlegroups.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: fb1f8,75377a07268430fc
X-Google-Thread: 10a749,75377a07268430fc
X-Google-Thread: 114aac,75377a07268430fc
X-Google-Thread: f7d8a,2fbc1cad392d0236
X-Google-Attributes: gidfb1f8,gid10a749,gid114aac,gidf7d8a,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news2.google.com!postnews.google.com!57g2000hsv.googlegroups.com!not-for-mail
From:  RHF <rhf-newsgroups@pacbell.net>
Newsgroups: rec.audio.tech,rec.audio.car,rec.radio.shortwave,ba.broadcast
Subject: Re: DRM -Ain't- IBOC
Date: Fri, 05 Oct 2007 16:57:12 -0700
Organization: http://groups.google.com
Lines: 80
Message-ID: <1191628632.480985.29890@57g2000hsv.googlegroups.com>
References: <1191201354.812168.82840@19g2000hsx.googlegroups.com>
   <fdrf0l$tb8$1@registered.motzarella.org>
   <1191324370.137789.13750@w3g2000hsg.googlegroups.com>
   <1191367070.722183.304380@r29g2000hsg.googlegroups.com>
   <1191412958.156924.149200@50g2000hsm.googlegroups.com>
   <470434d7$0$227$e4fe514c@news.xs4all.nl>
   <1191508280.215104.47160@57g2000hsv.googlegroups.com>
NNTP-Posting-Host: 71.133.180.218
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Trace: posting.google.com 1191628632 7047 127.0.0.1 (5 Oct 2007 23:57:12 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 5 Oct 2007 23:57:12 +0000 (UTC)
In-Reply-To: <1191508280.215104.47160@57g2000hsv.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; YPC 3.2.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: 57g2000hsv.googlegroups.com; posting-host=71.133.180.218;
   posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0