wrel3.1.me

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

the \fIxlabel\fP window remains connected to the foo.sd display, regardless
of other signals that may subsequently included in the foo display
ensemble.  If several signals are included in foo, and the original
signal (foo.sd in this case) is removed, \fIxlabel\fP reverts to the old
behavior of attaching to the most recently created signal display.
.lp
The \fIxspectrum\fP "Window Limits From:" panel item has new choice labels
to more clearly reflect the semantics of this control item.
.br
Now: "Cursor +- step/2" and "Markers"
.br
Was: "Local" and "Host"
.lp
\fIXspectrum\fP no longer repositions the markers or recomputes the
spectrum if the "Window limits from:" item is changed.  Formerly, if
the markers had been carefully positioned in preparation for a new
spectrum computation, and the user then switched the limits source,
the hand-set window limits would be lost.

.sh 1 "BUGS FIXED"
.sh 2 \fIxwaves\fP
.lp
Commands added to the \fIxwaves\fP menus by the \fIadd_espsf\fP facility
previously did not handle multiple output files correctly.  Now, if a
process creates several related output time series as the result of
operations on an \fIxwaves\fP signal, these may all be displayed
automatically.  (See the discussion of \fIoutputs\fP under the \fIadd_esps\fP
command in the \fIxwaves\fP manual.)
.lp
Multiple views of the same signal in \fIxwaves\fP now display correctly.
There was a bug that caused incorrect displays to be generated if more
than one view of the same signal was generated in the display
ensemble.  Now it is possible to have several views of the same signal
displayed correctly at different scales.
.lp
When \fIxwaves\fP was being used to manipulate headerless files, or files
with foreign headers, it would eventually use up all available file
descriptors and refuse to display any more files.  This has been
corrected.  An unlimited number of cycles of load and destroy may now
be performed on such files.
.lp
The \fIverbose\fP startup messages issued by \fIxwaves\fP regarding the use of
DSP hardware were often confusing (or just plain wrong).  These are
now correct.
.lp
The \fIxwaves\fP file-browser windows did not follow symbolic directory
links correctly.  This has now been corrected.
.lp
The \fIxwaves\fP file-browser facility would fail to detect that a typed
specification was a directory unless a final "/" was entered.  As a
consequence, \fIxwaves\fP would load such nodes as though they were signals!
All directory nodes are now displayed as directories whether entered
with, or without the trailing "/".
.lp
When \fIxwaves\fP exited before a "play" command was complete, some types of
internal DSP hardware were not reset correctly and would endlessly
repeat fragments of the output.  All play operations in progress are
now stopped before \fIxwaves\fP exits.
.lp
Previously, the SGI Indigo internal "play" function locked out \fIxwaves\fP
interaction for the duration of the play operation.  This has now been
fixed.  The workaround for this had been to use the external play
program (sgplay) as the definition for \fIplay_prog\fP.  This has the
disadvantage of being somewhat slower, so SGI users that resorted to
this should now comment out the play_prog specifications in their
\.wave_pro and/or command files.

.sh 2 "Auxiliary Programs"
.lp
A/D and D/A conversion on the SGI Indigo is now possible for all
Indigo sample rates for stereo and mono files.  Previously, a bug in
our buffer specifications prevented correct operation at frequencies
over 24kHz.
.lp
Dual-channel play on SURF from within \fIxwaves\fP now works correctly.
Several other play deficiencies in FAB2 and SURF \fIxwaves\fP play operations
were also fixed.
.lp
The \fIxwaves\fP-internal play function has been fixed to handle non-ESPS
files correctly when the played region is not in display window.
Formerly this could cause extreme distortion due to variances in data
type or byte ordering.
.lp
\fIXwaves\fP now handles incorrect colormap names gracefully.  Previously,
it would load the current directory (!!) as a colormap if the
specified colormap didn't exist, causing bizarre spectrogram displays.
.lp
Single-record FEA_SPECT files may now be displayed as spectrograms.
Previously, this caused a core dump.
.lp
There were several situations which caused \fIxwaves\fP to exit without
freeing the Entropic license.  This prevented subsequent use of that
license until after a three-minute timeout period.  This has now been
fixed for all cases except an explicit SIGKILL (e.g. via kill -9
<pid>).  A new command, \fIfreewaves\fP, has been added to handle this latter
case and the timeout period has been reduced to 30 seconds.
.lp
\fIXwaves\fP now uses the \fIoutput_dir\fP specification much more rationally:
If the user specifies a fully qualified name (i.e as beginning with a
directory, ./ or /) output_dir is ignored.  Output_dir is only applied
to automatically generated names (e.g. temporary files) and those
output files specified as simple base names by the user.
.lp
Simple filenames entered into \fIxwaves\fP no longer have "./" automatically
prepended.  This behavior caused subquent references to files loaded
into \fIxwaves\fP to be incorrect, since the user had no way of knowing that
the name (as far as \fIxwaves\fP was concerned) had a leading "./".  This
fixes apparent bugs in several commands (e.g. align) that reference
specific files.
.lp
If the \fIstart\fP and \fIend\fP time specifications for a \fIspectrogram\fP command
are omitted, the spectrogram will now be computed over the entire
\fIxwaves\fP buffer interval automatically.  Previously, if these were
omitted, no spectrogram was computed.  Users who resorted to the
workaround of setting \fIstart\fP 0.0 and \fIend\fP 10000 (or some such) may now
revert to a more rational model if they wish.  In fact, if the file is
10000 seconds long, the new \fIxwaves\fP will compute the whole spectrogram,
so be careful!
.lp
In some cases the temporary files created during computation of
spectrograms by \fIxwaves\fP-external processes were getting crossed up so
that the spectrogram that was eventually displayed was not of the
desired signal.
.lp
Formerly, spectrogram segments saved using \fIxwaves\fP' "save segment in
file" facility, were not saved correctly and could not be used with
many Entropic programs (such as plotsgram).  This has been fixed.
.lp
Quantization by \fIxwaves\fP of the start and end times sent to external
spectrogram programs would cause these to fail with messages about bad
start and/or end times.  This was particularly troublesome for files
with start and/or end times greater than 99 sec.  The spectrogram
programs (e.g. \fIsgram\fP, \fIs32csgram\fP) have relaxed their requirements by
simply limiting the spectrogram computation to the file limits if
necessary.  Also, the quantization of the time specifications by
\fIxwaves\fP has been made much finer.
.lp
Temporary waveform files created by the spectrogram command are now
placed in \fIoutput_dir\fP, and are automatically deleted.
.lp
Previously, spectrogram computations launched by \fIxwaves\fP, but executed
by an external program (such as \fIsgram\fP) were limited to signal segments
that were buffered in \fIxwaves\fP.  That is, if an external program is
called to compute a spectrogram, the entire segment upon which it was
to be based needed to be present in \fIxwaves\fP' display buffer. In Version 3.1, segments
of any size consistent with the limits of the file being analyzed may
now be specified for the \fIstart\fP and \fIend\fP values to the \fIspectrogram\fP
command.  Specifications exceeding the file limits will be
automatically adjusted as necessary.

.sh 2 Attachments
.lp
The tendency for \fIxwaves\fP and the attachments to hang up the computer's
mouse and display has now been eliminated.  \fIXwaves\fP and the attachments
can no longer "grab all input".
.lp
The tendency for \fIxwaves\fP and the attachments to loose synchronization
has been greatly reduced.  A new inter-process communication technique
has been implemented that makes interactions faster and less error
prone.  Problems eliminated include: negative times being printed in the
\fIxlabel\fP window; failure of label files to load correctly; lock up of
attachments; and failure to execute commands.
.lp
Previously, the \fIxlabel\fP and \fIxmarks\fP label displays
positioned themselves to overlap the signal view and obscured the
lower part of its window.  This has been corrected.
.lp
\fIXlabel\fP now automatically inherits the current display ensemble name
from \fIxwaves\fP.  This eliminates the "Object doesn't exist (can't add
file ...)" message from \fIxlabel\fP (unless it is really true!).
.lp
When \fIoutput_dir\fP is specified, \fIxlabel\fP now applies it correctly.
Previously, two bugs caused bizarre things (including core dumps) when
\fIoutput_dir\fP was specified and \fIxlabel\fP was used.  Now, if the
label file name is fully qualified (begins with ./ or /), it will be
used unchanged.  If only a basename is specified, \fIoutput_dir\fP
will be prepended.
.lp
\fIXspectrum\fP now responds correctly to the \fIxwaves\fP
\fIdo_color\fP setting.  When black-and-white plots are requested by
setting \fIdo_color\fP 0, the \fIxspectrum\fP window is rendered accordingly
and can now be dumped to a hardcopy printer/plotter.  Previously, some
\fIxwaves\fP colormaps caused all-black \fIxspectum\fP hardcopies.
.lp
\fIXspectrum\fP had a display instability when two or more spectrum displays
overlapped.  They could keep sending refresh messages to one another
and alternately perform "raise" operations (forever!) if
\fIxspectrum_datwin_forward\fP was enabled.  This has been fixed.
.lp
\fIXspectrum\fP occasionally crashed when the related \fIxwaves\fP
display object was killed.  This has been fixed.
.lp
\fIXspectrum\fP now permits computation of extremely large FFT's
(limited only by the user's patience and hardware).  A soft limit is
still implemented via the \fIxspectrum\fP global \fImax_fft_size\fP,
which defaults to 65536, to protect against accidents!  To change
this, just send a command to \fIxspectrum\fP like
.ce 1
send set max_fft_size 1000000".
.lp
The \fIxspectrum\fP manual page had several errors regarding maximum window
sizes, and it has also been corrected.

.sh 1 NOTES
.lp
Smooth operation of \fIxwaves\fP is dependent upon the configuration
of your operating environment.  For an overview, please refer to the
document $ESPS_BASE/xview/README (also available under the "Other
Documents" item on the \fIeinfo\fP menu).  In particular, you may need
to put the following items in your $HOME/.Xdefaults file:
.sp
.nf
	*Foreground:			black
	*Background:			white
	window.color.foreground:	black
	window.color.background:	white
	4Dwm*positionIsFrame:		T
	4Dwm*positionOnScreen:		T
	4Dwm*interactivePlacement:	F
	4Dwm*clientAutoPlace:		false
	Mwm*interactivePlacement:	False
	Mwm*clientAutoPlace:		False
	XView.ICCCMCompliant:		False
.fi
.lp
This release of \fBwaves+\fP comes without a Sunview version.  The old
program \fIwaves+\fP, (alias svwaves, waves, svwaves+, ...) no longer
exists.  Entropic no longer ships or maintains a Sunview-compatible
version of \fIxwaves\fP.  We strongly urge users of \fBwaves\fP+ to try the new X
version which has all of the features you are familiar with, is very
robust, and has many new features never available under Sunview.
.lp
\fIWplay\fP and \fIwrecord\fP have been eliminated.  They have been
replaced by a family of play and record programs with considerably
enhanced capabilities.  See "eman play" and "eman record".
.lp
All programs are now linked "static".  Although this results in larger
program binaries, it should greatly ease the installation and
maintenance problems for \fIxwaves\fP and related programs.
Previously, it was necessary to either force the use of the graphics
libraries shipped from Entropic through use of the LD_LIBRARY_PATH
UNIX environment variable, or run the risk of having version skews in
the dynamically-loaded libraries.  These complications have been
eliminated.  All references to Entropic directories can be removed
from the LD_LIBRARY_PATH definition (e.g. in .cshrc files).