KVR Audio

S0lo · Post by **S0lo** » Tue Feb 13, 2024 10:51 pm

Problem was fixed, but I actually found similar high oversampling problems in a couple of other modules too. Should be all fixed within a day or so. Will post a link soon.

S0lo · Post by **S0lo** » Wed Feb 14, 2024 6:53 pm

Update links:

64bit Version: link in first post
32bit Version: link in first post

The problem was manifesting at very high over sampling with modulators, EGs or sequencers that have internal clocks or external clock inputs. All should work now. If anything, I'm here.

Genetic_Junk · Post by **Genetic_Junk** » Wed Feb 14, 2024 7:40 pm

Thanks for checking the other modules and the quick fix.

S0lo · Post by **S0lo** » Wed Feb 14, 2024 8:29 pm

A different thing, I've noticed in the last patch you posted. Seamed you were to trying to make a unison sound? If so, then there is actually an easy method to detune these S304 without dialing the big knobs and without any guess work. Sorry if this is not clear from the UI. Here is a modified version:

Feedback Filter.v2.zip

Genetic_Junk · Post by **Genetic_Junk** » Wed Feb 14, 2024 9:55 pm

I think I was trying to tune a chord with a 5th or 7th (can't remember) and an octave. But I did read about the detune link feature on the product page of the S304. Thanks for the patch. Makes it easy to try out that feature. Seems pretty unique.

Genetic_Junk · Post by **Genetic_Junk** » Thu Feb 15, 2024 5:06 am

There might be something wrong with oversampling and the S620 module.

No oversampling: https://archive.org/download/solo-rack- ... one%29.mp3
64x oversampling: https://archive.org/download/solo-rack- ... 64x%29.mp3

patch: https://archive.org/download/solo-rack- ... y%20v2.srp

S0lo · Post by **S0lo** » Thu Feb 15, 2024 7:53 am

The S620 in particular is very sampling/oversampling rate sensitive when it gets over 8X. For this I'll quote the technical details from module description:

The S620 is particularly heavy on CPU. Oversampling will multiply the CPU usage of the S620 very rapidly. Because of this, the S620 does NOT support more than 8X (16X and above) oversampling. If you go higher, it will work but will start to loose base and allow some artifacts. We could have easily avoided this, but the demand on CPU above X8 is just not practical. Also, .......

S0lo · Post by **S0lo** » Thu Feb 15, 2024 7:59 am

Moreover, as a general guide line for all modules. Using different oversampling will and should sound different!!, this is because oversampling is supposed to remove aliasing from the sound. And that aliasing might be playing a part in the modules, such as causing or preventing modules from clipping or distortion.

Regarding clipping, the general rule, is to attenuate first then amplify later in the signal path. If you do the opposite, clipping is expected at module level. Which can also change the sound undesirably or desirably at different sampling and oversampling rates.

Edit: btw you can change the clipping level in the per module right click menu. But still the best strategy is as said above, attenuate first then amplify later

S0lo · Post by **S0lo** » Thu Feb 15, 2024 11:13 am

I'm going to revise those delay line modules like the S616 and S612 and may be a few others that seam to have base loss at very high oversampling. I'll post a fix soon. Still this won't fix the S620 since thats a different design limitation.

Genetic_Junk · Post by **Genetic_Junk** » Thu Feb 15, 2024 1:26 pm

Sorry about that. I should have read the S620 page before posting. Thanks for the tips on avoiding clipping. Although this case was intentional. I like how the patch sounds with the harmonics created by the clipping.

And point taken about how oversampling is intended to change the sound. Although I didn't notice any aliasing without oversampling, there is pretty big difference in how the S212 (the gargle) sounds at higher rates (even 4x). At no oversampling with max resonance and feedback, it sounds smoother when the cutoff is at lower frequencies (less gargle). At higher rate there is more "gargle" distortion that occurs at lower frequencies with high resonance and feedback. But the S212 info page notes that oversampling can change the cutoff freq range of the module. So I figured the difference in sound at different rates is intentional - not a bug.

S0lo · Post by **S0lo** » Thu Feb 15, 2024 6:09 pm

Yes the gargle filter (S212) is also oversampling sensitive. I've designed this filter way back, even before SoloRack had oversampling. It is quirky and non-standard in many ways. I haven't visited that code for long while, lets see if I can make it produce more consistent results across oversampling rates. It may or may not be possible though.

Genetic_Junk · Post by **Genetic_Junk** » Fri Feb 16, 2024 12:17 am

Cool. Like I said, I haven't heard any aliasing even without oversampling. So no worries on my part.

Another demo with a patch. This is using the same patch on three different midi parts, slightly modifying the filter cutoff for each of the parts.

Audio: https://archive.org/download/solo-rack- ... 9thOct.mp3
Patch: https://archive.org/download/solo-rack- ... 20Lead.srp

S0lo · Post by **S0lo** » Fri Feb 16, 2024 3:14 pm

Nice one, Yeah the VCOs them selves are already internally anti-aliased. But wave shapers and distortion modules are not. Oversampling will help with that if needed. But in many cases, it's just not needed.

S0lo · Post by **S0lo** » Mon Feb 19, 2024 7:00 pm

This update fixes all obvious oversampling bugs I could find so far. Including drops in base with some effect modules. And a few more things.

The S212, S620, S609, S205 and probably one or more that I forgotten remain sensitive to sampling and oversampling rates because of design or technical limitations. Obviously, they will work, but they will work differently as you have noticed above. You just have to choose a flavor that you like.

64bit Version: https://drive.google.com/file/d/1xfpT4v ... sp=sharing
32bit Version: https://drive.google.com/file/d/1z9Q1ea ... sp=sharing

Genetic_Junk · Post by **Genetic_Junk** » Tue Feb 20, 2024 9:23 pm

Thanks! I'll check out the new version tonight.

SoloRack v2.2 Release, CLAP support and new modules