edit 16th July 2020 : The plugin is now available in the VCV Library.
We have worked with Pyer for the past weeks on the reworked version of Plaits/Macro Oscillator 2. It is called Palette and part of the new Atelier VCV plugin. We think it’s now ready for public beta testing before applying to be included in the VCV Library.
Thousands of thanks to Pyer for enduring with this!
edit : Omri Cohen provided some very valuable testing and suggestions!
New modules may be added into the plugin in the future, but for now it only has the Palette module.
i’ve been somewhat reluctantly using the polyplaits seeing the conversations around that one in the past… this module is such an elegant step forward, i’m sure its going to be part of my default soundpalette.
…and yes i had to make that pun before anyone else:)
thanks for this module and congrats, cant wait to see what will be new in the future
Amazing one! A build of the version with the edited panel had never left my rack since I got a chance to try it out.
To me, the real value of that Macro Polyoscillator 2 wasn’t even the polyphony, but the LPG to Timbre/Morph knobs. And that of Palette will definitely be that I won’t ever have to leave the Rack and yet again load up the manual to remember what the knobs do.
So many fantastic additions, and I only played with it for a few minutes. The ability to have multiple detuned voices from monophonic input is turning it into an even bigger monosynth beast
This is simply awesome. Having all the features of each different oscillator ‘exposed’ is priceless alone. Add in the polyphony, detune, visual modulation indicator, LPG control…truly the mother of all oscillators. Beautiful interface as well. Thank you so much for this.
I work with it since I could compile it and I must say, what you and Pyer did with this module is amazing. It is so much more than Plaits and the gui sets a new standard for the handling of complex modules.
Thank you guys and gals for your positive comments, This one was a long run!
Great pleasure to work with you @Xenakios, such a gifted developer you are! I hope we can do more ATELIER modules
High CPU use is quite expected when polyphony is used. No special optimizations were done for the polyphony. (Doing such optimizations wasn’t really feasible, because of the large number of synthesis engines. Basically everything would need to be rewritten with SIMD optimizations…)
However, if you are getting 25% CPU use for a single voice from the module, that doesn’t necessarily sound normal. Which synthesis engine are you using? (Classic waves, FM, wavetable…?)
Higher sample rates will of course use proportionately more CPU also.