Gents,
I don't know if this is the key here, but RealProducer (at least at G2
version) defaults to NTSC. I believe it initialises and monopolises the
driver itself. So, any attempt to use v4lctl before running RealProducer is
overwritten on launch, and RealProducer seems to prevent v4lctl talking to
the hardware once running (a "busy" error message). This certainly has a
detrimental effect when receiving a PAL-I signal, so may equally be to blame
for PAL-M?
In the README that accompanies the product is the section:
----------------------------------
Known Problems
----------------------------------
+ Capture video format may be specified only by using the VCAP_FORMAT
environment variable. Valid values are PAL, SECAM, and NTSC. If the
environment variable is absent or different from the above, NTSC is
assumed.
Examples for setting format to PAL for different shells follow:
bash% VCAP_FORMAT=PAL xrealproducer
[...]
Hope this is of some assistance?
--
Mike Onyskiw
***********************************************************************************
The contents of, and the information contained in this email and any files transmitted
with it are confidential and legally privileged, and are sent for the personal attention
of the addresse(s). If you are not the intended addressee, any use, disclosure or
copying of this document is unauthorised.
Thank you
NTL
***********************************************************************************
