Why there is that much difference?
Aliasing?
I only change sample rate in Ableton preferences.

 

Too many answers, too little info. Why dont you explain what you did. What was the original sample rate of project? Did you render to audio and converted? Did you play the instrument at different sample rates and exported? What plugin are you using and version?

 

When Project was set to 48kHz I record TD-3 via external audio in.
Then processing it using few plugins.
FabFilter Saturn v1.20 -> Softube Weiss EQ1 v2.5.12 -> FabFilter Saturn v1.20 -> OTT (Ableton) -> Limiter (Ableton)
Export to wav 48kHz.
Then I change sample rate to 96kHz in Ableton preferences and export to wav 96kHz.

Yeah.

These two are the same as on Soundcloud:
https://anonfiles.com/D9ieF86bqb/48_kHz_With_Processing_wav
https://anonfiles.com/z1f6F66aqc/96_kHz_With_Processing_wav

These two are without processing:
https://anonfiles.com/HcS2Ed6fq1/48_kHz_Clean_wav
https://anonfiles.com/h9U1E163qc/96_kHz_Clean_wav

 

Last edited: Feb 25, 2021

Some plugins simply s*cks in 48kHz
That's why i ALWAYS mix in 96 or 44.1

 

Do you have the oversampling mode turn on on Saturn ? (it's the "high quality" button at the bottom of the plugin)

 

Nope it was off.
But now I check and turn it on in both. In this one before Weiss and this one after and like nothing changed.

I think there is possibly something wrong with Weiss plugin.
48kHz project sounds like with low pass filter or bumped mid frequencies.
Weiss is eq so this is my suspect.
Unfortunately my sound card support only 48kHz and 96kHz.
I can't run many plugins at 96kHz because my PC starting to goes crazy.

 

Last edited: Feb 25, 2021

I think the Weiss EQ got some oversampling option too, if you open the option there is a "set # overs", I'm not sure if it's that but it sound like it is

 

I check and changed it to max (16) and like nothing changed.

 

Your sample is a real worst case scenario for audio processing: DC coupled recording of analog saw wave with extreme DC offset. Combine this with different up-/downsampling algorithms/filters and clipping/distortion/limiting and you've got unpredictable results.

 

I changed now in audio settings driver type from ASIO to Windows MME/DirectX
And changed sample rate to 44.1kHz and it sounds same as 48kHz in ASIO.

 

Then there is just the OTT (don't think there's an oversampling option, but not sure, I'm using the XFer version cause I'm not on Ableton). Maybe try to export the 2 version without it to see if that's the cause of the problem

Other thing to try could be to import the 96khz version in Ableton and export it again without FX at 44khz to see if that's a plugin issue or an Ableton export issue. If the problem come from a plugin (or it could be because of lot of thing cause by the plugin chain) and not the DAW itself, then that's a solution to export in 44 without losing sounds characteristic

 

playing both soundcloud tracks together is an orgasm
thanks @Roject

 

When you changed sample rate to 96k did you record again at 96 or did you keep the original TD-3 which you had recorded at 48?

 

Different drivers or sample rates are not the problem, but working with audio exceeding the usual (in analog gear) audible range in digital algorithms is, cause many conversions may lead to unwanted results.

 

Same sample in both recorded originally at 48kHz.
I only switch from 48kHz to 96kHz in settings.
I don't remember exactly but probably I do almost everything then switch to 96kHz and add OTT then tweak and my PC start lagging so I again switch and go back to 48kHz.
And I say hey what? Why it is so flat at 48kHz.
What You hear at 96kHz is much closer to this what I want get.

 

-

 

Last edited: Feb 26, 2021

Hmmm. I don't understand. It using recording so it isn't the same every time?

 

Whoa huge bass difference. Do renders with no plugs then add one at a time to narrow it down? Or just remove the suspected culprit Weiss and do a comparison?