From: wk <handygewinnspiel@gmx.de>
To: Andreas Oberritter <obi@linuxtv.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Why Parameter 'INVERSION' is really needed?
Date: Wed, 17 Sep 2008 19:18:46 +0200 [thread overview]
Message-ID: <48D13BF6.8050500@gmx.de> (raw)
In-Reply-To: <48CFF4FC.1000005@linuxtv.org>
Andreas Oberritter wrote:
> handygewinnspiel@gmx.de wrote:
>
>> 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.
>>
>
> If you find two devices which need different inversion settings in the
> same network, then it's a driver bug, which can easily be corrected.
>
>
How can this be a drivers bug, if in the dvb api documentation no
*default value* for inversion was ever defined?
Seems to be a bug inside API (linux-dvb-api-1.0.0.pdf, see
http://www.linuxtv.org/docs.php).
> Spectral inversion depends on the transmitter, too. It can change
> anytime a broadcaster decides to change it. It happens, although not
> very often.
>
> Specifying the inversion parameter can speed up the tuning process,
> especially for devices which don't support automatic swapping in
> hardware. But I would not recommend to store this parameter in a service
> list.
>
> If we decide to keep the parameter, we should probably use four options:
> INVERSION_OFF, INVERSION_ON, INVERSION_AUTO_OFF_FIRST,
> INVERSION_AUTO_ON_FIRST, which matches the capabilities of most
> demodulators. A typical application would then probably use only the
> last two options, while the first two options would rather be used for
> diagnostics and to read back the detected inversion.
>
>
>
May be. But since the application cannot get any information about
transmitters inversion only AUTO makes sense here, neither ON or OFF.
No information field is reserved for inversion inside terrestrial
delivery system descriptor and cable delivery system descriptor,
so applications are not able to figure out useful settings from NIT.
Please try to see this from the application side, not from hardware
point of view.
Regards,
Winfried
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-17 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 17:31 [linux-dvb] Why Parameter 'INVERSION' is really needed? handygewinnspiel
2008-09-16 18:03 ` Andreas Oberritter
2008-09-17 17:18 ` wk [this message]
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=48D13BF6.8050500@gmx.de \
--to=handygewinnspiel@gmx.de \
--cc=linux-dvb@linuxtv.org \
--cc=obi@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