.wave_pro

speech signal process tools

# unless you specifically want to use an external play program for some 
# reason.  However, if you are running on a SUN with 8-bit CODEC audio 
# or specifically want to use another external play program, you will
# need to change the value of play_prog.  
# NOTE: play_prog is only activated if use_internal_audio is set to 0.  
# Normally, the use_internal_audio global SHOULD NOT be set in the profile, 
# since xwaves tries to do the "right thing" if use_internal_audio is not 
# specified.  (use_internal_audio is automatically set to 0 for xwaves at 
# startup on the DEC Alpha and set to 1 for architectures with internal
# audio code in xwaves.)
# Possible values for play_prog include, but are not limited to: 
# splay, s16play, sgplay, hpplay, decplay, lplay, c30play, s32cplay, v32play.  
# Any program that can accept a "range" argument and an ESPS FEA_SD file 
# as input is acceptable.  See eman play.  
# Uncomment the following line to use splay if you have 8-bit CODEC 
# audio on a SUN; be sure to set use_internal_audio to 0 also.
# play_prog   splay
# The play_prog setting below makes xwaves use decplay if you run on a 
# DEC Alpha.  If you want to use some other external play program, 
# comment it out and set play_prog appropriately and use_internal_audio to 0.
#
# eplay is an architecture specific link to a stand alone play program. 
# Doing it this way, allows the etsm play extensions to work from the
# xwaves menus.
play_prog   eplay

# In release 5.1.1 of xwaves, the xwaves-internal play function for SUN, 
# SGI, HP, and Linux is disabled if use_internal_audio is 0.  This is a 
# mechanism for forcing external play operations, if required, for example for
# remote play operations.  Set the external play program with the
# symbol play_prog.  Normally, the use_internal_audio global SHOULD
# NOT be set in the profile, since xwaves tries to do the "right
# thing" if use_internal_audio is not specified.  NOTE: use_dsp32 and
# use_internal_audio are alternate names for the same symbol. 
#use_internal_audio 0

# show_play_position provides control over cursor tracking during playback.  
# If it is set to 0, the cursor will not track in any views; if it is 1, 
# the cursor will track only in the view representing the actual signal 
# being played; if it is set to a value greater than 1, the cursor will
# track in all views in the ensemble.  The default value is 1.
# show_play_position 1

# da_stop_pos_view allows you to control whether the data view will be 
# repositioned to center on the sample which was being played when
# D/A output is interrupted (interrupt with the left mouse button).  
# The view will not reposition if da_stop_pos_view is zero.  The default, 
# compiled-in value is 1, and the data view is repositioned to be centered 
# on the last played data sample.
# da_stop_pos_view 1

# If da_location is set, it should be given the sample around which 
# xwaves needs to focus its window when D/A output is interrupted with 
# the left mouse button.  This is the only moment at which xwaves looks 
# at this value.  The internal D/A software and the ESPS play programs 
# set this value.  For examples on how to use it yourself, see chapter 17.  
# If gotten with the "get" command during playback, it gives the value of 
# the sample that is currently played.  If you do two "get"s in sequence 
# and this value does not change, you may be sure that xwaves has stopped 
# the playback operation.
# da_location 0

# By default, the value of stop_play_error is 1, and waves will stop a 
# playback on an underflow error ("Lost realtime connection").  If set 
# to 0, then a message will be printed but playback will continue on 
# such errors.  
# stop_play_error 1

# Try setting play_buff_factor to a positive integer (e.g., 2, 3, 8) if
# you experience problems with the audio output "stuttering" during
# playback or get the message "lost realtime operation" during audio
# playback.  If the value is non-zero, then use this factor to increase play
# buffer size.  You should choose the smallest number that works for you.
# The default value is 0.
# play_buff_factor 2

# If remote_path is defined (and not overriden by either 
# remote_input_path or remote_output_path as described below), it
# is prefixed to the basename of all input and output file names in
# external calls (play operations, spectrogram operations, operations
# from add_esps*).  This is useful for operation in an NFS directory
# with rsh.  If remote_path is defined, it overrides output_dir in the
# case of external calls.
#remote_path

# If remote_input_path is defined, it is prefixed to the basename of all
# input file names in external calls.  It overrides any definition of
# remote_path.
#remote_input_path

# If remote_output_path is defined, it is prefixed to the basename of all
# output file names in external calls.  It overrides definitions of
# remote_path and output_dir
#remote_output_path

# whether or not to show numeric values for each trace in a waveform 
# display (1 means show the values)
show_vals    1

# whether or not to show field labels for each trace in a waveform 
# display (1 means show the labels)
show_labels  1

# Image_clip is used to determine the upper clipping limit for mapping
# spectrogram or other 2D image levels to display color/intensity.  For
# monochrome displays (or when do_color is zero) it is used by the
# digital halftone algorithm.  The halftone algorithm assumes that the
# maximum displayed value, MAX, is 127.  Values between MAX and (MAX
# -image_clip) are displayed in black.  The default value is 7 (i.e., in
# spectrogram terms, everything above 119dB is shown in black).  For
# color/greyscale displays the interpretation of image_clip is slightly
# different, but it has approximately the same effect.  In this case all
# levels above image_clip are represented as the same (high) entry in
# the colormap table.
image_clip 7

# Image_range is the range (e.g. in dB) over which the display
# intensity/color is linearly modulated by the data levels.  For
# dithered monochrome images, everything below (MAX - image_clip -
# image_range) is shown in white.  The default is 40 (i.e., in
# spectrogram terms, assuming 7 as the value of image_clip, everything
# more than 47db down from the maximum possible value is shown in white.
# For greyscale/color displays, the available colormap entries are
# linearly interpolated over the range specified by image_range.
# Everything below (MAX - image_clip - image_range) is set to the same
# (low) colormap entry.
image_range 40

# Some X servers reverse the sense of monochrome images.  
# Setting invert_dither to 1 causes the display of
# digital-halftone images to appear with black and white pixels reversed
invert_dither 0

# the path for xwaves temporary files that are destroyed after use.
temp_path /usr/tmp

# number of INET socket port to use when operating in display-server mode
# This is the INET domain socket port to be used when xwaves is
# operating as a display server (as the result of the -s option or the
# enable_server command).  If set, socket_port overrides the
# WAVES_PORT environment variable or the value given by the -p
# option.  Note that this port number is no longer relevant for the
# send_xwaves program.  It is, however, still used when communicating
# with the send_xwaves (3-ESPS) library calls and with the program
# plot3D.  This inconsistency will be removed in a future release.
# If not specified, the default value is 4050.  Xwaves and the socket library
# have 4050 as the default value for socket port.  
#socket_port

# name of a command file to be executed on startup
# if init_file is omitted, a default will be invoked (providing
# a standard button control panel).  If you don't want any init_file
# behavior (including the default), then use "/dev/null" as the 
# init_file name 
init_file  $ESPS_BASE/lib/waves/commands/xw_init.WC

# name of a writable directory to used for all xwaves output files.  
# Do not define this global unless you want it used, and make sure that
# the named directory exists and is writable.  If output_dir is defined,
# all output files from xwaves, xspectrum, and xlabel will go into 
# this directory (including edited files, saved file segments, spectrogram
# output files, outputs from add_espsf, etc.).  It is OK to include
# environment variables in the path.  
# output_dir $HOME/waves_temp

# If command_step is non-zero, the execution of command files is paused after
# every command; pressing "CONTINUE" will execute the next command. 
command_step   0

# When enabled, the "save" command and the "save segment in file" menu
# operator will append "extensions" to the saved file's name that are
# related to the file type.  Else, the extensions are not appended.
append_extensions 1

# The operator to be invoked after the menu operator item "blow up;
# function" is executed.  Attachments typically bind their own "mark"
# operation to blowup_op, but you can bind any existing operator to it.
blowup_op ""

# This disables the saving of spectrogram data files on most contexts
# where signal files would normally be saved.  If you really need to do
# operations like "save segment in file" on spectrograms, be sure this
# boolean is 0.
dont_save_sgrams 1

# When editing waveforms by "drawing" on the view with a mouse button,
# this boolean causes the data values to be written immediately after
# the drawing button is released.  Otherwise the data is not written
# until the view is destroyed or xwaves exits.
rewrite_after_edit 1

# When editing data by "drawing" on the view with a mouse button,
# redraw_on_release causes the view to be redrawn each time the drawing
# button is released.  For some view types, this might be painfully
# slow, so you may prefer to disable this behavior.
redraw_on_release 1

# When vector signals are overlaid on spectrograms (e.g. "formant
# trajectories"), the overlay positions can be indicated as numerals,
# rather than as colored dots.  Enabling this boolean causes numbers to
# be used.  This can be helpful when preparing monochrome hardcopy or
# when working on monochrome monitors.
overlay_as_number 0

# The internal convention in xwaves is to represent samples in a file
# starting the count at 0.  Other programs (including most ESPS
# programs) start counting at 1.  "s_range_offset" is a means to adjust
# this discrepancy or to allow you to define built-in offsets for some
# other purpose (perhaps to compensate for a system delay, etc.)  This
# offset is added to all "sample number" view-specific variables.  Its
# default value is 1.  It has no other impact on xwaves operation.
s_range_offset 1

# The internal convention in xwaves is to represent channels in a file
# starting the count at 0.  ESPS programs also start counting at 0.  
# "c_range_offset" is a means to allow you to define built-in offsets 
# for some other purpose.  This offset is added to all "channel number" 
# view-specific variables.  Its default value is 0.  It has no other 
# impact on xwaves operation. 
c_range_offset 0

# The string contained in this variable is prepended to all sample
# "ranges", of the form M:N, returned by the view-specific symbols
# "range_samp" and "mark_range_samp".  By default it is "-r" which
# meshes well with ESPS programs that have a command-line range option.
# You may specify a null prefix with \"\".
samp_range_prefix -r

# If enabled, this boolean causes the file name displayed in the
# upper-left corner of each data view to be simplified to its base name
# with any path prefix removed.
shorten_header 0

# The string contained in this variable is prepended to all time
# "ranges", of the form A:B, returned by the view-specific symbols
# "range_time" and "mark_range_time".  By default it is "-r".
# You may specify any prefix, including a null prefix with \"\".
time_range_prefix -s

# If a Heurikon or AT&T SURF or a FAB2 DSP board is present, xwaves
# will use it for play and spectrogram operations by default.  You can
# disable use of the board by setting use_dsp32 to 0 (in which case
# external ESPS programs will be used for the play and spectrogram
# operations).  Setting use_dsp32 to 1 will result in the board being
# used again.  Normally, the use_dsp32 global SHOULD NOT be set in the
# profile, since xwaves tries to do the "right thing" if use_dsp32 is
# not specified.  NOTE: use_dsp32 and use_internal_audio are alternate names
# for the same symbol.
#use_dsp32 0

# If one of the DSP boards mentioned above is present, it requires data
# in SHORT format for the fast, on-board spectrogram computations.
# If fea_sd_special == 1, xwaves will convert all ESPS FEA_SD 
# files to SHORT on input.  Note that this is not in general a 
# good thing to do unless necessary.  If a board is detected, 
# fea_sd_special is set to 1 on startup, but you can override this
# by uncommenting the following (you can also use the "set" command
# after startup) 
fea_sd_special 0

# By default, a primitive lock-and-wait mechanism is used to allow 
# more than one program to use a DSP board.  dsp32_wait is the maximum 
# amount of time (in seconds) to wait for board access.  Note that the
# locking mechanism can be disabled by setting the environment 
# variable DSP_NO_LOCK (see espsenv (1-ESPS))
dsp32_wait     5

# if 1 (default) means correct P8574 part is on the Ariel analog
# module for the AT&T Surfboard; set to 0 if the wrong (A) part is there
#P8574_type 1

# ARIEL_16 specifies which crystal is on the Ariel VME-16 ProPort 
# Ariel analog module for the AT&T Surfboard.  Set to 0 (the default), to
# specify the standard 24 Mhz crystel; set to 1 to specify the 16 Mhz crystal. 
#ARIEL_16 0

# ARIEL_HK enables processing appropriate for the Ariel ProPort and
# Heurikon dsp32c (SURF) combination.  Its value is irrelevant if your
# system does not have a SURF board.
# ARIEL_HK 1

# non-zero values for debug_level result in various debugging-related output 
# messages; higher values yield more messages
debug_level     0

# non-zero values for verbose results in assorted output messages that
# inform the user about what xwaves is doing.  A value of 0 yields 
# silent operation.  The default level of 1 yields the following: 
# (1) startup messages (reporting on the profile that is read and 
# whether or not a DSP board has been detected); (2) the command lines
# of any external program calls caused by play, spectrogram, add_espsn, 
# add_espsf, add_espst, and shell commands; (3) the pid of any forked 
# process; (4) notification that a forked process has terminated.  
# If verbose is 2 or higher, you get all of the above, plus some details
# about xwaves command processing.  
verbose        0


# Cross_level and find_crossing are global and view-specific variables
# that control the positioning of the cursor (and hence the markers) in
# relation to level crossings in the signal.  If find_crossing is
# non-zero, the cursor will only jump to locations in the waveform
# corresponding to positive crossings of the signal level cross_level.
# This is convenient when cutting and splicing is done, since it ensures
# reasonable waveform continuity between segments cut consistently at
# positive crossings of a particular level.  It is wise to set these
# only on a view-specific basis, since you may not want this behavior
# enabled in all views, but it is possible to initialize them from the
# globals defined herein.  Note that if the signal on view does not
# contain a crossing of cross_level, the cursor will move as usual.
cross_level	0.0
find_crossing	0

# Show_processes is a boolean that enables a "process pending"
# indication in xwaves.  An optional GUI widget appears if the global
# "show_processes" is nonzero and if any external processes launched
# from xwaves are pending.  The simple display shows the list of PID's
# of all top-level processes pending.  Mousing the PID's on this list
# opens a display showing the full command-line.  This expanded process
# view also has an option to kill the process.
show_processes 1

# By default, most xwaves errors show up in a popup message panel,
# (the error message GUI) rather than going to the tty window that
# started xwaves (standard error (stderr)).  "show_error_gui" enables