Difference between revisions of "AVWizard"

From LinuxMCE
Jump to: navigation, search
m (What to do if A/V Wizard does not start)
Line 1: Line 1:
{| align="right"
  | __TOC__
This page covers the aspects of the AVWizard that the end user will be interested in.  If you want to customise the AVWizard for your needs, like writing a separate backend, see [[AVWizard for developers]].
This page covers the aspects of the AVWizard that the end user will be interested in.  If you want to customise the AVWizard for your needs, like writing a separate backend, see [[AVWizard for developers]].

Revision as of 05:44, 30 November 2008

This page covers the aspects of the AVWizard that the end user will be interested in. If you want to customise the AVWizard for your needs, like writing a separate backend, see AVWizard for developers.


LinuxMCE is intended to act like a normal consumer A/V device, even though it is PC based. As a result, the process for configuring displays is substantially different from configuring X11 on a normal Linux machine, and the A/V Wizard has been designed to make this process as easy as possible. Please see the EDID page for more details on the reasons behind the way it has been designed.

Starting A/V Wizard


This wizard is started automatically the very first time the system boots; it does not automatically start after that.

Starting A/V Wizard from the LinuxMCE menu

The A/V wizard can be restarted at any time from the LinuxMCE menu by choosing Advanced--> Advanced--> A/V Wizard.

Restarting the AVWizard during bootup

Alternatively, the AV Wizard can be started during bootup. Either hold down the Shift key on the keyboard, or press the "A/V Menu" button on the remote to make the A/V wizard start. During bootup you should hear a series of escalating beeps to tell you when LinuxMCE is monitoring the Shift (and "A/V Menu") keys.

When you hear the descending beeps it means that you're too late; the bootup has already gone past the AV Wizard check and LinuxMCE has already started.

How A/V Wizard Starts

When A/V Wizard starts it always outputs 640x480 on the VGA connector. If you are not using a VGA connector, you will likely see a black screen when the A/V Wizard starts (even if you previously saw the Kubuntu boot splash). You will know that the A/V Wizard is running, however, because you will hear a series of beeps. If you then have video after hearing the beeps, proceed to complete the A/V Wizard. If not, see the next section.

What to do if A/V Wizard does not start

Press the number 1 through 5 on the keyboard (or the remote control) to switch to the active connector. Wait 15 seconds, and you will hear that same sequence of beeps telling you that A/V Wizard has now restarted. If you don't hear the beeps after 15 seconds, press the number for your connector again.

 Keys for choosing a connector:

1: DVI
2: VGA
3: Component
4: Composite
5: S-Video

If you hear the beeps but still don't see a picture, it's possible that the display you're using cannot handle 640x480. Press the number 6-9, or 0, as shown below, to select your resolution. Again, 15 seconds later, you should hear the beeps when the A/V Wizard is restarted. If you again need to choose a connector (other than the default VGA), press the 1-5 key (as above) and wait until you hear the beeps again. Repeat as often as needed.

Keys for choosing a resolution:

6: 640x480
7: 1024x768
8: 720p
9: 1080i
0: 1080p

(Note: Due to a bug in the 0704 release, the numeric keys 0-9 on the Windows XP I/R remote may not be able to set your output connector & resolution. Use the 0-9 keys on the keyboard instead, or use another remote.)

Once you have a picture you can proceed to complete the A/V Wizard. You can then resize your user interface to fit your screen, choose your audio outputs, and so on. Follow the AVWizard Step by Step instructions.

If you have more than one video card, or a video card and an onboard video chipset LMCE might not be using the correct one, and so you will still get a black screen. To use a card rather than your onboard chipset, go into your BIOS and disable the onboard chipset - note some BIOSs cannot disable, they can only set your card as the primary or initial video chipset, if so then do that.

If you were able to disable the onboard chipset in your BIOS, then you should be ready to run the AV Wizard - the Linux kernel will not even see the onboard chipset, so will select the card for output.

If you could only set the card as primary (and not disable the onboard chipset) the you will probably notice that you now see the Kubuntu splash screen and progress bar during start up that you didn't see before. However, once you reach the AV Wizard, the screen goes black again - here it is defaulting to your onboard chipset.

To correct this, reboot and hit Escape during the GRUB boot menu (just after the BIOS self test), and choose the recovery option. Once you get a command line, you can execute the lspci command - this will list all your PCI interfaced devices, including the onboard and card video chipsets. Make a note of the PCI BusID of the card, eg 2:0:0

Now use a text editor and edit /etc/X11/xorg.conf. In the Device section you will see the PCI BusID specified - this is probably set to your onboard chipset's ID. Change this to the ID you noted above, save the file and reboot.

AVWizard steps

See AVWizard Step by Step for detailed screen-by-screen instructions.

AVWizard is an easy 10 step configuration wizard:

  • AV Welcome screen
  • AV Resolution and Refresh screen
  • AV Video Resolution counter
  • AV UI Switcher
  • AV Video Output
  • AV Audio Connector
  • AV Audio Volume
  • AV Dolby Test
  • AV DTS Test
  • AV Final Selections

After that an Orbiter Generator will be launched, to create an Orbiter (remote control) for that tool.

Running A/V Wizard from the Commandline

If you are having difficulty running the AVWizard normally (by selecting the option in the Orbiter) it can be run manually by typing in the command line.

Note that you should kill X and any process trying to reload it before running the wizard. You should only do this if your attempt to run it normally fails for whatever reason.

Note: I had to use
sudo -s /usr/pluto/bin/AVWizard_Run.sh
to get my AVWizard to restart.