Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

I couldn't help but notice that, when "Speed and Pitch" on its own is enabled and configured so that the individual speed and pitch settings are not decoupled, it seems to always resample the resulting audio to the same sampling rate as the source.

But does that then mean that, if I also have either "Sample Rate Converter" or "SoX Resampler" enabled and configured to a different sampling rate, that the audio is actually being resampled twice?

As an example, what I was hoping to do was to, say, take a 44100Hz audio and slow it down/down-pitch it by, let's say 10% to 39690Hz. From there would it not make much more sense if it could be directly resampled to something other than the source (e.g. 48kHz, 96kHz, or 192kHz in this example) instead of it just being sampled back to the source 44100Hz and then possibly needing to be resampled a second time to the likes of 48kHz, 96kHz, 192kHz, etc?

This could be especially true if the source audio has a weird native sampling rate, such as those found with retro video game consoles, such as the 32006Hz and 22047Hz commonly found in Nintendo 64 games - you wouldn't want the "Speed and Pitch" filter to resample the audio back to that oddball source 32006Hz sampling rate as you're going to then just have to resample a second time to something your PC's audio hardware can actually play anyway.

Historically I've actually kind of done this manually using the function historically labeled as "set rate" in Audacity and then setting the project rate to whatever sampling rate I want it to resample to while making sure that its real-time resampling is configured to the highest quality option but, on discovering the "Speed and Pitch" function in Audacious, I was kind of hoping to more closely automate this process - especially when dealing with audio of differing sampling rates.