Sitala

This sampler could be an excellent replacement for way more advanced TX16Wx, if it wasn't for the very obvious high frequency roll off. Every time I import any type of cymbal sound, Sitala removes some of the brightness from it. I made three comparisons so far and they all gave me the same results. Of course all settings in the plugin were in default neutral positions. I level matched both rendered samples and original was always brighter. I can not only hear the difference. Voxengo SPAN clearly shows, that there is a problem. Decompose could finally fix it. Then they would be a real competition for abovementioned, somewhat complicated TX16Wx. Unless that's what they were aiming at - a sampler that gives it's own "character" to imported samples. If so, it could just as well be a user dependent option.

We'd love to see spectrograms. We do actually test this, and particularly as of the last release, we bypass all processing other than volume when the knobs are in their default position.

I uploaded all three tests. Two of them were made on two consecutive days, so they look the same. I wanted to be thorough and make sure, that I haven't made a mistake.

I have put dates next to all files for easy identification. https://www.mediafire.com/folder/x277ql1e9wn07/sitala

It looks like the colorization happenes at resampling. Can you retry with a sample that matches the project's sample rate?

luzifer that was a great suggestion.

I created two projects. First one at 44100 Hz, which was the original sample rate of the used sample. Second one was at 48000 Hz. I took the screenshots of SPAN and here are my conclusions.

Spectrum analysis of the original sample looks the same in both projects.

Spectrum analysis of sample played from Sitala looks the same as original, but only in the project at 44100 Hz rate. That was the 'a-ha' moment for me. Finally some explanation what was going on.

Spectrum analysis of sample played from Sitala in the project at 48000 Hz rate has the above-mentioned roll off.

My question is: Since original sample in both projects has the same spectrum analysis, does this mean that Sitala is performing a resampling from 441000 to 48000 Hz, which causes played sample to sound and look different?

I think I accidentally removed a reply on this, when trying to cancel my own reply, but yes, since we think we can see what's happening here, this is something we've added to our Q&A process for the next release and will ensure that this problem doesn't happen in future releases. It's something that's happening out of Sitala's code itself, but rather in JUCE (which a lot of plugins use), so we'll have to dig a bit deeper before we can talk about a definitive fix for the issue.

Thanks for your reply scotchi. I posted a reply to Ikaz7's message yesterday, but now I see it's been removed. Definitely not by me. I wonder how long this message is going to stay here.

Actually, I think I accidentally removed it -- see here. I thought clicking on "remove" was going to remove my reply (I decided, "meh, I'll answer this tomorrow") and it removed your comment instead.

I had no idea, that some users had the option to remove someone else's comments. Thanks for clarifying.

At the moment I keep wondering about Sitala's GUI resize option. Any chance of that happening?

It's coming in the next update. Already mostly working.