Ventrilo - Events Setup

Ventrilo can inform the user by playing a wave file or generating a Text-to-speech sound when ever certain events occur with in the program. The program allows the user to control how each of the events is handled. All of the following items in the Events setup page has one of several possible choices, but not all of them apply to every event type.

You connect to server

This event is played when ever you connect to the server. Having a sound generated by this event is very handy when you are having connection problems and you would like to know when the program has auto-reconnected (if you have that feature enabled in the Network settings of the program).

You disconnect from server

This event is played when ever you disconnect from the server or if you are having network problems, in which case the program will automatically disconnect from the server. Its also possible the server was taken down or restarted in which case the connection would be broken as well. Having a sound generated by this event is useful if you are busy doing something else and don't have time to look at the programs status, or if you are unable to view it at the current time.

Users connect to server

This event is played when someone else connects to the same server you are connected to. Setting this option to Text-to-speech is very useful when you do not have direct access to the program. The sound generated would be the name of the person connecting in to the server.

Setting this option to Custom Wave will force the program to look for a custom wav\<username>\UserConnect.wav file. Click here for more details.

Users disconnect from server

Similar to the Users Connect to Server option this event will inform you when another user has disconnected from the same server. Setting this option to Text-to-speech would generate a sound announcing the name of the user who has disconnected.

Setting this option to Custom Wave will force the program to look for a custom wav\<username>\UserDisconnect.wav file. Click here for more details.

Comments

This event is played when ever you or another user sends a comment to be displayed next to the users name. Setting this option to Text-to-speech will generate a sound announcing the users name and the comment that was sent.

You switch channels

This event is played when ever you switch to a different channel or back out to the lobby. Setting this option to Text-to-speech will generate a sound announcing the name of the channel you have just moved into.

Users switch channels

This event is played when ever another user connected to the same server you are enters or leaves the channel you are currently in.

Setting this option to Custom Wave will force the program to look for a custom wav\<username>\UserChannelJoin.wav or wav\<username>\UserChannelLeave.wav files. Click here for more details.

Toggle mute sound

This event is played when ever you press a key that you have bound to toggle the "mute sound" on the main window of the program. Setting this option to Text-to-speech will generate a sound informing you of the actual state of the "mute sound" setting.

Toggle mute microphone

This event is played when ever you press a key that you have bound to toggle the "mute mic" on the main window of the program. Setting this option to Text-to-speech will generate a sound informing you of the actual state of the "mute mic" setting.

Toggle Binds

This event is played when ever you press a key that you have bound to toggle the active binds on and off. Setting this option to Text-to-speech will generate a sound informing you of the actual state of the your active binds settings.

Switch Bindings

This event is played when you activate a function bind that switches your current active bindings to a new set of bindings. See Bind Editor help pages for more info about configuring bind switching.

Ventrilo Event Text file

This option lets you chose the Ventrilo Event Text (VET) file that is used for generating the Text-to-speech audio messages when certain events occur. Basically, if you or anyone else has generated other VET files you can chose which one to use. Generally speaking they will be based on theme's just like your system sounds are based on theme's. Ventrilo only comes with the "default.vet" file.


How to setup custom wav files:

First it's important to understand where the "wav\" directory should be located. When you create a user login account on Ventrilo you have the option to give it a working directory, or if you leave it blank the program will decide where the working directory is.

On the NT, 2000 and XP platforms you can get this information by opening a command prompt window and typing in the command "echo %APPDATA%". This will be the base location for application data but there will be another directory below it called Ventrilo that contains all of the Ventrilo specific user files. The following is what the path might look like if you logged into one of these operating systems with the login name "Flagship".

C:\Documents and Settings\flagship\Application Data\Ventrilo

On Win98/ME systems the location of this directory is different and less system logon specific. Assuming you installed your OS on the C: drive then your default working directory will be like this.

C:\Windows\Application Data\Ventrilo

If this directory does not already contain a "Wav" directory underneath it then you will need to create one. But the wav directory is just a place holder for more specific directory names. This is where we get involved with the custom wave files.

Let's assume that you have custom wave files for people who's login names are Joe and Mary. You would need the two following directory names using the above example.

C:\Documents and Settings\flagship\Application Data\Ventrilo\wav\Joe
C:\Documents and Settings\flagship\Application Data\Ventrilo\wav\Mary

In each of these directories you would place the custom wave files that use hard coded names like UserConnect.wav, UserDisconnect.wav, UserChannelJoin.wav and UserChannelLeave.wav

If you have your client configured to play a custom wav file when someone connects to the server, Ventrilo will determine your current user's working directory, tack on the wav\ and then tack on the connecting users name Joe\. It will then tack on the UserConnect.wav because that is the event being generated.

When you setup or edit your Ventrilo user name you have the option to override the default working directory. In this case what ever you enter is what the program will use when tacking on the "wav\" directory for locating files. For example, let's assume you manually enter a working directory of "C:\MyVentrilo". The program will then build a path name like this when trying to access the bind wave files or custom User???.wav files.

C:\MyVentrilo\wav\Joe
C:\MyVentrilo\wav\Mary
C:\MyVentrilo\wav\Fun_Fragger

Note: If you assign bind keys to play wave files then the location of the "Wav\" directory shown in the above examples is the same but with one difference. Wave file binds are more generic and should be broken down into themes where each them is it's own directory. For example, if you had 4 wave files that are part of a theme called Fun_Fragger you would have a directory structure that looks similar to this:

C:\Documents and Settings\flagship\Application Data\Ventrilo\wav\Fun_Fragger

And it would contain the four files that you would like to bind to. Wave files should not be placed directly into the wav\ directory. Instead they must always be in subdirectories below it.