24/96khz

[S0lo]

Someone knows of a off-line FFT comparision tool that loads different sampling rate files side by side? I want to know what the funk is going on.

Not offline, but the best FFT I tried yet is the simplest one, "Signal Analyzer" by www.rs-met.com. Can freeze too.

[Compyfox]

Must try that one again, I hope Schmidt's tool keep's the freeze. But I remember that I could not change the color.

Oh, and I meant spectrogram view with my last post, not audiogram. But I need an FFT. Again, thanks for the recommendations.

[Compyfox]

I think I found the culprit on my end.

Apparently, the default setting of my UltraMatch was with "Emphasis on" on the output side (which seems to be a constant for 44/48kHz, but not 96kHz). So if there is no Emphasis bit sent on the source, there can be no emphasis added/substracted.

This clears the sound difference. But I need more checks just to be sure.

[t3toooo]

i tested 64khz with my rme card and thought the sound is maybe a bit smoother when playing a lot of high content at once,different instruments through filters for example.
the cpu strain is rather marginal higher.


definitively compelling,let's see if hibidy got me on that!

[davidka]

I've seen this article
http://varietyofsound.wordpress.com/201 ... ing-rates/

And that raised up a few questions regarding sample rates:

Let's say I switch to 192khz samplerate instead of 44.1khz.
When speaking about plugins which are flexible (eg. not using a fixed internal sampling rate): Am I silly to think that it means I no longer need to use my plugins' oversampling options?
As they should work at the higher rate dictated by the host, I think further oversampling would be innecessary for them.

EDIT: And apart from A/B tests; is there a way to check a plugin's internal sampling rate, or I'll have to believe in what the dev says?

[DuX]

Yes, davidka, you can safely turn the oversampling options off in plugins. It's actually desirable to do so [read the VOS post once again]. However, I would leave them turned on in VSTis since they sound even better at bigger sample rates, but I wouldn't go beyond 192kHz with VSTis since 100kHz of audio bandwidth should be quite enough for any synth to sound best. I'm talking real-time synthesis synths here, not ROMplers.

[Compyfox]

I've seen this article
http://varietyofsound.wordpress.com/201 ... ing-rates/

I hope my answer to that article will be posted soon. Might clear some Q's as well.

Let's say I switch to 192khz samplerate instead of 44.1khz.
When speaking about plugins which are flexible (eg. not using a fixed internal sampling rate): Am I silly to think that it means I no longer need to use my plugins' oversampling options?
As they should work at the higher rate dictated by the host, I think further oversampling would be innecessary for them.

It depends on what you want to go for. If you say "192kHz is more than fine for me, no need to further OS", do it. If your CPU is strong enough, your DAC supports it and you think that such an high SR is benefital - do it.

But keep in mind, certain plugins can't be turned off in terms of OS (internal fixed OS for example, see SKnote and VoS plugins). So the CPU will be taxed. And some tools might still benefit from it (compressors especially).

EDIT: And apart from A/B tests; is there a way to check a plugin's internal sampling rate, or I'll have to believe in what the dev says?

If the dev says "works from 44,1kHz and up", you can usually(!) trust him (we all know that there are still black sheep around). To be totally sure, use something like the old C.Budde VST Plugin Analyser.

It however doesn't give you distinct readouts of what SR this thing works best at, just the one you currently setup (until 96kHz), it also doesn't show which OS multiplier is used internaly (if ever).

And... you need to know how to interpret the plots.