Inconsistent wavwrite() operation between octave and matlab

[Randy Yates]

The wavwrite() function requires an signal vector in the range [-1,+1]
in both matlab and octave, and both must quantize this signal vector
before output to the file. Apparently octave uses the convention that
1 corresponds to 32767, while matlab uses the convention that 1
corresponds to 32768. This ought to be corrected so that consistent
results are produced.

octave:25> version
ans = 2.9.8

[david bateman]

Post by Randy Yates
The wavwrite() function requires an signal vector in the range [-1,+1]
in both matlab and octave, and both must quantize this signal vector
before output to the file. Apparently octave uses the convention that
1 corresponds to 32767, while matlab uses the convention that 1
corresponds to 32768. This ought to be corrected so that consistent
results are produced.
octave:25> version
ans = 2.9.8
--
% Randy Yates % "Remember the good old 1980's, when
%% Fuquay-Varina, NC % things were so uncomplicated?"
%%% 919-577-9882 % 'Ticket To The Moon'

This is an octave core function. If you think you've found a bug,
please send a full bug report with sample code for this to
***@octave.org

D.