public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: handygewinnspiel@gmx.de
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Why Parameter 'INVERSION' is really needed?
Date: Tue, 16 Sep 2008 19:31:21 +0200	[thread overview]
Message-ID: <20080916173121.202250@gmx.net> (raw)

Hi,

By looking at the actual proposals for DVB API and trying to understand what happens there some questions arised to me. May be someone can give some answer on this items.

What is the *real need* for giving applications the possibility of I-Q-Inversion? Why this strange one is included in next API's?

If i understand this parameter correctly it swaps I and Q inputs of an qam capable receiver. But otherwise that means that somewhere in the reception chain some real mistake was made, either on hardware or driver side.

And if some inversion is needed it should be corrected inside the dvb frontend, since for such piece of hardware *always* this inversion is needed. Correcting this later on application level is terrible, since somebody may use hardware with different inversion settings inside the same application with the very same channel definition.

By looking on EN300468 nowhere 'inversion' is stated, channel definition is made by:

DVB-T
 * centre_frequency
 * bandwidth
 * priority
 * Time_Slicing_indicator
 * MPE-FEC_indicator
 * constellation
 * hierarchy_information
 * code_rate-HP_stream
 * code_rate-LP_stream
 * guard_interval
 * transmission_mode

DVB-C uses
 * frequency
 * FEC_outer
 * modulation
 * symbol_rate
 * FEC_inner

DVB-S/S2
 * frequency
 * orbital_position
 * west_east_flag
 * polarization
 * modulation_system
 * roll off
 * modulation_type
 * symbol_rate

Therefore my question: Is it possible to skip Inversion property in future API's at all? Or are other standards out there where this channel property explicitely stated?

Are these following parameters missing or only named misleading? If so, what are there names?
 * MPE-FEC_indicator (DVB-T)
 * FEC_OUTER (DVB-C)

Why was DVB-T Hierachy split into two different parameters, Alpha and Hierarchy? One Parameter seems to be enough? EN300468 says

000 non-hierarchical, native interleaver
001 α = 1, native interleaver
010 α = 2, native interleaver
011 α = 4, native interleaver
100 non-hierarchical, in-depth interleaver
101 α = 1, in-depth interleaver
110 α = 2, in-depth interleaver
111 α = 4, in-depth interleaver


Sorry for this huge bunch of questions,
Winfried
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2008-09-16 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 17:31 handygewinnspiel [this message]
2008-09-16 18:03 ` [linux-dvb] Why Parameter 'INVERSION' is really needed? Andreas Oberritter
2008-09-17 17:18   ` wk
2008-09-17 19:57     ` Andreas Oberritter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080916173121.202250@gmx.net \
    --to=handygewinnspiel@gmx.de \
    --cc=linux-dvb@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox