Difference between revisions of "Ventrilo"

From ArchWiki
Jump to: navigation, search
(Finding the input device)
Line 10: Line 10:
 
The acceptable input devices are in /dev/input/. If you want to use a mouse use the event-mouse in /dev/input/by-id/. For a keyboard use /dev/input/event[#].
 
The acceptable input devices are in /dev/input/. If you want to use a mouse use the event-mouse in /dev/input/by-id/. For a keyboard use /dev/input/event[#].
  
You'll probably need to do a bit of trial and error to find the proper event number or device. The best way to do this is just to run ventriloctrl /dev/input/[whatever], and press keys or click your mouse and see if it is detected by the program. If it is detected, it will show an example line with a number at the end. That number is the button number that you will use to run ventriloctrl in the future.
+
You'll probably need to do a bit of trial and error to find the proper event number or device. The best way to do this is just to run ventriloctrl /dev/input/[whatever] as root, and press keys or click your mouse and see if it is detected by the program. If it is detected, it will show an example line with a number at the end. That number is the button number that you will use to run ventriloctrl in the future.
  
 
For example, my <tt>ventriloctrl /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse</tt> shows:
 
For example, my <tt>ventriloctrl /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse</tt> shows:

Revision as of 18:40, 30 March 2009


Introduction

Ventrilo is a voice communication program for Windows that runs quite well on the latest wine. This article outlines a few workarounds necessary to using Ventrilo naturally on Linux.

Global Push to Talk Hotkey

One problem that wine Ventrilo users face is that the push to talk hotkey only being detected when a wine window (such as Ventrilo itself) is in focus. The solution to this is using ventriloctrl, a simple program that sends X input to Ventrilo.

Finding the input device

The acceptable input devices are in /dev/input/. If you want to use a mouse use the event-mouse in /dev/input/by-id/. For a keyboard use /dev/input/event[#].

You'll probably need to do a bit of trial and error to find the proper event number or device. The best way to do this is just to run ventriloctrl /dev/input/[whatever] as root, and press keys or click your mouse and see if it is detected by the program. If it is detected, it will show an example line with a number at the end. That number is the button number that you will use to run ventriloctrl in the future.

For example, my ventriloctrl /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse shows:

 ventriloctrl /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse 272

If that was the button I wanted to use, I would run ventriloctrl with that line in the future.

UDev Rule

Ventriloctrl needs access to your input event. This can be done by running ventriloctrl as root, or preferably by setting a udev rule so it can be accessed by a user. First off, find out what input device you want to use. If you don't mind running it with sudo, skip this section and simply put sudo in front of the command in the next section.