.wave_pro

speech signal process tools

# @(#).wave_pro	1.41 9/24/98 ERL ATT

# This file specifies many of the parameters for the program xwaves.
# Specifications take the form
#		key_word <value>
# One or several of these pairs may appear on each line.  Lines in this
# file which begin with # are ignored.  The comments and blank lines seen here
# are optional and may be deleted in personalized copies.  A full set of
# specifications is included here as documentation, but any subset
# is acceptable.  If specifications are to be deleted, remove both the
# keyword and the value.  Empty text values can be indicated with a
# double quote ("").

# In this file, each global variable symbol is preceded by a brief
# description of its meaning.  For more detail, refer to the "Symbols"
# section of the xwaves manual.  In some cases, the definition is
# commented out, in others, a reasonable, or recommended setting is
# specified.  To remove a specification, it may either be commented out,
# or deleted entirely.  Any symbols not defined here are automatically
# given reasonable values.

# As of xwaves version 5.0, many of these variables are simply used as
# default values for the creation of new data views.  Individual views may now 
# have most of their attributes specified on a per-view basis.
# The xwaves view "set" command provides this access.

###################################################################
################ XWAVES GLOBAL SYMBOL DEFINITIONS #################
###################################################################

# maximum size of signal data buffer (in bytes).  This limit is
# established to reduce the chance that extremely long signal files will
# accidently be read in their entirety.  It may also be necessary to
# avoid exceeding the per-process swap space available.
# max_buff_size	2000000

# whether or not to write ESPS common after marking segments.
# Generally a bad idea and it slows things down, but might be useful
# when xwaves calls certain ESPS programs.
write_common 0

# Filename of a header for use with headerless files or files that do
# not have ESPS/waves+ format headers (e.g. with foreign headers).  
# NOTE: in the case of ESPS files, it is better to set the unix environment 
# variable DEF_HEADER before calling xwaves, as this will have the desired 
# effect for all ESPS programs as well as xwaves.  The default search path 
# used for default header file names is
#    .:$ESPS_BASE/lib/waves/files
#
# Default header files available in the directory $ESPS_BASE/lib/waves/files:
# 1.  def_head.feasd    -- an ESPS FEA_SD header for single-channel, 
#                          SHORT, sampled-data with sampling rate 8000 Hz.
# 2.  def_head.sig      -- a header for SIGnal format files.
# 3.  def_head.HTK10khz -- a header for HTK 2.0 format waveform files,
#                          with 10kHz sampling rate.
# 4.  def_head.HTK16khz -- a header for HTK 2.0 format waveform files,
#                          with 16kHz sampling rate.
# 5.  def_head.sunau8   -- a header for Sun audio format waveform files,
#                          with mu-encoded, 8KHz sampling rate data.  
def_header $ESPS_BASE/lib/waves/files/def_head.feasd

# initial height in pixels of waveform display frame (Sun CRT screen
# is 900 high)
# Limits:	50 to 900  (pixels)
wave_height     200

# initial width in pixels of waveform display frame (Sun CRT screen is
# 1152 wide)
# Limits:	50 to 1152  (pixels)
wave_width	1100

# minimum height in pixels of spectrogram windows 
# If min_spec_height is larger than the "natural" height of 
# spectrogram windows (which is related to the number of FFT 
# points), and if vertical rescaling is enabled (v_spect_rescale == 1), 
# then spectrogram windows will be rescaled vertically when painted.  
# Set this to 50 to avoid any rescaling on initial window display (i.e.,
# for fastest painting)
# Limits:	50 to 900  (pixels)
min_spec_height 50

# minimum width in pixels of spectrogram windows 
# Initial spectrogram painting puts up one pixel-column per record 
# (i.e., per FFT). The "natural" width is somewhat more than the 
# number of records (if this fits on the screen).  If min_spec_width
# is larger than the number of records, a larger window is created.  
# You might want larger windows to see more of the digital readouts.  
# Limits:	50 to 1152  (pixels)
min_spec_width 350

# whether or not to display the reticle grid on spectrogram and waveform
# displays (0 means don't display grid).
reticle_grid  1

# whether or not to draw lines across the reticle grid on spectrogram and
# waveform displays.  If major_lines is set to 1, it draws lines across 
# the display; if it is 0 it doesn't draw lines across the display.  
# reticle_grid must be 1 (display reticle grid) for this to work. 
# By default is does not draw lines across the plot.  Default value is 0.
major_lines 0

# whether or not to interpolate spectrogram displays (0 means plot 
# uniform rectangles)
spect_interp  1

# whether or not to rescale spectrogram displays vertically (1 means
# rescale, 0 means don't rescale); note that rescaling can be an 
# expensive operation
v_spect_rescale 1

# whether or not to rescale spectrogram displays horizontally (1 means
# rescale, 0 means don't rescale); note that rescaling of interpolated 
# data can be an expensive operation if spect_rescale_scope has the 
# value "buffer"
h_spect_rescale 1

# whether horizontal rescaling of interpolated data is computed for the
# entire xwaves buffer (value is "buffer") or for just the current
# window width (value is "view").  Rescaling for the entire buffer can
# be quite slow if the ratio of the current view to the entire buffer is
# large, but has the advantage that horizontal scrolling is very fast
# once the new image is computed (since it is stored).  Rescaling just
# the current view is faster, but has the disadvantage that the
# rescaling takes place every time the viewpoint is moved (i.e.,
# scrolling is slower).  
spect_rescale_scope view

# files specifying parameters for generating spectrograms
# These are text files with format similar to that used herein.
nb_spect_params	 $ESPS_BASE/lib/waves/files/nb_params
wb_spect_params	 $ESPS_BASE/lib/waves/files/wb_params

# location of upper left of first waveform frame ((0,0) is upper left of CRT)
# Limits:	x: 0 to 1152-wave_width;  y: 0 to 900-wave_width  (pixels)
first_x		10
first_y		200

# location of the upper left corner of the xwaves control window (pixels)
# if tempted to set both of these to 0, it's better to use 1 since that
# permits twm users to set usePPosition "non-zero".  Note that standard
# xview command line option "-Wp <x> <y>" can be used to set position from 
# command line 
ctlwin_x 1
ctlwin_y 1

# whether or not the main control panel is iconized or not on startup; 
# control panel will be visible unless ctlwin_iconized is nonzero; Note that
# the standard xview command line options -Wi (iconic) and +Wi (open) 
# can be used to determined the initial iconization state.  Also, 
# the position of the icon can be determined by the standard xview 
# command line option "-WP <x> <y>".  
ctlwin_iconized 0

# number of pixels to advance upon creation of subsequent waveform frames
# Limits:	x: 0 to 1152; y: 0 to 900  (pixels)
x_increment	0
y_increment	200

# set initial state of xwaves to color or monochrome 
# This must be 1 (for color) or 0 (for monochrome)
# This is set automatically on startup -- uncomment to override
# do_color 1

# plotting style to use for waveforms.
# 1 ==> standard "connect-the-dots;" 2 ==> additional lines are drawn from the
# true data point to the base line (histogram like).
# 3 ==> DSP-style (vertical lines from zero to to data points);
# 4 ==> 1 and 3 combined
line_type 1

# height in pixels of the region used to display and operate the scrollbars
scrollbar_height 12

# height in pixels of the region above the scrollbar used to display
# digital readouts.
readout_bar_height 20

# link various signal data and view manipulations across all members of
# a display ensemble (booleans).
scroll_ganged 1
zoom_ganged 0
edit_ganged 0

# default signal input file (appears in Waveform Manipulator panel)
# May be a complete or partial pathname (completed after xwaves is run).
#inputname	speech.sd

# default output file (or file containing lists of output names)
# See xwaves Help frame for output name usage.
outputname	foo1

# default name to put in "Overlay name:" item in command 
# window (does not load file) 
#overlayname ""

# a default name to use for the first display ensemble generated by xwaves
# If omitted it becomes the simplified basename of the first file read.
# objectname ""

# colormap used for waveform and spectrogram displays
# The program cmap may be used to generate these RGB colormaps.
colormap	$ESPS_BASE/lib/waves/colormaps/TImap

# default (initial) duration of waveform displays (page size); (sec)
# The upper limit on this is determined by your patience or the value
# of max_buff_bytes, whichever is smaller.  (E.g. 10sec of 16kHz, short
# integer data is 320000 bytes)
ref_size	10.0

# default step size for waveform "paging" (sec)
ref_step	3.0

# default (initial) starting location in speech file (sec)
# This should be less than the file duration + start time.
ref_start	0.0

# ratio used for "zoom" operations on waveforms
# Any value except zero should work.
zoom_ratio	0.5

# Specify an external function (program) to "attach" to xwaves on startup.
# The ones currently available are the labelers (xlabel, xchart and xmarks)
# and a frequency-spectrum estimation program, (xspectrum).
# The user's existing unix search path is used to find the actual 
# program to execute. 
#funcname	xspectrum

# Specify the attachment options to be provided as pushbuttons on the
# main xwaves Control Panel.  The specifications are in the form of a
# list of space-separated attachment program names.  If the
# distinguished string "none" is used for the value, no attachment
# options will appear in the xwaves control panel.
attachments "xspectrum xlabel xchart"

# variables which set: (1) the fraction of "F0" displays used for the
# F0 feature (2) the minimum F0 displayed (Hz); and (3) the range (in
# Hz) of F0 displayed.
# These apply only to the specialized F0 view created for FEA files
# with a field named "F0".
# f0_min 50, f0_range 150 is good for normal pitch-range male speakers
# f0_min 100, f0_range 250 is good for normal pitch-range female speakers
# f0_min 50, f0_range 250 accomodates both male and female speakers
f0_size	.6
f0_min	50
f0_range 250

# Determine the plotting style for F0; argument elements are type,
# plotting char., x-offset and y-offset, respectively.  If type is 0,
# the usual connect-the-dots paradigm is used; if type is 1, the data
# points are discretely plotted using the plot character.  x- and
# y-offsets are pixel offsets required to center the data points (font
# dependent).  BUG: The plot character specification is ignored in xwaves.  
# A solid square is always used instead of a character because no way of
# plotting text in the "transparent" mode has been found in xview.
f0_plot_specs 1 * 4 6

# The globals plot_max and plot_min provide a flexible means of
# overriding the automatic vertical scaling of plot data.  These may be
# set globally, or on a view-specific basis.  The global defaults may be
# overridden after the view is created using the view "set" command.
# If plot_max is greater than plot_min, xwaves will scale every new plot
# so that the top and bottom of the windows correspond to the specified
# values.  Values outside of the range are simply clipped by the top and
# bottom of the display window (extending into the scrollbar).  Setting
# the view-specific boolean "v_rescale" to 1 will cause auto scaling to
# resume.
plot_max 0.0
plot_min 0.0

# sig_max_override is used to specify a fixed maximum to be assumed for
# all internal D/A operations.  If its value is zero, the default
# behavior of xwaves is to left shift all samples prior to D/A operation
# so as to maintain approximately constant audio output, regardless of
# the overall scaling of the signal in the file.  If non-zero, the D/A
# scaling is performed as though sig_max_override were the actual
# waveform absolute maximum in the file.  Thus, large numbers cause less
# scaling up; small numbers cause more scaling up.  0 means use
# autoscaling.
sig_max_override 0

# Determine the initial definitions of left and middle button presses
# for new waveform windows.
# left_op and middle_op can be set to any of the waveform view
# menu items, either built-in, or defined using the add_op command.
# They may also be any of the following, distinguished items:
# "up/down move" "move closest" "modify signal"
# "repeat previous"  "blow up; function" "blow up time"
left_op	up/down move
middle_op play between marks

# Determine the initial definitions of left and middle button presses
# for new spectrogram windows.
# spec_left_op and spec_middle_op can be set to any of the spectrogram
# menu items, either built-in, or defined using the add_op command.
# They may also be any of the following, distinguished items:
# "modify intensity" "move contour" "up/down move"
# "repeat previous" "mark formants" "move closest"
spec_left_op	up/down move
spec_middle_op modify intensity

# Move_op is a new event-handling feature implemented in xwaves.  This
# permits binding of any xwaves hard or soft command to the cursor
# movement event (the event that happens on each pixel crossing as the
# cursor is moved in a view).  move_op is settable and gettable in the
# same way that "middle_op" and "left_op" are.  No distinction is made
# between spectrogram views and waveform views (though, of course, the
# variable can be set individually for any view).  The hope was that, for
# instance, this "move_op" allows the connection of xspectrum to the
# xwaves cursor so that whenever the cursor is moved, the corresponding
# short-time spectral display is updated continuously as the cursor was
# moved.  This is rather slow on older machines, but yields quite
# acceptable performance on, for instance, SGI Indy R4600 machines.
move_op ""

# name (and options, if any) of external program to call for 
# spectrogram calculations
sgram_prog   sgram

# name (and options, if any) of external program to call for D/A
# operations.  Most architectures automatically do the right thing and
# use the audio code in xwaves to play directly to the hardware audio. 
# This is the case for SUN (except with old 8-bit CODEC), SGI, HP, and,
# Linux.  The default case for DEC Alpha is to use play_prog eplay
# (see below).  If play_prog is not explicitly set and internal audio code is 
# available (SUN, SGI, HP, Linux), then you do not need to set play_prog