@griffinboy Yes, I am aware of that. But the question is: Is HISE using an internal sample rate, which is different from the host sample rate? It could use an internal sample rate, while still doing all the things you mentioned.
Maybe my question is mostly for @Christoph-Hart :-)
Or I should actually go and read the C++ code!

Hi!

Might be a strange question, but:
I am wondering if the audio engine in HISE is using a fixed sample rate (like, say, always 48kHz) or if it is forwarding the DAW/host sample rate right through to the sample reading?

Or in other words:
If using a fixed sample rate, the audio engine would internally always run at 48kHz and would not be aware of the host sample rate. Of course at some point HISE would have to resample the internal sample rate to the host sample rate. But that would be very high up in the call chain. That would basically mean, HISE would have two points of resampling: first going from the WAV file sample rate to the internal audio engine sample rate. And later on going from the internal audio engine sample rate to the host sample rate.
If on the other hand the whole audio engine is fully aware of the host sample rate, then only one point of resampling would be needed: going from the WAV files to the host sample rate.

I am thinking about the case when you exported an instrument you made with HISE. I.e. how the exported instrument plugin handles it.

I realise that I could just look through the C++ code. But the code is huge and would take me a bit of time to understand :-)