wrel20.me

来自「speech signal process tools」· ME 代码 · 共 978 行 · 第 1/4 页

programs are run.  EDR format output files can be obtained in general
for all programs by creating the UNIX environment variable ESPS_EDR
and giving it the value "on".  The conversion program \fIaddfeahd\fP
(add an ESPS header to an existing headerless, binary file) has an
option to specify whether the data are in NATIVE or EDR format.  
.lp
The ESPS and \fIwaves\fP+ input routines can not in general handle
files written in native mode by other architectures \- files to be
exchanged should be written in EDR format unless the native modes
happen to match.  This lack of generality is a compromise that
supports file sharing but only requires a single machine-dependent
conversion module for each architecture (the module converts between
native mode and ESPS external format).  Some exceptions to the
foregoing have been allowed for.  In particular, the input
routines will usually recognize cases where NATIVE modes differ only
with respect to byte order.  Thus, for example, NATIVE format files
from a DECStation 3100 or Sun 386i can be read by \fIwaves\fP+
running on a Sun 4 or Concurrent (and \fIvice\fP \fIversa\fP).
.lp
Using the ESPS external format can result in increased file I/O times,
but the feature can be turned off (so that native formats are always
used) when it isn't needed.  As mentioned, the default is to use
native formats.  
.sh 2 "New Menu Item"
.lp
A "kill-window" item has been added to display menus.  This is useful
since some window managers do not facilitate the operation.  (For
example, \fItwm\fP's window kill operation ends up terminating
\fIwaves\fP+).  
.sh 2 "New \fIwaves\fP+ Globals"
.lp
The following globals have been added in \fIwaves\fP+ Version 2.0:
.nf
.i

	fea_sd_special
	max_buff_size
	temp_path
	write_common
	readout_bar_height
	min_spec_height
	min_spec_width

.r
.fi
.np
The global \fIfea_sd_special\fP was added to control the handling of
FEA_SD files (see the description above).  It is set on \fIwaves\fP+
startup to be the same setting as \fIuse_dsp32\fP after the presence
or absence of a DSP board is established (i.e., 1 if a board is
present, 0 otherwise).  Thus, special treatment for FEA_SD files
occurs by default only if a board is present.  Processing of the
\fIwaves\fP+ startup profile now occurs after the board check, so 
an explicit setting of \fIfea_sd_special\fP in your profile will take
precedence over the default.  
.np
The global \fImax_buff_size\fP determines a limit on the number of
bytes of storage that \fIwaves\fP+ will attempt to allocate for
in-memory data storage for any one signal.  Previously this was a
compiled-in constant with a value of 1048576.  The value is now
2000000 by default, and this can be changed with an entry for
\fImax_buff_size\fP in the startup profile or with the \fIset\fP
command.  If this limit is set high enough for a signal to be
contained entirely in memory, operations such as scrolling through the
signal will be faster than they would be otherwise, since \fIwaves\fP+
will not have to reread data repeatedly from a disk file.  Smaller
values of the limit may be necessary to prevent \fIwaves\fP+ from
failing by running out of memory.
.np
The global \fItemp_path\fP determines the directory in which
\fIwaves\fP+ will write temporary files (e.g., files generated by
external ESPS calls that result from \fIwaves+\fP commands
\fIadd_espsf\fP or \fIadd_espst\fP).  The default for \fItemp_path\fP
is "." (i.e., current working directory).  
.np
The global \fIwrite_common\fP determines whether or not ESPS Common is
written whenever the user marks a new segment in a \fIwaves\fP+
window.  If \fIwrite_common\fP is 1, each time the mouse is used to
change the position of segment markers, the file name ("filename"),
starting record ("start"), and number of records ("nan") are written
to ESPS Common; if write_common is 0, Common is not written.  For more
information about ESPS Common processing, see various ESPS manual
pages (e.g., \fIgetparam\fP (1\-\s-1ESPS\s+1) \fIread_params\fP 
(3\-\s-1ESPS\s+1), \fIxprompt\fP (1\-\s-1ESPS\s+1)).  
.np
The global \fIreadout_bar_height\fP determines the height of a
region containing digital readouts for waveform and spectrogram
windows.  This readout bar is below the title bar and above the
scrollbar.  The readout bar is only used under X Windows, so the
global can be ignored if you are running under Sunview.  
Under Sunview, the readout bar is not used, since the
readouts are inserted into the title bar.  
.lp
The global \fImin_spec_height\fP gives the minimum height in pixels of
spectrogram windows; if there are more spectral values per record than
\fImin_spec_height\fP, the initial window size is set at one pixel per
spectral value up to a pre-defined maximum. 
.lp
The global \fImin_spec_width\fP gives minimum width in pixels of
spectrogram windows; regardless of window width, spectrograms are
painted as one record per pixel column.
.sh 2 "New Waves Commands"
.sh 3 "Add External ESPS (No Output) Call to \fIwaves\fP+ Menu (\fIadd_espsn\fP
.lp
The new \fIadd_espsn\fP command is a companion to the existing
\fIadd_espsf\fP and \fIadd_espst\fP commands; like them, it 
may be directed at \fIwaves\fP+.  All three of the "add_esps" commands
add an item to the \fIwaves\fP+ that can be used to invoke an external
ESPS program on a marked signal segment.  There are three
corresponding classes of ESPS programs that can be invoked from within
\fIwaves\fP+: (1) programs that take two ESPS file arguments (input
file and output file) and produce an ESPS output file (for example,
\fIfilter\fP (1\-\s-1ESPS\s+1)); (2) programs that take a single ESPS
input file argument and produce ASCII text output on standard
output (for example, \fIstats\fP (1\-\s-1ESPS\s+1)); and (3) programs
that produce no direct output (but may have side effects like printing
or plotting), for example, \fIplotsgram\fP (1\-\s-1ESPS\s+1).  To
summarize the correspondence:
.ip 
\fIadd_espsf\fP: adds call to program that produces an ESPS file
.ip 
\fIadd_espst\fP: adds call to program that produces text
.ip 
\fIadd_espsn\fP: adds call to program that produces no direct output
.lp
The \fIadd_espsn\fP command takes two keywords, \fIname\fP and
\fIcommand\fP.  As with the other "add_esps" commands, \fIname\fP is
the menu label, and \fIcommand\fP is the corresponding external
command to be invoked on the marked segment (including any options or
\fIrsh\fP prefixes).  When \fIname\fP is invoked from the menu, a
system call is issued to run \fIcommand\fP in the background.
(WARNING: you can't QUIT \fIwaves\fP+ until all such background jobs
have terminated.)  As with the other "add_esps" commands, the
\fIremote_path\fP global is used as a prefix to the file name in order
to handle the case of remote executions on files accessible via NFS.
Only one external ESPS program can be incorporated at a time with
\fIadd_espsn\fP.  Subsequent uses of \fIadd_espsn\fP just override the
current values.  For details, see "RUNNING ESPS PROGRAMS FROM \fIwaves\fP+"
in the \fIwaves\fP+ manual.
.lp
Here are a couple of examples: In order to view spectrogram segments
without interpolation (i.e., so that each data point is displayed as a
uniform rectangle), one might use:
.nf

     add_espsn name rect_sgram command plotsgram -D 

.fi
One could then mark a spectrogram segment and invoke the "rect_sgram" 
menu entry, the result being an separate ESPS plot of the marked
segment.  Similarly, 
.nf

     add_espsn name print_sgram command plotsgram -Tpostscript

.fi
could be use to plot the marked segment on a local postscript printer,
assuming one was set up in the ESPS installation script.  One could
the same thing for sampled data files by means of \fIplotsd\fP
(1\-\s-1ESPS\s+1).  
.sh 3 "Change Working Directory (\fIcd\fP)"
.lp
The command \fIcd\fP, which may be directed to \fIwaves\fP+, changes
the current working directory.  The optional keyword \fIpath\fP gives
the new directory.  If issued without the keyword \fIpath\fP, the
user's home directory is assumed.  All file names passed to
\fIwaves\fP+ (e.g., in the INPUTfile item of the control panel) are
interpreted relative to the current working directory.  On startup,
the working directory is the directory in which \fIwaves\fP+ is
invoked.
.sh 3 "Page Signal in Window (\fIpage\fP)"
.lp
The command \fIpage\fP, which may be sent to display ensembles, 
provides a means for paging forward or backwards from command files
(in previous versions, this function was available only as a menu
item).  There are three optional keywords:
.ip \ \ \fIfile\fP: 12
The name of the signal to be paged forward or back. If
omitted, the name from INPUTfile in the command window is used.
.ip \ \ \fIstep\fP: 12
If positive, the number of seconds to page forward; if
negative, the number of seconds to page backwards.  If omitted, the
value of the global \fIref_step\fP is used.
.ip \ \ \fIref_step\fP: 12
Optional new value for the global \fIref_step\fP. 
.sh 3 "Play Signal in Window (\fIplay_wind\fP)"
.lp
The command \fIplay_wind\fP, which may be sent to display ensembles, 
provides a means for playing the data currently displayed in a window
(in previous versions, this function was available only as a menu
item).  The optional keyword \fIfile\fP names the signal to be played. 
If \fIfile\fP is not given, some heuristics are used to find a window to
play.  
.sh 3 "Save Signal Segment (\fIsave\fP)"
.lp
The command \fIsave\fP, which may be sent to display ensembles,
provides a means for saving specific segments of signals (in previous
versions, this function was available only as a menu item).  There are
three optional keywords:
.ip \ \ \fIfile\fP: 12
The name of the signal file containing the segment to be
saved.  The name of the in which the segment is saved is determined by
the OUTPUTfile item in the \fIwaves\fP+ control panel (see description
in the \fIwaves\fP+ manual).  Note that the base name for the output
file can be changed by re-setting the global \fIoutputname\fP.
.ip \ \ \fIstart\fP: 12
The start time of the segment to be saved.  
.ip \ \ \fIend\fP: 12
The end time of the segment to be saved.
.sh 2 "Spectrogram Improvements"
Spectrograms are now painted significantly faster than previously
when interpolation is unnecessary \- that is, when the vertical scale is
one frequency point per pixel.  (By default, spectrograms are
automatically initially painted at that scale unless they would be too
tall to fit on the screen or below a minimum height that corresponds
to 153 frequency points.)
.np
The spectrogram computations performed by the DSP board were cleaned
up.  A faulty assumption about the analysis window symmetry was
corrected, resulting in improved spectral dynamic range.  Parameter
range checking was made more robust.  Buffer overrun problems causing
vertical stripes on spectrograms for certain parameter settings have
been fixed.  An initialization problem that caused a glitch near the
beginning of the spectrogram has been fixed.
.sh 2 "\fIwaves\fP+ as a Display Server"
.lp
\fIwaves\fP+ can now optionally accept commands from stdin, and
therefore can use the UNIX pipe facility in the usual way or be run in
the background as a display server with invocations like:
.sp .5
.nf
	waves \- < /dev/ptyra &
.fi
.sp .5
Any waves commands subsequently sent to /dev/ttyra will be received
and executed by waves.
.sh 2 "Visual Cues for Colormap Dynamics"
.lp
A special ESPS FEA_SPEC file (ESPS/lib/waves/color.fspec) is available
to provide visual cues about the current colormap.  To use it, just
load the file (enter its full path name as the "INPUTfile:" in the
control panel).  This file has a series of identical records, with
each record containing all possible numerical values for spectra.  As
viewed on the screen, the values range from -64 at the bottom of the
window to +50 at the top; these are displayed with the first 115