#129 handling samplerate greater than 192kHz


I\\\\\\\'m working with scientists that often play with sample rates greater than 192kHz. They need a tool to quickly check spectrogram of data they have just acquired. I just found your grrrreat application but sadly, it doesn\\\\\\\'t handle sample rates greater than 192kHz due to PulseAudio (Assertion \\\\\\\'s\\\\\\\' failed at pulse/stream.c:1898, function pa_stream_set_state_callback(). Aborting.), so we\\\\\\\'re still using AUDACITY for quick check and OCTAVE for deeper inspect...
Maybe a 1st step could be to just disabling audio output for this kind of file, but down-sampling for replay would be a must...
Thank you again for this software.


  • JF Argentino

    JF Argentino - 2010-10-01

    192001 Hz sampling rate wave file

  • Anonymous - 2010-10-01

    Handling files with samplerates higher than 192Khz should not be a problem in SV: Choos Jack instead of PulseAudio.
    You have to install jackd on your system (guessing you are using Linux or a Mac). You can use QJackctl or the command line to run and configure jack. Jackd comes with a dummy audio interface that can handle almost any samplerate as it is not tied to any hardware. I have no problem here running jackd with dummy interface and SV with 512Khz sample rate.
    Here is the commandline to start jack if you do not have qjackctl installed:
    /usr/bin/jackd -ddummy -r512000 -p1024

  • JF Argentino

    JF Argentino - 2010-10-01

    shame on me, I haven't test it with jack!!! Thank you for the trick

  • Chris Cannam

    Chris Cannam - 2010-10-02

    I would never have thought of using the JACK dummy back end myself -- nice one!

    The feature request is still a fair one though -- it would be good to be able to handle files that can't directly be played, without also resampling them for display.

    One other possibility (which I haven't tried yet) might be to load a file at a common audio rate first, and then load the file you really want to analyse as the second or subsequent file in the session. It should then initialise the audio driver at the rate of the first file, and play back the other(s) at the wrong rate but display them correctly. I think.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks