[linux-dvb] Why Parameter 'INVERSION' is really needed?
obi at linuxtv.org
Tue Sep 16 20:03:40 CEST 2008
handygewinnspiel at 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.
Spectral inversion depends on the transmitter, too. It can change
anytime a broadcaster decides to change it. It happens, although not
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
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.
More information about the linux-dvb