[Octave-bug-tracker] [bug #59149] [octave forge] (signal) Resampling from 22050 to 48000 Hz introduces strange and unexpected artifacts

[anonymous]

Follow-up Comment #16, bug #59149 (project octave):

I reproduced the error! I had to compile Octave and the two packages (control
and signal) with no extra options passed to configure. But then I could get
the extra dots. Results attached.

This likely means that certain configuration and compilation flag combinations
are safe, and the generic ones more typically used by distro package
repositories are unsafe, at least for this resample operation on this
hardware. You can "diff unsafe.txt safe.txt" to see the differences. The most
plausible changes are to use the compiler flag "-march=native" and to use the
config options "--enable-64" and "--enable-openmp" if they are not already
switched on by default.

If you are in a position to build Octave and those two packages with the
"safe" configuration and compilation flags, please try it and see if you get
better results.

Dmitri and others: Is it possible to rebuild only the packages with the new
compiler flag, instead of having to build Octave?

(file #49852, file #49853, file #49854, file #49855)
    _______________________________________________________

Additional Item Attachment:

File name: dots2.safe.png                 Size:8 KB
    <https://file.savannah.gnu.org/file/dots2.safe.png?file_id=49852>

File name: dots2.unsafe.png               Size:9 KB
    <https://file.savannah.gnu.org/file/dots2.unsafe.png?file_id=49853>

File name: safe.txt                       Size:19 KB
    <https://file.savannah.gnu.org/file/safe.txt?file_id=49854>

File name: unsafe.txt                     Size:19 KB
    <https://file.savannah.gnu.org/file/unsafe.txt?file_id=49855>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59149>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/