thank you for that, by the way. it means a lot as i’ve been feeling kind of self-conscious about the oscillator specifically.
great! thanks for the help
I think the only reliable solution to this issue is to do your test builds with the rack build tool chain. I remember reading that GitHub action builds don’t always pick the right libraries.
yeah, i imagine that’s true. unfortunately, i don’t have access to the Mac SDK necessary to do so locally. for the time being, the build action we’ve been using has worked great with no issues beyond the one experienced by @dreamer which has already been fixed. so at least until i have access to a Mac, or until the build action fails me worse than a minor inconvenience, i’ll have to stick with what we’ve got.
oh, for sure. Luckily for me my wife has a mac, so I get the sdk from her. But you can make just win and linux builds on the toolchain if you want.
Because the original jp8000 supersaw had so much aliasing it was common (anecdotally) to filter out some high frequencies and replace it with white noise. So I guess it became a thing… super saw with some noise sprinkled on top…
ah, interesting, ok. I’ll buy that. but, wait, I’m not the only person on the world who doesn’t like a----ing? oh - to get that sound you would need to LPF the saws while the noise goes through unfiltered, right? do either of these modules do that?
well Turbulence certainly doesn’t, since i wouldn’t know how to add filtering even if i wanted to.
there is a new build available here.
Cascade now has functioning output range settings in the context menu for all 4 individual channels, their connecting sections, and the central Cascade section.
there is also an “All Ranges” submenu, with a toggle to override the individual range settings. when this is toggled on, current individual settings will be saved, and restored when it is toggled back off.
quick fix update: i forgot to save and restore all the output range settings between Rack restarts. here is an updated build that will do so