FREQUENTLY ASKED QUESTIONS
~~~~~~~~~~~~~~~~~~~~~~~~~~

----------------------------------------------------------------------

Q: When switching the TV on, I can see only part of my screen because 
   the screen has a much larger resolution than what is displayed on 
   the TV.

A: If you have modes for smaller resolutions in your XF86Config file,
   you can switch to those with the 'X Video mode' button *before*
   enabling TV out. See the documentation about XFree on howto make
   a mode with a special resolution. Resolutions like 800x600 or 640x480
   are often preconfigured, or can be selected with the setup programs
   for XFree. There is also a command line option to automatically
   switch, see USAGE.

----------------------------------------------------------------------

Q: I don't get an image on the TV at all.

A: Maybe the connector autodetection doesn't work for you, because
   the line is not properly terminated in your TV. Switch the connector
   to 'both', and try again. Of course, there may be lots of different
   reasons, like a damaged connector cable, etc.

----------------------------------------------------------------------

Q: I can see an image on the TV, but no image on the monitor in some or
   in all modes, even though I have dualview enabled.

A: Some monitors don't like the low frequencies (50 Hz/60 Hz vertical
   for PAL/NTSC, and 30-40 kHz horizontal) the dual view mode has to
   use. If you cannot get an image on the monitor in nearly all modes,
   you should disable dualview completely. (Remember, if you destroy 
   your monitor, it's your responsibility, not mine). However, most
   modern monitors should cope with that.
  
   The second reason is that in some modes, especially those with
   large overscan (i.e., small overscan percantage, and a large image)
   don't leave the monitor enough time to 'retrace'. In that case,
   if you really need dualview, you should use a different mode (or
   even make a new one if you have the Brooktree chip).

----------------------------------------------------------------------

Q: The image on my TV is only black and white. How can I get color?

A: There are many possible reasons for this. 

(a) You have chosen the wrong color encoding system (PAL/NTSC/...), 
    or your TV uses a color encoding system that is not supported yet.

(b) You have a S-VHS to VHS connector that uses only the luminance (Y)
    line of the S-VHS connection. If you have a Brooktree chip, try
    selecting 'Convert' on the 'Config'-page as connector setting.
    This will output the composite (FBAS) signal on the Y-line.
    If you have a Chrontel chip, however, this settings will not help; 
    'Convert' in this case is the same as the 'S-VHS' setting. You will 
    need a proper connector that 'mixes' both the Y-line and the C-line
    of the S-VHS output.

(c) The cable connecting your TV with your computer is too long, or
    external electrical signals interfere with the color signal.

(d) On some systems, especially with Chrontel cards, the frequency of
    the color carrier is wrong. You can change this frequency with the 
    two 'FSCI' spinbuttons on the Chrontel register page, and similarly
    with the 'msc' spinbuttons on the Brooktree register page. Don't
    forget to 'Apply' or 'AutoApply' your changes. If you need to change
    this values and find proper ones, please mail me the mode and the  
    values. There is also a 'pseudo' TV system called 'PAL-X' which has
    a few modes with different color carrier. Maybe those work for you,
    maybe they don't.

----------------------------------------------------------------------

Q: I have the Brooktree chip, and if I use the Huge modes, the cursor
   disappears, or the system even freezes completely.

A: The NVidia cards need some time during the vertical refresh phase.
   If this time is too short, the above effects may happen. You
   can use a software cursor instead of a hardware cursor by using  
   the options "SWCursor" or "HWCursor" in your XF86Config file as 
   described in the README of the NVidia driver. If this does not help,
   use a different mode (or make your own).

----------------------------------------------------------------------

Q: Can I have true dualhead view with one image on the monitor and a 
   different image on the TV?

A: No, this is not possible with nvtv. Of all the NVidia cards, only
   the GeForce MX has two heads and can produce two different images.
   However, the video overlay will only work on one of those images,
   and worse, I currently do not know how to program the dualhead
   mode.

----------------------------------------------------------------------

Q: My TV can show images in true 16:9 widescreen format. How can I use
   this feature, for example to view DVDs in this format?

A: You should be able to switch your TV manually in the 16:9 mode.
   It will then take the normal TV signal and display it in widescreen.
   To make this work with DVD player programs, you have to prevent the
   program from scaling the anamorphic DVD, or for true widescreen
   formats, you have to horizontally scale down the image, in both
   cases by a factor of 1.3333. The xine subdirectory contains a
   patch to xine which allows you to do this with the --display-ratio
   command line switch.

----------------------------------------------------------------------

Q: Can I use two X servers, one for the TV, and one for the monitor,
   and switch between them by switching between the virtual terminals?

A: No. The X server doesn't know that the card is in TV mode, and 
   therefore does not save all the state that is necessary. You
   might be lucky and able to switch out of TV mode, but you'll never
   be able to switch into it again.
   The only way to get this to work is to integrate nvtv in the XFree
   server (which is a long term goal).

----------------------------------------------------------------------

Q: It's tiring to always have to start nvtv, pick a mode, and switch on
   the tv, and then to start an application. Can I automatize that?

A: You can use the command line options. For example,
   
     nvnv -r 800,600 -s Normal -t

   switches to 800x600 tv mode with 'Normal' overscan size. Type nvnv -?
   to see all the command line options. Write a simple shell script that
   swicthes to tv mode, runs your application, and switches back to monitor
   mode.

----------------------------------------------------------------------

Q: I have the Chrontel chip, and the "Macrovision" button on the Settings
   page is grayed and off. Why can't I enable Macrovision?

A: It is not possible to enable Macrovision in all modes, because we
   do not have enough information how to do that. Therefore, the
   Macrovision button will be insensitive and off for those modes,
   and sensitive (and also off by default) for the others. Since most
   people do not want Macrovision anyway, this is not a serious drawback.

----------------------------------------------------------------------

Q: I have a Riva128, and nothing works. Are these cards not supported?

A: The Riva128 card uses a completely different way to produce TV-out.
   Also, as far as I know, it can send a picture either to the
   monitor or to the TV, because it uses the same chip pins to supply
   the data, and decides which one to choose at power-on time. 
   So if someone can figure out a way to switch between TV and monitor
   output later, I'd be happy to hear about it, but at the moment
   it seems it just won't work.

----------------------------------------------------------------------

Q: While using TV-out, after some time (10, 20 or 30 minutes) something
   happens to the image: There may be some disturbances (black lines),
   or the image may even disappear completely. What's wrong here?

A: This is probably the X screen saver. You can disable it with
   'xset -dpms s off'. Don't forget to enable it later on if you need
   it. Read the manpage for details.

----------------------------------------------------------------------

Q: I have an NVidia dualhead card (Geforce MX), and nvtv cannot detect 
   may tv chip.

A: You probably have Twinview enabled in the NVidia 'nvidia' X driver.
   Disable it, and nvtv will detect the chip.

