Hey! Cool video, some very nice sounds ❤FWIW, we did anticipate that the plugin would be used for sound design, which is why it has the PURIFY and ELECTRIFY controls. It just took ten years for the world to realize...at the time even the somewhat conservative notion of changing the key of a loop/song etc was considered (too) far out by some, so we settled on what was the "simpler" message. At any rate, PITCHMAP indeed bypasses what it sees as transients to some extent, which makes sense for the change-key and correct tuning applications, or in other words: for realistic, non-resonant use cases. This can be countered by raising PURIFY - higher purify means less transient bypassing, and more resonance. Regarding the KEY TRANSFORM: as described in the manual (wink, wink), this is a macro that sets the actual sliders - so it has no need to remember its setting, it's a one-way street. The setting is stored in the sliders, aka the pitch map. It does come up regularly, so in v2 we'll probably have that part implemented differently. And finally, regarding latency: correcting monophonic pitch is an entirely different process than correcting it within a mix. It is an apples and oranges comparison, as the latter requires taking the mixed signal apart first, using a spectral transform. The longer the spectral transform, the higher the frequency resolution is = more bands. You can not cleanly re-tune all harmonics of say a film score or any other polyphonic instrument signal without enough bands. PITCHMAP uses 4096 bands, resulting in the accordingly slightly higher latency (which IS compensated for in all usual playback circumstances, btw). Resonators, on the other hand, do not actually separate the content into its components - a resonator is basically bank of feedback filters and can be produced with very low latency (but can also not bypass the transients or actually tune the content, it super-imposes new frequencies using resonances).
Oh, so it was not that much of a surprise after all :) anyway, thx for clearing up so many of the implementation details and even the early marketing strategy. Must feel crazy to try to hold back on purpose on these showcase-y events.
@@Beatsbasteln We had certainly hoped for an "auto-tune" type use scenario, where the artifcats would become a "thing". That it turned out to be specifically color bass (which I dig a lot) was not anticipated, though :-)
yeah robbert's github page is like "oh yeha, then you have to go here and then you have to go there. just kidding, you would have to have clicked on that first haha" but you can actually find them if you try hard enough!
Hey! Cool video, some very nice sounds ❤FWIW, we did anticipate that the plugin would be used for sound design, which is why it has the PURIFY and ELECTRIFY controls. It just took ten years for the world to realize...at the time even the somewhat conservative notion of changing the key of a loop/song etc was considered (too) far out by some, so we settled on what was the "simpler" message.
At any rate, PITCHMAP indeed bypasses what it sees as transients to some extent, which makes sense for the change-key and correct tuning applications, or in other words: for realistic, non-resonant use cases. This can be countered by raising PURIFY - higher purify means less transient bypassing, and more resonance.
Regarding the KEY TRANSFORM: as described in the manual (wink, wink), this is a macro that sets the actual sliders - so it has no need to remember its setting, it's a one-way street. The setting is stored in the sliders, aka the pitch map. It does come up regularly, so in v2 we'll probably have that part implemented differently.
And finally, regarding latency: correcting monophonic pitch is an entirely different process than correcting it within a mix. It is an apples and oranges comparison, as the latter requires taking the mixed signal apart first, using a spectral transform. The longer the spectral transform, the higher the frequency resolution is = more bands. You can not cleanly re-tune all harmonics of say a film score or any other polyphonic instrument signal without enough bands. PITCHMAP uses 4096 bands, resulting in the accordingly slightly higher latency (which IS compensated for in all usual playback circumstances, btw). Resonators, on the other hand, do not actually separate the content into its components - a resonator is basically bank of feedback filters and can be produced with very low latency (but can also not bypass the transients or actually tune the content, it super-imposes new frequencies using resonances).
Oh, so it was not that much of a surprise after all :) anyway, thx for clearing up so many of the implementation details and even the early marketing strategy. Must feel crazy to try to hold back on purpose on these showcase-y events.
@@Beatsbasteln We had certainly hoped for an "auto-tune" type use scenario, where the artifcats would become a "thing". That it turned out to be specifically color bass (which I dig a lot) was not anticipated, though :-)
COOL ideas will be absorbing all the knowledge
It's nice to see someone use Chroma and PITCHMAP side-by-side instead of just replacing one with the other.
hella good video wtffffff
this is nerdy perfection
I heard Stock X might sell you the Xi Xing Ping Editions while thinking you bought the offishu tisshu's.🤔🤷🏾♂
@@coldskoolbeatz what? :D
i tried to download diopser but they make it so complicated
yeah robbert's github page is like "oh yeha, then you have to go here and then you have to go there. just kidding, you would have to have clicked on that first haha" but you can actually find them if you try hard enough!